Watchdog: rspamd-mailcow service hit the error rate limit

[Conan179]

Hallo erst mal.
Ich hab eben meine Mailcow innstallation Aktualisiert.
Jetzt bekomme ich vom Watchdog, im 5 Minuten tackt die nachricht:
Watchdog: rspamd-mailcow service hit the error rate limit

Wo steht das das für ein Fehler ist?

Gruss Conan

[xyng]

I had the same problem. After looking into the master, i opted to manually revert the latest commit to master. This updated the rspamd version, and I guess that this problem was caused by that.
I did not get any new errors by now.

[andryyy]

Can you share your logs of rspamd-mailcow and the output of docker-compose ps ?

[Conan179]

An wlecher stelle ich den Log von rspamd-mailcow?
`root@:~# cd /opt/mailcow-dockerized/
root@:/opt/mailcow-dockerized# docker-compose ps
Name Command State Ports

mailcowdockerized_acme-mailcow_1 /sbin/tini -g -- /srv/dock ... Up
mailcowdockerized_clamd-mailcow_1 /sbin/tini -g -- /bootstrap.sh Up 3310/tcp
mailcowdockerized_dockerapi-mailcow_1 python2 -u /server.py Up
mailcowdockerized_dovecot-mailcow_1 /docker-entrypoint.sh /bin ... Up 0.0.0.0:110->110/tcp, 127.0.0.1:19991->12345/tcp, 0.0.0.0:143->143/tcp, 0.0.0.0:4190->4190/tcp, 0.0.0.0:993->993/tcp, 0.0.0.0:995->995/tcp
mailcowdockerized_ipv6nat_1 /docker-ipv6nat --retry Up
mailcowdockerized_memcached-mailcow_1 docker-entrypoint.sh memcached Up 11211/tcp
mailcowdockerized_mysql-mailcow_1 docker-entrypoint.sh mysqld Up 127.0.0.1:13306->3306/tcp
mailcowdockerized_netfilter-mailcow_1 python2 -u /server.py Up
mailcowdockerized_nginx-mailcow_1 /bin/sh -c envsubst < /etc ... Up 188.40.243.212:443->443/tcp, 188.40.243.212:80->80/tcp
mailcowdockerized_php-fpm-mailcow_1 /docker-entrypoint.sh php- ... Up 9000/tcp
mailcowdockerized_postfix-mailcow_1 /bin/sh -c exec /usr/bin/s ... Up 0.0.0.0:25->25/tcp, 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp, 588/tcp
mailcowdockerized_redis-mailcow_1 docker-entrypoint.sh redis ... Up 6379/tcp
mailcowdockerized_rspamd-mailcow_1 /docker-entrypoint.sh /usr ... Up
mailcowdockerized_sogo-mailcow_1 /bin/sh -c exec /usr/bin/s ... Up
mailcowdockerized_unbound-mailcow_1 /docker-entrypoint.sh /usr ... Up 53/tcp, 53/udp
mailcowdockerized_watchdog-mailcow_1 /sbin/tini -g -- /bin/sh - ... Up
`

[andryyy]

docker-compose logs --tail=1000 rspamd-mailcow watchdog-mailcow is sufficient, I think.

[andryyy]

I think I know what went wrong...

[andryyy]

Can you please run this?

docker-compose restart rspamd-mailcow; docker-compose logs --tail=200 -f rspamd-mailcow | grep -i 'elements of settings'

It will take a few seconds, but you should see something like rspamd-mailcow_1 | 2018-09-25 20:53:29 #9(normal) <9ijszs>; lua; settings.lua:659: loaded 5 elements of settings.

Does it say "0 elements of settings" or something like that?

[Conan179]

Es kommt das:

root@:/opt/mailcow-dockerized# docker-compose restart rspamd-mailcow; docker-compose logs --tail=200 -f rspamd-mailcow | grep -i 'elements of settings' Restarting mailcowdockerized_rspamd-mailcow_1 ... done
rspamd-mailcow_1 | 2018-09-25 20:57:05 #1(main) <9ijszs>; lua; settings.lua:659: loaded 0 elements of settings

[andryyy]

Fixed in a few minutes.

[Conan179]

Jup, hat bei mir Funktioniert.
Danke :)

[mkuron]

@andryyy, that commit only updates the image version number but doesn‘t contain an actual fix. Did you forget to add a file?

[Knight1]

This brings us back to where they are build?

I also just found out that :latest is not correctly tagged.

[ntimo]

I think having the images build with travis would be great for transparency and this way the user can also check if the image was build successful and is already available.

[andryyy]

@mkuron yes, the Dockerfile will be added tomorrow/today. I just moved the settings file from modules.d to the Rspamd root folder.