On Fri, Apr 09, 2004 at 01:30:12AM -0500, Will Trillich said
> something is making our xinetd process self-terminate, which
> throws a monkey wrench into sending and receiving email... and
> we'd like to know what we can do to find out a) what's sending
> these signals, and b) how to stop it...
>
> from /var/log/syslog this morning --
>
> Apr 6 06:36:16 boss xinetd[10615]: {general_handler} (10615) Unexpected signal: 11
> (Segmentation fault)
> Apr 6 06:36:16 boss last message repeated 9 times
> Apr 6 06:36:16 boss xinetd[10615]: {bad_signal} Received 10 signals in 1 seconds.
> Exiting...
> Apr 6 06:36:16 boss xinetd[10616]: {general_handler} (10616) Unexpected signal: 11
> (Segmentation fault)
> Apr 6 06:36:17 boss last message repeated 9 times
> Apr 6 06:36:17 boss xinetd[10616]: {bad_signal} Received 10 signals in 1 seconds.
> Exiting...
> Apr 6 06:36:16 boss xinetd[10617]: {general_handler} (10617) Unexpected signal: 11
> (Segmentation fault)
> Apr 6 06:36:17 boss last message repeated 9 times
> Apr 6 06:36:17 boss xinetd[10617]: {bad_signal} Received 10 signals in 1 seconds.
> Exiting...
> Apr 6 06:36:16 boss xinetd[5525]: {general_handler} (5525) Unexpected signal: 11
> (Segmentation fault)
> Apr 6 06:36:17 boss last message repeated 9 times
> Apr 6 06:36:17 boss xinetd[5525]: Resetting...
> Apr 6 06:36:17 boss xinetd[5525]: {general_handler} (5525) Unexpected signal: 11
> (Segmentation fault)
> Apr 6 06:36:17 boss last message repeated 8 times
> Apr 6 06:36:17 boss xinetd[5525]: Resetting...
> Apr 6 06:36:17 boss xinetd[10623]: {general_handler} (10623) Unexpected signal: 11
> (Segmentation fault)
> Apr 6 06:36:17 boss last message repeated 8 times
> Apr 6 06:36:17 boss xinetd[10623]: {bad_signal} Received 10 signals in 1 seconds.
> Exiting...
> Apr 6 06:36:17 boss xinetd[5525]: {general_handler} (5525) Unexpected signal: 11
> (Segmentation fault)
> Apr 6 06:36:17 boss last message repeated 8 times
> Apr 6 06:36:17 boss xinetd[5525]: Resetting...
> Apr 6 06:36:17 boss xinetd[5525]: {general_handler} (5525) Unexpected signal: 11
> (Segmentation fault)
> Apr 6 06:36:17 boss last message repeated 2 times
> Apr 6 06:36:17 boss xinetd[5525]: {bad_signal} Received 50 bad signals. Exiting...Have you run memtes86 lately? Bad ram could make it segfault. But since it's a network service, so could (potentially) a remote attack. I don't know anything about xinetd, but can you see if it was receiving connections just before each segfault, and from who? -- Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: un-Australian AUTODIN mindwar ASIO Mole Perl-RSA Dateline
signature.asc
Description: Digital signature
