Conference azur::mcc

6446.0. "memory leakage in Polycenter network manager 400 2.4" by BACHUS::KNEUTS (Erwin Kneuts DTN 856-8726) Fri May 03 1996 14:32

First of all I am not sure this is the right conference.  I do not see much 
entries on network manager inhere.  I did not find a specific notesfile though.
Please redirect if needed.

Is there a location on the net containing the latest patches for this product?

I have following problem with it.
Any advise welcome.

Erwin

 AS TEST CASE I UPGRADED OPEN VMS ON A VAXSTATION 4000/60 FROM V5.5-2 TO V6.1.
AFTER THE UPGRADE I ALSO UPGRADED DECMCC WITH THE POLYCENTER NETWORK MANAGER 400
VERSION 2.4
THE UPGRADES WERE OK, ALL INSTALLATION VERIFICATION TESTS WERE OK.
I CAN START UP DECMCC AGAIN. BUT AFTER A WHILE, THE PROCESS STOPS. IN THE LOG
I FIND:
%DEBUGBOOT-W-EXQUOTA, process quota exceeded
%DEBUGBOOT-W-EXQUOTA, process quota exceeded
%CMA-F-EXCCOP, exception raised; VMS condition code follows
-SYSTEM-F-INSFMEM, insufficient dynamic memory
-SYSTEM-F-INSFMEM, insufficient dynamic memory
  OPERATOR     job terminated at  2-MAY-1996 16:28:06.12
    Accounting information:
  Buffered I/O count:           35499         Peak working set size:   23041
  Direct I/O count:              2100         Peak page file size:    209981
  Page faults:                 120840         Mounted volumes:             0
  Charged CPU time:           0 00:07:38.24   Elapsed time:     0 08:54:09.19

I NOTICED THAT THE PEAK PAGE FILE SIZE INCREASES UNTIL IT REACHES THE VALUE
MENTIONED ABOVE. THIS VALUE IS  SOMEWHAT HIGHER THAN THE PGFLQUO OF THE PROCESS
(= 200000). IT HAPPENS EACH TIME, EVEN WHEN I ENABLE ONLY A FEW RULES IN
DECMCC.
SYSGEN PARAMETERS AND USER QUOTAS SHOULD BE MORE THAN SUFFICIENT. I RAN THE
MCC_AUDIT AND DID IT NOT INDICATE ANY PROBLEM.
THIS IS THE CONTENTS OF THE MCC_AUDIT_LOG.TXT:
MCC_AUDIT X1.3.11.a   3-MAY-1996 09:43:47.24,
          on node GRM005, a VAXstation 4000-60, running VMS V6.1
 Checking Process Quotas
 - No process quotas found to be too small for user OPERATOR
 Checking DECnet Parameters.
 Checking Sysgen Parameters.
 - No Active Sysgen parameters found to be too small.
 Checking installed images
 - DNS$client.exe not installed. Check that DNS Client startup has run.
 Checking Disk Space
  MCC_COMMON:
  SYS$LOGIN:
  SYS$SYSDEVICE:
 Checking Memory
 - 32Mb of Main Memory is less than needed for good performance
 -    40Mb or more is reccomended for production use of DECmcc
 Checking Pagefile Size

 Pagefile Size for system GRM005 is 200000 blocks.

 Checking DNS Client Version

Audit Complete

MIN_SRPCOUNT = 2048                 ! Ok current value is 2146236416
MIN_CLISYMTBL = 250                 ! Ok current value is 250
MIN_LOCKIDTBL = 2048                ! Ok current value is 2048
MIN_PROCSECTCNT = 200               ! Ok current value is 200
MIN_RESHASHTBL = 512                ! Ok current value is 2048
MIN_MAXBUF = 1200                   ! Ok current value is 9064
MIN_PAGEDYN = 1000448               ! Ok current value is 1400320
MIN_NPAGEDYN = 900096               ! Ok current value is 1399808
MIN_GBLPAGFIL = 12200               ! Ok current value is 12200
MIN_CTLPAGES = 32                   ! Ok current value is 100
MIN_PQL_MASTLM = 600                ! Ok current value is 600
MIN_WSMAX = 16000                   ! Ok current value is 24600
MIN_CHANNELCNT = 512                ! Ok current value is 512
MIN_GBLSECTIONS = 600               ! Ok current value is 740
            

    The patches for MCC are typically issued by the CSC.  Give them a
    shout; if you need a pointer you might try asking Phillipe Tabone if he
    knows where they might be on the net... this is a problem we've seen
    before and there's a "known" fix...
    
    good luck,
    
    /Mic