Stalwart v0.10 panicks #805
Replies: 5 comments
-
I don't know if helpful, but if you do not have any valuable data in the database I'd try to move that directory to a new location so that stalwart creates a new database on the next launch, you can then proceed to import your data... |
Beta Was this translation helpful? Give feedback.
-
That's correct, it is a bug migrating data on FoundationDB but it does not affect data integrity. The recent commit for #784 fixes it, you can either recompile Stalwart from |
Beta Was this translation helpful? Give feedback.
-
Hi @mdecimus, Thanks for confirming that. I did just try to compile the latest commit from the main branch, but I am getting various compile errors when following the instructions for Linux that I found here: https://stalw.art/docs/development/compile Maybe I'll just wait for the next release. :) |
Beta Was this translation helpful? Give feedback.
-
v0.10.1 is being compiled with the fix. |
Beta Was this translation helpful? Give feedback.
-
Hi, Version 0.10.1 works just fine, thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
Hi,
Yesterday I was testing the v0.10 enterprise version, which was a fresh install. I was testing the import of a bunch of email into an account using the imapsync CLI tool. At some point, disk space started to get tight on the partition with the FoundationDB data. I sorted out the disk space issue, but meanwhile stalwart had crashed:
Sep 25 20:45:33 email1 stalwart-mail[102584]: thread 'main' panicked at /home/runner/work/mail-server/mail-server/crates/directory/src/backend/internal/mod.rs:266:35:
Sep 25 20:45:33 email1 stalwart-mail[102584]: index out of bounds: the len is 0 but the index is 0
Sep 25 20:45:33 email1 stalwart-mail[102584]: note: run with
RUST_BACKTRACE=1
environment variable to display a backtraceSep 25 20:45:33 email1 systemd[1]: stalwart-mail.service: Main process exited, code=exited, status=101/n/a
Now stalwart won't start at all, it immediately crashes when I try to start the service.
How do I fix this? Is this related to this issue and recent commit?: #784
This is a fresh v0.10 install, so there shouldn't be any database migration needed, so I'm a bit confused.
Thanks in advance for any help.
Beta Was this translation helpful? Give feedback.
All reactions