Eli, Two ideas:
1. signal 11 is a sementation violation. This is usually triggered by a process that accesses a protected memory space... and more specifically the classic NULL pointer dereference. So probably at some point the child process tries to dereference a NULL pointer and this signal is generated. The default action for this signal in serverchild.c is to exit(1). You could comment out the SIGSEGV line in the SetChildSigHandler() function so that the system default handler will get called and a core file will be generated from which you can then do a post mortem on the core file to determine the line and file that was executed when the signal was generated which would expose the cause of segmentation violation. 2. You may also try increasing the log level of the imap or pop3 tasks inside the dbmail.conf file to something higher than ERROR... try setting TRACE_LEVEL=5 in the [POP] and [IMAP] sections and hopefully you may get more error log output surrounding the problem which may reveal more about the problem. --Dave ----- Original Message ----- From: [EMAIL PROTECTED] To: [email protected] Sent: Monday, December 23, 2002 3:54 PM Subject: [Dbmail] dbmail-pop3d sig11'ing, not accepting connections. I'm repeating (essentially) an email I sent last week about the same subject. On my dbmail-1.0(release) system, dbmail-pop3d has started sig11'ing on connect and dumping connections. The problem is mysteriously getting worse for no (apparent) reason. As indicated by the error log below, the problem does not "go away" on its own, if left untampered. Here are shown 4 sequential (5-minute interval) pop checks that fail, followed by a single outgoing message on the user account, to the same account then POP3 works, then several minutes later it stops functioning again. Any ideas on resolving this, other than waiting for a full release? /eli Dec 23 14:25:10 tardis dbmail/pop3d[823]: PerformChildTask(): incoming connection from [192.168.1.1 ({HOSTNAME})] Dec 23 14:25:10 tardis dbmail/pop3d[823]: pop3_handle_connection(): error, uncomplete session Dec 23 14:30:10 tardis dbmail/pop3d[775]: PerformChildTask(): incoming connection from [192.168.1.1 ({HOSTNAME})] Dec 23 14:30:10 tardis dbmail/pop3d[775]: ChildSighandler(): got signal [11] Dec 23 14:35:10 tardis dbmail/pop3d[613]: PerformChildTask(): incoming connection from [192.168.1.1 ({HOSTNAME})] Dec 23 14:35:10 tardis dbmail/pop3d[613]: ChildSighandler(): got signal [11] Dec 23 14:40:10 tardis dbmail/pop3d[829]: PerformChildTask(): incoming connection from [192.168.1.1 ({HOSTNAME})] Dec 23 14:40:10 tardis dbmail/pop3d[829]: pop3_handle_connection(): error, uncomplete session Dec 23 14:40:40 tardis dbmail/pop3d[606]: ChildSighandler(): got signal [11] Dec 23 14:40:45 tardis dbmail/pop3d[721]: ChildSighandler(): got signal [11] Dec 23 14:41:02 tardis dbmail/smtp[946]: insert_messages(): message id=465, size=1321 is inserted Dec 23 14:41:07 tardis dbmail/pop3d[611]: ChildSighandler(): got signal [11] Dec 23 14:42:01 tardis dbmail/pop3d[883]: PerformChildTask(): incoming connection from [192.168.1.21 (Lookup failed)] Dec 23 14:42:01 tardis dbmail/pop3d[883]: pop3(): user estair logged in [messages=2, octets=2754] Dec 23 14:42:02 tardis dbmail/pop3d[883]: pop3_handle_connection(): user estair logging out [message=0, octets=0] Dec 23 14:45:07 tardis dbmail/pop3d[814]: ChildSighandler(): got signal [11] Dec 23 14:45:10 tardis dbmail/pop3d[818]: PerformChildTask(): incoming connection from [192.168.1.1 ({HOSTNAME})] Dec 23 14:45:10 tardis dbmail/pop3d[818]: pop3_handle_connection(): error, uncomplete session
