[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

1202.0. "PCM 1.6-111 and ACCVIO in controller process" by 42441::ROOME () Wed Feb 14 1996 05:43

 PCM 1.6+NSI_111
 VAX VMS 6.1
 LAT CONNECTIONS

 Dear All,

 I currently have a customer who is experiencing intermittent controller 
process crashes. I've included the crash details captured in the 
controller log file. Its worth noting that the crash, leaves 4 out the 
16 LTA devices still active on the system. The customer then has to delete 
the ports manually before the new controller process will start correctly.

 Does anyone know what is causing the crash ?

 Is the crash fixed in PCM_127_VAX61.BCK - unfortunately there 
are no release notes that would give me a clue ?

 Look forward to your response

 Martin Roome 
 VMS Specialist
 CSC Basingstoke.



$ SET NOON
$!==============================================================================
$!                 
$! NEW VERSION OF THIS PROCEDURE CREATED.  PRM.   9-Dec-1994
$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$ IF (F$MODE() .NES. "INTERACTIVE") THEN GOTO LBL_NONINTER
$LBL_NONINTER:
$! Non-interactive-mode commands only in this section
$!
$ WRITE SYS$OUTPUT "Time now is 11-FEB-1996 03:05:55.90"
Time now is 11-FEB-1996 03:05:55.90
$!
$!------------------------------------------------------------------------------
$LBL_ALL_MODES:
$! Commands in this section executed in all modes of login
$!
$ EXIT
$ !
$ ! Start a Child Controller process, name_num 2, child_num 2
$ !
$ CHILD :== $CONSOLE$IMAGE:CONSOLE$DAEMON.EXE
$ CHILD "child" 2
POLYCENTER Console Manager
Console Controller Daemon Version V1.6-110
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved

CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_DVCR01 
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_DVCR01 
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_EMF_C 
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_EMF_E 
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_GMXA_ALARMS 
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_FOZZY 
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000006C, PC
=0002F656, PSL=03C00004

  Improperly handled condition, image exit forced.

 Signal arguments       Stack contents

 Number = 00000005   00000000
 Name   = 0000000C   00000001
   00000000   00000000
   0000006C   207C0000
   0002F656   7FEA0B44
   03C00004   7FEA0B24
      00025D1C
      0012AA20
      FFFFFF3C
      00001488

 Register dump

 R0 = 00000000  R1 = 00000000  R2 = 00000000  R3 = FFFFFF3C
 R4 = 00000000  R5 = 00000CD4  R6 = 7FEA0918  R7 = 00000001
 R8 = 7FFECA48  R9 = 7FFECC50  R10= 7FFED7D4  R11= 7FFE2BDC
 AP = 7FEA08A8  FP = 7FEA0868  SP = 7FEA08E4  PC = 0002F656
 PSL= 03C00004

  SYSTEM       job terminated at 13-FEB-1996 17:22:07.91
    Accounting information:
  Buffered I/O count:         1485982         Peak working set size:    2904
  Direct I/O count:            162721         Peak page file size:      7869
  Page faults:                   6239         Mounted volumes:             0
  Charged CPU time:           0 00:37:25.46   Elapsed time:     2 14:16:12.39

T.RTitleUserPersonal
Name
DateLines
1202.1update please?42326::NICHOLSONACSC/UK 7833 3105Mon Mar 18 1996 11:4710
    
      I still have this call open with this customer. The problem with the 
    controller process access violating was originally very intermittent
    problem but for the customer still worrying. Is it possible to get an
    answer to the original note, or at least a pointer to some release
    notes which would least tell me if a problem has been documented.
    
    Many thanks
    Avril Nicholson
    
1202.2CSC32::BUTTERWORTHGun Control is a steady hand.Wed Mar 20 1996 14:285
    As of this writing the ECO 2 kit has no known problems with the
    controller processes crashing including your footprint.
    
    Regs,
       Dan