I synchronized my emails today because I realized the database was stale since the last one:
root@srv /e/s/system# msgvault sync XXX
Starting incremental sync for XXX
Last history ID: 21733647
time=2026-04-16T14:43:08.174+02:00 level=INFO msg="incremental sync" email=XXX start_history=21733647 current_history=21815230
Scanned: 4188 | Added: 555 | Skipped: 0 | Rate: 7.8/s | Elapsed: 1m 12s time=2026-04-16T14:44:29.830+02:00 level=WARN msg="incremental sync completed with errors" errors=160 history_id=21815230
Sync complete!
Duration: 1m22s
Changes: 4188 processed, 555 added
Downloaded: 29.20 MB
Errors: 160
time=2026-04-16T14:44:29.830+02:00 level=INFO msg="incremental sync completed" email=XXX messages_added=555 elapsed=1m21.862393322s
Ha, something went wrong, let's try again then!
root@srv /e/s/system# msgvault sync XXX -v
Starting incremental sync for XXX
Last history ID: 21815230
time=2026-04-16T14:44:51.150+02:00 level=INFO msg="incremental sync" email=XXX start_history=21815230 current_history=21815230
time=2026-04-16T14:44:51.150+02:00 level=INFO msg="already up to date"
Sync complete!
Duration: 0s
Changes: 0 processed, 0 added
Downloaded: 0.00 MB
time=2026-04-16T14:44:51.151+02:00 level=INFO msg="incremental sync completed" email=wXXX messages_added=0 elapsed=253.859749ms
Ah crap, msgvault is not detecting any new emails since the last synch -- which is correct. But what do I do with the 160 errors?
Fortunately the documentation has a section about troubleshooting using logs!
# View today's log
msgvault logs
Let's go!
root@srv /e/s/system# msgvault logs
Error: unknown command "logs" for "msgvault"
Run 'msgvault --help' for usage.
Ah re-crap 🙂
My first question is about how to handle the 160 errors in today's first run
The second one is about this logs command (in the meantime I will check if logs are enabled in my config file in the first place -- it won't help for today but at least there will be a trace someday EDIT: it was not 😕)
I synchronized my emails today because I realized the database was stale since the last one:
Ha, something went wrong, let's try again then!
Ah crap,
msgvaultis not detecting any new emails since the last synch -- which is correct. But what do I do with the 160 errors?Fortunately the documentation has a section about troubleshooting using logs!
Let's go!
Ah re-crap 🙂
My first question is about how to handle the 160 errors in today's first run
The second one is about this
logscommand (in the meantime I will check if logs are enabled in my config file in the first place -- it won't help for today but at least there will be a trace someday EDIT: it was not 😕)