bitwarden_rs crashes from some kind of panic #2742

Closed
opened 2026-04-06 04:02:37 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @GNY-001F2 on 10/28/2020

Subject of the issue

Bitwarden_rs crashes after a few hours of running. If I understand the logs correctly, rust enters some kind of state of panic? I am unfamiliar with Rust.

Your environment

  • Bitwarden_rs version: 1.17.0
  • Install method: Built from source, rust-nightly is downloaded via rustup
  • Operating system: OpenSUSE tumbleweed x86_64 with the most recent snapshots.
  • Clients used: Mozilla Firefox extension and Android bitwarden clients
  • Reverse proxy and version: Nginx v1.19.3 reverse proxy
  • Other relevant information:
    Sometimes bitwarden_rs fails to restart with a manual systemctl start bitwarden_rs.service after crashes. However that apparently has not happened just before posting this report. I did change the path from a symbolic link to the actual directory, so that may have played a role in allowing it to restart successfully?

Steps to reproduce

I actually do not do anything to reproduce this issue. bitwarden_rs gets started during every reboot via a systemd .service file, modified from the default service file in the wiki, and after a few hours of running it crashes.

Relevant logs

Note: hostname changed to localhost in the log. It shows the trailing end of the second-last crash, before I restarted the service.
bitwarden.txt
Full log for more details (output via journalctl --unit=bitwarden_rs.service -xe):
bitwarden_full.txt
The systemd service file:
Note: actual path name is changed from what I use on my system to custom_services, and the systemd user field's name has been changed from the username on my server to my github nickname.
bitwarden_rs.service.txt

*Originally created by @GNY-001F2 on 10/28/2020* ### Subject of the issue Bitwarden_rs crashes after a few hours of running. If I understand the logs correctly, rust enters some kind of state of panic? I am unfamiliar with Rust. ### Your environment * Bitwarden_rs version: 1.17.0 * Install method: Built from source, rust-nightly is downloaded via rustup * Operating system: OpenSUSE tumbleweed x86_64 with the most recent snapshots. * Clients used: Mozilla Firefox extension and Android bitwarden clients * Reverse proxy and version: Nginx v1.19.3 reverse proxy * Other relevant information: Sometimes bitwarden_rs fails to restart with a manual ```systemctl start bitwarden_rs.service``` after crashes. However that apparently has not happened just before posting this report. I did change the path from a symbolic link to the actual directory, so that may have played a role in allowing it to restart successfully? ### Steps to reproduce I actually do not do anything to reproduce this issue. bitwarden_rs gets started during every reboot via a systemd .service file, modified from the default service file in the wiki, and after a few hours of running it crashes. ### Relevant logs Note: hostname changed to localhost in the log. It shows the trailing end of the second-last crash, before I restarted the service. [bitwarden.txt](https://github.com/dani-garcia/bitwarden_rs/files/5452209/bitwarden.txt) Full log for more details (output via ```journalctl --unit=bitwarden_rs.service -xe```): [bitwarden_full.txt](https://github.com/dani-garcia/bitwarden_rs/files/5452219/bitwarden_full.txt) The systemd service file: Note: actual path name is changed from what I use on my system to custom_services, and the systemd user field's name has been changed from the username on my server to my github nickname. [bitwarden_rs.service.txt](https://github.com/dani-garcia/bitwarden_rs/files/5452265/bitwarden_rs.service.txt)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#2742