You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Martin Gregorie <ma...@gregorie.org> on 2016/02/11 13:02:13 UTC
Child-related errors
Every so often I see the following in my nightly logwatch report:
Child-related errors
spamd: cannot send SIGINT to child process [___]: No such process:
1 Time(s)
On at least one occasion it seems to be related to systemd deciding its
time to restart my mailing system because systemd is logging stuff
while dovecot, postfix and spamd are all stopped and restarted.
I'm running SA 3.4.1 under Fedora 22.
Is this a known problem? If not what, if anything, would you like to
see?
Martin
Re: Child-related errors
Posted by Martin Gregorie <ma...@gregorie.org>.
On Fri, 2016-02-12 at 15:06 +0000, RW wrote:
> On Thu, 11 Feb 2016 21:05:26 +0000
> Martin Gregorie wrote:
>
> > Feb 7 00:29:22 zoogz spamd[9347]: spamd: server killed by SIGTERM,
> > shutting down
> > Feb 7 00:29:22 zoogz spamd[9347]: spamd: cannot send SIGINT to
> > child
> > process [9352]: No such process
> > Feb 7 00:29:22 zoogz spamd[9347]: spamd: cannot send SIGINT to
> > child
> > process [9353]: No such process
>
> I do find it a bit strange that in both examples there are two child
> processes involved. I tried to reproduce this, but only saw one at a
> time.
>
Is that the default minimum number of child processes? I set max to 5
and default min because this is a personal system and I don't need any
more than that.
Martin
Re: Child-related errors
Posted by RW <rw...@googlemail.com>.
On Thu, 11 Feb 2016 21:05:26 +0000
Martin Gregorie wrote:
> On Thu, 2016-02-11 at 19:09 +0000, RW wrote:
> > On Thu, 11 Feb 2016 12:02:13 +0000
> > Martin Gregorie wrote:
> >
> > > Every so often I see the following in my nightly logwatch rep
> > >
> > > Child-related errors
> > > spamd: cannot send SIGINT to child process [___]: No such
> > > process:
> > Is it literally "[___]" in the log?
> >
> No, that looks like logwatch's doing because, in maillog the child's
> PID is inside the square brackets.
>
> This only happens during a shutdown:
Yes, the warning comes from the SIGTERM/SIGINT handler, in the main
spamd process, when it tries to kill all the children.
Child processes are reaped in the SIGCHLD handler, but the PIDs are
removed from the list later in the select loop, so there is a window
where the SIGINT handler could find such a PID.
> Feb 7 00:29:22 zoogz spamd[9347]: spamd: server killed by SIGTERM,
> shutting down
> Feb 7 00:29:22 zoogz spamd[9347]: spamd: cannot send SIGINT to child
> process [9352]: No such process
> Feb 7 00:29:22 zoogz spamd[9347]: spamd: cannot send SIGINT to child
> process [9353]: No such process
I do find it a bit strange that in both examples there are two child
processes involved. I tried to reproduce this, but only saw one at a
time.
Re: Child-related errors
Posted by Martin Gregorie <ma...@gregorie.org>.
On Thu, 2016-02-11 at 19:09 +0000, RW wrote:
> On Thu, 11 Feb 2016 12:02:13 +0000
> Martin Gregorie wrote:
>
> > Every so often I see the following in my nightly logwatch rep
> >
> > Child-related errors
> > spamd: cannot send SIGINT to child process [___]: No such
> > process:
> > 1 Time(s)
> >
>
>
> Is it literally "[___]" in the log?
>
No, that looks like logwatch's doing because, in maillog the child's
PID is inside the square brackets.
This only happens during a shutdown: here are two episodes as shown in
maillog interspersed with sections of the messages log to give context.
=======================================================================
##### This was during a reboot after a system update that had replaced
the kernel.
In maillog:
===========
Dec 24 18:59:48 zoogz dovecot: anvil: Warning: Killed with signal 15
(by pid=1 uid=0 code=kill)
Dec 24 18:59:48 zoogz dovecot: master: Warning: Killed with signal 15
(by pid=1 uid=0 code=kill)
Dec 24 18:59:48 zoogz dovecot: log: Warning: Killed with signal 15 (by
pid=1 uid=0 code=kill)
Dec 24 18:59:48 zoogz dovecot: auth-worker(7090): Warning: Killed with
signal 15 (by pid=1 uid=0 code=kill)
Dec 24 18:59:48 zoogz dovecot: config: Warning: Killed with signal 15
(by pid=1 uid=0 code=kill)
Dec 24 18:59:48 zoogz dovecot: auth: Error: read(anvil-auth-penalty)
failed: EOF
Dec 24 18:59:48 zoogz dovecot: auth: Error: net_connect_unix(anvil-auth
-penalty) failed: Permission denied
Dec 24 18:59:48 zoogz dovecot: auth: Warning: Killed with signal 15 (by
pid=1 uid=0 code=kill)
Dec 24 18:59:48 zoogz spamd[30333]: spamd: server killed by SIGTERM,
shutting down
Dec 24 18:59:48 zoogz spamd[30333]: spamd: cannot send SIGINT to child
process [30419]: No such process
Dec 24 18:59:48 zoogz spamd[30333]: spamd: cannot send SIGINT to child
process [30418]: No such process
Dec 24 18:59:51 zoogz postfix/postfix-script[7164]: stopping the
Postfix mail system
Dec 24 18:59:51 zoogz postfix/master[1607]: terminating on signal 15
Dec 24 19:01:56 zoogz dovecot: master: Dovecot v2.2.19 starting up for
pop3 (core dumps disabled)
Dec 24 19:02:05 zoogz postfix/postfix-script[1683]: starting the
Postfix mail system
Dec 24 19:02:06 zoogz postfix/master[1734]: daemon started -- version
3.0.3, configuration /etc/postfix
Dec 24 19:02:20 zoogz spamd[1417]: rules: meta test RCVD_IN_MSPIKE_WL
has dependency 'RCVD_IN_MSPIKE_H3' with a zero score
Dec 24 19:02:21 zoogz spamd[1417]: spamd: server started on
IO::Socket::IP [::1]:783, IO::Socket::IP [127.0.0.1]:783 (running
version 3.4.1)
Dec 24 19:02:21 zoogz spamd[1417]: spamd: server pid: 1417
Dec 24 19:02:21 zoogz spamd[1417]: spamd: server successfully spawned
child process, pid 2043
Dec 24 19:02:21 zoogz spamd[1417]: spamd: server successfully spawned
child process, pid 2044
Dec 24 19:02:21 zoogz spamd[1417]: prefork: child states: IS
Dec 24 19:02:21 zoogz spamd[1417]: prefork: child states: II
In messages:
============
Dec 24 18:59:48 zoogz systemd: Stopping Spamassassin daemon...
##### This time systemd stopped and restarted spamd without
restarting the system. Its possible this was me forcing
an SA restart to pick up a modified set of local rules.
In maillog:
===========
Feb 7 00:29:22 zoogz spamd[9347]: spamd: server killed by SIGTERM,
shutting down
Feb 7 00:29:22 zoogz spamd[9347]: spamd: cannot send SIGINT to child
process [9352]: No such process
Feb 7 00:29:22 zoogz spamd[9347]: spamd: cannot send SIGINT to child
process [9353]: No such process
Feb 7 00:29:26 zoogz spamd[3054]: rules: meta test RCVD_IN_MSPIKE_WL
has dependency 'RCVD_IN_MSPIKE_H3' with a zero score
Feb 7 00:29:26 zoogz spamd[3054]: spamd: server started on
IO::Socket::IP [::1]:783, IO::Socket::IP [127.0.0.1]:783 (running
version 3.4.1)
Feb 7 00:29:26 zoogz spamd[3054]: spamd: server pid: 3054
Feb 7 00:29:26 zoogz spamd[3054]: spamd: server successfully spawned
child process, pid 3059
Feb 7 00:29:26 zoogz spamd[3054]: spamd: server successfully spawned
child process, pid 3060
Feb 7 00:29:26 zoogz spamd[3054]: prefork: child states: IS
Feb 7 00:29:26 zoogz spamd[3054]: prefork: child states: II
In messages:
============
Feb 7 00:29:22 zoogz systemd: Stopping Spamassassin daemon...
Feb 7 00:29:22 zoogz audit: <audit-1131> pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=spamassassin
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Feb 7 00:29:22 zoogz systemd: Started Spamassassin daemon.
Feb 7 00:29:22 zoogz audit: <audit-1130> pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=spamassassin
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Feb 7 00:29:22 zoogz systemd: Starting Spamassassin daemon...
Feb 7 00:29:22 zoogz audit: <audit-1131> pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sa-update
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Feb 7 00:30:07 zoogz systemd: Starting dnf makecache...
=======================================================================
Martin
Re: Child-related errors
Posted by RW <rw...@googlemail.com>.
On Thu, 11 Feb 2016 12:02:13 +0000
Martin Gregorie wrote:
> Every so often I see the following in my nightly logwatch report:
>
> Child-related errors
> spamd: cannot send SIGINT to child process [___]: No such process:
> 1 Time(s)
>
Is it literally "[___]" in the log?