Bug 2297 - runaway spamd's
Summary: runaway spamd's
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 2.55
Hardware: Sun Solaris
: P5 normal
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-06 17:26 UTC by David Burns
Modified: 2003-08-06 16:15 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Burns 2003-08-06 17:26:16 UTC 
On 2 of 3 servers I recently upgraded to SA 2.55, spamd's are running away.  All
are running Solaris 8 (I don't know what is different about the "good" box.)
This is using perl v5.6.1.

This doesn't happen for every message, but it happens pretty often (maybe 1 in
100 messages?)

I truss'ed a spamd process while running, and it made no system calls.  Here
is a gdb backtrace:

(gdb) bt
#0  0xff23ee94 in .rem () from /usr/lib/libc.so.1
#1  0xfefb6efc in gdbm_store ()
   from /usr/local/lib/perl5/5.6.1/sun4-solaris/auto/GDBM_File/GDBM_File.so
#2  0xfefb4004 in XS_GDBM_File_STORE ()
   from /usr/local/lib/perl5/5.6.1/sun4-solaris/auto/GDBM_File/GDBM_File.so
#3  0x76454 in Perl_pp_entersub ()
#4  0x6ee40 in Perl_runops_standard ()
#5  0x251e4 in perl_call_sv ()
#6  0x24c68 in perl_call_sv ()
#7  0x24a0c in perl_call_method ()
#8  0x67040 in Perl_magic_setnkeys ()
#9  0x67390 in Perl_magic_setpack ()
#10 0x65314 in Perl_mg_set ()
#11 0x6f3d4 in Perl_pp_sassign ()
#12 0x6ee40 in Perl_runops_standard ()
#13 0x24700 in perl_run ()
#14 0x24350 in perl_run ()
#15 0x21750 in main ()

finish gets out of .rem(), but not out of gdbm_store()

I thank anyone who can offer assistance.

--David Burns
davburns@cat.pdx.edu
Comment 1 Justin Mason 2003-08-06 17:55:05 UTC 
Subject: Re: [SAdev]  New: runaway spamd's 


>On 2 of 3 servers I recently upgraded to SA 2.55, spamd's are running away.  All
>are running Solaris 8 (I don't know what is different about the "good" box.)
>This is using perl v5.6.1.

Solaris perl is very problematic.  I suggest (a) using ActiveState's
version of perl and (b) making sure the DB_File module is installed.
Anything else is very likely to be unstable.

--j.
Comment 2 David Burns 2003-08-07 00:15:08 UTC 
Thanks for that tip, Justin.  I had tried this with both our site-built perl and
Solaris perl, but adding Berkely DB seems to have fixed or just avoided the
problem, whatever it was.