Vault loading issues (attachments?) #2132

New Issue

MrUnknownDE · 2026-04-06T03:08:28+02:00

MrUnknownDE commented

2026-04-06 03:08:28 +02:00

Originally created by @Decicus on 5/23/2022

Subject of the issue

After updating from 1.24.0 to 1.25.0, I am having issues loading my vault.
Error messages indicate issues with attachments (included error logs under "Troubleshooting data").

Other account settings seem to work fine (changing equivalent domains or updating 2FA settings still worked), so it seems to only affect the vault data.

No issues on 1.24.0. In fact, I could revert Vaultwarden back to 1.24.0 without restoring my database from backups and the vault seems to load just fine again. Syncing from the browser extension works fine too.

Deployment environment

vaultwarden version: 1.25.0

Install method: Docker
Clients used: Web vault & official browser extension
MySQL/MariaDB or PostgreSQL version: 10.5.15-MariaDB-1:10.5.15+maria~focal

Steps to reproduce

Docker Compose with the latest tag, upgrade from 1.24.0 (pull, down, up)
No other changes were done, except using 1.24.0 instead of latest when reverting back.

Log into web vault / sync with browser extension.

Actual behaviour

Web vault was empty with no entries. Browser extension (where previously logged in & synced) just returned a sync error.

Troubleshooting data

vaultwarden    | 2022-05-23T19:45:16.513924114Z [2022-05-23 19:45:16.513][panic][ERROR] thread 'rocket-worker-thread' panicked at 'Error loading attachments: DatabaseError(__Unknown, "Commands out of sync; you can't run this command now")': src/db/models/attachment.rs:196
vaultwarden    | 2022-05-23T19:45:16.516877999Z    0: vaultwarden::init_logging::{{closure}}
vaultwarden    | 2022-05-23T19:45:16.516917724Z    1: std::panicking::rust_panic_with_hook
vaultwarden    | 2022-05-23T19:45:16.516969010Z    2: std::panicking::begin_panic_handler::{{closure}}
vaultwarden    | 2022-05-23T19:45:16.516997363Z    3: std::sys_common::backtrace::__rust_end_short_backtrace
vaultwarden    | 2022-05-23T19:45:16.517034252Z    4: rust_begin_unwind
vaultwarden    | 2022-05-23T19:45:16.517048589Z    5: core::panicking::panic_fmt
vaultwarden    | 2022-05-23T19:45:16.517079778Z    6: core::result::unwrap_failed
vaultwarden    | 2022-05-23T19:45:16.517093013Z    7: tokio::runtime::enter::exit
vaultwarden    | 2022-05-23T19:45:16.517123690Z    8: tokio::runtime::thread_pool::worker::block_in_place
vaultwarden    | 2022-05-23T19:45:16.517135091Z    9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
vaultwarden    | 2022-05-23T19:45:16.517161912Z   10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
vaultwarden    | 2022-05-23T19:45:16.517174946Z   11: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
vaultwarden    | 2022-05-23T19:45:16.517209531Z   12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
vaultwarden    | 2022-05-23T19:45:16.517224429Z   13: tokio::runtime::task::harness::poll_future
vaultwarden    | 2022-05-23T19:45:16.517266849Z   14: tokio::runtime::task::harness::Harness<T,S>::poll
vaultwarden    | 2022-05-23T19:45:16.517280976Z   15: std::thread::local::LocalKey<T>::with
vaultwarden    | 2022-05-23T19:45:16.517307125Z   16: tokio::runtime::thread_pool::worker::Context::run_task
vaultwarden    | 2022-05-23T19:45:16.517318657Z   17: tokio::runtime::thread_pool::worker::Context::run
vaultwarden    | 2022-05-23T19:45:16.517350286Z   18: tokio::macros::scoped_tls::ScopedKey<T>::set
vaultwarden    | 2022-05-23T19:45:16.517365504Z   19: tokio::runtime::thread_pool::worker::run
vaultwarden    | 2022-05-23T19:45:16.517397605Z   20: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
vaultwarden    | 2022-05-23T19:45:16.517412883Z   21: tokio::runtime::task::harness::Harness<T,S>::poll
vaultwarden    | 2022-05-23T19:45:16.517460072Z   22: tokio::runtime::blocking::pool::Inner::run
vaultwarden    | 2022-05-23T19:45:16.517476022Z   23: std::sys_common::backtrace::__rust_begin_short_backtrace
vaultwarden    | 2022-05-23T19:45:16.517518501Z   24: core::ops::function::FnOnce::call_once{{vtable.shim}}
vaultwarden    | 2022-05-23T19:45:16.517536144Z   25: std::sys::unix::thread::Thread::new::thread_start
vaultwarden    | 2022-05-23T19:45:16.517572913Z   26: start_thread
vaultwarden    | 2022-05-23T19:45:16.517588172Z   27: clone
vaultwarden    | 2022-05-23T19:45:16.517619471Z

*Originally created by @Decicus on 5/23/2022*   ### Subject of the issue After updating from 1.24.0 to 1.25.0, I am having issues loading my vault. Error messages indicate issues with attachments (included error logs under "Troubleshooting data"). Other account settings seem to work fine (changing equivalent domains or updating 2FA settings still worked), so it seems to only affect the vault data. No issues on 1.24.0. In fact, I could revert Vaultwarden back to 1.24.0 without restoring my database from backups and the vault seems to load just fine again. Syncing from the browser extension works fine too. ### Deployment environment     * vaultwarden version: 1.25.0  * Install method: Docker * Clients used: Web vault & official browser extension * MySQL/MariaDB or PostgreSQL version: `10.5.15-MariaDB-1:10.5.15+maria~focal` ### Steps to reproduce  Docker Compose with the `latest` tag, upgrade from 1.24.0 (`pull, down, up`) No other changes were done, except using `1.24.0` instead of latest when reverting back. Log into web vault / sync with browser extension. ### Actual behaviour Web vault was empty with no entries. Browser extension (where previously logged in & synced) just returned a sync error. ### Troubleshooting data ``` vaultwarden | 2022-05-23T19:45:16.513924114Z [2022-05-23 19:45:16.513][panic][ERROR] thread 'rocket-worker-thread' panicked at 'Error loading attachments: DatabaseError(__Unknown, "Commands out of sync; you can't run this command now")': src/db/models/attachment.rs:196 vaultwarden | 2022-05-23T19:45:16.516877999Z 0: vaultwarden::init_logging::{{closure}} vaultwarden | 2022-05-23T19:45:16.516917724Z 1: std::panicking::rust_panic_with_hook vaultwarden | 2022-05-23T19:45:16.516969010Z 2: std::panicking::begin_panic_handler::{{closure}} vaultwarden | 2022-05-23T19:45:16.516997363Z 3: std::sys_common::backtrace::__rust_end_short_backtrace vaultwarden | 2022-05-23T19:45:16.517034252Z 4: rust_begin_unwind vaultwarden | 2022-05-23T19:45:16.517048589Z 5: core::panicking::panic_fmt vaultwarden | 2022-05-23T19:45:16.517079778Z 6: core::result::unwrap_failed vaultwarden | 2022-05-23T19:45:16.517093013Z 7: tokio::runtime::enter::exit vaultwarden | 2022-05-23T19:45:16.517123690Z 8: tokio::runtime::thread_pool::worker::block_in_place vaultwarden | 2022-05-23T19:45:16.517135091Z 9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll vaultwarden | 2022-05-23T19:45:16.517161912Z 10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll vaultwarden | 2022-05-23T19:45:16.517174946Z 11: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll vaultwarden | 2022-05-23T19:45:16.517209531Z 12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll vaultwarden | 2022-05-23T19:45:16.517224429Z 13: tokio::runtime::task::harness::poll_future vaultwarden | 2022-05-23T19:45:16.517266849Z 14: tokio::runtime::task::harness::Harness<T,S>::poll vaultwarden | 2022-05-23T19:45:16.517280976Z 15: std::thread::local::LocalKey<T>::with vaultwarden | 2022-05-23T19:45:16.517307125Z 16: tokio::runtime::thread_pool::worker::Context::run_task vaultwarden | 2022-05-23T19:45:16.517318657Z 17: tokio::runtime::thread_pool::worker::Context::run vaultwarden | 2022-05-23T19:45:16.517350286Z 18: tokio::macros::scoped_tls::ScopedKey<T>::set vaultwarden | 2022-05-23T19:45:16.517365504Z 19: tokio::runtime::thread_pool::worker::run vaultwarden | 2022-05-23T19:45:16.517397605Z 20: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll vaultwarden | 2022-05-23T19:45:16.517412883Z 21: tokio::runtime::task::harness::Harness<T,S>::poll vaultwarden | 2022-05-23T19:45:16.517460072Z 22: tokio::runtime::blocking::pool::Inner::run vaultwarden | 2022-05-23T19:45:16.517476022Z 23: std::sys_common::backtrace::__rust_begin_short_backtrace vaultwarden | 2022-05-23T19:45:16.517518501Z 24: core::ops::function::FnOnce::call_once{{vtable.shim}} vaultwarden | 2022-05-23T19:45:16.517536144Z 25: std::sys::unix::thread::Thread::new::thread_start vaultwarden | 2022-05-23T19:45:16.517572913Z 26: start_thread vaultwarden | 2022-05-23T19:45:16.517588172Z 27: clone vaultwarden | 2022-05-23T19:45:16.517619471Z ```

MrUnknownDE closed this issue

2026-04-06 03:08:28 +02:00

MrUnknownDE added the wontfix Third party wontfix wontfix Third party Third party Third party Third party Third party Third party Third party Third party Third party Third party labels 2026-04-06 03:08:30 +02:00

Sign in to join this conversation.

No Label Third party Third party Third party Third party Third party Third party Third party Third party Third party Third party Third party wontfix wontfix wontfix

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#2132