Hi all,
yesterday I migrated my mailcow according the docs in https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_migration/

mailcow.github.io
https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_migration/
No preview could be generated for this link
.

After migrating my mailcow from one host to another everything seems to be as it was before.
Except that since being on the new host I receive watchdog-emails every ~ 8 mins with the following message:

Rspamd settings check failed, score returned: 
Milter check succeeded

this message repeats lots of times.

No reboot of the whole server nor even an update.sh helps here.

Can anybody help?
It also seems as if everything that had been learned regarding spam now is away.

  • after deleting and reinstalling the rspamd container everything is up and running again. Thanks, @diekuh

5 days later

Maybe this log output helps to clarify. It repeats itself over and over…

rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_crash_sig_handler: caught fatal signal 11(Segmentation fault), pid: 53, trace:
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 0: 0000000000000000: <unknown>
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 1: 00007F50290565E5: corei7_hs_scan()+0×545
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 2: 00007F5029B9331D: rspamd_match_regexp_map_single()+0×8d
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 3: 00007F5029B236BF: lua_check_cryptobox_hash()+0×59f
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 4: 00007F5029C55C65: luaL_openlibs()+0×1eb5
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 5: 00007F5029C3F2A3: lua_pcall()+0×93
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 6: 00007F5029B4CCF7: rspamd_lua_run_config_post_init()+0×367
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 7: 00007F5029BB977A: rspamd_symcache_is_symbol_enabled()+0×51a
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 8: 00007F5029BBF46A: rspamd_symcache_process_symbols()+0×52a
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 9: 00007F5029A33D25: rspamd_task_process()+0×225
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 10: 00007F5029A34007: rspamd_task_process()+0×507
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 11: 00007F5029A34007: rspamd_task_process()+0×507
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 12: 000055937FA712B3: <unknown>
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 13: 00007F5029BDC08A: rspamd_session_pending()+0×5a
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 14: 00007F5029BE8914: rspamd_session_remove_event_full()+0×244
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 15: 00007F5029B41BC0: luaopen_config()+0×2b20
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 16: 00007F5029A5B660: redisProcessCallbacks()+0xd0
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 17: 00007F50296B4A9E: ev_invoke_pending()+0×5e
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 18: 00007F50296BA4B8: ev_run()+0xf08
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 19: 000055937FA7087A: <unknown>
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 20: 00007F5029BAA0F2: rspamd_fork_worker()+0×7a2
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 21: 000055937FA6987F: <unknown>
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 22: 00007F50296B4A9E: ev_invoke_pending()+0×5e
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 23: 00007F50296BA4B8: ev_run()+0xf08
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 24: 000055937FA62AEB: <unknown>
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 25: 00007F502951109B: __libc_start_main()+0xeb
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_print_crash: 26: 000055937FA6303A: <unknown>
rspamd-mailcow_1 | 2021-04-05 09:20:49 #53(controller) rspamd_crash_sig_handler: please see Rspamd FAQ to learn how to dump core files and how to fill a bug report
rspamd-mailcow_1 | 2021-04-05 09:20:49 #1(main) <28dd32>; main; rspamd_check_termination_clause: controller process 53 terminated abnormally by signal: Segmentation fault and created core file; please see Rspamd FAQ to learn how to extract data from core file and fill a bug report
rspamd-mailcow_1 | 2021-04-05 09:20:49 #1(main) <28dd32>; main; rspamd_cld_handler: respawn process controller in lieu of terminated process with pid 53
rspamd-mailcow_1 | 2021-04-05 09:20:51 #1(main) <28dd32>; main; rspamd_fork_worker: prepare to fork process controller (0); listen on: /var/lib/rspamd/rspamd.sock mode=0666 owner=nobody
rspamd-mailcow_1 | 2021-04-05 09:20:51 #54(controller) <28dd32>; main; rspamd_worker_set_limits: use system max file descriptors limit: 1024KiB cur and 1024KiB max
rspamd-mailcow_1 | 2021-04-05 09:20:51 #54(controller) <28dd32>; main; rspamd_worker_set_limits: use system max core size limit: -1B cur and -1B max
rspamd-mailcow_1 | 2021-04-05 09:20:51 #54(controller) <7yya7w>; controller; rspamd_controller_password_sane: your normal password is not encrypted, we strongly recommend to replace it with the encrypted one

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

since I moved mailcow to the new host it seems as if rspamd is not working at all. no mail is being moved to the junk folder and no mail is being quarantined.

Please help!

permissions in folder /opt/mailcow-dockerized/data/conf/rspamd have been checked (compared to those on the source host)

7 days later

after deleting and reinstalling the rspamd container everything is up and running again. Thanks, @diekuh

2 months later

Hi all,

This is an old topic but wanted to share findings as it seems there’s only a one-way conversation going on here.

I had a similar issue with ‘rspamd’ after migrating to a new host. Faults included:

  • Disconnects when sending emails - sending host would connect and disconnect 3 x times before finally sending (noted in Postfix logs). This meant sending emails took around 15 seconds per email.
  • DKIM Failure - Sent emails would occasionally bounce with: '550-5.7.26 Unauthenticated email from DOMAIN.TLD is not accepted due to domain's 550-5.7.26 DMARC policy.
  • DKIM tests to check-auth@verifier.port25.com would return - dkim none (message not signed)
  • docker-compose logs -f rspamd-mailcow would return multiple crashes during an email being sent; rspamd_crash_sig_handler: caught fatal signal 11(Segmentation fault).

Before doing anything, it’s worth going to /opt/mailcow-dockerized and running git diff origin/master to check if you have any config changes that could break the system.

To resolve this issue I took inspiration from the comment above, stopped all containers with docker-compose down and docker volume rm mailcowdockerized_rspamd-vol-1.
Once completed, I restarted the stack with docker-compose up -d.
See: Docs for removing volumes

mailcow.github.io
Redirecting...
. There is a possibility of data loss with the wrong command being used - so back up!

Hopefully this helps someone in future.

    3 years later

    JXGA thanks, this did the trick for me and got my server working again. One question, when I remove the rspamd volume and restart mailcow, will I lose all my historical rspamd learning? Or is that stored in another database somewhere (Redis?)?

      No one is typing