Newbie Question on console escape sequence

[Chuck Ciesinski]

To all,

On the console, the prompt does not respond after someone entereed an escape sequence. The only response is from the 'BREAK' key and the prompt just moves diagonally across the screen. Entering CNTL B and then going back to CO does not free up the console. Is there another sequence in HP-UX to free up the console. /etc/shutdown is NOT an option at this time.

HP-UX Newbie,

Chuck Ciesinski

[Steven E. Protter]

Reset the console itself.

If its a web console, simply shutdown the power to the web console itself.

If its a serial console, turn of the power, bring it up holding down the ctrl-shift-D keys simultaneously. Hold for a good 30 seconds, release and the device should come up in default mode.

SEP

[Chuck Ciesinski]

Steven,

Yep, the console cam back in 'DEFAULT' mode and then prompted for me to enter to continue. After entering, the problem condition continued. The prompt only responds to a break key and each time, it drops down a line and shifts over to the rightr making up the diagonal pattern.

Chuck

[Kent Ostby]

Chuck --

Turn the monitor off.

Hold down the "d" key.

Turn the monitor on while holding the "d" key down.

Count to 8 (really)

You should get a message that says "Default Configs Used Press Return to clear".

Do this and it should be clear.

[Chuck Ciesinski]

Kent,

We tried that too. Still no change in the behavior of the system console terminal.

Chuck

[Rita C Workman]

Hello Chuck,

I'm at home...so no console to look at.
But once, somebody went hitting some things on one of our consoles so it seemed 'stuck'.
I reset it as the others mention, but still stuck.
I looked at the console on another server and noticed that those function options (those 8 boxes at the bottom) weren't EXACTLY the same. By simply hitting the PF keys that were different - it turned back on what got switched.

Just a thought...may not apply in your case, but what the heck....now back to paying bills.

Rgrds,
Rita

[Hoang Chi Cong_1 · Accepted solution]

Hi Chuck Ciesinski

In normal case, if you logout the console then the next time you have login again.
When exit, the out put like this:
GSP> exit


EX

EX command was initiated by the LAN Port (IP: 10.0.95.18).
That port will be disconnected, and all other users will return
to the Console.

Confirm? (Y/[N]): y
y

Disconnecting LAN port ...

When you connect again, the out put like this:
Service Processor login: admin
Service Processor password:




Hewlett-Packard Guardian Service Processor

(c) Copyright Hewlett-Packard Company 1999-2001. All Rights Reserved.

System Name: IPCASPAGSP



[Read only - use ^Ecf for console write access.]

[Read only - use ^Ecf for console write access.]
You need to press Ctrl+Shift+e+c+f then the out put like this:
[bumped user - ]


GenericSysName [HP Release B.11.11] (see /etc/issue)
Console Login:

This time, you can hit the Ctrl+b and you can login the console as well:
Leaving Console Mode - you may lose write access.
When Console Mode returns, type ^Ecf to get console write access.

GSP Host Name: IPCASPAGSP
GSP>

If you can not login, it seem that the console had a problem.
Need to reset the GSP console and configure again!

Hope this helps
HoangChiCong

[Steve Lewis]

Having reset the console to defaults without any change it appears that the HP-UX session thinks the terminal is acting in another way.

So with that in mind is this just a simple case of needing to type (in HP-UX console mode)

reset [ctrl-j]

or

stty sane [ctrl-j]

?

[Hoang Chi Cong_1]

To reset withow press "Reset" button of GSP card, try to execute this command when logged in as root in the console:

# stty +resetGSP < /dev/GSPdiag1


Regard,
HoangChiCong

[Kent Ostby]

Chuck --

If you are still having problems after doing the hard reset of the console that I mentioned above, then it's not a HW issue, it's SW.

Do the following from another login:

ps -ef | grep console

Then kill this process with "kill " where is the first number after the user ID


EXAMPLE:

ps -ef | grep console
root 2000 1 0 Feb 17 console 0:00 /usr/sbin/getty console console

So I would do :

kill 2000

[Chuck Ciesinski]

To All,

Thank you for the great responses. We ended up doing the last suggestion from Kent, which was to kill the console session and that worked. Onto other things.

Wishing everyone a wonderful 'Spring Forward!'

Chuck

[Bill Hassell]

I've seen this happen when someone accidently lists a binary file (like an executable) on an HP console. Within a few seconds, the console and the shell get all sorts of crazy sequences and getting a normal prompt back is very difficult because so many things get changed. Killing the console login session (and any other session in a similar state) is the best way to fix the problem.

[Paul Cross_1]

I've seen that too Bill. On a few occasions, with both hp-ux and solaris I have been able to execute the exact same command and reverse the problem. IE: send the same escape sequence.
This is difficult if not impossible if you don't have command history enabled, as you can't see what you typed previously.