Thanks to everyone who responded.
HP Called back, and we tried the normal -- CTRLQ, CTRL-S, CTRL-A, etc, with
no luck. HP Even had me configure the secondar Lan GSP port and telnet in to
that to try to do a CTRL-A, but that didn't work either. So, tonight after
our backup, HP wants us to do a CTRL-B RS, and power cycle the N-class box
-- pull all the plugs to make sure the GSP fully resets. Hopefully that'll
solve it.
BTW, Art, we're on 7.0 exp 1, so I don't know if the patch you suggested
applies to us, but I'll follow up on it. thx
Thanks for all the suggestions.
John MacLerran wrote:
> Hi HP-3000-L members,
>
> A situation has come up on our new N4000 200/440 that has me stumped.
>
> We have a hung console. Here's the scoop.
> The operator was doing a showjob and hit the escape key to try to stop
> the screen listing (on the 900 series console, the STOP key is where the
> escape key now is, so it's habit). This resulted in a keyboard lock.
> The only way we've been able to clear the keyboard lock previously was
> to power-cycle the console, which the operator did. That resulted in a
> hung session logged in as operator.sys.
>
> We did an abortjob on the session, an abortio on ldev 20, and even
> attempted TERMDSM and Abortcon (neither worked, because the console is
> not on a DTC nor is it on a lan). A showproc for the hung session shows
> that the process is at CS 150, and is getting no CPU time.
>
> SOS shows that the process is in a 'Terminal Write' wait state, whatever
> that is.
>
> I have an open call with the response center, and they've had me reset
> the console terminal to default configs and power cycle it again, to no
> avail. We can do a CTRL-B and get to the GSP on the console, so it
> doesn't seem to be a hung port or terminal hardware failure.
>
> HP has suggested we restart the system, and I concur -- we were going to
> anyway, because I had made some changes to spooled printing and wanted
> to do a start norecovery to get those changes permanently into the
> configs. However, we cannot do a CTRL-A from a session that is not the
> master console, so we're faced with an ungraceful shutdown.
>
> What is the protocol for doing such a shutdown? Our normal backup
> procedures are to get everyone off the system, abort the background
> jobs, bring down network services, stop the spoolers, then do our
> backup. Once the backup is finished, can we just do a CTRL-B RS, or do
> we need to do something additional to safeguard the system.
>
> Any guidance would be most helpful.
> Thanks!
> --
> ----------------------------------------------------------------------
> John MacLerran
> IT Systems Analyst email: [log in to unmask]
> Idaho State University V(208) 282-2954
> http://www.isu.edu/~macljohn F(208) 282-3673
> ----------------------------------------------------------------------
--
----------------------------------------------------------------------
John MacLerran
IT Systems Analyst email: [log in to unmask]
Idaho State University V(208) 282-2954
http://www.isu.edu/~macljohn F(208) 282-3673
----------------------------------------------------------------------
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
