Hi List,
Netview V7.1.4 on Redhat AS2.1
I have created a ruleset that has two event
attribute nodes. Both attribute nodes connect to one action node each. The
attribute nodes check for interface down and interface up events from netmon and
the action node starts a perl script which extracts information from a flat
file(that is a dump of the topo database) and then does a wpostemsg to
TEC.
Everything seems to be working fine. The script is
quick. If I run it manually it completes instantly and an event is posted to
TEC. However, what I noticed is happening is that there are times when interface
events arrive in trapd.log but my script is not executed. When I looked in
nvaction.alog I can see the event attributes coming through for the events and
then suddenly the following message appears 5-10 times:
2003/04/12 17:08:16
./nl_Actionsvr.C[616] : 69 action command timed out. 2003/04/12
17:08:16 ./nl_Actionsvr.C[616] : 70 action command timed
out. 2003/04/12 17:08:18 ./nl_Actionsvr.C[616] : 71 action
command timed out. 2003/04/12 17:08:18 ./nl_Actionsvr.C[616]
: 73 action command timed out.
2003/04/12 17:08:19
./nl_Actionsvr.C[616] : 74 action command timed out.
2003/04/12 17:08:19
./nl_Actionsvr.C[616] : 74 action command timed out.
How can I check what is holding actionsvr daemon?
Is it possible that the script is been held up when it is executed by
actionsvr?
Any ideas?
Thanks
Pritesh
|