[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

3044.0. "MCC-E-RECVERR/NOTIFICATION_FM/ULTRIX T1.2.7" by ZTOIS1::VISTA (Renato VISTA, SIS Strasbourg, France) Thu May 21 1992 05:22

    
    
    Hi,
    
    On a official FT DECmcc/ULTRIX T1.2.7 platform, my customer an I have
    got unexpectable messages in the following situation :
    
    1)	Let's assume that the notify domain option is set (customized) to
    DISABLE.
    
    2)	The Notification Services window is opened, and the NOTIFY
    REQUEST.. window is opened too (the idea is to follow the action of
    creating and enabling the domain's associated request)
    
    3)	A domain of 40 sub-domains (on 4 levels) is loaded (=> nothing in
    the NOTIFY REQUEST window (OK))
    	The notify domain option is now set to ENABLE.
    
    4)	In the NOTIFY REQUEST window, the messages "Being created" followed
    by "Being enabled" are displayed...(corresponding to the opened domain)
    
    5)	...while error messages are sent
    
    	- through DECwindow/MCC windows with "MCC-E-RECVEERROR, Error
    		Trying to receive a packet"
    	- in the #mcc_iconic_map DECterm window with several 
    		"Disaster IPC Server unmarshall input sanity check failure"
    		messages
    
    6)	Note that, after closing DECwindow/MCC windows, the request is in
    ENABLE state and alarms/events messages are effectively notified on the
    map.
    
    7)	Note also that, if the notify domain option is customize to ENABLE,
    the same messages are displayed during the domain/sub-domains loading
    phase...
    
    Have you got any idea about that strange behavior ??
    
    Many thanks.
    Renato
T.RTitleUserPersonal
Name		DateLines
3044.1MIR init_fail PRSSUD::CARRAYROUFri May 22 1992 11:1118
    I had the same problem and more with DECMCC ULTRIX T1.2.7 + ELM127 + FDS127
    
    Same problem 
    
    Twice , I might reinstall DECMCC without problem
    
    All was OK. yesterday the product worked fine .
    
    But now I can access the MIR
    
    %MCC-F-MIR_init_FAIL,the mir could not be initialized 
    
    When I start decmcc I have this message
    
    waiting:MM mcc_notification_fm has not completed startup
    
    
    Didier
3044.2re: .0 - probably a resource problemMCC1::DITMARSPeteFri May 22 1992 17:5735
RE: .1

>    5)	...while error messages are sent
>    
>    	- through DECwindow/MCC windows with "MCC-E-RECVEERROR, Error
>    		Trying to receive a packet"
>    	- in the #mcc_iconic_map DECterm window with several 
>    		"Disaster IPC Server unmarshall input sanity check failure"
>    		messages

I suspect this is a resource limitation.  We've done work since t1.2.7 to
reduce the number of resources consumed by the notification FM.

Is your customer's ultrix kernel configured as recommended in
the installation guide?  Especially the max_nofiles in
param.c?  Perhaps boosting a few resources will help get them past the 
problem for now.

Here's a test you can try:  issue an individual notify request with
EXPAND = FALSE for each domain in your customer's hierarchy, e.g.

notify domain domain1 expand = false
notify domain domain2 expand = false
	:
	:

I suspect that only a certain number of them will succeed.  The 
"expand = false" override's the notification FM's default behavior, which
is to expand the notification to apply to all subdomains.  Thus, the
list of notify requests will roughly simulate what the notification FM
is trying to do when your customer opens the top-level domain.  But you'll
get an idea of how far along it's getting when it fails.

In the latest baselevel, the expansion being done by the notification FM 
is much cheaper than in t1.2.7.
3044.3re: .1 - corrupt MIR files?MCC1::DITMARSPeteFri May 22 1992 18:029
Did you have a lot of targets set up?  The notification FM maintains a MIR
of targets.  These are stored in /var/mcc.  If you don't have a backup of
that location from when things were working correctly, then try moving the
target files and the mir_repo files out of that directory
and try starting the notification FM again.  (The mir_repo files will be
automatically recreated)

Watch the protections and ownership of those files after recreating them.
Make them be the same as the other files in that directory.