Most people suggested to restart
inetd because this proccess was killed
when the system try to free up some space.
This was not possible as I could not log in.
(no network connection of course and
the console didn't allow to log in too).
Sean (sean_at_stat.Duke.EDU) suggested to hook
up a serial terminal and try to get a prompt.
This would have been the only way to actually get
a prompt but I couldn't try because we didn't
have everything here and I was pressed for time.
Finally we had to do a hard reboot.
Thanks to:
sean_at_stat.Duke.EDU
Caprica7_at_aol.com
becker_at_eurocontrol.de1
tom_at_radar.tu-graz.ac.at
lawallace_at_escocorp.com
garry_at_pp.nsw.gov.au
matth_at_itsa.ucsf.edu
hank.lee_at_vta.org
ggallen_at_slackinc.com
Davis_at_Tessco.Com
stevev_at_hexadecimal.uoregon.edu
Vito_Munoz_Jr_at_sabre.com
Original message
I am facing a strange problem. I cannnot
connect to my DU box. Telnet tells me:
"telnet: Unable to connect to remote host:
Connection refused". The same thing happens
when trying to use rlogin or remsh/rsh.
The console is just a black screen although
the green monitor light is on.
This happened after the machine ran out of
swap space. It had two fairly large jobs
(2*91MB) and a debugger running (256 Mb
of memory and 512 Mb swap, set to lazy).
Due to reasons I don't really understand
the debugger job grew enormously so that
the machine ran out of swap space. Anyway
the machine still lives, I can ping it but it is
fairly useless.
Any suggestions other than hard rebooting??
Will summarize
Setup: DU 4.0D, LX board 533MHz 2Mb cache,
256 Mb Ram, 512Mb swap space.
--
Christian Hasse
Institut fuer Technische Mechanik
RWTH Aachen
http://www.itm.rwth-aachen.de/staff/hasse/Christian.Hasse.html
Received on Thu Feb 04 1999 - 18:23:00 NZDT