samperi@mancol.UUCP (Dominick Samperi) (05/13/88)
Every once in a while (perhaps once per month) a 3b2/300 that we are using
here gets a little "sick," and I was wondering if somebody in this group
could perhaps shed some light on the problem. What happens is that the
dialin lines become unusable. One can connect, but characters don't seem to
get through to the machine. Some do (they are echoed), and sometimes it is
possible to actually login by blindly typing a username/password, each
terminated with CTRL-J (the newline key doesn't work). A reboot always
fixes the problem, but if someone is not around to reboot for a day or
two, there are problems, since this machine polls for news each night,
and news gets backed up at the feed. Thanks.
--
Dominick Samperi, Manhattan College, NYC
manhat!samperi@NYU.EDU ihnp4!rutgers!nyu.edu!manhat!samperi
philabs!cmcl2!manhat!samperi ihnp4!rutgers!hombre!samperi
(^ that's an ell) uunet!swlabs!mancol!samperipaddock@mybest.UUCP (Steve Paddock) (05/15/88)
In article <383@mancol.UUCP> samperi@mancol.UUCP (Dominick Samperi) writes: >Every once in a while (perhaps once per month) a 3b2/300 that we are using >here gets a little "sick," .... What happens is that the >dialin lines become unusable. One can connect, but characters don't seem to >get through to the machine. Some do (they are echoed), and sometimes it is >possible to actually login by blindly typing a username/password, each >terminated with CTRL-J (the newline key doesn't work). A reboot always >fixes the problem, but if someone is not around to reboot for a day or >two, there are problems, since this machine polls for news each night, >and news gets backed up at the feed. Thanks. You forgot to mention release number, which can be important. If it is 2.0, you might try the ports-hang fix from the Hotline. It could also be the high PID count bug. There is a fix for 2.0.4, and it is finally fixed in one of the 3.n releases, but there was a documented bug, finally proven, that the system began to ignore ports as the process id numbers approached rollover at 32K. Part of why this took so long to find and fix was that the common solution (which you might try) was to put shutdown -y -g0 -i6 in crontab each night. I've also seen similar symptoms in the getty wars problem where a modem and port (or a direct link) are echoing login: login: back to one another. Good luck... This can be solved once you find the particular cause at your site. -- ------------------------------------------------------------------------------ Steve Paddock ut-emx!mybest!paddock or uunet!bigtex!mybest!paddock