Hi Johan,
Thanks for the information on the startsess command. I'll try that next time
this happens.
What the RC had us do was to completely power down the system after issuing the
RS command. They had us switch the power off, and un-plug the 3 power cables in
the back of the box. This last step is important, because the GSP retains power
even if the front panel switch is off. In order to fully reset the GSP, the
power has to be completely off.
We did that as part of our weekly maintenance cycle, and, so far, it has seemed
to solve the problem.
Thanks again.
Beghein Johan wrote:
> Hi John,
>
> I have the same problem on my system (N4000-100-330) for a week now.
>
> The problem wam up when pressing the 'Break' key during a showout sp.
>
> The console hangs, and takes a lot of cpu. Sometimes it's enough to press
> only the break key to hang the console.
>
> Since I have the problem for a week, I moved the console on another
> terminal, also logged as operator.sys, where there is no trouble.
>
> I can 'unlock' the console by aborting the operator.sys session, on it, or
> try the following:
>
> - abortio 20
> or
> - go into GSP, and return to console mode
>
> - startsess 20;operator.sys
>
> Until now, I had only to do a 'RS' once, the other times, I could unlock the
> console.
>
> This week-end, a did a reboot of my system ( here also it was difficult to
> get the '=' prompt, I had to type it twice ), and after the reboot,
> everything was ok for a few hours, and than the problem reoccured.
>
> I have an open call at the RC for a week, but they can't reproduce the
> problem.
>
> I let you know if I have additional information.
>
> Regards,
>
> Beghein Johan
> [log in to unmask]
> John MacLerran <[log in to unmask]> a écrit dans le message :
> 3C11385B.997E1C3D@isu.edu...
> > 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 *
|
