Conference csc32::consolemanager

1358.0. "Console locked when connection window vanishes" by WOTVAX::DAVIESG (I had too much to dream last night) Fri Aug 16 1996 04:42

    Following an office move, I reconnected my system management
    workstation and the systems whose consoles I monitor through PCM. After
    the initial problems, I got back a C3 display which showed all the
    systems as up and manageable. However, when I attempt to do console
    connect to one system (the others work), the following happens...
    
    1. Reboot system management workstation
    
    2. Start PCM (I do this through OSCint)
    
    3. Get PCM C3 display on screen
    
    4. Select remote system (in this case its a Digital Unix 3.2d Alpha
    DEC 3000) and with right hand mouse button, click on connect to
    console.
    
    5. Console screen comes up
    
    6. Password prompt appears
    
    7. Console window vanishes
    
    8. Console to remote system remains locked (little green square over
    its icon)
    
    9. Unlock console through GUI
    
    10. Attempt to reconnect to console, but get following error...
    
    System is currently locked by root. Use Monitor Interface
    
    11. Reset and reconfigure options do not cure this.
    
    12. Reboot system and go through whole proceedure again.
    
    It would appear that the console connection which vanishes (the window,
    that is) is the one that is locking the console. There is no process
    associated with this window once it vanishes. No other system has this
    problem.
    
    The system management system is an Alpha Server 1000, running Digital
    Unix 3.2d. The following event messages are logged when you start up
    the manager node relating to the remote system. The remote system is
    called "gasaxp", all of these appear in the multi-line window.
    
    gasaxp	Fri Aug 16 11:24:55 CMgr Archive Started Starting archive
    procedure for system gasaxp
    gasaxp	Fri Aug 16 11:24:55 CMgr Archive Aborted Archive aborted -
    user root is connected
    
    This is console manager v1.6. I had no problems before the office move.
    Although there are other notes reporting locking of archiving (394 &
    1244) they do not appear to be the same problem as this (plus they're
    on VMS!). What is going on, I'm currently baffled. Any ideas
    appreciated.
    
    Console related processes on manager node...
    
    692 ??	I	 0:00.12 consoled
    700 ??	S	 0:00:12 console_ensd
    807 ??	I	 0:00:01 sh -c /usr/bin/X11/dxconsole
    809 ??	I	 0:00.20 /usr/bin/X11/dxconsole
    914 ??	I	 0:00.70 /var/opt/console/actions/console_eventlist
    warloc
    796 console I  +	 0:00.08 /usr/sbin/getty console console vt100
    820 ttyp1	S  +	 o:oo.89 /usr/opt/DCR160/bin/OSF/console_c3
    
    on remote system...
    
    381 ??	I 	 0:00.01 sh -c /usr/bin/X11/dxconsole
    383 ??	I	 0:00.22 /usr/bin/X111/dxconsole
    398 console I  +	 0:00.03 /usr/sbin/getty console console vt100
    
    ...lastly monitor interface just shows a blank screen for the remote
    system.
    
    Thanks in advance
    
    Guy

    Ok, put another system onto this segment and get exactly the same
    problem. This time its a VAX/VMS system. The same thing happens initial
    connection goes through, window vanishes, system becomes locked. PCM
    can no longer connect to any of the working systems. Looks like a
    faulty segment screwing up PCM functionality. I'm going to swap out as
    much of the network connectivity I can and try again!
    
    Guy

    Well, its not the network segment. So its back to PCM, has anyone seen
    something like this before?
    
    Guy

    Now none of my consoles work?!?!
    
    On starting up PCM, the multi-line window appears, you then attempt to
    connect to a system. The console window appears, press return on this
    and the login propmt appears then the window vanishes and the console
    is locked, no further connections can be made to other consoles. I've
    checked all the log files and can't see any pointers. What on earth is
    going on?!?!
    
    The multi-line window recognises the initial connection but reports no
    further events!
    
    Guy

    OK, although I can't identify what was corrupted or why it manifested
    itself in the way it did, the problem was all down to LAT.
    
    I reinstalled LAT on the management node and rebooted, suddennly
    everything works again! No pointers from LAT as to what the problem
    was, my configuration and services remain identical?
    
    Guy

    OK,last entry in here about this.
    
    I have identified one Console connection as being the culprit! Having
    reinstalled LAT all my consoles work fine, multiple console opening,
    reboots, the works. Apart from this one. Open up the console connection
    click on the window and low and behold the window vanishes and LAT is
    blown away!?! At the server end there is no difference in lat/PCM
    configuration, at the terminal server end the port looks identical to
    the others in use. I'm baffled and will probably move this console to
    another terminal server port, which will hopefully cure the problem. If
    anyone has any ideas please post them in here.
    
    Guy