What does this ruleset you put into ESE.automation look like?
Does it have a Forward in it?  Is the initial node ("purple pizza") set to
PASS rather than BLOCK?

Both of those are no-nos because they only refer to using a display and the
actionsvr daemon who gets the output from rulesets in ESE.automation has no
display, so he cannot deal with events which come to him without a command
to be executed.

When your rulesets stop, do a  netstat -a.  Bet you will see some daemons
with huge numbers of messages in their send and receive queues.  One of
these will be nvcorrd.  That is a sure sign that a ruleset running in the
background is not correctly built.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Mark van Kerkwyk <kerkwyk AT COMTECH.COM DOT AU> on 02/11/99 04:03:13 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.ucsb DOT edu>

To:   NV-L AT UCSBVM.ucsb DOT edu
cc:    (bcc: James Shanks)
Subject:  ruleset running from ESE.automation simply stops after a couple
      of days





Hi again,
     I have been having this problem for a while , I reverted back to
running the rulset from the workspace but it isn't a good long term
solution.
My main ruleset is being run from ESE.automation, it works fine except that
after a couple of days, the rules simply stop being triggered and I have no
idea why.

When I stop and start Netview, the ruleset starts running again.

Has anyone seen this before ??

Mark