| 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 |
My customer experienced a crash of the Console control process.
He has the following questions:
- Why did he get an Opcom message indicating success?
- What is the meaning of the following entry in the logfile?
"CMHostControlErrorCB: code = -196, error_code = 0"
- Is ECO4 an official ECO, if yes, why is it not available in TIMA?
He would also like to have time stamps next to each entry in the
logfile.
Extract from Operator.log
--------------------------
%%%%%%%%%%% OPCOM 16-APR-1997 11:31:13.45 %%%%%%%%%%%
Message from user PCM$MANAGER on BPOLY1
POLYCENTER Console Manager - Version V1.6-201
Console Controller Daemon : Child controller (index = 5) exited with success
Controller logfile
---------------------
$ if f$mode().eqs."INTERACTIVE" then set noverify
$ if f$mode().nes."INTERACTIVE" then exit
$ !
$ ! Start a Child Controller process, name_num 5, child_num 5
$ !
$ CHILD :== $CONSOLE$IMAGE:CONSOLE$DAEMON.EXE
$ CHILD "child" 5
POLYCENTER Console Manager
Console Controller Daemon Version V1.6-201
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_LPOLY1
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_MEGABOX_1
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_MEGABOX_2
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_MEGABOX_3
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_MEGABOX_4
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_PBRG1
CMHostControlErrorCB: code = -196, error_code = 0
Read error on Local socket CONSOLE_CTRL_PBRG2
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC
=000721D0, PS=0000001B
Improperly handled condition, image exit forced.
Signal arguments: Number = 00000005
Name = 0000000C
00000000
00000000
000721D0
0000001B
Register dump:
R0 = 0000000000000007 R1 = 0000000000184758 R2 = 0000000000015E90
R3 = 00000000001BD450 R4 = 00000000000301F0 R5 = 0000000000000000
R6 = 0000000000000000 R7 = 0000000000000000 R8 = 00000000001DB3F0
R9 = 000000007FF9C400 R10 = 000000007FF9D228 R11 = 000000007FFBE3E0
R12 = 0000000000000000 R13 = 000000007EF0C900 R14 = 0000000000000000
R15 = 000000007EF0BDA0 R16 = 00000000001BD450 R17 = 0000000000000200
R18 = 05129E7A001BC2E0 R19 = 000000007F0A27C8 R20 = 0000000077770000
R21 = 0000000000000000 R22 = 0000003147524250 R23 = 00000000001BD525
R24 = F00D000000000000 R25 = 0000000000000003 R26 = FFFFFFFF80619B48
R27 = 000000007F3E0760 R28 = 00000000000000FF R29 = 000000007EE77740
SP = 000000007EE776E0 PC = 00000000000721D0 PS = 200000000000001B
PCM$MANAGER job terminated at 16-APR-1997 11:31:13.37
Is this type of crash fixed by ECO4?
Thanks for your help,
Joerg
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1522.1 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Fri Apr 18 1997 12:48 | 67 | |
>My customer experienced a crash of the Console control process.
>He has the following questions:
> - Why did he get an Opcom message indicating success?
Clearly the code didn't do the right thing.
> - What is the meaning of the following entry in the logfile?
> "CMHostControlErrorCB: code = -196, error_code = 0"
This can happen when the controller reads from a socket and the write
has gone away. You can induce this message when you use the Motif
Window Manager menu's and Close a DECTerm that had CONNECT/MONITOR
running in it.
> - Is ECO4 an official ECO, if yes, why is it not available in TIMA?
Yes, it is. It's not in TIMA becuase CA now owns the product and TIMA
is for Digital product ECO's.
>He would also like to have time stamps next to each entry in the
>logfile.
The code doesn't flush include time-stamps but this has been suggested
as an enhancement.
>Controller logfile
>---------------------
>
>$ if f$mode().eqs."INTERACTIVE" then set noverify
>$ if f$mode().nes."INTERACTIVE" then exit
>$ !
>$ ! Start a Child Controller process, name_num 5, child_num 5
>%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC
>=000721D0, PS=0000001B
> Improperly handled condition, image exit forced.
> Signal arguments: Number = 00000005
> Name = 0000000C
> 00000000
> 00000000
> 000721D0
> 0000001B
>
> Register dump:
> R0 = 0000000000000007 R1 = 0000000000184758 R2 = 0000000000015E90
> R3 = 00000000001BD450 R4 = 00000000000301F0 R5 = 0000000000000000
> R6 = 0000000000000000 R7 = 0000000000000000 R8 = 00000000001DB3F0
> R9 = 000000007FF9C400 R10 = 000000007FF9D228 R11 = 000000007FFBE3E0
> R12 = 0000000000000000 R13 = 000000007EF0C900 R14 = 0000000000000000
> R15 = 000000007EF0BDA0 R16 = 00000000001BD450 R17 = 0000000000000200
> R18 = 05129E7A001BC2E0 R19 = 000000007F0A27C8 R20 = 0000000077770000
> R21 = 0000000000000000 R22 = 0000003147524250 R23 = 00000000001BD525
> R24 = F00D000000000000 R25 = 0000000000000003 R26 = FFFFFFFF80619B48
> R27 = 000000007F3E0760 R28 = 00000000000000FF R29 = 000000007EE77740
> SP = 000000007EE776E0 PC = 00000000000721D0 PS = 200000000000001B
> PCM$MANAGER job terminated at 16-APR-1997 11:31:13.37
>
>
>Is this type of crash fixed by ECO4?
There is a very good chance. Your going to need to put it on anyway
as we don't escalate against ECO 2 (V1.6-201) anymore. There are
several lin controller crashes fixed since ECO 2.
REGS,
Dan
| |||||