Arch Linux

MaxW7

Member

Registered: 2020-09-25

Posts: 7

[SOLVED] Vaultwarden install results in paniced threads

Hi all,

I am trying to get the vaultwarden package installed inside of a unpriviliged LXC container, so without the docker setup they explain on their docker implementation. I have been playing around with the settings given in "/etc/vaultwarden.env", but I can't seem to get the system to work as the systemctl service packaged with the package returns a "thread unnamed panicked" error:

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.23.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/
[2021-11-29 19:49:02.077][start][INFO] Rocket has launched from http://0.0.0.0:8000
[2021-11-29 19:49:02.157][panic][ERROR] thread 'unnamed' panicked at 'failed to spawn thread: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }': /rustc/dfc5add915e8bf4accbb7cf4de00351a7c6126a1/library/std/src/thread/mod.rs:630
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: start_thread
  14: __GI___clone
[2021-11-29 19:49:02.157][panic][ERROR] thread 'main' panicked at 'internal error: entered unreachable code: the call to `handle_threads` should block on success': /build/.cargo/git/checkouts/rocket-8bf16d9ca7e90bdc/263e39b/core/lib/src/rocket.rs:751
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: __libc_start_main
  13: <unknown>

The container runs on a Linux 5.10.82-1-lts kernel.

This error does not seem to exist anywhere on the internet, which I found very strange by itself already. I hope any of you have any experience or any clues on how to fix this.

Last edited by MaxW7 (2021-11-30 20:48:24)

MaxW7

Member

Registered: 2020-09-25

Posts: 7

Re: [SOLVED] Vaultwarden install results in paniced threads

Allright the solution was simple, but a bit obscure to find. In the systemctl service file the parameter LimitNPROC seems to cause this thread panick. Removing / commenting it out as stated on their wiki solves this problem.