bugSpamAssassin Milter Plugin - Bugs: bug #1099, Crashes after some hours

 
 

bug #1099: Crashes after some hours

Submitter:  None
Submitted:  Thu 29 Aug 2002 07:32:35 AM UTC
   
 
Category:  None Severity:  1 - Wish
Item Group:  None Status:  Works For Me
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 01 Aug 2020 06:53:10 PM UTC, comment #43: 

Please open a new bug with new data.  Probably this is fixed and there are multiple issues anyway.

 Greg Troxel <gdt>
Group Member
Sun 01 Feb 2004 11:10:00 PM UTC, comment #42: 

I was looking for the answer to this maximum threads problem for a libmilter, and found that in order to get > 1022 threads you will need to make come changes to the kernel source and glibc source, this is discussed at many places including http://www.kegel.com/c10k.html#limits.threads .

What I had to really scrounge for was that I was only getting 256 threads and not this 1023 limit.  The reason was evident in the stack size, and on lowering the stack size with ulimit, I was able to use more threads.

# to view your current stack size in the current shell
ulimit -s
8192

# to set the stack size for the current shell
# do this before you run your threaded program
# test with different stack sizes
ulimit -s 512

I am still yet to work out the optimum setting for this, but it seems to divide up a limited amount of space, the lower the number the more threads.  In order to get >1022 you need to recompile as stated above.

Good luck!  

Stuart Clark


Anonymous
Tue 07 Oct 2003 01:33:31 PM UTC, comment #41: 

Using RH8, sendmail-8.12.8-9.80, spamass-milter-0.2.0, dcc, pyzor-0.4.0, and razor-agents-2.36.

spamass-milter is dropping out on my site as well - unexpectedly.  I just placed the debug flags on the script which restarts the milter, so will hope for the best.

Was this an issue in the earlier version of spamass-milter?  We are using this to create an email gateway and it is crucial that the project succeed, so if there is any new information on this, please let me know.

 Anonymous
Wed 09 Jul 2003 10:41:15 AM UTC, comment #40: 

I'm sending you the links to the gdb backtrace and the core file it generated, from the hang process:

http://omni.isr.ist.utl.pt/~yoda/gdb-log.26489
http://omni.isr.ist.utl.pt/~yoda/core.26489

Invalid User ID <#20633>
Mon 07 Jul 2003 07:52:13 PM UTC, comment #39: 

Interesting.  That looks like it crashed trying to output the X-Envelope-From header, or trying to build the X-Envelope-To: header.  I can't tell which because I forgot to add debug logging to all ::output exit cases.  Neither one should cause a crash though.  Can you get a coredump, or if you're running Linux, can you run it under valgrind?

Dan Nelson <dnelson>
Group administrator
Mon 07 Jul 2003 04:39:57 PM UTC, comment #38: 

I'm using 0.2.0, with sendmail 8.12.9. I've been running spamass-milter with all possible debug flags, I have tons of logs. This was spamass-milter's last comunication, before hang:

Jul  7 15:30:25 omni spamass-milter[25076]: mlfi_connect: enter
Jul  7 15:30:25 omni spamass-milter[25076]: Checking 193.126.4.61 against:
Jul  7 15:30:25 omni spamass-milter[25076]: mlfi_connect: exit
Jul  7 15:30:26 omni spamass-milter[25076]: mlfi_envfrom: enter
Jul  7 15:30:26 omni spamass-milter[25076]: queueid=h67EUPTd025075
Jul  7 15:30:26 omni spamass-milter[25076]: mlfi_envfrom: exit
Jul  7 15:30:26 omni spamass-milter[25076]: ::output enter
Jul  7 15:30:26 omni spamass-milter[25076]: output "X-Envelope-From: <fcurado@isr.ist.utl.pt>^M "

Invalid User ID <#20633>
Mon 07 Jul 2003 03:53:15 PM UTC, comment #37: 

Try 0.2.0 and see if you still have problems.  I could never cause my Debian machine to hang with 0.1.3a (sendmail 8.12.9).

Dan Nelson <dnelson>
Group administrator
Mon 07 Jul 2003 10:14:33 AM UTC, comment #36: 

Same problem here. This bug is several months old, any progress done so far? Last thing I did was to switch on all debugging flags. The log files increased ten-fold, but it didn't crash ever since. It seems to work fine, so far. But I'll post the debug info as soon as it crashes (if ever).

 Invalid User ID <#20633>
Sat 01 Feb 2003 11:45:39 AM UTC, comment #35: 

I run another spamassassin-milter (from this URL:
http://ftp.runestig.com/pub/misc/) and it runs
very fine on SuSE 8.0 (Sendmail 8.12.3), not much traffic, but running straight for several months now.

So I don't think its just a milter problem. Btw, RedHat
6.1/6.2 come with sendmail 8.9.3, RH71 with 8.11.2, I guess
that's just too old for a stable milter interface, which
became stable just on 8.12.

Only reason I don't use spamass-milter is the lack of
support of spamd running on a different host. But I already
found a patch to add this to spamass-milter, maybe it will
be added in the next release, then I give it a try.

Invalid User ID <#15368>
Tue 28 Jan 2003 08:49:40 PM UTC, comment #34: 

I have this problem running spamass-milter & also the milter-virus solution mentioned by Thomas. It occurs on several different hardware platforms, but all running RH7.3. I also have the milter-virus solution running on RH7.1 and have had no problems for over a year. The 7.1 system is not loaded! The others are sometimes. As someone else said "I would like to put this in production" but I am getting "leary" about it too! Has anyone spoken to sendmail about it? It seems that if it is present on two different milters, then there may be a milter interface problem. I had thought it might be a compile time problem with the first milter, but I have been through the directions several times to correct this, so I doubt it. Could it be the threads? Has anyone tried compiling sendmail without threads?



Invalid User ID <#15231>
Tue 21 Jan 2003 06:22:06 AM UTC, comment #33: 

Same thing here

Crashes about thrice a day, on RedHat 6.1 (so with all the updates applied it's almost everywhere 6.2 :-), spamassassin 2.43, sendmail 8.12.7, spamass-milter-0.1.3a.

No problems so far on another, similar machine with a lot less traffic (though it's only been running for a couple of days...)

 Anonymous
Fri 17 Jan 2003 08:42:36 AM UTC, comment #32: 

today crashed twice on the redhat 6.2 machine
(04:18 and 04:34)

 Invalid User ID <#14225>
Tue 14 Jan 2003 04:47:59 PM UTC, comment #31: 

today had a hang/crash (only 1 spamass-milter process running) on my redhat 7.3 installation (which was running spamass-milter ok for 2 weeks (since 0.13a installation)

the redhat 6.2 (which had all the crashes before) is running ok since the last crash friday 9 jan

 Invalid User ID <#14225>
Thu 09 Jan 2003 02:36:49 PM UTC, comment #30: 

and again (i wonder why it runs ok sometimes for days, and then crashes 5 times a day...) :

(gdb) run -p /var/run/spamass.sock
Starting program: /usr/sbin/spamass-milter -p /var/run/spamass.sock
[New Thread 6929 (manager thread)]
[New Thread 6928 (initial thread)]
[New Thread 6930]
[New Thread 6943]
[New Thread 6946]
[New Thread 6955]
[New Thread 6962]
[New Thread 6965]
[New Thread 6968]
[New Thread 6973]
[New Thread 6978]
[New Thread 6986]
[New Thread 6989]
[New Thread 6990]
[New Thread 7006]
[New Thread 7013]
[New Thread 7019]
[New Thread 7024]
[New Thread 7032]
[New Thread 7044]
[New Thread 7048]
[New Thread 7058]
[New Thread 7064]
[New Thread 7068]
[New Thread 7076]
[New Thread 7082]
[New Thread 7089]
[New Thread 7091]
[New Thread 7107]
[New Thread 7109]
[New Thread 7127]
[New Thread 7141]
[New Thread 7149]
[New Thread 7154]
[New Thread 7169]
[New Thread 7174]
[New Thread 7180]
[New Thread 7186]
[New Thread 7188]
[Switching to Thread 7186]

Program received signal SIGSEGV, Segmentation fault.
0x8052867 in __eh_alloc ()
(gdb) thread apply all backtrace

Thread 39 (Thread 7188):
#0  0x401380de in __select () from /lib/libc.so.6
#1  0x5 in ?? ()
#2  0x805765e in __eh_alloc ()
#3  0x80573fa in __eh_alloc ()
#4  0x8055dd7 in __eh_alloc ()
#5  0x80556c0 in __eh_alloc ()
#6  0x4007db85 in pthread_start_thread (arg=0xbafffe40) at manager.c:241

Thread 38 (Thread 7186):
#0  0x8052867 in __eh_alloc ()
#1  0x80597dd in _IO_stdin_used ()
#2  0x80601e0 in __ctype_b ()
Cannot access memory at address 0x74010100
(gdb)

 Invalid User ID <#14225>
Thu 09 Jan 2003 02:08:25 PM UTC, comment #29: 

argh and again within a few minutes :

(gdb) run -p /var/run/spamass.sock
Starting program: /usr/sbin/spamass-milter -p /var/run/spamass.sock
[New Thread 6701 (manager thread)]
[New Thread 6697 (initial thread)]
[New Thread 6702]
[New Thread 6707]
[New Thread 6720]
[New Thread 6727]
[New Thread 6735]
[New Thread 6752]
[New Thread 6758]
[New Thread 6794]
[New Thread 6798]
[New Thread 6805]
[New Thread 6810]
[New Thread 6814]
[New Thread 6815]
[New Thread 6816]
[New Thread 6820]
[New Thread 6822]
[New Thread 6823]
[New Thread 6824]
[Switching to Thread 6814]

Program received signal SIGSEGV, Segmentation fault.
0x8052867 in __eh_alloc ()
(gdb) thread apply all backtrace

Thread 20 (Thread 6824):
#0  0x401380de in __select () from /lib/libc.so.6
#1  0x0 in ?? ()

Thread 19 (Thread 6823):
#0  0x401380de in __select () from /lib/libc.so.6
#1  0x0 in ?? ()

Thread 18 (Thread 6822):
#0  0x401380de in __select () from /lib/libc.so.6
#1  0x0 in ?? ()

Thread 17 (Thread 6820):
#0  0x401380de in __select () from /lib/libc.so.6
#1  0x0 in ?? ()

Thread 16 (Thread 6816):
#0  0x401380de in __select () from /lib/libc.so.6
#1  0x0 in ?? ()

Thread 15 (Thread 6815):
#0  0x401380de in __select () from /lib/libc.so.6
#1  0x0 in ?? ()
Thread 14 (Thread 6814):
#0  0x8052867 in __eh_alloc ()
#1  0x80597dd in _IO_stdin_used ()
#2  0x80601e0 in __ctype_b ()
Cannot access memory at address 0x65010100

 Invalid User ID <#14225>
Thu 09 Jan 2003 02:02:30 PM UTC, comment #28: 

and a few minutes later :

Starting program: /usr/sbin/spamass-milter -p /var/run/spamass.sock
[New Thread 6560 (manager thread)]
[New Thread 6559 (initial thread)]
[New Thread 6561]
[New Thread 6565]
[New Thread 6568]
[New Thread 6571]
[Switching to Thread 6568]

Program received signal SIGSEGV, Segmentation fault.
0x8052867 in __eh_alloc ()
(gdb) thread apply all backtrace

Thread 6 (Thread 6571):
#0  0x401380de in __select () from /lib/libc.so.6
#1  0x0 in ?? ()

Thread 5 (Thread 6568):
#0  0x8052867 in __eh_alloc ()
#1  0x80597dd in _IO_stdin_used ()
#2  0x80601e0 in __ctype_b ()
Cannot access memory at address 0x2e010100
(gdb)

 Invalid User ID <#14225>
Thu 09 Jan 2003 01:57:33 PM UTC, comment #27: 

again :

[Switching to Thread 6470]

Program received signal SIGSEGV, Segmentation fault.
0x8052867 in __eh_alloc ()
(gdb) thread apply all backtrace

Thread 190 (Thread 6470):
#0  0x8052867 in __eh_alloc ()
#1  0x80597dd in _IO_stdin_used ()
#2  0x80601e0 in __ctype_b ()
Cannot access memory at address 0x70010100
(gdb)

 Invalid User ID <#14225>
Thu 09 Jan 2003 12:31:11 PM UTC, comment #26: 

and other crash :

Program received signal SIGSEGV, Segmentation fault.
0x8052867 in __eh_alloc ()
[Switching to Thread 4063]

Program received signal SIGSEGV, Segmentation fault.
0x8052867 in __eh_alloc ()
(gdb) thread apply all backtrace

Thread 555 (Thread 4071):
#0  pthread_handle_sigrestart (sig=2055208200, ctx={gs = 40220, __gsh = 16392,
      fs = 65088, __fsh = 31359, es = 65316, __esh = 31359, ds = 16387,
      __dsh = 0, edi = 0, esi = 0, ebp = 0, esp = 0, ebx = 0, edx = 0,
      ecx = 0, eax = 0, trapno = 0, err = 0, eip = 0, cs = 0, __csh = 0,
      eflags = 0, esp_at_signal = 0, ss = 0, __ssh = 0, fpstate = 0x0,
      oldmask = 0, cr2 = 0}) at pthread.c:629
#1  0x4007fc62 in __pthread_wait_for_restart_signal (self=0x7a7ffe40)
    at pthread.c:783
#2  0x4007db7a in pthread_start_thread (arg=0x7a7ffe40) at restart.h:26

Thread 554 (Thread 4067):
#0  pthread_handle_sigrestart (sig=2057305108, ctx={gs = 40220, __gsh = 16392,
      fs = 65088, __fsh = 31391, es = 1, __esh = 0, ds = 16387, __dsh = 0,
      edi = 0, esi = 0, ebp = 0, esp = 0, ebx = 0, edx = 0, ecx = 0, eax = 0,
      trapno = 0, err = 0, eip = 0, cs = 0, __csh = 0, eflags = 0,
      esp_at_signal = 0, ss = 0, __ssh = 0, fpstate = 0x0, oldmask = 0,
      cr2 = 0}) at pthread.c:629
#1  0x4007fc62 in __pthread_wait_for_restart_signal (self=0x7a9ffe40)
    at pthread.c:783
#2  0x400812a2 in __pthread_lock (lock=0x4017a100, self=0x7a9ffe40)
    at spinlock.c:68
#3  0x4007e7ba in __pthread_mutex_lock (mutex=0x4017a0f0) at mutex.c:84
---Type <return> to continue, or q <return> to quit---
#4  0x400e76c3 in free_atfork (mem=0x8063fa8, caller=0x80573db)
    at malloc.c:4744
#5  0x400e4f17 in __libc_free (mem=0x8063fa8) at malloc.c:2991
#6  0x80573db in __eh_alloc ()
#7  0x8055dd7 in __eh_alloc ()
#8  0x80556c0 in __eh_alloc ()
#9  0x4007db85 in pthread_start_thread (arg=0x7a9ffe40) at manager.c:241

Thread 553 (Thread 4066):
#0  0x400a9dcb in __sigsuspend (set=0x7abffc34)
    at ../sysdeps/unix/sysv/linux/sigsuspend.c:48
#1  0x4007fc62 in __pthread_wait_for_restart_signal (self=0x7abffe40)
    at pthread.c:783
#2  0x400812a2 in __pthread_lock (lock=0x4017a100, self=0x7abffe40)
    at spinlock.c:68
#3  0x4007e7ba in __pthread_mutex_lock (mutex=0x4017a0f0) at mutex.c:84
#4  0x400e4f8e in __libc_free (mem=0x8065f68) at malloc.c:3021
#5  0x80573db in __eh_alloc ()
#6  0x8055dd7 in __eh_alloc ()
#7  0x80556c0 in __eh_alloc ()
#8  0x4007db85 in pthread_start_thread (arg=0x7abffe40) at manager.c:241

Thread 552 (Thread 4063):
#0  0x8052867 in __eh_alloc ()
---Type <return> to continue, or q <return> to quit---
#1  0x80597dd in _IO_stdin_used ()
#2  0x80601e0 in __ctype_b ()
Cannot access memory at address 0x26010100
(gdb)

 Invalid User ID <#14225>
Thu 09 Jan 2003 09:15:11 AM UTC, comment #25: 

ok another hang

gdb output :

(gdb) thread apply all backtrace

Thread 3 (Thread 19282):
#0  0x400a9dcb in __sigsuspend (set=0xbf7ffc60)
    at ../sysdeps/unix/sysv/linux/sigsuspend.c:48
#1  0x40080162 in sigwait (set=0xbf7ffd08, sig=0xbf7ffd04) at signals.c:211
#2  0x8056817 in __eh_alloc ()
#3  0x4007db85 in pthread_start_thread (arg=0xbf7ffe40) at manager.c:241
(gdb)

 Invalid User ID <#14225>
Wed 08 Jan 2003 08:03:29 PM UTC, comment #24: 

hmms reading ls output it looks like these core files are 260Megabyte ?
but they are taking less diskspace :

du core.*
400     core.11692
416     core.7723
216     core.9727

packed in tgz it is 1Megabyte

 Invalid User ID <#14225>
Wed 08 Jan 2003 07:53:41 PM UTC, comment #23: 

eh VSZ = 264912
reading man ps :

vsize        total VM size in bytes

so it is only 263Kbyte ?

also i found 3 coredumps from today :

-rw-------    1 root     root     268808192 Jan  8 16:55 core.11692
-rw-------    1 root     root     268824576 Jan  8 14:42 core.7723
-rw-------    1 root     root     268677120 Jan  8 15:43 core.9727

i don't want to put them public (since there are some email details inside them)
will mail them to Dan

 Invalid User ID <#14225>
Wed 08 Jan 2003 06:51:52 PM UTC, comment #22: 

Wow. vsz is huge.  That could mean problems, but a vsz of 263MB is pretty much impossible, unless you're trying to email 200mb files around.  More likely the number is screwed up because of the crash.

Dan Nelson <dnelson>
Group administrator
Wed 08 Jan 2003 04:06:32 PM UTC, comment #21: 

and again:

Jan  8 17:05:01 mail sendmail[11802]: h08G11TN011802: Milter (spamassassin): timeout before data read
Jan  8 17:05:01 mail sendmail[11802]: h08G11TN011802: Milter (spamassassin): to error state
Jan  8 17:05:01 mail sendmail[11802]: h08G11TN011802: Milter (spamassassin): init failed to open
Jan  8 17:05:01 mail sendmail[11802]: h08G11TN011802: Milter (spamassassin): to error state

[root@mail /root]# ps lww -C spamass-milter     
  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
040     0 10198     1   9   0 264912 1036 rt_sig S   ?          0:00 spamass-milter -p /var/run/spamass.sock -f

sometimes it happens multiple times a day
and sometimes it runs ok for a few days

 Invalid User ID <#14225>
Wed 08 Jan 2003 03:03:05 PM UTC, comment #20: 

ps output after restart :

[root@mail /root]# ps lww -C spamass-milter 
  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
040     0 10196     1   9   0  1676  804 do_sel S    pts/6      0:00 spamass-milter -p /var/run/spamass.sock -f
040     0 10197 10196   8   0  1676  804 do_pol S    pts/6      0:00 spamass-milter -p /var/run/spamass.sock -f
040     0 10198 10197   9   0  1676  804 rt_sig S    pts/6      0:00 spamass-milter -p /var/run/spamass.sock -f

so when it hangs the VSZ is realy high ?
(and no subprocesses)

 Invalid User ID <#14225>
Wed 08 Jan 2003 02:59:31 PM UTC, comment #19: 

and again :

Jan  8 15:59:11 mail sendmail[9992]: h08EtBTN009992: Milter (spamassassin): timeout before data read
Jan  8 15:59:11 mail sendmail[9992]: h08EtBTN009992: Milter (spamassassin): to error state
Jan  8 15:59:11 mail sendmail[9992]: h08EtBTN009992: Milter (spamassassin): init failed to open
Jan  8 15:59:11 mail sendmail[9992]: h08EtBTN009992: Milter (spamassassin): to error state

ps output :

[root@mail /root]# ps lww -C spamass-milter
  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
040     0  8032     1   9   0 263828 848 rt_sig S    ?          0:00 spamass-milter -p /var/run/spamass.sock -f

 Invalid User ID <#14225>
Wed 08 Jan 2003 01:50:00 PM UTC, comment #18: 

ok next hang :

Jan  8 14:49:11 mail sendmail[7786]: h08DjBTN007786: Milter (spamassassin): timeout before data read
Jan  8 14:49:11 mail sendmail[7786]: h08DjBTN007786: Milter (spamassassin): to error state
Jan  8 14:49:11 mail sendmail[7786]: h08DjBTN007786: Milter (spamassassin): init failed to open
Jan  8 14:49:11 mail sendmail[7786]: h08DjBTN007786: Milter (spamassassin): to error state

ps shows :

[root@mail /root]# ps lww -C spamass-milter
  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
040     0 11033     1   9   0 264932 908 rt_sig S    ?          0:00 spamass-milter -p /var/run/spamass.sock -f

 Invalid User ID <#14225>
Mon 06 Jan 2003 04:25:14 PM UTC, comment #17: 

ok again :

Jan  6 17:15:23 mail sendmail[14960]: h06GFNTN014960: Milter (spamassassin): error connecting to filter: Connection refused by /var/run/spamass.sock
Jan  6 17:15:23 mail sendmail[14960]: h06GFNTN014960: Milter (spamassassin): to error state
Jan  6 17:15:24 mail sendmail[14960]: h06GFNTN014960: localhost.localdomain [127.0.0.1] did not issue MAIL/EXPN/VRFY/ETRN during connection to Daemon1
Jan  6 17:15:27 mail sendmail[14961]: h06GFRTN014961: Milter (spamassassin): error connecting to filter: Connection refused by /var/run/spamass.sock
Jan  6 17:15:27 mail sendmail[14961]: h06GFRTN014961: Milter (spamassassin): to error state

[root@mail /root]# service spamass-milter status
spamass-milter dead but subsys locked

but no core :( (next time it should dump a core)

(ps also nothing, but as expected)

 Invalid User ID <#14225>
Mon 06 Jan 2003 03:29:08 PM UTC, comment #16: 

Make sure you have coredumps enabled (run "ulimit -c unlimited" just before launching the milter in the startup script), and when it crashes it will create a file called "core".  You can determine where is will end up by starting up the milter, and running "lsof -c spamass-milter", and looking for a "cwd" line.  That's the processes current directory.

Dan Nelson <dnelson>
Group administrator
Mon 06 Jan 2003 03:24:30 PM UTC, comment #15: 

ok next time i will do a "ps lww -C spamass-milter"

if i get another 'spamass-milter dead but subsys locked' how do i dump it to a core then ?

 Invalid User ID <#14225>
Mon 06 Jan 2003 02:12:34 AM UTC, comment #14: 

A coredump from the crash on the 2nd would have been nice;  as for the hangs, what does "ps lww -C spamass-milter" print?  I'm most interested in the WCHAN and TIME columns.


Dan Nelson <dnelson>
Group administrator
Sun 05 Jan 2003 11:20:38 PM UTC, comment #13: 

today again, is there anything to debug ?


Jan  5 23:55:24 mail sendmail[11850]: h05MpOTN011850: Milter (spamassassin): tim
eout before data read
Jan  5 23:55:24 mail sendmail[11850]: h05MpOTN011850: Milter (spamassassin): to
error state
Jan  5 23:55:24 mail sendmail[11850]: h05MpOTN011850: Milter (spamassassin): ini
t failed to open
Jan  5 23:55:24 mail sendmail[11850]: h05MpOTN011850: Milter (spamassassin): to
error state


[root@mail /root]# /etc/rc.d/init.d/spamass-milter status
spamass-milter (pid 20618) is running...
[root@mail /root]# /etc/rc.d/init.d/spamass-milter restart
Shutting down spamass-milter:          [  OK  ]
Starting spamass-milter:               [  OK  ]

 Invalid User ID <#14225>
Thu 02 Jan 2003 10:37:09 AM UTC, comment #12: 

again i needed to restart spamass-milter :

Jan  2 11:30:45 mail sendmail[20540]: h02AUjTN020540: Milter (spamassassin): err
or connecting to filter: Connection refused by /var/run/spamass.sock
Jan  2 11:30:45 mail sendmail[20540]: h02AUjTN020540: Milter (spamassassin): to
error state

Jan  2 11:31:48 mail sendmail[20546]: h02AVmTN020546: Milter (spamassassin): err
or connecting to filter: Connection refused by /var/run/spamass.sock
Jan  2 11:31:48 mail sendmail[20546]: h02AVmTN020546: Milter (spamassassin): to
error state

[root@mail log]# service spamass-milter status
spamass-milter dead but subsys locked

[root@mail log]# service spamass-milter restart
Shutting down spamass-milter:                 [FAILED]
Starting spamass-milter:                      [  OK  ]


Invalid User ID <#14225>
Thu 02 Jan 2003 10:10:43 AM UTC, comment #11: 

looks like 1.0.3a still has a lock bug or something :

Jan  2 11:05:03 mail sendmail[19120]: h02A13UW019120: Milter (spamassassin): timeout before data read
Jan  2 11:05:03 mail sendmail[19120]: h02A13UW019120: Milter (spamassassin): to error state
Jan  2 11:05:03 mail sendmail[19120]: h02A13UW019120: Milter (spamassassin): init failed to open
Jan  2 11:05:03 mail sendmail[19120]: h02A13UW019120: Milter (spamassassin): to error state

(and this for all emails for about 15 minutes)

spamass-milter was still running
fixed by restarting spamass-milter

(spamassmilter 1.03a / sendmail 8.12.6 / redhat 6.2 +updates)

Invalid User ID <#14225>
Fri 15 Nov 2002 12:31:21 PM UTC, comment #10: 

hi everybody

i hope you can help me. after some time i get this in my maillog and
sendmail stop's acceppting or sendind email. the only solution i found is
restarting spamd - but this doesn't help all the time.

Nov 13 04:33:33 idefix sendmail[10093]: gAD3TXHI010093: Milter
(spamassassin): timeout before data read
Nov 13 04:33:33 idefix sendmail[10093]: gAD3TXHI010093: Milter
(spamassassin): to error state
Nov 13 04:33:33 idefix sendmail[10093]: gAD3TXHI010093: Milter
(spamassassin): init failed to open
Nov 13 04:33:33 idefix sendmail[10093]: gAD3TXHI010093: Milter
(spamassassin): to error state


my system is a quad xeon server with 1 gig of ram, installed sendmail 8.12.6
and SpamAssassin-2.43.

i configure spamassassin normally:
./configure
make
make install

and included the stuff to sendmail via:
INPUT_MAIL_FILTER(`spamassassin', `S=local:/var/run/spammilter/spamass.sock,
F=, T=C:15m;S:4m;R:4m;E:10m')

then started spamd with:
        rm /var/run/spammilter/spamass.sock
        /usr/local/sbin/spamassmilter -p /var/run/spammilter/spamass.sock -f
        /usr/bin/spamd -d -a -q -x

and looked into sendmail log:

Nov 14 00:17:06 idefix sendmail[25314]: gADNH6TB025314: from=<www@XXXX>,
size=832, class=0, nrcpts=1, msgid=<200211132319.AAA06437@web38.rainbow.ch>,
proto=ESMTP, daemon=MTA, relay=XXXX [x.x.x.x]
Nov 14 00:17:11 idefix sendmail[25314]: gADNH6TB025314: Milter add: header:
X-Spam-Status: Yes, hits=5.1
required=5.0\n\ttests=NO_MX_FOR_FROM,NO_REAL_NAME,ORDER_STATUS,SPAM_PHRASE_0
0_01,\n\t      UPPERCASE_25_50\n\tversion=2.43
Nov 14 00:17:11 idefix sendmail[25314]: gADNH6TB025314: Milter add: header:
X-Spam-Flag: YES
Nov 14 00:17:11 idefix sendmail[25314]: gADNH6TB025314: Milter add: header:
X-Spam-Report: Detailed Report\n  SPAM: -------------------- Start
SpamAssassin results ----------------------\n  SPAM: This mail is probably
spam.  The original message has been altered\n  SPAM: so you can recognise
or block similar unwanted mail in future.\n  SPAM: See
http://spamassassin.org/tag/ for more details.\n  SPAM: \n  SPAM: Content
analysis details:   (5.10 hits, 5 required)\n  SPAM: ORDER_STATUS
(-1.4 points) Subject looks like order info\n  SPAM: NO_REAL_NAME       (1.3
points)  From: does not include a real name\n  SPAM: SPAM_PHRASE_00_01  (0.8
points)  BODY: Spam phrases score is 00 to 01 (low)\n  SPAM: NO_MX_FOR_FROM
(3.1 points)  No MX records for the From: domain\n  SPAM: UPPERCASE_25_50
(1.3 points)  message body is 25-50% uppercase\n  SPAM: \n
 SPAM: -------------------- End of SpamAssassin
results ---------------------
Nov 14 00:17:11 idefix sendmail[25314]: gADNH6TB025314: Milter add: header:
X-Spam-Level: ***
Nov 14 00:17:11 idefix sendmail[25314]: gADNH6TB025314: Milter add: header:
X-Spam-Checker-Version: SpamAssassin 2.43 (1.115.2.20-2002-10-15-exp)
Nov 14 00:17:11 idefix sendmail[25314]: gADNH6TB025314: Milter change:
header  Subject: from Katalog - Order to [SPAM] Katalog - Order
Nov 14 00:17:11 idefix sendmail[25314]: gADNH6TB025314: Milter message: body
replaced
Nov 14 00:17:12 idefix sendmail[25314]: gADNH6TB025314: Milter add: header:
X-Virus-Scanned: by AMaViS/Sophos Anti-Virus for Unix
Nov 14 00:17:12 idefix sendmail[25329]: gADNH6TB025314: to=info@xxxxxx.xx,
delay=00:00:06, xdelay=00:00:00, mailer=esmtp, pri=62192,
relay=mail.xxxx.xx. [x.x.x.x], dsn=2.0.0, stat=Sent (gADNHAP07034 Message
accepted for delivery)

-> well, it works.

and it worked for about 1 day, then the strange error began:
sendmail didn't accepted any mail (in and outbound), even local delivery
didn't workd (could not connect..)

does anyone has an idea what happend? what went wrong? it's urgent, because
it's an running system...

greetings

steven

Invalid User ID <#12685>
Wed 30 Oct 2002 02:19:16 PM UTC, comment #9: 

Hi,
maybe this can do the trick !!!

signal(SIGCHLD, sigCHLD);

void sigCHLD() {
        int status;
        while(wait3(&status, WNOHANG, (struct rusage *) 0) >= 0);
        /* Sit around and twiddle our thumbs */
        }

-email is unavailable-

 Anonymous
Wed 30 Oct 2002 08:50:53 AM UTC, comment #8: 

Hi,
i have the same trouble but not with unix socket's but with TCP connection to it "/usr/sbin/spamass-milter -p inet:2007"

I hardly think that this could be tracked down to an error in the "libmilter" from sendmail. The ground is simple. I wrote/extend an virus filter on milter basis in c "milter-virus" and he have the same bad thing. BUT it was not from the start. There i think it happend after some fixes in the cleaning of the private ctx structure. So it maybe is only an error how and when to clean the structur in the milter doku.

Would be great if it will be fixed because in the current stage it is not useable for important mail server.

 Anonymous
Fri 18 Oct 2002 07:29:28 PM UTC, comment #7: 

 I too see problems from time to time. Not sure if it relates to this or not. On Solaris 8 spamass-milter seems to stablize at 59M on 1 and 32M on the other 2 boxes.

 Yesterday, I noticed a couple SPAM's sneak through so I took a look the headers. It was passed on with NO headers added. I checked the logs and sure enough, no messages about adding the headers. I was however receiving the "identified spam" and "clean message", which are being written to seperate log files via syslog-ng.

 Any info would be great. spamass-milter was still running. And nothing about it crashing.

 - Mike

 Anonymous
Wed 09 Oct 2002 03:27:35 PM UTC, comment #6: 

Check your maxprocs resource limit.  Error 11 is EAGAIN, and the pthread_create manpage says:

EAGAIN - not enough system resources to create a process for the new thread.

That means that it tried to fork a new thread but the kernel said there were too many processes running already.

Dan Nelson <dnelson>
Group administrator
Wed 09 Oct 2002 12:15:33 PM UTC, comment #5: 

Crashes on me too very frequently: Excerpt from maillog
Oct  9 05:08:49 nameserver2 spamass-milter[5981]: SpamAssassin: thread_create() failed: 11, abort
Oct  9 05:08:49 nameserver2 sendmail[22297]: g9998Hmo022297: Milter (spamassassin): read returned -1: Connection reset by [218
.2.142.156]
Will try some of the stuff here. I am willing to troubleshoot if anyone knowledgeable suggests something.

Currently I have a modified rc.script with an addtional parameter startifstopped running every 10 minutes.

Joe Maimon <jmaimon>
Tue 08 Oct 2002 02:44:02 PM UTC, comment #4: 

fty: try running spamass-milter this way:

LD_PRELOAD=watchmalloc.so.1 MALLOC_DEUBG=WATCH spamass-milter <etc etc>

That will load a debugging malloc library that might be able to track down the memory leak.  Or one of the Linux people with problems, try running under valgrind --leak-check=yes.

I can't reproduce the crashing problem on my Debian machine.  My milter has been runing for almost a month, and has stabilized at 16MB of memory.

USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root      2063  0.0  0.3 18280  392 ?        S    Sep11   0:41 /usr/local/sbin/spamass-milter -p /var/run/sendmail/spamass.sock

Dan Nelson <dnelson>
Group administrator
Tue 08 Oct 2002 11:36:43 AM UTC, comment #3: 

I'm seeing the milter crash on Solaris 2.8 as well.  No log
messages nor zombies.  I've setup a cron job to monitor it's
state every 10 minutes and restart it if necessary.  It crashes
on average about 1.5 times/day.  My monitor log shows that it
steadily leaks memory - vsz starts at about 2900 and climbs to
19700 or so at which point the monitor finds it is gone.

 Invalid User ID <#11086>
Mon 30 Sep 2002 09:39:43 PM UTC, comment #2: 

  We are having this problem as well. I initially responded to support issue #101229 but my comments there apply to this bug.

  Since then I have modified spamass-milter, adding a switch to turn off the replacement of the message body. The results o my initial study looked like it might be related to the attempt to replace message bodies of size 64k and greater. libmilter uses a chunk size of 64k when replacing text in the message, so this looked like a problem with libmilter.

  Anyway, after running the milter with message body replacment turned off, it still hangs. To keep it running, I've written this little script to check on it's health every five minutes:

#! /bin/csh

@ numprocs = `ps -ef | grep spamass-milter | wc -l`

if ( $numprocs < 3 ) then

  echo " "
  echo Milter dead at `date`
  /etc/init.d/spamass-milter restart
  exit

endif

echo -n $numprocs

Invalid User ID <#10991>
Sat 28 Sep 2002 02:12:05 PM UTC, comment #1: 

I too have seen this problem on a medium volume site. I woke up this morning and found 15 messages in my inbox that shouldn't have been there :)

 Seems to work fine while it's running. We are looking to roll this onto a heavy loaded server, but this makes me a little leary.

 Any help would be great.

BTW : I see the same info in the log files

 Anonymous
Thu 29 Aug 2002 07:32:35 AM UTC, original submission:  

spamass-milter crashes after some hours of running in a medium-volume setup. Symptoms are as follows:
- There ist just a single totally unresponsive spamass-milter process hanging around. (ltrace or strace
of that process does not do anything)
- In the log, the following appears:
  Aug 29 03:37:22 jenner sm-mta[22274]: g7T1MMHI022274: Milter (spamassassin): error connecting to filter: Connection timed out with /var/run/sendmail/spamass.sock

There are no signs of anything going wrong before.

 Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gdt (Updated the item)
  • -email is unavailable- added by kovert (Updated the item)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-08-01 gdt StatusNone Works For Me
    2020-08-01 gdt Open/ClosedOpen Closed
    2014-08-14 kovert Severity3 - Normal 1 - Wish

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.13-ec04.
    Corresponding source code