Conference csc32::consolemanager

1002.0. "Archive: No response from controllre - again." by 42441::ROOME () Mon Sep 25 1995 08:42

 Dear All,

 Following on from Notes entry 946, I currently have a customer with a
similar problem, if anyone from the engineering wishes to dial in, I can
arrange it.

 This is an intermittent problem when archiving, he does this on a daily basis.

 In the batch log file for the process producing the archive he recieves the 
message, this is the ninth node being archived. The problem node is 
WYTV10.

 Archiving log file.

$ if node .nes. "CONSOLEMANAGER" then Console Archive/Keep=24 WYTV10
POLYCENTER Console Manager
Archive facility Version V1.6-110
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved

Starting archive procedure for system WYTV10
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
 Archive: No response from controller Waiting...
    

 The archiving process is in HIB, 

 In the controller log file, you see the following message, however there 
appears to be no issues with the controller, it's possible to connect to the
other nodes that the line controller is monitoring. The LTA device to the 
"problem" node exists and the DECserver sees it has CONNECTED.

SMHW05>ty CONSOLE$ROOT:[TEMP]CONTROLLER_01.LOG;1
$       SET NOVERIFY
POLYCENTER Console Manager
Console Controller Daemon Version V1.6-110
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
.
.
.
.
.
Read error on Local socket CONSOLE_CTRL_HSCC08
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_UICV01
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_WYRS01
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_WYTV10
  
 Niether the archiving process or the controller proces have any channels to
either the archived, TIME, EVENT, or LOG files, or the original TIME, EVENT,
LOG files for the problem node.

 Look forward to your reply.

 Regards 

    Hello,
    
    I have same problem on OSF 3.2 con PCM 1.6. Stopping archiving
    processes we unlock receiving problem on one system.
    
    May be a deadlock on the system log files?
    
    Regards.
    
    Paolo