Milter-greylist

On Mon, Jul 11, 2005 at 08:02:06AM +0200, manu@... wrote:
> Will Aoki <waoki@...> wrote:
> 
> > Since putting milter-greylist 2.0 into production a few days ago on a
> > low- to moderate-volume Sendmail 8.12.10 system, it's started failing
> > regularly after about 24 hours of operation.

I changed the milter options to T=C:3s;E:8s to reduce the effects of the
hanging milter, and milter-greylist started staying up for four to ten
days at a time. I wonder if it's related or just a coincidence?

> Maybe you hit a system limit? 

Possibly, but I can't think of what. System logs don't indicate anything
running out of threads or being killed for exceeding resource limits.
Milter-greylist memory size starts around 12M and slowly grows to the
20M to 25M range. Resource limits are set high enough that they
shouldn't cause problems unless something is broken and out of control.

I don't yet have this data for a milter-greylist compiled with debugging
symbols, but attaching GDB to a hung milter-greylist process and getting
a backtrace showed this call stack:

 #0  0x0fe0f4d8 in sigset () from /lib/libc.so.6
 #1  0x0ff38c90 in sigwait () from /lib/libpthread.so.0
 #2  0x10010288 in mi_signal_thread ()
 #3  0x0ff35428 in pthread_start_thread () from /lib/libpthread.so.0
 #4  0x0feb5e68 in clone () from /lib/libc.so.6

I should have more useful data the next time it dies, since I'm now
running a milter-greylist compiled with debugging symbols.



On a somewhat related note, has anyone else noticed that the supplied
rc-debian.sh doesn't work to stop the milter? It usually won't die
unless I kill all five of its processes.

-- 
William Aoki     KD7YAF    waoki@...    5-1924