[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1253.0. "ECO2 problem" by 45769::CLEPHANEB () Tue Mar 26 1996 11:57

    
    I installed ECO2 last week here on customer site and it fixed our long
    outstanding problem. Its been running fine all week but earlier today
    I had to restartup PCM when trying to fix a locked up console
    connection. I have also rebooted the terminal server and have restarted
    PCM several times now. On investigation the logfile for controller 3
    contains the following (I saw something like this in an earlier note on
    Access Violations but not when running on ECO2),
    
    CMHostControlErrorCB: code = -196, error_code = 0
    Read error on Local socket CONSOLE_CTRL_ZEN
    CMHostControlErrorCB: code = -196, error_code = 0
    Read error on Local socket CONSOLE_CTRL_ZEN
    CMHostControlErrorCB: code = -196, error_code = 0
    Read error on Local socket CONSOLE_CTRL_PTZV15
    CMHostControlErrorCB: code = -196, error_code = 0
    Read error on Local socket CONSOLE_CTRL_PTZV15
    CMHostControlErrorCB: code = -196, error_code = 0
    Read error on Local socket CONSOLE_CTRL_PTZV15
    CMHostControlErrorCB: code = -196, error_code = 0
    Read error on Local socket CONSOLE_CTRL_PTZV07
    CMHostControlErrorCB: code = -196, error_code = 0
    Read error on Local socket CONSOLE_CTRL_PTZV07
    CMHostControlErrorCB: code = -196, error_code = 0
    Read error on Local socket CONSOLE_CTRL_PTZV07
    
    We have 38 systems configured over Telnet and Lat.
    
    Any ideas ?
    
    Bruce
    
T.RTitleUserPersonal
Name
DateLines
1253.1CSC32::BUTTERWORTHGun Control is a steady hand.Tue Mar 26 1996 16:449
Bruce,
  You can induce these types of socket errors by closing a decterm that was
running connect/monitor, i.e., you didn't exit conn/mon by using ctrl-e.

Is it just one port that is locked up? is PCM communicating with the other
systems on the same server?

Regs,
  Dan
1253.245769::CLEPHANEBWed Mar 27 1996 06:0613
    
    Dan,
    
    There are 11 systems using this terminal server. 4 of these systems are
    now giving this error. We were working on 1 of the 4 not working for most
    of yesterday when it locked up and have been unable to use it since. I
    will be rebooting this system in the next couple of hours - hopefully this
    will fix it. 
    
    Regards,
    
    Bruce
    
1253.3REBOOT fixed problem45769::CLEPHANEBWed Mar 27 1996 09:3110
    
    Dan,
    
    A reboot of the system running PCM has cleared the problem. PCM came up
    successfully configuring all systems.
    
    Regards,
    
    Bruce