Hello, Jorge;
You can run nvcorrd in debug mode after you have executed nvcdebug -d
<debug_option>. You must recycle nvcorrd for the change to take effect.
Try to send an event that meets the ruleset criteria and look at nvcorrd.alog
and nvcorrd.blog. See man nvcdebug for more info.
Also, James Shanks posted a valuable overview of designing and running rulesets
some time ago.
Best regards,
Vladimir.
Jorge A. Jiles wrote:
>
> Hello there I'm running netview version 5 on a rs6000 240 dual processor
> under AIX 4.2
>
> Here is the problem. It happens twice that rulesets do not get to be
> process and the nvevent display does not show any events; the only way
> to
> solve this problem is through stop/restart ovactiond, nvserverd, and
> nvcorrd. Reading the manuals it seems as if the problem is with nvcorrd,
> but I can not find what is wrong with it; the nvcorrd.log does not show
> any
> thing abnormal; actually the only lines in the log are the
> initialization
> and the level 11/13 of the daemon. Is there any debug level for this
> daemon
> that can show me a bit more information? the rulesets call scripts that
> alarm on abnormal behavior of devices; therefore when I have this
> problem
> the computer room operators don't have a clue of what is going on.
>
> Any ideas in what is going on would be appreciatte.
>
> Thanks.
--
********************************
Vladimir Petr
Datasys, s.r.o.
mail: petr@datasys.cz
********************************
If it were done when 'tis done, then 'twere well
It were done quickly.
|