On 09/03/06 02:29 PM, Dan Mahoney, System Admin wrote:
Thusfar, here's the continuing list:
1) This old friend.
Mar 9 01:38:18 quark spamd[61724]: Use of uninitialized value in
pattern match (m//) at
/usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/Conf/Parser.pm
line 547, <GEN954> line 2.
Mar 9 01:38:18 quark spamd[61724]: Use of uninitialized value in
pattern match (m//) at
/usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/Conf/Parser.pm
line 547, <GEN954> line 2.
I've also noticed that it will only be one child that gets hit with
this, which will log the error over and over again, while other children
will be fine.
We've addressed it, but from the bug reports, we can't isolate it --
shell is always an open offer.
This doesn't follow a logged "__alarm__", does it?
2) Right after that:
Mar 9 01:38:18 quark spamd[61724]: spamd: processing message
<[EMAIL PROTECTED]> for tinsc:58
Mar 9 01:38:18 quark spamd[61724]: Argument "a" isn't numeric in pack
at /usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/Util.pm line
711, <GEN954> line 48.
Mar 9 01:38:18 quark spamd[61724]: Argument "f" isn't numeric in pack
at /usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/Util.pm line
711, <GEN954> line 48.
Mar 9 01:38:18 quark spamd[61724]: Argument "eb" isn't numeric in pack
at /usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/Util.pm line
711, <GEN954> line 48.
You can ignore these, they are harmless. They're also fixed in 3.1.1.
If you want to get rid of them now, the patch from bug 4780 should
eliminate them. Additionally add the patch from bug 4485 to make sure
they don't happen.
Or... install the current 3.1.1 branch.
Daryl
