[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

580.0. "EXTRACT gives ACCESS VIOLATION" by BACHUS::WILLEMSG (Geert Willems MCS-Belgium) Thu Jan 26 1995 13:56


	Hi PCM engineering,

	OpenVMS VAX V6.1,PCM V1.5 + latest MUP installed.
	A customer has problems with the EXTRACT utility.
	He receives an access violation.

$ console extract arch01/since=today/out=arch01.gvh
POLYCENTER Console Manager
Extract facility Version V1.5-006
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved


Working ...
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00383600, PC
=00071CAC, PSL=0BC00004

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                00000000
                 00000000                2FFC0000
                 00383600                7FEE7D04
                 00071CAC                7FEE7CD4
                 0BC00004                00087E49
                                         00000001
                                         00000001
                                         003557D8
                                         00000001
                                         00000001
                                         003557D8
                                         00000001

        Register dump

        R0 = 05A054BD  R1 = 00379298  R2 = 0000F825  R3 = 003748A0
        R4 = 00000000  R5 = 000000CA  R6 = 003748A0  R7 = 003557D8
        R8 = FFFFF825  R9 = 7FEE7CC0  R10= FFFFF825  R11= 00000000
        AP = 7FEE7C40  FP = 7FEE7C00  SP = 7FEE7C7C  PC = 00071CAC
        PSL= 0BC00004


	This happens on one system only. Specify /before=yesterday
	gives no problem. I presume that there is some kind of
	corruption in his 'node'.log and/or 'node'.events and/or
	'node'.times file(s) ? The only thing that happened this
	night was that the disk was filling up. Another system was
	sending messages the whole night(logfile > 56000 blocks).
	Can this produce such a problem ?




----------------------------------------------------------------------------

	I did some further testing on my PCM system.
	OpenVMS VAX V6.0, PCM V1.5 + latest MUP installed.
	I tried to test the EXTRACT utility from the GUI for BRSDVP
	and I've got also an access violation 

POLYCENTER Console Manager
Extract facility Version V1.5-006
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved


Working ... done.
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=7365635C,PC
=0003EA88, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                0000001D
        Name   = 0000000C                00000000
                 00000001                200C0000
                 7365635C                7FEDEBF4
                 0003EA88                7FEDEBE0
                 03C00000                0007126B
                                         0034AE48
                                         0007125C
                                         00000001
                                         73656363

        Register dump

        R0 = 73656353  R1 = 00000001  R2 = 0034AE48  R3 = 00057008
        R4 = 0031E780  R5 = 00000000  R6 = 00000001  R7 = 00000000
        R8 = 00000000  R9 = 00000000  R10= 7FFED7D4  R11= 00000000
        AP = 7FEDEB78  FP = 7FEDEB38  SP = 7FEDEBB4  PC = 0003EA88
        PSL= 03C00000

	
        I specified another /since='some time yesterday' and then
	it went fine ...
POLYCENTER Console Manager
Extract facility Version V1.5-006
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved


Working ... done.



	I did an analyze/rms on the 'node'.log, .events, .times files
	and indeed there are error.
$ana/rms CONSOLE$ROOT:[LOG]BRSDVP.events
Check RMS File Integrity                     26-JAN-1995 14:41:26.52   Page 1
CONSOLE$ROOT:[LOG]BRSDVP.EVENTS;1


FILE HEADER

        File Spec: CONSOLE$ROOT:[LOG]BRSDVP.EVENTS;1
        Global Buffer Count: 0
...
***  VBN 23:  Last stream record does not contain a delimiter.
Unrecoverable error encountered in structure of file.

$ ana/rms CONSOLE$ROOT:[LOG]BRSDVP.times
Check RMS File Integrity                     26-JAN-1995 14:42:47.12   Page 1
CONSOLE$ROOT:[LOG]BRSDVP.TIMES;1


FILE HEADER

        File Spec: CONSOLE$ROOT:[LOG]BRSDVP.TIMES;1
...
        Global Buffer Count: 0
***  VBN 10056:  Last stream record does not contain a delimiter.
Unrecoverable error encountered in structure of file.

$ ana/rms CONSOLE$ROOT:[LOG]BRSDVP.log -->no errors


	I tried to convert these files(.events and .times), but than
	my monitor session is access violating.



	Engineering, is this a known problem ? What can we do about it ?
	Stop PCM and delete these 3 files ?
	What produced this access violation ?

	Any help is welcome.

	Thanks in advance.


	Geert

PS	I you want to take a closer look, you can always login at my
	system if want. Just send me a mail.
T.RTitleUserPersonal
Name
DateLines
580.1CSC32::BUTTERWORTHGun Control is a steady hand.Thu Jan 26 1995 21:2027
    Geert,
       The ACCVIO PC's listed in -1 are within an RTL routine and not the
    EXTRACT image. This is also the case of the frame contained in the
    stack dump. The point is we cannot tell what caused the ACCVIO with 
    only what we have in the stack dumps. Since you can reproduce it
    here's what I suggest you do:
    
    $ INSTALL REMOVE CONSOLE$IMAGE:CONSOLE$EXTRACT 
    $ SET PROC/DUMP
    $ CONS EXTRACT blah-blah
    
    When it ACCVIO'S you should have CONSOLE$EXTRACT.DMP in your current
    directory. We can then analyze this dump.
    
    I do suggest that you rename the PCM logfiles and restart the product.
    It is possible the ACCVIO is caused by a pre-MUP problem having to do 
    with a bug found in the controller daemon that in effect causes
    "logical" corruption in the logfiles. The problem with the daemon
    has been fixed but if you still have a logifle with corruption it could
    cause some other problems.
    
    I wouldn't worry about the RMS error right now as I have found this
    common to all PCM systems. I have a feeling it has to do with the way
    PCM flushes records. I see this on systems that have had PCM shutdown
    normally. I have yet to link a problem to it - of course you could
    have uncovered something finally. The dump will tell us what we need to
    know.
580.2CONSOLE$EXTRACT.DMPBACHUS::WILLEMSGGeert Willems MCS-BelgiumFri Jan 27 1995 12:4518
    
    
    Hi Dan,
    
    
    I can't simulate it anymore on my system. So, I contacted the 
    customer, because he still can simulate it. I have copied the
    CONSOLE$EXTRACT.DMP to BRSDVP""::CONSOLE$EXTRACT.DMP .
    
    Can I conclude that (to be sure) I can advise to every customer
    to start a CONSOLE ARCHIVE for all systems, stop PCM, delete the
    'node'.log,.events,.times and restart PCM. 
    
    Thanks for your help.
    
    Rgds,
    
    Geert
580.3Do we get a prize for two?PCBOOT::HUGHESASwimming against the tide @#%*Fri Jan 27 1995 12:4838
    
    Gentlemen,
    
    	I also have an access violation on extract, but with a different
    	PC. I am running PCM v1.5 MUP A on OpenVMS v6.1 (VAX).
    
    Andy.
    
ITOCK>cons extrac tokens/sin=26-jan-1995:16:30   <--- command used
    
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=005EC02C, PC
=0003EA88, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                00000000
                 00000001                200C0000
                 005EC02C                7FE46BF4
                 0003EA88                7FE46BE0
                 03C00000                00078033
                                         003B6AD8
                                         00078024
                                         00000001
                                         005EC033

        Register dump

        R0 = 005EC023  R1 = 00000001  R2 = 003B6AD8  R3 = 0005B408
        R4 = 00368DB0  R5 = 00000000  R6 = 00000001  R7 = 00000001
        R8 = 00000000  R9 = 00000000  R10= 7FFED7D4  R11= 00000000
        AP = 7FE46B78  FP = 7FE46B38  SP = 7FE46BB4  PC = 0003EA88
        PSL= 03C00000

ITOCK>