You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "@lbutlr" <kr...@kreme.com> on 2019/08/15 22:41:56 UTC
SIGCHLD died
I am getting many many pop these errors:
spamd: handled cleanup of child pid [89330] due to SIGCHLD: DIED, signal 11 (000b)
It doesn’t appear to be affecting mail delivery, but still, I’d like to avoid them.
I have spamass-milter running:
/usr/local/sbin/spamass-milter -f -p /var/run/spamass-milter.sock -u spamd -r 10 -i 65.121.55.40/29 -i 127.0.0.1 -e covisp.net
And spamd:
/usr/local/bin/perl -T -w /usr/local/bin/spamd -c -Q -u spamd -H /var/spool/spamd -d -r /var/run/spamd/spamd.pid
Though o don’t recall how those options are set (they are not in rc.conf like spamass-milter) and I’m not sure why it is passing -Q since I currently;y do not have an SQL database setup for Spamassassin. Asmyway, the -Q flags says it needs -x which is not there, so I suspect this config is wrong, even if it is not the cause of the above issue.
👹 # spamassassin -D [16:40] [~]
Aug 15 16:40:29.889 [31757] dbg: logger: adding facilities: all
Aug 15 16:40:29.890 [31757] dbg: logger: logging level is DBG
Aug 15 16:40:29.890 [31757] dbg: generic: SpamAssassin version 3.4.2
Aug 15 16:40:29.890 [31757] dbg: generic: Perl 5.028002, PREFIX=/usr/local, DEF_RULES_DIR=/usr/local/share/spamassassin, LOCAL_RULES_DIR=/usr/local/etc/mail/spamassassin, LOCAL_STATE_DIR=/var/db/spamassassin
Aug 15 16:40:29.890 [31757] dbg: config: timing enabled
Aug 15 16:40:29.891 [31757] dbg: config: score set 0 chosen.
Aug 15 16:40:29.894 [31757] dbg: util: running in taint mode? yes
Aug 15 16:40:29.894 [31757] dbg: util: taint mode: deleting unsafe environment variables, resetting PATH
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/usr/local/bin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/root/bin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/usr/local/bin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/usr/local/bin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/sbin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/bin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/usr/sbin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/usr/bin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/usr/local/sbin', keeping
Aug 15 16:40:29.894 [31757] dbg: util: PATH included '/usr/local/bin', keeping
Aug 15 16:40:29.895 [31757] dbg: util: final PATH set to: /usr/local/bin:/root/bin:/usr/local/bin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
Aug 15 16:40:29.897 [31757] dbg: util: secure_tmpfile created a temporary file /tmp/.spamassassin31757VFYz2Vtmp
--
If a pig loses its voice, is it disgruntled?
Current Song: Pearl by Chapterhouse from Pearl - EP (5:16)
Re: SIGCHLD died
Posted by RW <rw...@googlemail.com>.
On Fri, 16 Aug 2019 11:04:38 -0400
Bill Cole wrote:
> On 16 Aug 2019, at 8:50, @lbutlr wrote:
> > /usr/local/etc/rc.d/sa-spamd:
> > # Set defaults
> > : ${spamd_enable:="NO"}
> > : ${spamd_flags="-c -Q -u spamd -H /var/spool/spamd"}
> >
> > Seems like a strange set of defaults to me.
>
> Indeed: it looks like that is controlled by a non-default build-time
> option in the FreeBSD port.
In the port Makefile:
.if ${PORT_OPTIONS:MMYSQL} || ${PORT_OPTIONS:MPGSQL}
SUB_LIST+= SQL_FLAG="-Q"
.else
SUB_LIST+= SQL_FLAG=""
.endif
Re: SIGCHLD died
Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 16 Aug 2019, at 8:50, @lbutlr wrote:
> On 15 Aug 19, at 23:06 , Bill Cole
> <sa...@billmail.scconsult.com> wrote:
>> On 15 Aug 2019, at 18:41, @lbutlr wrote:
>>
>>> I am getting many many pop these errors:
>>>
>>> spamd: handled cleanup of child pid [89330] due to SIGCHLD: DIED,
>>> signal 11 (000b)
>>
>> How fun... A segfault: something in a worker spamd process ( a child
>> of the master spamd process reporting the error) tried to access a
>> completely bogus memory address.
>>
>> IMHO spamd shouldn't segfault in anything like normal circumstances.
>> It's a Perl script, so most of the easy ways to segfault are blocked
>> by how how Perl interprets and precompiles the script.
>>
>>> It doesn’t appear to be affecting mail delivery, but still, I’d
>>> like to avoid them.
>>
>> Is any scoring being done?
>
> Yes, Spamassassin-milter is checking incoming mail and some few
> messages are getting encapsulated into safe-report mails (though I
> don’t have any of those in the last 24 hours, I never have very many
> since I am aggressive about deleting a lot of spam before it even gets
> o the Junk folder.
>
> It is possible this is hitting on specific mails (ones too large,
> perhaps?) or that it is a new problem since I updated some packages
> earlier this week.
>
>>> /usr/local/bin/perl -T -w /usr/local/bin/spamd -c -Q -u spamd -H
>>> /var/spool/spamd -d -r /var/run/spamd/spamd.pid
>>>
>>> Though o don’t recall how those options are set (they are not in
>>> rc.conf like spamass-milter)
>>
>> That's the normal place on FreeBSD, but you might have set options in
>> /usr/local/etc/rc.d/sa-spamd
>
> Evidently these ar the default flags:
>
> /usr/local/etc/rc.d/sa-spamd:
> # Set defaults
> : ${spamd_enable:="NO"}
> : ${spamd_flags="-c -Q -u spamd -H /var/spool/spamd"}
>
> Seems like a strange set of defaults to me.
Indeed: it looks like that is controlled by a non-default build-time
option in the FreeBSD port. See
/usr/ports/mail/spamassassin/files/sa-spamd.in and maybe report the
issue to the port maintainer (or package builder, if you used the binary
package.)
--
Bill Cole
bill@scconsult.com or billcole@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Re: SIGCHLD died
Posted by "@lbutlr" <kr...@kreme.com>.
On 15 Aug 19, at 23:06 , Bill Cole <sa...@billmail.scconsult.com> wrote:
> On 15 Aug 2019, at 18:41, @lbutlr wrote:
>
>> I am getting many many pop these errors:
>>
>> spamd: handled cleanup of child pid [89330] due to SIGCHLD: DIED, signal 11 (000b)
>
> How fun... A segfault: something in a worker spamd process ( a child of the master spamd process reporting the error) tried to access a completely bogus memory address.
>
> IMHO spamd shouldn't segfault in anything like normal circumstances. It's a Perl script, so most of the easy ways to segfault are blocked by how how Perl interprets and precompiles the script.
>
>> It doesn’t appear to be affecting mail delivery, but still, I’d like to avoid them.
>
> Is any scoring being done?
Yes, Spamassassin-milter is checking incoming mail and some few messages are getting encapsulated into safe-report mails (though I don’t have any of those in the last 24 hours, I never have very many since I am aggressive about deleting a lot of spam before it even gets o the Junk folder.
It is possible this is hitting on specific mails (ones too large, perhaps?) or that it is a new problem since I updated some packages earlier this week.
>> /usr/local/bin/perl -T -w /usr/local/bin/spamd -c -Q -u spamd -H /var/spool/spamd -d -r /var/run/spamd/spamd.pid
>>
>> Though o don’t recall how those options are set (they are not in rc.conf like spamass-milter)
>
> That's the normal place on FreeBSD, but you might have set options in /usr/local/etc/rc.d/sa-spamd
Evidently these ar the default flags:
/usr/local/etc/rc.d/sa-spamd:
# Set defaults
: ${spamd_enable:="NO"}
: ${spamd_flags="-c -Q -u spamd -H /var/spool/spamd"}
Seems like a strange set of defaults to me.
(bayes files in /car/spool/spamd/s,pamassassion/ are getting at least touched)
--
One of the universal rules of happiness is: always be wary of any
helpful item that weighs less than its operating manual. —Jingo
Re: SIGCHLD died
Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 15 Aug 2019, at 18:41, @lbutlr wrote:
> I am getting many many pop these errors:
>
> spamd: handled cleanup of child pid [89330] due to SIGCHLD: DIED,
> signal 11 (000b)
How fun... A segfault: something in a worker spamd process ( a child of
the master spamd process reporting the error) tried to access a
completely bogus memory address.
IMHO spamd shouldn't segfault in anything like normal circumstances.
It's a Perl script, so most of the easy ways to segfault are blocked by
how how Perl interprets and precompiles the script.
> It doesn’t appear to be affecting mail delivery, but still, I’d
> like to avoid them.
Is any scoring being done?
> I have spamass-milter running:
>
> /usr/local/sbin/spamass-milter -f -p /var/run/spamass-milter.sock -u
> spamd -r 10 -i 65.121.55.40/29 -i 127.0.0.1 -e covisp.net
>
> And spamd:
>
> /usr/local/bin/perl -T -w /usr/local/bin/spamd -c -Q -u spamd -H
> /var/spool/spamd -d -r /var/run/spamd/spamd.pid
>
> Though o don’t recall how those options are set (they are not in
> rc.conf like spamass-milter)
That's the normal place on FreeBSD, but you might have set options in
/usr/local/etc/rc.d/sa-spamd
> and I’m not sure why it is passing -Q since I currently;y do not
> have an SQL database setup for Spamassassin.
That COULD cause a segfault, I suppose... Still a bug, arguably, but
with an easy and obvious workaround.
> Asmyway, the -Q flags says it needs -x which is not there, so I
> suspect this config is wrong, even if it is not the cause of the above
> issue.
Yes. You should definitely fix this. It's local config.
> 👹 # spamassassin -D
That will not touch spamd. To get spamd to emit debugging info, you
would need to add '-D' to spamd_flags in rc.conf or wherever the args
are being set.
--
Bill Cole
bill@scconsult.com or billcole@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)