try using "strace -fp {PID}" to see what is causing those
deaths...Chris Blaise writes: > > Can you verify that it's not in the "child create/due" loop? > Tailing my log, I see the following: > > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: spamd: server started on UNIX > domai > n socket /dev/spamd (running version 3.2.2) > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: spamd: server pid: 4553 > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: spamd: server successfully > spawned > child process, pid 4556 > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: spamd: server successfully > spawned > child process, pid 4557 > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: spamd: server successfully > spawned > child process, pid 4558 > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: prefork: child states: SSS > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: prefork: server reached > --max-child > ren setting, consider raising it > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: prefork: child states: SSS > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: prefork: server reached > --max-child > ren setting, consider raising it > 2007 Jul 25 08:41:01 ThreatWall spamd[4553]: spamd: handled cleanup of child > pid > 4556 due to SIGCHLD > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: server successfully > spawned > : > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: handled cleanup of child > pid > 4558 due to SIGCHLD > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: prefork: child states: S > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: server successfully > spawned > child process, pid 4560 > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: server successfully > spawned > child process, pid 4561 > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: handled cleanup of child > pid > 4559 due to SIGCHLD > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: handled cleanup of child > pid > 4560 due to SIGCHLD > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: prefork: child states: S > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: server successfully > spawned > child process, pid 4562 > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: server successfully > spawned > child process, pid 4563 > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: prefork: child states: SSS > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: prefork: server reached > --max-child > ren setting, consider raising it > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: handled cleanup of child > pid > 4561 due to SIGCHLD > 2007 Jul 25 08:41:02 ThreatWall spamd[4553]: spamd: handled cleanup of child > pid > 4562 due to SIGCHLD > .... > > Until I kill the parent spamd process. I run it with: > > /usr/bin/spamd -d -x --max-conn-per-child=20 --socketpath=/dev/spamd > --socketgroup=mail -m3 --min-spare=3 -u mail > > Chris > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 25, 2007 9:06 AM > To: Chris Blaise > Cc: users@spamassassin.apache.org > Subject: Re: ANNOUNCE: Apache SpamAssassin 3.2.2 available > > > Chris Blaise writes: > > When starting up on a Perl 5.6.1 system under x86 Linux, spamd goes > > into a child spawn/die loop because of the fix for bug 5518 which replaces > > the previous set uid/gid routines fails and causes the newly spawned child > > to immediately die. > > > > Is Perl 5.6.1 no longer the lowest support version? > > works fine for me with perl 5.6.1; make test passes: > > t/spamd.....................ok > t/spamd_allow_user_rules....ok > t/spamd_hup.................ok > t/spamd_kill_restart........ok > [.etc.] > > and 'sudo make test TEST_FILES=t/root_spamd*' similarly passes: > > t/root_spamd....................ok > t/root_spamd_tell...............ok > t/root_spamd_tell_paranoid......ok > t/root_spamd_tell_x.............ok > t/root_spamd_tell_x_paranoid....ok > t/root_spamd_x..................ok > t/root_spamd_x_paranoid.........ok > All tests successful. > > --j.
