Conference azur::mcc

4465.0. "EXPORTER Aborts daily" by POBOX::WOODJ () Thu Jan 28 1993 11:08

    I have had the MCC exporter running for approx 2 weeks now and the 
    MCC_EXPORTER_BACKGROUND process aborts daily, and I have seen 3
    different reasons so far.  The most frequent error is:
    
    	%MCC-E-QWRITERR, error writing queue file
    
    Next is an insufficient dynamic memory error, which I may have
    resolved by increasing PGFLQUOTA and VIRTUALPAGECNT, but haven't run
    long enough since to tell for sure.
    
    Also I have seen one ACCVIO, Access Violation.
    
    
    CURRENT STATUS OF PROBLEM:
    -------------------------
    
    I have spent several hours working with the CSC/CS internal support on
    this, but they have run out of ideas.  
    
    This is DECmcc BMS V1.2-3 running on a VAXstation 4000 VLC with 24 Mb
    memory.  The system also has VCS installed and is monitoring 4 nodes.
    Memory is very tight, but VMS Memory Mgt is handling it well.  There
    are generally 6-8 job swapped.  
    
    I have reduced the number of exported entities by approx 50%.  The
    currently exported entities include 4 NODE4 entities and their lines
    and circuits and 4 SNMP (proteon routers) nodes each with 4-5
    interfaces.  
    
    The process is fully privileged, UIC [1,5] with the following quotas
    
    Maxjobs:	  0	Fillm:	  150	Bytlm:	  100000
    Maxacctjobs:  0	Shrfillm:   0	Pbytlm:        0
    Maxdetach:	  0	BIOlm:	  100	JTquota:    1024
    Prclm:	 10	DIOlm:	  100	WSdef:	     512
    Prio:	  4	ASTlm:	  100	WSquo:	    4000
    Queprio:	  0	TQElm:	  150	WSextent:  20000
    CPU:    (none)	Enqlm:	 2000	Pgflquo:  100000
    
    The batch queue has no quota restrictions on it.
    
    The job executes fine for 5 - 30 hours prior to the abort.
    
    
    
    HISTORY OF THE PROBLEM:
    -----------------------
    
    DECmcc BMS V1.2 was installed originally without the reports. In trying
    to figure out a way to get the reports without a complete reinstall of 
    DECmcc I ran accross node 3.208 in this notesfile and I send the author
    a mail message asking if I could install on BMS V1.2.  His reply was
    "It might work".  
    I installed the Historian kit from that save set.
    I then restored the .G saveset from the BMS012 kit, which contains all
     of the reports procedures.  
    I then applied the MCC BMS v1.2-3 upgrade
    
    
    Much tuning has taken place on the system, and everything else seems to
    be working fine.  Again, memory is very tight, but does not appear to
    be completely exhausted, unlike my ideas on how to fix this problem!
    
    Thanks in advance for any ideas you can provide.  
    Jerry
    
     I
    restored saveset .G of the same kit to get the reports files.
    

>    	%MCC-E-QWRITERR, error writing queue file

	Check "open file quota" and "file limit" parameters.
        If you run mcc_audit it should help you check if the system 
	is correctly configured for mcc.