[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

1276.0. "ARCHIVE produces ACCVIO" by HANSBC::BACHNER (Mouse not found. Click OK to continue) Tue Apr 23 1996 12:46

PCM V1.6 / OpenVMS

A customer has reported the following problems:

- archiving seems to work, but finishes with a 'failed' message:

Starting archive procedure for system SYSTEM_1
Timefile  Pass 1: Working ... done.
Timefile  Pass 2: Working ... done.
Logfile   Pass 1: Working ... done.
Logfile   Pass 2: Working ... done.
Eventfile Pass 1: Working ... done.
Archive procedure for system SYSTEM_1 failed
Starting archive procedure for system SYSTEM_2
Timefile  Pass 1: Working ... done.
Timefile  Pass 2: Working ... done.
Logfile   Pass 1: Working ... done.
Logfile   Pass 2: Working ... done.
Eventfile Pass 1: Working ... done.
Archive procedure for system SYSTEM_2 failed

I had them increase the processes BYTLM from 300,000 to 500,000 without getting
rid of the error.

- recently, they also observe ACCVIOs:

...
Archive procedure for system CAVI03 completed successfully
Starting archive procedure for system CAVI04
Timefile  Pass 1: Working ... done.
Timefile  Pass 2: Working ... done.
Logfile   Pass 1: Working ... -
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00184000,
PC=8048EF98, PS=0000001B

  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 00000005
                        Name   = 0000000C
                                 00000004
                                 00184000
                                 8048EF98
                                 0000001B


    Register dump:
    R0  = 0000000000002000  R1  = 0000000000002000  R2  = 000000007F3CB250
    R3  = 00000000001114C0  R4  = FFFFFFFFFFFFFAFE  R5  = 0000000000000001
    R6  = FFFFFFFFFFFE9AFE  R7  = 0000000000000001  R8  = 0000000000183F88
    R9  = 0000000000000001  R10 = 0000000000000001  R11 = 0000000000000000
    R12 = FFFFFFFFFFFFF800  R13 = FFFFFFFFFFFFFFF8  R14 = FFFFFFFFFFFC517E
    R15 = 0000000002F41A47  R16 = 0000000000184008  R17 = 0000000000001F58
    R18 = 000000000013C080  R19 = 7266282020202025  R20 = 2D303320204D4F43
    R21 = 0000000000000000  R22 = 000000000013C000  R23 = 00000000000000B0
    R24 = 0000000000002000  R25 = 0000000000000000  R26 = FFFFFFFF8057B8C0
    R27 = 7266282020202025  R28 = 363939312D4E414A  R29 = 000000007EE6E980
    SP  = 000000007EE6E980  PC  = FFFFFFFF8048EF98  PS  = 000000000000001B
$

Should ECO 2 resolve this problem ?  Any other ideas what they could try ?

Thanks in advance,
Hans.
T.RTitleUserPersonal
Name
DateLines
1276.1ALEXWS::ELLAThu Apr 25 1996 10:247
Hello,

	We are investigating the problem. We will send reply as soon as 
	possible.

Regards,
	Ella.
1276.2just trying to help a customerHANSBC::BACHNERMouse not found. Click OK to continueFri May 17 1996 10:028
�	We are investigating the problem. We will send reply as soon as 
�	possible.

The last reply is now three weeks old... would it speed things up if I escalate
this problem as an IPMT ?

Thanks for your advice,
Hans.
1276.3three months later...LNZALI::BACHNERMouse not found. Click OK to continueFri Aug 02 1996 08:1712
.1�	We are investigating the problem. We will send reply as soon as 
.1�	possible.

Any news on this one ?  I'd really appreciate an answer so I can inform the
customer about the current state of the problem.

And I'll ask again: do you want/need an IPMT or is it sufficient for you to
learn about the problem here ?  I understand that IPMTs keep several people busy
administering and tracking them, so I'd rather avoid one unless you require it.

Thanks for your help,
Hans.
1276.4Another occurance of the problemLEMAN::NEUWEILERTue Aug 06 1996 07:5430
I got the following problem report from a customer, This seems to
be the same kind of problem as described in the basenote. They got 
this problems since they switched from a VAX to an Alpha machine.

-------------------------
Customers problem report
-------------------------

Running the Console Manager V1.6-201 under OpenVMS 6.2, I have a job 
that archives the logfiles with the command

CONSOLE ARCHIVE/NOCONFIRM/BEFORE=-7-00 ALL

For over 50% of the systems (91 systems in total), I receive the 
following error messages

Starting archive procedure for system CHORUS2
Timefile  Pass 1: Working ... done.
Timefile  Pass 2: Working ... done.
Logfile   Pass 1: Working ... done.
Logfile   Pass 2: Working ... done.
Eventfile Pass 1: Working ... done.
Archive procedure for system CHORUS2 failed

This job runs at 06:00 every morning and also seems to have the effect 
of blocking/crashing the Console Ctrl processes.

Are there any known problems with this ARCHIVE command ?