xinetd dies on occasion, and we'd love to know why (and what to
do about it). any rtfm (with 'm' indicator) or other pointers
gladly accepted.
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...
when folks couldn't get their email, we noticed it.
i just re-started it by hand (/etc/init.d/xinetd restart) and all
seems well again, for now.
Apr 6 09:51:09 boss xinetd[11849]: xinetd Version 2.3.4 started with libwrap loadavg
options compiled in.
Apr 6 09:51:09 boss xinetd[11849]: Started working: 9 available services
$ cat /etc/debian_version
3.0
$ strings `which xinetd` | grep Version
xinetd Version 2.3.4
xinetd Version 2.3.4
what does this portend? how would we go about tracking the suorce
of those 50 bad signals? thanks in advance for any assistance!
--
I use Debian/GNU Linux version 3.0;
Linux boss 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i586 unknown
DEBIAN NEWBIE TIP #10 from Will Trillich <[EMAIL PROTECTED]>
:
Looking to run a command or two at REGULAR INTERVALS? Try
"crontab -e" for starters (see "man cron" or "man crontab").
You might also investigate the "anacron" package (apt-get install
anacron).
Also see http://newbieDoc.sourceForge.net/ ...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
