Conference azur::mcc

3197.0. "Collector event sink issue/question" by BIS1::COLLEYE () Wed Jun 17 1992 11:53

Greetings,

I encountered an issue with the DECmcc event_sink (mcc_evc_sink):

We are using MCC V1.2T7.

From a remote node, I was sending events to a collector entity and to a reference
entity registered in my DECmcc instance, the appropriate request notifications
being enabled.
The command procedure to send the events is attached.

The five first events (on the collector) were correctly captured by DECmcc and 
appeared in the notification window.
The five next events (on the reference entity) were not captured and did not 
appear in the notificatrion window.

We (the system manager) re-executed the MCC_STARTUP_EVC_SINK.COM; command
procedure.

After this re-execution, all the ten events were captured by DECmcc.

The (partial) log file of the event sink (MCC_EVC_SINK.LOG) is attached
and shows that errors have been encountered by the event sink.

QUESTIONS:

1) what does the following error message and status means ?
">>Error translating MCC event 3, status = 52875650,17-JUN-1992 15:36:22.77"
   
2) why does re-starting the sink solved the problem ?


Maurice.

$!==============================================================================
$!                    
$!                    SEND_EVENT.COM
$!                    
$!==============================================================================
$!                    
$ mcc_send_event :== $mcc_d_sexa:MCC_EVC_SEND.EXE
$!                    
$ mcc_send_event TPLAB "MC_COLLECTOR" "" "EVENT1" "BLABLA" Warning
$ mcc_send_event TPLAB "MC_COLLECTOR" "" "EVENT2" "BLABLA" Minor
$ mcc_send_event TPLAB "MC_COLLECTOR" "" "EVENT3" "BLABLA" Major
$ mcc_send_event TPLAB "MC_COLLECTOR" "" "EVENT4" "BLABLA" Clear
$ mcc_send_event TPLAB "MC_COLLECTOR" "" "EVENT5" "BLABLA" Critical
$ mcc_send_event TPLAB "MC_COLLECTOR" "REFERENCE POD_2" "EVENT1" "BLABLA" Warning
$ mcc_send_event TPLAB "MC_COLLECTOR" "REFERENCE POD_2" "EVENT2" "BLABLA" Critical
$ mcc_send_event TPLAB "MC_COLLECTOR" "REFERENCE POD_2" "EVENT3" "BLABLA" Major
$ mcc_send_event TPLAB "MC_COLLECTOR" "REFERENCE POD_2" "EVENT4" "BLABLA" Minor
$ mcc_send_event TPLAB "MC_COLLECTOR" "REFERENCE POD_2" "EVENT5" "BLABLA" Clear

=========================== extract of MCC_EVC_SINK.LOG ===================

$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$! Turn verification off
$!
$    no_verify = F$VERIFY(0)
$    EXIT
$!
$! This command procedure is a framework for building an individual
$! login command procedure. It is executed every time that you log
$! into your account.
$!
$  IF F$MODE() .NES. "INTERACTIVE" THEN GOTO ENDINTER
$ENDINTER:
$  IF F$MODE() .NES. "BATCH" THEN GOTO ENDBATCH
$ENDBATCH:
$!
$! Put commands that you want executed in any mode of login below.
$!
$
$manage/enterprise/presentation=mcc_evc_sink
Wait for connect request from a COLLECTOR,10-JUN-1992 13:45:41.19
Connected to COLLECTOR,17-JUN-1992 12:22:52.66

           . . . 

Connected to COLLECTOR,17-JUN-1992 15:35:12.67
Received a COLLECTER event,17-JUN-1992 15:35:12.70
Sent event #3 to MCC event manager,17-JUN-1992 15:35:12.86
Disconnect the link to the COLLECTOR,17-JUN-1992 15:35:12.71
Wait for connect request from a COLLECTOR,17-JUN-1992 15:35:12.87
Connected to COLLECTOR,17-JUN-1992 15:35:20.28
Received a COLLECTER event,17-JUN-1992 15:35:20.29
Disconnect the link to the COLLECTOR,17-JUN-1992 15:35:20.29
Wait for connect request from a COLLECTOR,17-JUN-1992 15:35:20.37
Sent event #3 to MCC event manager,17-JUN-1992 15:35:20.49
Connected to COLLECTOR,17-JUN-1992 15:35:28.52
Received a COLLECTER event,17-JUN-1992 15:35:28.63
Sent event #3 to MCC event manager,17-JUN-1992 15:35:28.66
Disconnect the link to the COLLECTOR,17-JUN-1992 15:35:28.64
Wait for connect request from a COLLECTOR,17-JUN-1992 15:35:28.68
Connected to COLLECTOR,17-JUN-1992 15:35:37.02
Received a COLLECTER event,17-JUN-1992 15:35:37.06
Disconnect the link to the COLLECTOR,17-JUN-1992 15:35:37.07
Wait for connect request from a COLLECTOR,17-JUN-1992 15:35:37.11
Sent event #3 to MCC event manager,17-JUN-1992 15:35:37.12
Connected to COLLECTOR,17-JUN-1992 15:35:46.14
Received a COLLECTER event,17-JUN-1992 15:35:46.28
Disconnect the link to the COLLECTOR,17-JUN-1992 15:35:46.28
Wait for connect request from a COLLECTOR,17-JUN-1992 15:35:46.33
Sent event #3 to MCC event manager,17-JUN-1992 15:35:46.72
Connected to COLLECTOR,17-JUN-1992 15:35:56.13
Received a COLLECTER event,17-JUN-1992 15:35:56.14
>>Error translating MCC event 3, status = 52875650,17-JUN-1992 15:35:56.16
Disconnect the link to the COLLECTOR,17-JUN-1992 15:35:56.15
Wait for connect request from a COLLECTOR,17-JUN-1992 15:35:56.19
Connected to COLLECTOR,17-JUN-1992 15:36:05.56
Received a COLLECTER event,17-JUN-1992 15:36:05.56
>>Error translating MCC event 3, status = 52875650,17-JUN-1992 15:36:05.60
Disconnect the link to the COLLECTOR,17-JUN-1992 15:36:05.57
Wait for connect request from a COLLECTOR,17-JUN-1992 15:36:05.75
Connected to COLLECTOR,17-JUN-1992 15:36:14.50
Received a COLLECTER event,17-JUN-1992 15:36:14.55
Disconnect the link to the COLLECTOR,17-JUN-1992 15:36:14.56
Wait for connect request from a COLLECTOR,17-JUN-1992 15:36:14.66
>>Error translating MCC event 3, status = 52875650,17-JUN-1992 15:36:14.67
Connected to COLLECTOR,17-JUN-1992 15:36:22.73
Received a COLLECTER event,17-JUN-1992 15:36:22.76
>>Error translating MCC event 3, status = 52875650,17-JUN-1992 15:36:22.77
Disconnect the link to the COLLECTOR,17-JUN-1992 15:36:22.77
Wait for connect request from a COLLECTOR,17-JUN-1992 15:36:22.81
Connected to COLLECTOR,17-JUN-1992 15:36:33.86
Received a COLLECTER event,17-JUN-1992 15:36:34.06
>>Error translating MCC event 3, status = 52875650,17-JUN-1992 15:36:34.07
Disconnect the link to the COLLECTOR,17-JUN-1992 15:36:34.06
Wait for connect request from a COLLECTOR,17-JUN-1992 15:36:34.13
Received a request to disable the sink #1,17-JUN-1992 15:52:59.02
Terminate sink management thread, no more active sink,17-JUN-1992 15:52:59.02
>>Error receiving link request,status = 44,17-JUN-1992 15:52:59.07
Disconnect the link to the COLLECTOR,17-JUN-1992 15:52:59.07
Disconnect the link to the COLLECTOR event sink,17-JUN-1992 15:52:59.07
Terminate COLLECTOR event sink, 17-JUN-1992 15:52:59.12
  SYSTEM       job terminated at 17-JUN-1992 15:52:59.98

  Accounting information:
  Buffered I/O count:             819         Peak working set size:    2308
  Direct I/O count:               228         Peak page file size:     12818
  Page faults:                   2144         Mounted volumes:             0
  Charged CPU time:           0 01:44:28.74   Elapsed time:     7 02:07:34.23

    Hi there,
    	We've seen some problems recently with the Event Logging Sinking,
    on a VMS system.  When we startup the MCC_STARTUP_DNA4_EVL.COM as part
    of the MCC startup, we keep seeing a privilege violation?  We've setup
    proxy to the 'target node' and on the local 'sink' (MCC Station), and
    the only thing we've changed recently was DNS to local/MIR.
    	Our goal has been to setup our alarms and are using DECalert with a
    rep from Colorado Springs/New Ventures.  It's been very frustrating,
    that we can't get the MCC_DNA4_EVL process going...  Any ideas?
    
    thanks,
    
    /Mic
    

    
    this is reply to .1:
    
    	Check your default privileges, do you have SYSNAM,DETACH,TMPMBX and
    NETBMX?  Have you started MCC_dna4_EVL sink successfully before T1.2.7?
    
    	DNA4 EVL sinking process is NOT the same as Collector sink.  If
    you would like to describe more details on your environment, please
    contact took::d_ball.  
    
    	Jean
    

Is the problem consistently reproduceable or is it intermittent?

I *used* get "Unable to translate" when I was sending > 127 character messages or
messages with funny escape sequences in them.   I think that was fixed.


I'll let jean answer what the error code means, since I'm not that familiar
with the DC AM sink code.


    

    The problem has been encountered once... but in the present case where
    we want to rely 100% on the sink to receive events, it is one too much.
    
    The message text I sent is any way < 127 characters... (FT
    documentation specify 250 as a limit)
    
    I am really interresed in the meaning of the error code.
    
    Maurice.

    this is also a reply to .1:
    ( 1 ) jean is correct about the privileges...
    ( 2 ) note 2790 (1...7) can also help if this is T1.2.7
    ( 3 ) I am located at took::d_ball and 226-5345 if there
          are further problems
    ( 4 ) set verify before running the startup and send me the
          results
    
    
    
    Thank you...
    
    
    - darryl

    
Reply to .0:

>>1) what does the following error message and status means ?
>>">>Error translating MCC event 3, status = 52875650,17-JUN-1992 15:36:22.77"
>>2) why does re-starting the sink solved the problem ?

   This status tells me that the sink failed loading in the parse
   table, thus the translation of the target entity failed.

   I am still investigating this problem.

   Q:  can you reliably re-produce this problem?  
   Q:  if yes, can you observe any pattern? any environment factor?  
   Q:  when this problem occurred, were there more than one MCC running?
   Q:  is it possible the sink was enabled before this new kit was installed?
       in other words, have you disabled the sink before you installed the
       new kit?

   Thank you for reporting this problem.  More information from you will 
   help me to understand the problem better.  If you like, send me
   mail @took::jean_lee.

   Jean

I just encountered this same problem last night, the person was
upgrading from T1.2.4 to T1.2.7. Between these releases the
codes of some entity classes (collector for certain) were modified
making old sinks and new AMs incompatible. What the person did
was they did the upgrade without taking the sink down, meaning that
the sink was not compatible. They were unable to then communicate
between the old sink and new AM. We simply brought down the sink and
that cleared the problem. One other thing to note, is that if you
didnt' bring the sink down and then did the upgrade you would see
the parser errors that you are getting (no parse table) because
the files would be automatically purged at install time and
the sink does not attempt to go out and get the new pointer.

Now all of this is based on the simple question; did you just recently
do an upgrade? And have  you used the sink since the upgrade?

Also check sys$share:mcc_evc_sink.exe and make sure there isn't an
old on in your sys$specific.

jill

    response .1 has been taken offline...
    
    
    
    
    
    
    - darryl