| 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 |
Hello!
Our customer has installed pcm v1.6 sbb kit eco1 (same customer on note 879)
and he is experiencing others errors descreibed below.
Mail From customer:
I have been Field Testing V1.6 of PolyCenter Console Manager since June
1995. I have recently installed the V1.6 SSB kit + ECO1. The current
version I am running is V1.6-110. The current problems that I am
experiencing are described in the DSN database article.
[PLY_CM] CONSOLE SHUTDOWN Doesn't Cleanup PCM Processes After a Failure
Last Technical Review: 16-MAY-1995
A CONSOLE SHUTDOWN command does not clean up PCM processes when there
has been any type of failure.
These failures can be :
1) console reconfig - will not complete
2) attempt to use ENS results in access violation of one of the
controller processes
3) just attempting to use a console
This afternoon, a controller Console Ctrl 04 access violated and
exited. A restart of PCM restarts these controller processes but
all consoles controlled by Console Ctrl 04 are disabled or unavailable.
A reboot is required.
Currently, a reboot per day is required and since we have 60 consoles
attached to PCM, this is causing us many problems and I would appreciate
a formulae for correctly resarting PCM that does not require a reboot.
******************* end of mail *************************************
Thanks for any info
Domenico
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 894.1 | 45401::PHILIP | And through the square window... | Thu Jul 27 1995 06:54 | 7 | |
Domenico, If you want this resolved then you will have to formally escalate via IPMT it on behalf of your customer. Cheers, Phil | |||||
| 894.2 | 29067::BUTTERWORTH | Gun Control is a steady hand. | Thu Jul 27 1995 14:52 | 17 | |
Can you post the logfile of the access violation please. Aloso,
assuming that these systems are using LAT as the interconnect do the
following before restarting PCM. You'll need to have some knowledge of
the terminal server names and port names that the nodes are connected
to:
$ mcr latcp sho port
Note the LTA devices that appear to be mapped to terminal servers and
ports being used by PCM. Do a DELETE PORT xxxxx command against each
port and then restart PCM. I'm betting here that the LTA devices are
hung. We put a fix in 1.6 to help handle this situation but it may not
be handling all cases. We really want that accvio as that problem needs
to be dealt with.
REgs,
Dan
| |||||
| 894.3 | lta hung | 49575::LA_GIOIA | We do ...the best | Wed Aug 09 1995 12:15 | 19 |
Hi Dan!
> $ mcr latcp sho port
>
> Note the LTA devices that appear to be mapped to terminal servers and
> ports being used by PCM. Do a DELETE PORT xxxxx command against each
> port and then restart PCM. I'm betting here that the LTA devices are
> hung. We put a fix in 1.6 to help handle this situation but it may not
> be handling all cases. We really want that accvio as that problem needs
> to be dealt with.
You are right the lta devices are hung and deleting the port and
restart pcm, it unlock the port lta.
As our customer is on holidays, I can note post the logfile. I will do
it as soon as possible. If already a fix for this problem is available,
please tell me the pointer.
Thanks a lot
Domenico
| |||||
| 894.4 | 29067::BUTTERWORTH | Gun Control is a steady hand. | Wed Aug 09 1995 14:51 | 7 | |
A fix to handle some issues was put into the ECO kit for 1.6 so that
the connections would drop when the process died. Based on your note it
sounds like the LTA devices were still present after controller 4 dies.
Is this correct?
Regards,
Dan
| |||||
| 894.5 | not really | 49575::LA_GIOIA | We do ...the best | Thu Aug 10 1995 10:46 | 20 |
Dan!
> A fix to handle some issues was put into the ECO kit for 1.6 so that
> the connections would drop when the process died. Based on your note it
> sounds like the LTA devices were still present after controller 4 dies.
> Is this correct?
Not really.
In fact the system manager's backup told me that the process controller
4 (or any other process controller) never die. In a normal situation
this process is in HIB state, and when it drops, it is in LEF state.
Deleting port ltaxxx and restart the pcm the system runs again.
This hang comes intermittently when somebody press ctrl-g.
I have read the note 909 which explain the same problem.
I hope this helps you.
Thanks
Domenico
| |||||
| 894.6 | 29067::BUTTERWORTH | Gun Control is a steady hand. | Fri Aug 11 1995 14:03 | 29 | |
Yes it does. At least I have a clear picture and it isn't the problem
I thought it was. There have been to many reports of this at this
point. Here is what I need to at least try and understand why the code
is hanging:
When the controller hangs do the following SDA> commands:
$ ANA/SYSTEM
SDA> SHO SUMMARY
!find the process that is hung and note it's index number. This is the
2nd column from the left and then do:
SDA>SHO PROC/INDEX=index-number-from-above
SDA> SET OUT CALL_STACK.LOG
SDA>SHO CALL
SDA>SHO CALL/NEXT
Repeat the SHO CALL/NEXT until you get an error and then exit SDA
Send me the CALL_STACK.LOG file.
Thanks,
Dan
P.S. To anyone that has experienced this problem, please do the above
excercise and send me the results!
| |||||
| 894.7 | logfile | 49575::LA_GIOIA | We do ...the best | Mon Sep 04 1995 05:26 | 291 |
Hi Dan!
The customer was on holidays and I get the log only today.
*******************************************************************************
A blocked console put the Ctrl 03 in LEF. Here is the trace information that
you requested.
SDA> sho summ
Current process summary
-----------------------
Extended Indx Process name Username State Pri PCB PHD Wkset
-- PID -- ---- --------------- ----------- ------- --- -------- -------- ------
00000081 0001 SWAPPER HIB 16 83A8C5A0 83A8C400 0
00000085 0005 IPCACP SYSTEM HIB 10 84415E00 8595D800 173
00000086 0006 ERRFMT SYSTEM HIB 8 84418B00 85B06C00 230
00000087 0007 OPCOM SYSTEM HIB 8 843CB580 85BDB600 128
00000088 0008 AUDIT_SERVER AUDIT$SERVER HIB 10 8441A940 85CB0000 845
00000089 0009 JOB_CONTROL SYSTEM HIB 9 8441D480 85D84A00 395
0000008A 000A QUEUE_MANAGER SYSTEM HIB 8 84421000 85E59400 1105
0000008B 000B SECURITY_SERVER SYSTEM HIB 10 8442A640 85F2DE00 1344
00000091 0011 NETACP DECNET HIB 10 84431B00 861ABC00 1064
00000092 0012 EVL DECNET HIB 6 84431040 86002800 373
00000093 0013 SNS$WATCHDOG SYSTEM HIB 5 84456200 86429A00 796
00000096 0016 NSCHED SYSTEM LEF 8 8445E0C0 866A7800 1069
00000099 0019 SCHED_REMOTE SYSTEM LEF 6 84431440 8677C200 643
0000009A 001A REMACP SYSTEM HIB 9 8445FE80 864FE400 87
0000009D 001D SMISERVER SYSTEM HIB 9 8445D640 86280600 541
0000009E 001E UCX$INET_ACP INTERnet HIB 9 84430E40 860D7200 355
000000A1 0021 LATACP SYSTEM HIB 14 8448F940 86850C00 325
Press RETURN for more.
Current process summary
-----------------------
Extended Indx Process name Username State Pri PCB PHD Wkset
-- PID -- ---- --------------- ----------- ------- --- -------- -------- ------
000000A4 0024 DECW$SERVER_0 OPS HIB 6 8440BAC0 869FA000 4226
000000A5 0025 DECW$SESSION OPS LEF 7 844AFD80 865D2E00 3047
000000A6 0026 Console Daemon SYSTEM HIB 6 8449E8C0 85A32200 458
000000A7 0027 Console Notify SYSTEM HIB 6 843DCA80 86355000 735
000000A8 0028 Console Ctrl 01 SYSTEM HIB 6 84431240 86925600 598
000000A9 0029 Console Ctrl 02 SYSTEM HIB 5 8448F280 86ACEA00 540
000000AA 002A Console Ctrl 03 SYSTEM LEF 7 844BBDC0 86BA3400 772
000000AB 002B Console Ctrl 04 SYSTEM HIB 4 844BD400 86C77E00 531
000000AD 002D DECW$MWM OPS LEF 4 8451A8C0 86E21200 2676
000000AF 002F VUE$OPS_3 OPS LEF 5 8451CC80 86FCA600 414
000000B0 0030 VUE$OPS_4 OPS LEF 5 8451D700 8709F000 425
000000B1 0031 DECW$TE_00B1 OPS LEF 6 84459F40 87173A00 5887
000000B2 0032 OPS OPS LEF 7 84519440 86D4C800 351
000000B3 0033 _FTA6: OPS LEF 9 8451EF40 87248400 332
000000BB 003B OPSMGR OPSMGR CUR 10 84441640 873F1800 1242
000000D6 0056 SERVER_0022 OPSMGR LEF 7 8443F300 874C6200 304
000000D7 0057 SERVER_0021 OPSMGR LEF 7 844427C0 86EF5C00 369
SDA> set process/index=2a
SDA> sho call
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB5D88 00000000
SP Align Bits = 00 7FEB5D8C 2FFC0000
Saved AP 7FEB5D90 7FEB5E1C
Saved FP 7FEB5D94 7FEB5DFC
Return PC 7FEB5D98 0002E147
R2 7FEB5D9C 000EFAE8
R3 7FEB5DA0 000E57B8
R4 7FEB5DA4 000011D8 UCB$M_UNLOAD+001D8
R5 7FEB5DA8 00108628
R6 7FEB5DAC 00000000
R7 7FEB5DB0 00000001
R8 7FEB5DB4 7FFECA48
R9 7FEB5DB8 00000CCC SWP$SHELINIT+000CC
R10 7FEB5DBC 7FFED7D4
R11 7FEB5DC0 7FFE2BDC CTL$AG_CLIDATA+00180
Align Stack by 0 Bytes =>
Argument List 7FEB5DC4 0000000C
Press RETURN for more.
Call Frame Information
----------------------
7FEB5DC8 00000031
7FEB5DCC 00000530 BUG$_STATENTSVD
7FEB5DD0 00000030
7FEB5DD4 000EFB48
7FEB5DD8 00000000
7FEB5DDC 00000000
7FEB5DE0 0010990C
7FEB5DE4 00000001
7FEB5DE8 00000000
7FEB5DEC 00000000
7FEB5DF0 00000000
7FEB5DF4 00000000
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB5DFC 00000000
SP Align Bits = 00 7FEB5E00 201C0000
Saved AP 7FEB5E04 7FEB5F68
Saved FP 7FEB5E08 7FEB5F34
Return PC 7FEB5E0C 00025510
R2 7FEB5E10 000F4350
R3 7FEB5E14 000E57B8
R4 7FEB5E18 000011D8 UCB$M_UNLOAD+001D8
Align Stack by 0 Bytes =>
Argument List 7FEB5E1C 00000003
7FEB5E20 000EFAE8
7FEB5E24 0010990C
7FEB5E28 00000001
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB5F34 00000000
SP Align Bits = 00 7FEB5F38 23FC0000
Saved AP 7FEB5F3C 7FEB5FA4
Saved FP 7FEB5F40 7FEB5F88
Return PC 7FEB5F44 0000A72D
R2 7FEB5F48 001E19A0
R3 7FEB5F4C 00109900
R4 7FEB5F50 000011D8 UCB$M_UNLOAD+001D8
R5 7FEB5F54 7FFE5E00 MMG$IMGHDRBUF
R6 7FEB5F58 00000000
R7 7FEB5F5C 00000001
R8 7FEB5F60 7FFECA48
R9 7FEB5F64 7FFECC50
Align Stack by 0 Bytes =>
Argument List 7FEB5F68 00000006
7FEB5F6C 001E19A0
7FEB5F70 00000022
Press RETURN for more.
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB5F88 00000000
SP Align Bits = 00 7FEB5F8C 200C0000
Saved AP 7FEB5F90 7FEB5FD4
Saved FP 7FEB5F94 7FEB5FBC
Return PC 7FEB5F98 000211AB
R2 7FEB5F9C 000011D8 UCB$M_UNLOAD+001D8
R3 7FEB5FA0 00109AF8
Align Stack by 0 Bytes =>
Argument List 7FEB5FA4 00000004
7FEB5FA8 001DF628
7FEB5FAC 00109900
7FEB5FB0 0000000E
7FEB5FB4 001E19A0
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB5FBC 00000000
SP Align Bits = 00 7FEB5FC0 20040000
Saved AP 7FEB5FC4 7FEB6008
Saved FP 7FEB5FC8 7FEB5FE4
Return PC 7FEB5FCC 00015410
R2 7FEB5FD0 000011D8 UCB$M_UNLOAD+001D8
Align Stack by 0 Bytes =>
Argument List 7FEB5FD4 00000002
7FEB5FD8 00109AF8
7FEB5FDC 0010FB38
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB5FE4 00000000
SP Align Bits = 00 7FEB5FE8 203C0000
Saved AP 7FEB5FEC 00109AF8
Saved FP 7FEB5FF0 7FEB6018
Return PC 7FEB5FF4 00015280
R2 7FEB5FF8 000011D8 UCB$M_UNLOAD+001D8
R3 7FEB5FFC 000E5700
R4 7FEB6000 7FEB5F5D
R5 7FEB6004 7FFE5EBC MMG$IMGHDRBUF+000BC
Align Stack by 0 Bytes =>
Argument List 7FEB6008 00000001
7FEB600C 00109AF8
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB6018 00000000
SP Align Bits = 00 7FEB601C 200C0000
Saved AP 7FEB6020 00000000
Saved FP 7FEB6024 7FEB603C
Return PC 7FEB6028 00015112
R2 7FEB602C 0009DB00
R3 7FEB6030 000E57B8
Align Stack by 0 Bytes =>
Argument List 7FEB6034 00000000
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB603C 00000000
SP Align Bits = 00 7FEB6040 20040000
Saved AP 7FEB6044 00000001
Saved FP 7FEB6048 7FEB605C
Return PC 7FEB604C 00014E75
R2 7FEB6050 0009DB80
Align Stack by 0 Bytes =>
Argument List 7FEB6054 00000000
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB605C 00000000
SP Align Bits = 00 7FEB6060 20040000
Saved AP 7FEB6064 000A2F70
Saved FP 7FEB6068 7FEB6190
Return PC 7FEB606C 00004A7D UCB$M_SHD_WLGSTA_CHA+00A7D
R2 7FEB6070 00000000
Align Stack by 0 Bytes =>
Argument List 7FEB6074 00000000
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB6190 000BB71C
SP Align Bits = 00 7FEB6194 2FFC0000
Saved AP 7FEB6198 7FEB61FC
Saved FP 7FEB619C 7FEB61E8
Return PC 7FEB61A0 7FF37FDC
R2 7FEB61A4 0000000F
R3 7FEB61A8 7FF37C73
R4 7FEB61AC 7FFE5E0C MMG$IMGHDRBUF+0000C
R5 7FEB61B0 7FFE5EBC MMG$IMGHDRBUF+000BC
R6 7FEB61B4 00000000
R7 7FEB61B8 00000001
R8 7FEB61BC 7FFECA48
R9 7FEB61C0 7FFECC50
R10 7FEB61C4 7FFED7D4
R11 7FEB61C8 7FFE2BDC CTL$AG_CLIDATA+00180
Align Stack by 0 Bytes =>
Argument List 7FEB61CC 00000006
Press RETURN for more.
Call Frame Information
----------------------
7FEB61D0 7FFE5E3C MMG$IMGHDRBUF+0003C
7FEB61D4 00000000
7FEB61D8 7FFE5E0C MMG$IMGHDRBUF+0000C
7FEB61DC 7FFE5EBC MMG$IMGHDRBUF+000BC
7FEB61E0 010000A8 UCB$M_ALTBSY+000A8
7FEB61E4 00000001
SDA> sho call/next
Call Frame Information
----------------------
Call Frame Generated by CALLS Instruction
Condition Handler 7FEB61E8 80002248 EXE$CATCH_ALL
SP Align Bits = 00 7FEB61EC 20000000
Saved AP 7FEB61F0 00000000
Saved FP 7FEB61F4 00000000
Return PC 7FEB61F8 7FF37F3E
Align Stack by 0 Bytes =>
Argument List 7FEB61FC 00000000
SDA> sho call/next
Call Frame Information
----------------------
SDA> exit
*******************************************************************************
Does this help you?
Thanks
Domenico.
| |||||
| 894.8 | more info | 49575::LA_GIOIA | We do ...the best | Tue Sep 05 1995 09:05 | 38 |
Hello!
This morning I have received others infos from this customer, and I
hope it will help you.
*******************************************************************
Domenico,
I think I understand what causes this problem...
We have a Sparcstation connected to PCM. Attached to the Sparcstation
is a
StorageWorks box containing RZ26 and RZ28 disks. A probe-scsi command
on the Sun
console issues a scsi inquiry command and the RZ28 disk returns a
stream of
bytes....
DEC D41C42751507 and then a hexadecimal 13 which is an XOFF stop
transmission !
(it's byte 54 which contains the hardware revision number) which
"hangs" the
terminal and subsequenly requires a restart of the console manager
software.
I think that this should be passed to Engineering support for PCM and I
would be
interested to hear their reaction.
Thanks Tim
***********************************************************************
Thanks
Domenico
| |||||
| 894.9 | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Tue Sep 05 1995 11:17 | 7 | |
Domenico,
You might be better off posting this in the terminal server notes
file. It's located at TOOK::TERMINAL_SERVERS. It would seem that this
is a setting on the terminal server. Just a guess on my part.
Dave
| |||||
| 894.10 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Wed Sep 06 1995 18:08 | 10 | |
If it really sends the XOFF character and doesn't display it as some
printable interpretation then there is little we can do! We cannot
know if the XOff is erroneous or not. If we ignore it and it's a
legitamate flow control character then by ignoring it we could
overflow the console port's buffer. VCS would have reacted slightly
differently but the net effect would still be a hung port.
Regards,
Dan
| |||||