Conference csc32::consolemanager

  Steve,

  I assume it was starting OK at some point, if so, what have you changed? 
  have you added anything to the database (filters, actions etc).

  Also, are there any mailboxes which look like they belong to an old 
  incarnation of ENS (check CONSOLE$LOGICAL_NAMES logical name table.

Cheers,
Phil

    Phil,
    
    Yep ENS has been running happily, ever since we shutdown OSCint that
    is, but this morning at about 4am, the Notify process went into RWMBX.
    PCM was shutdown, and the notify and one of the control processes had
    to be individually stopped.
    
    The CONSOLE STATUS/CONT display still shows ENS as running, but the
    process doesn't exist.  There are no mailbox logicals, there are no
    active processes accessing any part of PCM.
    
    We do see this every now and then, and the process which PCM thinks is
    still running ENS does most of the time, eventually go away.  This does
    become a little inconvenient. There also has been no new actions or
    filters added recently.
    
    Thanks
    Steve

    Phil,
    
    One more observation, when continuously watching the status display,
    and starting and shutting down PCM.  The ENS PID does change every time
    PCM is restarted, but when PCM is shutdown the ENS PID stays there. 
    When you try to look at that process, it is nonexistent.
    
    I have tried all versions of software that I have, from -000 through
    -003, and the same thing happens.
    
    Any help, thoughts appreciated.
    Steve

    Steve,
      That status info is kept in a global section and there is no rundown
    handler declared to go an clean-up this info. Personally, I think that
    leaving the old pid in there is useful for debugging. You could feed
    that pid into the ACCOUNTING utility to see what it's exit status is.
    
    Regs,
      Dan

    
    	I have a problems starting the ENS daemon.
    	Process Console Notify dies after about 20 seconds.
    	PCM Version 1.5 (MUP 1)
    	
    	The output in CONSOLE$TMP:CONSOLE_NOTIFY_OUTPUT.LOG is:
    
    	NO verify performedCMProcessLocalAccept: failed to create output mbx!!
        CONSOLE$ENS_DAEMON: eventport_error Callback
        errno_val : 10772
             msg1 : Failed to create Local socket CONSOLE_EVT_ENS
             msg2 : %SYSTEM-F-EXBYTLM, exceeded byte count quota
        CONSOLE$ENS_DAEMON: eventport_error Callback
        errno_val : 0
             msg1 : Failed to create Local socket CONSOLE_EVT_ENS
             msg2 : error 0
         Event Listener Closed unexpectedly, unable to restart!, exiting.
    
	Double the byte count quota limits does not help.
    
    	Any help will be appreciated.
    
    	Thanks,
    
    	ahmad 

    
>>	Double the byte count quota limits does not help.

  Where did you double them? You have to change the values in the 
  CONSOLE$STARTUP.COM file.

  Out of interest, what are your sysgen parameters DEFMBXBUFQUO and
  DEFMBXMXMSG

Cheers,
Phil

    
    
    	I have changed in the UAF and CONSOLE$STARTUP.COM
    	
    	My sysgen params are as follows DEFMBXBUFQUO 32000
    	DEFMBXMXMSG 2400
    
    	rgds,
    
    	ahmad

>>    	I have changed in the UAF and CONSOLE$STARTUP.COM

  Good, although the UAF parameters wont make too much difference.
    	
>>    	My sysgen params are as follows DEFMBXBUFQUO 32000
>>    	DEFMBXMXMSG 2400

  Why so high, the defaults for VMS out of the box are something like 1056 
  and 256, but, having said that, these high values are more than likely the 
  cause of your problem as we create A LOT of mailboxes each one created uses 
  these parameters to decrement your quotas accordingly.

Cheers,
Phil

    
    
    	Phil,
    
    	Thank you very much, its up and running.
    
    	rgds,
    
    	ahmad