spamd constantly failing
Upgraded a server to cPanel 110 - not sure if that's related, but issue didn't present itself while the server was on cPanel 102.
Seems spamd just constantly fail.
Even running spamd in an interactive shell:
[plain]/usr/local/cpanel/3rdparty/perl/536/bin/spamd --allowed-ips=127.0.0.1,::1 --max-children=5 --pidfile=/var/run/spamd.pid --start-dormant[/plain]
It dies in less than a minute
[plain]Jul 5 10:05:01.222 [2931557] info: prefork: child states: III
Jul 5 10:05:01.223 [2931557] info: prefork: adjust: 3 idle children more than 2 maximum idle children. Decreasing spamd children: 2931660 killed.
Jul 5 10:05:01.230 [2931557] info: prefork: child states: IIK
Jul 5 10:05:01.230 [2931557] info: spamd: handled cleanup of child pid [2931660] due to SIGCHLD: interrupted, signal 2 (0002)[/plain]
Anybody else having this issue?
-
Hey there! This seems to happen from time to time, but there never seems to be one particular problem that causes it. Usually we end up performing an strace on the spamd process and we'll find that it's hanging on a missing file or some other configuration error. But no, unfortunately I don't have an easy fix as there can be several causes. 0 -
It looks like the issue was that I had immuted [font="courier new">/usr/local/cpanel/3rdparty/bin/spamd at some point (this is why I'm a do as I say, not as I do preacher). I guess at some point [font="courier new">/usr/local/cpanel/3rdparty/bin/spamd became a symlink to [font="courier new">/usr/local/cpanel/3rdparty/perl/536/bin/spamd and since my [font="courier new">/usr/local/cpanel/3rdparty/bin/spamd was immutable, that symlink was not allowed to be created. Fixing the symlink SEEMS to have fixed the issue for me, although it sometimes took spamd a while to fail before. 0 -
Oh nice - I'm glad you found that! 0
Please sign in to leave a comment.
Comments
3 comments