starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

the bitwarden_rs can not run after synology reboot #970

New Issue
Closed
opened 2026-02-04 23:31:11 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-04 23:31:11 +03:00
Owner
Copy Link

Originally created by @ihxperfect on GitHub (Mar 12, 2021).

after my nas reboot,the bitwarden_rs can not run,the logs shows:

date stream content
2021-03-12 16:50:51 stdout  
2021-03-12 16:50:51 stdout 16: _start
2021-03-12 16:50:51 stdout 15: __libc_start_main
2021-03-12 16:50:51 stdout 14: main
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/rt.rs:51:25
2021-03-12 16:50:51 stdout std::rt::lang_start_internal
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panic.rs:396:14
2021-03-12 16:50:51 stdout std::panic::catch_unwind
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:343:19
2021-03-12 16:50:51 stdout std::panicking::try
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:379:40
2021-03-12 16:50:51 stdout std::panicking::try::do_call
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/core/src/ops/function.rs:259:13
2021-03-12 16:50:51 stdout 13: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once
2021-03-12 16:50:51 stdout 12: std::rt::lang_start::{{closure}}
2021-03-12 16:50:51 stdout 11: std::sys_common::backtrace::__rust_begin_short_backtrace
2021-03-12 16:50:51 stdout 10: bitwarden_rs::main
2021-03-12 16:50:51 stdout 9: bitwarden_rs::util::retry_db
2021-03-12 16:50:51 stdout 8: bitwarden_rs::db::DbPool::from_config
2021-03-12 16:50:51 stdout 7: bitwarden_rs::db::sqlite_migrations::run_migrations
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/core/src/option.rs:1268:5
2021-03-12 16:50:51 stdout 6: core::option::expect_none_failed
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/core/src/panicking.rs:92:14
2021-03-12 16:50:51 stdout 5: core::panicking::panic_fmt
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:493:5
2021-03-12 16:50:51 stdout 4: rust_begin_unwind
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/sys_common/backtrace.rs:141:18
2021-03-12 16:50:51 stdout 3: std::sys_common::backtrace::__rust_end_short_backtrace
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:497:13
2021-03-12 16:50:51 stdout 2: std::panicking::begin_panic_handler::{{closure}}
2021-03-12 16:50:51 stdout at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:595:17
2021-03-12 16:50:51 stdout 1: std::panicking::rust_panic_with_hook
2021-03-12 16:50:51 stdout 0: bitwarden_rs::init_logging::{{closure}}
2021-03-12 16:50:51 stdout [2021-03-12 16:50:51.852][panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "file is not a database")': src/db/mod.rs:275
2021-03-12 16:50:51 stdout  
2021-03-12 16:50:51 stdout [INFO] No .env file found.
2021-03-12 16:50:51 stdout  
2021-03-12 16:50:51 stdout --------------------------------------------------------------------/
2021-03-12 16:50:51 stdout |   https://github.com/dani-garcia/bitwarden_rs/issues/new           \
2021-03-12 16:50:51 stdout | Report suspected bugs/issues in the software itself at:            \
2021-03-12 16:50:51 stdout |   https://bitwardenrs.discourse.group/                             \
2021-03-12 16:50:51 stdout | Send usage/configuration questions or feature requests to:         \
2021-03-12 16:50:51 stdout | official channels to report bugs/features, regardless of client.   \
2021-03-12 16:50:51 stdout | This is an unofficial Bitwarden implementation, DO NOT use the   \
2021-03-12 16:50:51 stdout |--------------------------------------------------------------------\
2021-03-12 16:50:51 stdout |                           Version 1.18.0                           \
2021-03-12 16:50:51 stdout |                       Starting Bitwarden_RS                        \
2021-03-12 16:50:51 stdout /--------------------------------------------------------------------\

I have tried replace the db.sqlite3 file that onedrive backup,but it still not work.

Originally created by @ihxperfect on GitHub (Mar 12, 2021). after my nas reboot,the bitwarden_rs can not run,the logs shows: date | stream | content -- | -- | -- 2021-03-12 16:50:51 | stdout |   2021-03-12 16:50:51 | stdout | 16: _start 2021-03-12 16:50:51 | stdout | 15: __libc_start_main 2021-03-12 16:50:51 | stdout | 14: main 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/rt.rs:51:25 2021-03-12 16:50:51 | stdout | std::rt::lang_start_internal 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panic.rs:396:14 2021-03-12 16:50:51 | stdout | std::panic::catch_unwind 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:343:19 2021-03-12 16:50:51 | stdout | std::panicking::try 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:379:40 2021-03-12 16:50:51 | stdout | std::panicking::try::do_call 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/core/src/ops/function.rs:259:13 2021-03-12 16:50:51 | stdout | 13: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once 2021-03-12 16:50:51 | stdout | 12: std::rt::lang_start::{{closure}} 2021-03-12 16:50:51 | stdout | 11: std::sys_common::backtrace::__rust_begin_short_backtrace 2021-03-12 16:50:51 | stdout | 10: bitwarden_rs::main 2021-03-12 16:50:51 | stdout | 9: bitwarden_rs::util::retry_db 2021-03-12 16:50:51 | stdout | 8: bitwarden_rs::db::DbPool::from_config 2021-03-12 16:50:51 | stdout | 7: bitwarden_rs::db::sqlite_migrations::run_migrations 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/core/src/option.rs:1268:5 2021-03-12 16:50:51 | stdout | 6: core::option::expect_none_failed 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/core/src/panicking.rs:92:14 2021-03-12 16:50:51 | stdout | 5: core::panicking::panic_fmt 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:493:5 2021-03-12 16:50:51 | stdout | 4: rust_begin_unwind 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/sys_common/backtrace.rs:141:18 2021-03-12 16:50:51 | stdout | 3: std::sys_common::backtrace::__rust_end_short_backtrace 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:497:13 2021-03-12 16:50:51 | stdout | 2: std::panicking::begin_panic_handler::{{closure}} 2021-03-12 16:50:51 | stdout | at rustc/da384694807172f0ca40eca2e49a11688aba6e93/library/std/src/panicking.rs:595:17 2021-03-12 16:50:51 | stdout | 1: std::panicking::rust_panic_with_hook 2021-03-12 16:50:51 | stdout | 0: bitwarden_rs::init_logging::{{closure}} 2021-03-12 16:50:51 | stdout | [2021-03-12 16:50:51.852][panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "file is not a database")': src/db/mod.rs:275 2021-03-12 16:50:51 | stdout |   2021-03-12 16:50:51 | stdout | [INFO] No .env file found. 2021-03-12 16:50:51 | stdout |   2021-03-12 16:50:51 | stdout | \--------------------------------------------------------------------/ 2021-03-12 16:50:51 | stdout | \|   https://github.com/dani-garcia/bitwarden_rs/issues/new           \| 2021-03-12 16:50:51 | stdout | \| Report suspected bugs/issues in the software itself at:            \| 2021-03-12 16:50:51 | stdout | \|   https://bitwardenrs.discourse.group/                             \| 2021-03-12 16:50:51 | stdout | \| Send usage/configuration questions or feature requests to:         \| 2021-03-12 16:50:51 | stdout | \| official channels to report bugs/features, regardless of client.   \| 2021-03-12 16:50:51 | stdout | \| This is an *unofficial* Bitwarden implementation, DO NOT use the   \| 2021-03-12 16:50:51 | stdout | \|--------------------------------------------------------------------\| 2021-03-12 16:50:51 | stdout | \|                           Version 1.18.0                           \| 2021-03-12 16:50:51 | stdout | \|                       Starting Bitwarden_RS                        \| 2021-03-12 16:50:51 | stdout | /--------------------------------------------------------------------\ I have tried replace the db.sqlite3 file that onedrive backup,but it still not work.
OVERLORD commented 2026-02-04 23:31:16 +03:00
Author
Owner
Copy Link

@pfgcoder commented on GitHub (Mar 13, 2021):

I was curious as my Synology had not been rebooted in 41 days so I just tried a reboot and had no issues with bitwarden_rs coming back up after the reboot. Based on the errors in the log I think bitwarden_rs is unable to access your database file which might be a permissions issue for the user which runs bitwarden_rs.

@pfgcoder commented on GitHub (Mar 13, 2021): I was curious as my Synology had not been rebooted in 41 days so I just tried a reboot and had no issues with bitwarden_rs coming back up after the reboot. Based on the errors in the log I think bitwarden_rs is unable to access your database file which might be a permissions issue for the user which runs bitwarden_rs.
OVERLORD commented 2026-02-04 23:31:22 +03:00
Author
Owner
Copy Link

@ihxperfect commented on GitHub (Mar 13, 2021):

I was curious as my Synology had not been rebooted in 41 days so I just tried a reboot and had no issues with bitwarden_rs coming back up after the reboot. Based on the errors in the log I think bitwarden_rs is unable to access your database file which might be a permissions issue for the user which runs bitwarden_rs.

Thanks for your reply,but after I change the db.sqlite3 file to 777 for everyone,the problem still there.

@ihxperfect commented on GitHub (Mar 13, 2021): > I was curious as my Synology had not been rebooted in 41 days so I just tried a reboot and had no issues with bitwarden_rs coming back up after the reboot. Based on the errors in the log I think bitwarden_rs is unable to access your database file which might be a permissions issue for the user which runs bitwarden_rs. Thanks for your reply,but after I change the db.sqlite3 file to 777 for everyone,the problem still there.
OVERLORD commented 2026-02-04 23:31:24 +03:00
Author
Owner
Copy Link

@ultraloveninja commented on GitHub (Mar 16, 2021):

I'm starting to have this same issue within a docker container on my unraid server. Getting this error in the logs:

[panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")': src/db/mod.rs:275

Looks like it might be related. Figured I'd post up and see if this could be an inherit error as well. I can create another issue request if needed.

@ultraloveninja commented on GitHub (Mar 16, 2021): I'm starting to have this same issue within a docker container on my unraid server. Getting this error in the logs: ``` [panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(__Unknown, "disk I/O error")': src/db/mod.rs:275 ``` Looks like it might be related. Figured I'd post up and see if this could be an inherit error as well. I can create another issue request if needed.
OVERLORD commented 2026-02-04 23:31:28 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 16, 2021):

What kind of volume storage are you using? If it isa shared filesystem, like NFS, CIFS/Samba, then you need to disable WAL. Since this is embedded into the file, I'm actually not sure how to do that.

Could it be that something has changed on how volumes are configured on your system, or maybe some driver update.

The problem is that file locking isn't working is sqlite would want which causes this issue

@BlackDex commented on GitHub (Mar 16, 2021): What kind of volume storage are you using? If it isa shared filesystem, like NFS, CIFS/Samba, then you need to disable WAL. Since this is embedded into the file, I'm actually not sure how to do that. Could it be that something has changed on how volumes are configured on your system, or maybe some driver update. The problem is that file locking isn't working is sqlite would want which causes this issue
OVERLORD commented 2026-02-04 23:31:39 +03:00
Author
Owner
Copy Link

@ihxperfect commented on GitHub (Mar 16, 2021):

my volume storage is Btrfs,and I had a extra patch(extra.lama) about ds918+.

@ihxperfect commented on GitHub (Mar 16, 2021): my volume storage is Btrfs,and I had a extra patch(extra.lama) about ds918+.
OVERLORD commented 2026-02-04 23:31:47 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 16, 2021):

Are you able to copy the database somewhere else and try to open it to see if it is still valid?

It also looks like the file can't be found, or it is corrupt.

@BlackDex commented on GitHub (Mar 16, 2021): Are you able to copy the database somewhere else and try to open it to see if it is still valid? It also looks like the file can't be found, or it is corrupt.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#970
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?