Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!news.vbc.net!samba.rahul.net!rahul.net!a2i!hustle.rahul.net!rahul.net!a2i!news.clark.net!world1.bawave.com!news2.cais.net!news.cais.net!news1.erols.com!newsmaster@erols.com From: Ken Bigelow <kbigelow@www.play-hookey.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: telnetd dies on 2.1? Date: Mon, 10 Jun 1996 22:06:32 -0700 Organization: Erols Internet Services Lines: 39 Message-ID: <31BCFED8.43FF@www.play-hookey.com> References: <dhawkDsquyB.HGM@netcom.com> NNTP-Posting-Host: kenjb05.play-hookey.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.02 (Win16; I) David H wrote: > > I have a machine on the net that's running 2.1 FreeBsd. It was > up and running for 94 days without a hitch and then Something > Happened. Users couldn't login in to it. The web server was > still serving documents, but various process quit working -- > it didn't run its nightly crontab jobs. When it was rebooted > there wasn't anything in the messages file that indicated what > went wrong. > > Four days later the same thing happened. I had added a .rhosts > file and still couldn't get in. > > My guess is that telnetd is dying. Any way I can check this and > prevent it? Or is there some other lockup that could occur that > would let it answer pings and web requests but not accept logins? > I think you'll have to wait until the problem crops up again. Then, without rebooting or changing anything else, log onto that system directly as root and run ps -ax to monitor active processes. You may also find a message or two on the screen that didn't get recorded. My jump-at-conclusions guestimate is that for some reason inetd has quit on you. Since Apache is run in standalone mode it won't be affected, and as I recall ping is a low-level automated function that essentially takes care of itself. You can also look for error message on ttyv0 that may have scrolled off the screen. Hit Scroll Lock and the up arrow. The display will be restored when you hit Scroll Lock again. Be sure to record all error messages before you reboot, and the result of your search for the inetd process using ps. The exact status of everything can hold valuable troubleshooting info. I hope this helps! Ken