[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

5562.0. "NOTIFEXCP, NOTIFABORT when trying to log notific." by MUNICH::FERSTL () Fri Sep 03 1993 12:19

Hi,

I have a customer who uses a commandprocedure to do a

NOTIFY DOMAIN ...  , TO FILE ....

Sometimes the commands work, sometimes he gets the errors NOTIFEXCP,
NOTIFABORT.

Does someone have an idea what could be the reason for this errors?


Thanks in advance

      Birgit Ferstl / Digital Service Center Munich


Here are the commands:
**********************************************************************
$manage/enterprise
DECmcc (V1.3.0)
.
.
.
notify domain domain.be , to file mcc_notification.log                         
%MCC-S-NOTIFSTART, Notify request 1 started                                    
                                                                               
%MCC-E-NOTIFEXCP, notify request 1 encountered an exception                    
%MCC-W-NOTIFABORT, notify request 1 aborted due to error condition             
notify domain domain.be -                                                      
entity list=(collector mcc.collector.be,collector mcc.collector.be_hsc,-       
            node4 BEW016 remote node *,SNMP *), event=(any event),-            
            to file mcc_notification.log                                       
%MCC-S-NOTIFSTART, Notify request 2 started                                    
                                                                               
%MCC-E-NOTIFEXCP, notify request 2 encountered an exception                    
%MCC-W-NOTIFABORT, notify request 2 aborted due to error condition             
enable domain domain.be rule NODE4_REACHABILITY_HIDDEN                         
.
.
.
**************************************************************************

T.R	Title	User	Personal Name	Date	Lines
5562.1		SISE::DITMARS	Pete	`Tue Sep 07 1993 15:11`	1
	Perhaps there are problems retreiving information from the DNS server?
5562.2	check sinks as well	TOOK::CALLANDER		`Fri Sep 17 1993 13:36`	15
	the logging shouldn't be impacting or causing the receipt of an exception. Logging is handled completely in the PM while the exception is coming from the lower level FMs or AMs. Make sure that your sinks are running if you are setting up a notify that wants events from node4 or the collector. Also make sure that your DNS access is available (moot point if using local NS, but check file protections here). Please also keep in mind that you can simply USE LOGGIN ON to get all fcl data to log to a file. This will allow you to start multiple notify commands and have all of the data intermixed within a single output file. jil