Regarding the Event Console Trouble problem posted lately here...
The answers from Vladimir and Bryan were accurate. I'd like just to add
another hint, which is that basically, when you create a ruleset to
receive NetView events,
the nvserverd.baroc file MUST BE LOADED AFTER tecad_ov.baroc when
creating the initial rulebase.
If not, very unpredictable things can happen.
The way to verify this is to check
$BINDIR/TME/TEC/<name of ruleset directory>/TEC_CLASSES/.load_classes
This file lists all the baroc files in the rulebase in order.
If nvserverd.baroc is before tecad_ov.baroc you might see something like
this in your trace files:
>From /tmp/tec_master
Jun 22 08:53:58 tec_master[27471] ERR tec_exit_msg.c:247: Process T/EC
Rule exits with exit code 211: Process terminated...
Jun 22 08:53:58 tec_master[27471] ERR tec_exit_msg.c:247: Process TEC
Master exits with exit code 43: Child process died...
Jun 22 08:53:59 tec_master[27Jun 22 08:54:00 tec_dispatch[27477] ERR
tec_disp_msg.c:139: T/EC Dispatch terminates with error 67
Jun 22 08:54:00 tec_dispatch[27477] ERR tec_exit_msg.c:247: Process T/EC
Dispatch exits with exit code 40: Lost communic...
>From /tmp/tec_dispatch
Jun 22 08:54:00 tec_dispatch[27477] ERR tec_disp_msg.c:139: T/EC
Dispatch terminates with error 67
Jun 22 08:54:00 tec_dispatch[27477] ERR tec_exit_msg.c:247: Process T/EC
Dispatch exits with exit code 40: Lost communic...
Jun 22 08:54:00 tec_dispatch[27477] ERR tec_ipc_accept.c:145: ipc_accept
failed (error 67)
The TEC team is aware of this and appropriate documentation should be in
place for NetView 5.1. Meanwhile, remember to check this also when
forwarding your events from NetView to TEC.
Hope this helps,
Cristina Zabeu
|