Dccm troubles

Dale Hege fhege@sover.net
Fri Sep 5 16:16:33 UTC 2003


Well, I got a core. :)

BSD/OS 4.1, Sendmail 8.12.9, dcc 1.2.4 with -g on libmilter & dcc

Program terminated with signal 11, Segmentation fault.
#0  0xa007dc8a in _thread_sys_connect ()
(gdb) where
#0  0xa007dc8a in _thread_sys_connect ()
#1  0x805cce1 in clnt_xmit (emsg=0x80dcbb6 "", ctxt=0x8122a00,
xlog=0x8122a34, 
    ap=0x100b9bf8, msg=0x10181d04, msg_len=188) at clnt_send.c:1403
#2  0x805e213 in dcc_clnt_op (emsg=0x80dcbb6 "", ctxt=0x8122a00, grey=0, 
    act_inxp=0x10181c08, msg=0x10181d04, msg_len=188, op=DCC_OP_REPORT, 
    resp=0x10181c5c, resp_max_len=168, resp_su=0x0) at clnt_send.c:2317
#3  0x8056007 in dcc_ask (emsg=0x80dcbb6 "", ctxt=0x8122a00,
header=0x80dd078, 
    cks=0x80dd1a0, honorp=0x80dd8c4 "", local_tgts=1) at ask.c:84
#4  0x804a84a in ask_dcc (wp=0x80dc900) at dccm.c:1927
#5  0x804b184 in dccm_eom (milter_ctx=0x8116d00) at dccm.c:2258
#6  0x804e417 in st_bodyend ()
#7  0x804db81 in mi_engine ()
#8  0x804cae7 in mi_handle_session ()
#9  0x804c40f in mi_thread_handle_wrapper ()
#10 0xa0034de2 in _thread_kern_start ()


On Fri, 5 Sep 2003, Dale Hege wrote:

> 
> 
> On Thu, 4 Sep 2003, Vernon Schryver wrote:
> 
> > > From: Dale Hege <fhege@sover.net>
> > 
> > > Hello, I recently started using dccm to filter our email and have found
> > > that dccm seems to "die" fairly frequently. I have 4 dccm servers 3 are
> > 
> > > ...
> > > One from the 4.3.1 running dccm 1.2.2
> > 
> > > #1  0xa008831a in abort () from /shlib/libc_s.4.3.0
> > > #2  0xa0089d1b in _thread_aio_entry_init () from /shlib/libc_s.4.3.0
> > > #3  0xa0089b14 in _thread_sys_accept () from /shlib/libc_s.4.3.0
> > > #4  0x804ce35 in mi_listener ()
> > 
> > It might be interesting to compile the milter library with -g.
> 
> I have upgraded to 1.2.4 and compiled both libmilter and dcc with -g. So
> we'll see the next time I get a core. :)
> 
> > 
> > > #0  0xa007e623 in _thread_aio_suspend ()
> > > (gdb) where
> > > #0  0xa007e623 in _thread_aio_suspend ()
> > > #1  0xa007ce8f in _thread_sys_write ()
> > > #2  0x804909c in log_write (wp=0x80cec10, logbuf=0x1014eda4, len=77)
> > >     at dccm.c:866
> > 
> > That's also in the bowels of the BSD/OS thread package.
> > I've fought bugs in BSD/OS 4.2 pthreads.  The code aint pretty,
> > although that applies to about any threads that make do with
> > select() kludges.
> > 
> > > But most of the time it seems to just stop running with no core. The last
> > > messages in the logs look like this
> > >
> > > Sep  4 18:03:10 trout dccm[22855]: 1.2.2 rejected messages to 649 targets
> > > and discarded messages to 0 targets among 1306 total since 09/04/03
> > > 17:54:01
> > 
> > That looks like what should happen if the sendmail milter library
> > gets unhappy.  Have you looked in likely syslog places for
> > messages from libmilter?
> > 
> 
> Attached are the minutes leading up to one of my failures from
> sendmails milter (no core) 
> 
> Sep  4 18:47:48 walleye dccm[5739]: 1.2.2 rejected messages to 718 targets
> and discarded messages to 0 targets among 1197 total since 09/04/03
> 18:39:19
> 
> Looks like it gets busy and doesn't aways catch new connections. 
> 
> Any ideas on how to make milter a little more verbose to try and find why
> its unhappy?
> 
> Thanks,
> 
> -Dale
> 
> > 
> > Aother site running BSD/OS 4.2 has presistent dccm crashes that look
> > like stack corruption.  The corruption always seems to be the same,
> > but I've not yet tried to find the stack.  It looks like a thread
> > tried to return through a broken frame and went into the weeds, leaving
> > the thread's real stack I don't know where..
> > 
> > 
> > Vernon Schryver    vjs@rhyolite.com
> > _______________________________________________
> > DCC mailing list      DCC@rhyolite.com
> > http://www.rhyolite.com/mailman/listinfo/dcc
> > 
> 
> 




More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.