[v1.29.2] thread 'main' panicked at 'OS can't spawn worker thread: Operation not permitted (os error 1)' #5337

New Issue

Closed

opened 2026-03-07 20:19:56 -06:00 by GiteaMirror · 4 comments

GiteaMirror commented 2026-03-07 20:19:56 -06:00

Owner

Copy Link

Originally created by @floatingpurr on GitHub (Sep 8, 2023).

Subject of the issue

I'm experiencing this error in version 1.29.2. All worked fine up to version 1.29.1.

Deployment environment

• vaultwarden version: 1.29.2

• Install method: docker-compose

• Clients used: n/a

• Reverse proxy and version: n/a

• MySQL/MariaDB or PostgreSQL version: n/a

• Other relevant details: temporary fix: downgrade to 1.29.1. My OS:

Distributor ID:	Debian
Description:	Debian GNU/Linux 9.11 (stretch)
Release:	9.11
Codename:	stretch

Steps to reproduce

Just launch a container with docker-compose up starting from the image vaultwarden/server:1.29.2. Here is mine:

version: '3.7'

services:
  bitwarden:
    image: vaultwarden/server:1.29.2
    container_name: vaultwarden
    restart: always
    security_opt:
      - no-new-privileges:true
    networks:
      - proxy
    volumes:
      - ./bw-data:/data
    env_file:
      .bw.env

    labels:
      traefik.enable: true

      # bitwarden-ui
      traefik.http.routers.bitwarden-ui.rule: Host(`foo.org`)
      traefik.http.routers.bitwarden-ui.entrypoints: websecure
      traefik.http.routers.bitwarden-ui.tls.certresolver: tlsleresolver
      traefik.http.routers.bitwarden-ui.service: bitwarden-ui
      traefik.http.services.bitwarden-ui.loadbalancer.server.port: 80


networks:
  proxy:
    external: true

Expected behaviour

Vaultwarden gets up and running

Actual behaviour

An error is raised and the container exits

Status: Downloaded newer image for vaultwarden/server:1.29.2
Creating vaultwarden ... done
Attaching to vaultwarden
vaultwarden  | thread 'main' panicked at 'OS can't spawn worker thread: Operation not permitted (os error 1)', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.31.0/src/runtime/scheduler/multi_thread/worker.rs:447:13
vaultwarden  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Troubleshooting data

Here's the output with RUST_BACKTRACE=full

vaultwarden  | thread 'main' panicked at 'OS can't spawn worker thread: Operation not permitted (os error 1)', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.31.0/src/runtime/scheduler/multi_thread/worker.rs:447:13
vaultwarden  | stack backtrace:
vaultwarden  |    0:     0x55d349a16ca3 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbd7d55b7108d2ab8
vaultwarden  |    1:     0x55d34946f3df - core::fmt::write::h6d54cd7c9e155ec5
vaultwarden  |    2:     0x55d349a138d7 - std::io::Write::write_fmt::h6a453a71c692f63b
vaultwarden  |    3:     0x55d349a16a75 - std::sys_common::backtrace::print::h4ddf81241a51b337
vaultwarden  |    4:     0x55d349a184b0 - std::panicking::default_hook::{{closure}}::hff91f1f484ade5cd
vaultwarden  |    5:     0x55d349a18274 - std::panicking::default_hook::h21f14afd59f7aef9
vaultwarden  |    6:     0x55d349a18999 - std::panicking::rust_panic_with_hook::h45f66047b14c555c
vaultwarden  |    7:     0x55d349a188a4 - std::panicking::begin_panic_handler::{{closure}}::h49d1a88ef0908eb4
vaultwarden  |    8:     0x55d349a17096 - std::sys_common::backtrace::__rust_end_short_backtrace::hccebf9e57f8cc425
vaultwarden  |    9:     0x55d349a18642 - rust_begin_unwind
vaultwarden  |   10:     0x55d3493c2883 - core::panicking::panic_fmt::h54ec9d0e3180a83d
vaultwarden  |   11:     0x55d349a519f4 - tokio::runtime::blocking::pool::Spawner::spawn_blocking::h9e0ded7b77863876
vaultwarden  |   12:     0x55d349a50d05 - tokio::runtime::blocking::pool::spawn_blocking::hb15e5178f17f818b
vaultwarden  |   13:     0x55d349a6566b - tokio::runtime::scheduler::multi_thread::worker::Launch::launch::h6ce2d7d02be3860d
vaultwarden  |   14:     0x55d349a783f9 - tokio::runtime::builder::Builder::build::h6fb748647923ea1f
vaultwarden  |   15:     0x55d349e6f52e - vaultwarden::main::h222f937f9ca88bfc
vaultwarden  |   16:     0x55d34a2661d7 - std::sys_common::backtrace::__rust_begin_short_backtrace::h267d3b5af2cab27a
vaultwarden  |   17:     0x55d349dc0c38 - std::rt::lang_start::{{closure}}::h3ae0294076e6f9bb
vaultwarden  |   18:     0x55d349a0bf15 - std::rt::lang_start_internal::hf502095b101390bb
vaultwarden  |   19:     0x55d349e6f895 - main
vaultwarden  |   20:     0x7f20c3e1d1ca - <unknown>
vaultwarden  |   21:     0x7f20c3e1d285 - __libc_start_main
vaultwarden  |   22:     0x55d3494062b1 - _start
vaultwarden  |   23:                0x0 - <unknown>
vaultwarden exited with code 101

Originally created by @floatingpurr on GitHub (Sep 8, 2023). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> I'm experiencing this error in version 1.29.2. All worked fine up to version 1.29.1. ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.29.2 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker-compose * Clients used: n/a<!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Reverse proxy and version: n/a <!-- if applicable --> * MySQL/MariaDB or PostgreSQL version: n/a<!-- if applicable --> * Other relevant details: temporary fix: downgrade to 1.29.1. My OS: ``` Distributor ID: Debian Description: Debian GNU/Linux 9.11 (stretch) Release: 9.11 Codename: stretch ``` ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> Just launch a container with `docker-compose up` starting from the image `vaultwarden/server:1.29.2`. Here is mine: ```yml version: '3.7' services: bitwarden: image: vaultwarden/server:1.29.2 container_name: vaultwarden restart: always security_opt: - no-new-privileges:true networks: - proxy volumes: - ./bw-data:/data env_file: .bw.env labels: traefik.enable: true # bitwarden-ui traefik.http.routers.bitwarden-ui.rule: Host(`foo.org`) traefik.http.routers.bitwarden-ui.entrypoints: websecure traefik.http.routers.bitwarden-ui.tls.certresolver: tlsleresolver traefik.http.routers.bitwarden-ui.service: bitwarden-ui traefik.http.services.bitwarden-ui.loadbalancer.server.port: 80 networks: proxy: external: true ``` ### Expected behaviour Vaultwarden gets up and running ### Actual behaviour An error is raised and the container exits ``` Status: Downloaded newer image for vaultwarden/server:1.29.2 Creating vaultwarden ... done Attaching to vaultwarden vaultwarden | thread 'main' panicked at 'OS can't spawn worker thread: Operation not permitted (os error 1)', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.31.0/src/runtime/scheduler/multi_thread/worker.rs:447:13 vaultwarden | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` ### Troubleshooting data Here's the output with `RUST_BACKTRACE=full` ``` vaultwarden | thread 'main' panicked at 'OS can't spawn worker thread: Operation not permitted (os error 1)', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.31.0/src/runtime/scheduler/multi_thread/worker.rs:447:13 vaultwarden | stack backtrace: vaultwarden | 0: 0x55d349a16ca3 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbd7d55b7108d2ab8 vaultwarden | 1: 0x55d34946f3df - core::fmt::write::h6d54cd7c9e155ec5 vaultwarden | 2: 0x55d349a138d7 - std::io::Write::write_fmt::h6a453a71c692f63b vaultwarden | 3: 0x55d349a16a75 - std::sys_common::backtrace::print::h4ddf81241a51b337 vaultwarden | 4: 0x55d349a184b0 - std::panicking::default_hook::{{closure}}::hff91f1f484ade5cd vaultwarden | 5: 0x55d349a18274 - std::panicking::default_hook::h21f14afd59f7aef9 vaultwarden | 6: 0x55d349a18999 - std::panicking::rust_panic_with_hook::h45f66047b14c555c vaultwarden | 7: 0x55d349a188a4 - std::panicking::begin_panic_handler::{{closure}}::h49d1a88ef0908eb4 vaultwarden | 8: 0x55d349a17096 - std::sys_common::backtrace::__rust_end_short_backtrace::hccebf9e57f8cc425 vaultwarden | 9: 0x55d349a18642 - rust_begin_unwind vaultwarden | 10: 0x55d3493c2883 - core::panicking::panic_fmt::h54ec9d0e3180a83d vaultwarden | 11: 0x55d349a519f4 - tokio::runtime::blocking::pool::Spawner::spawn_blocking::h9e0ded7b77863876 vaultwarden | 12: 0x55d349a50d05 - tokio::runtime::blocking::pool::spawn_blocking::hb15e5178f17f818b vaultwarden | 13: 0x55d349a6566b - tokio::runtime::scheduler::multi_thread::worker::Launch::launch::h6ce2d7d02be3860d vaultwarden | 14: 0x55d349a783f9 - tokio::runtime::builder::Builder::build::h6fb748647923ea1f vaultwarden | 15: 0x55d349e6f52e - vaultwarden::main::h222f937f9ca88bfc vaultwarden | 16: 0x55d34a2661d7 - std::sys_common::backtrace::__rust_begin_short_backtrace::h267d3b5af2cab27a vaultwarden | 17: 0x55d349dc0c38 - std::rt::lang_start::{{closure}}::h3ae0294076e6f9bb vaultwarden | 18: 0x55d349a0bf15 - std::rt::lang_start_internal::hf502095b101390bb vaultwarden | 19: 0x55d349e6f895 - main vaultwarden | 20: 0x7f20c3e1d1ca - <unknown> vaultwarden | 21: 0x7f20c3e1d285 - __libc_start_main vaultwarden | 22: 0x55d3494062b1 - _start vaultwarden | 23: 0x0 - <unknown> vaultwarden exited with code 101 ```

GiteaMirror closed this issue 2026-03-07 20:19:56 -06:00

GiteaMirror commented 2026-03-07 20:19:57 -06:00

Author

Owner

Copy Link

@floatingpurr commented on GitHub (Sep 8, 2023):

(Probably related to #3839)

@floatingpurr commented on GitHub (Sep 8, 2023): (Probably related to #3839)

GiteaMirror commented 2026-03-07 20:19:57 -06:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Sep 8, 2023):

If you would have done a search, there are enough items already which reported this.

See #3827 .

@BlackDex commented on GitHub (Sep 8, 2023): If you would have done a search, there are enough items already which reported this. See #3827 .

GiteaMirror commented 2026-03-07 20:19:58 -06:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Sep 8, 2023):

(Probably related to #3839)

It has nothing to do with that item, if that was the case, you wouldn't had any output.

@BlackDex commented on GitHub (Sep 8, 2023): > (Probably related to #3839) It has nothing to do with that item, if that was the case, you wouldn't had any output.

GiteaMirror commented 2026-03-07 20:19:58 -06:00

Author

Owner

Copy Link

@floatingpurr commented on GitHub (Sep 8, 2023):

Hey @BlackDex, thank you. I'm sorry for the inconvenience. Thank you for the pointer.

@floatingpurr commented on GitHub (Sep 8, 2023): Hey @BlackDex, thank you. I'm sorry for the inconvenience. Thank you for the pointer.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.36.0

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#5337