[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

5988.0. "other CMA-F-EXCCOP + ACCVIO" by TRNOIS::TESTA (POLYpCENTER !?!) Wed May 11 1994 05:01

    HI,
    
    I have a customer that gets occasionally system access violation on the
    DECscheduler job as below showed.
    
    The configuration is VAX4100 with OVMS 5.5.2H4, DECmcc 1.3.0 and
    patches: VSCHED_E05A021, VAXDECW08_V0255, MOTVVECO07113, MCCECO01013.
    
    The log problem is:
    
    ...
    SHOW DOMAIN * RULE * ALL STATUS, AT START = 23:00
    %CMA-F-EXCCOP, exception raised; VMS condition code follows
    -SYSTEM-F-ACCVIO,access violation, reason mask=01, virtual
                                  address=61700074, pc=000f7e60, psl=03c00000
    %TRACE-F-TRACEBACK, symbolic stack dump follows
    module name  routine name     line   rel PC    abs PC
                                         0004b4c4  0004b4c4
                                         0007c382  0007c382
                                         000771dc  000771dc
                                         0007a878  0007a878
    
    
    Please, have you any idea?
    
    Thanks in advance.
    
    Ciao
    
    Paolo Testa

T.R	Title	User	Personal Name	Date	Lines
5988.1	Memory leak	BIKINI::KRAUSE	CSC Network Management/Hubs	`Mon May 16 1994 08:57`	10
	> -SYSTEM-F-ACCVIO,access violation, reason mask=01, virtual > address=61700074, pc=000f7e60, psl=03c00000 This looks like a memory leak somewhere. You should try to divide the alarm rules and run a separate job for each entity class (e.g. one for NODE4 rules, one for SNMP rules and so on). Then you'll see if all jobs eventually ACCVIO (common problem, e.g. in Alarms FM or Kernel) or if only one of them bombs out (problem in this particular Access Module). *Robert
5988.2	More info really needed	SCCA::dave	Ahh, but fortunately, I have the key to escape reality.	`Mon May 16 1994 11:11`	12
	Your initial entry has nowhere near enough information to even make a guess on what the problem really is. (my opinion, Robert may have his, too.) Most of these types of problem have been traced to incorrectly configured user accounts/systems. Things like a SYSGEN SHOW /MAJOR and a dump of the user account, as well as the resource file and the current MCC logicals might help in any case. If you think its a real problem, submit a CLD/SPR and include all of the above.