From: Mathias Schmassmann (mschassm@dallasisd.org)
Date: Thu Jun 30 2005 - 10:41:19 EDT
Dr. Thomas Blinn found my problem. His suggestion was:
"If you can telnet into the GS160, look for a logged in session that's
using /dev/tty00 and/or /dev/console (which if you have a serial console
is /dev/tty00)."
I checked it and there were two sessions using /dev/console:
operator 939949 524289 0.0 Jun 24 console 0:00.55 -ksh
(ksh)
operator 967931 939949 0.0 Jun 27 console 0:00.30 vi
/tmp/sh939949.Ccq0DmcI
After I killed these two processes, I could connect again from the
ConsoleWorks station.
Thanks for the helpful answer.
Mathias
>>> Mathias Schmassmann <mschassm@dallasisd.org> 6/30/2005 8:23:38 AM
>>>
This is a question about a problem with a connection from a
ConsoleWorks station (Windows NT) to a DEC terminal server connecting to
a serial port on a GS160 running Tru64 version 5.1B patch kit 3.
The connection from the ConsoleWorks station to the DEC terminal server
is okay. I can query the ports on the terminal server from the
ConsoleWorks station. However, the connection between the terminal
server and the serial port on the GS160 seems to be the problem.
When I try to connect to the GS160 I get these messages:
Trying localhost 5156 *
Sending authentication information *
Connected to localhost.
CONSOLE_MANAGER connecting to console CONSOLE_1 with write access
Here the process stops and nothing happens anymore.
The GS160 as system is up and running. It's a production Oracle
database server. Network connections are fine. The applications are up
and working fine. This is a 24/7 system. This system is running for
weeks and the ConsoleWorks application was okay until a few days ago.
There was no extraordinary event (i.e. power failure).
Is there a utility with Tru64 on the GS160 with which I can check the
serial port status on the GS160?
Thanks.
Mathias
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:20 EDT