Date: Sat, 4 May 2013 22:04:38 -0400 From: David Riley <fraveydank at gmail.com> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org> Subject: uVAX 3900 out to lunch after inactivity Message-ID: <0315AF5D-BB77-464C-9BD6-FE312DDCE21A at gmail.com> Content-Type: text/plain; charset=us-ascii The long saga of making my recent KA655 acquisition work continues! It's been mostly smooth sailing since I got a decent Plextor drive, but there's one persistent problem. Under VMS 7.3, after a longish period of inactivity (I've seen it after a few hours, but I've not been able to narrow it down beyond that), it seems to just kind of go out to lunch. VMS is still *running*... if I have a Telnet session running MONITOR, the clock will still update and the activity meters still move (a little; they show very little activity, but that's expected since there's not a lot going on on the machine yet). But if I terminate MONITOR (it responds interactively to ctrl-C, etc) and try to run anything else (say, HELP), it stops responding. Other terminals are totally unresponsive. If I try to open a Telnet session, TCP connects but no other traffic happens. This also happens if I turn TCP/IP off. I'm running with 16 MB RAM, which should be enough for a machine that's not really running much yet, and if I were having memory issues I would expect things like existing MONITOR sessions to have serious problems. If anyone has any idea what might be going on here, I'm all ears. I have seen this behavior a number of times when the disk has gone offline for some reason. I'm not sure there is a simple way to tell when the drive can no longer be accessed. Obviously, there will be no error logging of the condition, except that VMS may write some buffered error messages on the next boot that may offer a clue. Jon