-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watchdog: rspamd-mailcow service hit the error rate limit #1796
Comments
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. |
Can you share your logs of rspamd-mailcow and the output of |
An wlecher stelle ich den Log von rspamd-mailcow?
|
|
I think I know what went wrong... |
Can you please run this?
It will take a few seconds, but you should see something like Does it say "0 elements of settings" or something like that? |
Es kommt das:
|
Fixed in a few minutes. |
Jup, hat bei mir Funktioniert. |
@andryyy, that commit only updates the image version number but doesn‘t contain an actual fix. Did you forget to add a file? |
This brings us back to where they are build? I also just found out that :latest is not correctly tagged. |
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. |
@mkuron yes, the Dockerfile will be added tomorrow/today. I just moved the settings file from modules.d to the Rspamd root folder. |
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
The text was updated successfully, but these errors were encountered: