Per Jessen wrote: > Following a SIGHUP of spamd, spamd decided to just stop: > > Oct 25 01:20:38 louiswu7 spamd[3122]: prefork: child states: IBBII > Oct 25 01:20:38 louiswu7 spamd[3122]: spamd: handled cleanup of child > pid 21529 due to SIGCHLD Oct 25 01:20:39 louiswu7 spamd[21548]: spamd > reload - 1 updated files found > [SIGHUP] > Oct 25 01:20:39 louiswu7 spamd[3122]: spamd: child 18309 killed > successfully Oct 25 01:20:39 louiswu7 spamd[3122]: spamd: child 21466 > killed successfully Oct 25 01:20:39 louiswu7 spamd[3122]: spamd: child > 21469 killed successfully Oct 25 01:20:40 louiswu7 spamd[3122]: spamd: > child 20900 killed successfully Oct 25 01:20:39 louiswu7 spamd[3122]: > prefork: child states: IBII Oct 25 01:20:40 louiswu7 spamd[3122]: > prefork: child states: IBII Oct 25 01:20:40 louiswu7 spamd[3122]: > prefork: oops! no idle kids in need_to_del_server? at > /usr/lib/perl5/site_perl/5.10.0/Mail/SpamAssassin/SpamdForkScaling.pm > line 846. > > This is SA 3.2.5. Any idea what happened here?
I was about to open a bugreport on this until I did a search for spamd reports: https://issues.apache.org/SpamAssassin/buglist.cgi?quicksearch=spamd There are 195 reports, of which 90% or more seem to be new. Has the spamd maintainer gone away and died? /Per Jessen, Zürich