nv-l

Re: [nv-l] Lost contact with nvcorrd error

2003-01-15 11:42:44
Subject: Re: [nv-l] Lost contact with nvcorrd error
From: James Shanks <jshanks AT us.ibm DOT com>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 15 Jan 2003 11:07:12 -0500
I think you should call Support about this.
But just looking at actionsvr's log won't help.
Did you look at nvcorrd's?
Is nvcorrd coring?  Check /usr/OV/PD/cores/nvcorrd and find out. 
You might want to have the nvcdebug trace running to see what he's up to. 
But the four termination messages in the your actionsvr log would indicate 
to me that you have several copies of this thing running at one time.  If 
nvcorrd is being flooded then he may be too busy to respond to actionsvr, 
but that's just a guess.
What is your trapd rate when this occurs?

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group




"Bursik, Scott {PBSG}" <Scott.Bursik AT pbsg DOT com>
01/15/2003 10:45 AM

 
        To:     nv-l AT lists.tivoli DOT com
        cc: 
        Subject:        [nv-l] Lost contact with nvcorrd error



NetView 6.0.3 AIX 4.3.3

I have been fighting this for quite some time and was wondering if any of
you have seen this? About once a month the rules that I load in
ESE.automation stop firing. When I look in the nvaction.alog or blog I see
the following errors:

1704~public~2~US545A09.fritolay.pvt~Node Up.~1042624265
5984007~openview~3~N~0
2003/01/15 03:51:07 .//nl_Actionsvr.C[807] : Varbind contained an illegal
character.
Issuing sanitized version of the varbind:
2003/01/15 03:51:07 .//nl_Actionsvr.C[808] :
NVATTR_2="US545A09\.fritolay\.pvt"
2003/01/15 03:51:07 .//nl_Actionsvr.C[807] : Varbind contained an illegal
character.
Issuing sanitized version of the varbind:
2003/01/15 03:51:07 .//nl_Actionsvr.C[808] : NVATTR_3="Node Up\."
2003/01/15 07:22:49 : lost contact with nvcorrd. The daemon may have been
stopped
2003/01/15 07:22:49 : lost contact with nvcorrd. The daemon may have been
stopped
2003/01/15 07:22:49 : lost contact with nvcorrd. The daemon may have been
stopped
2003/01/15 07:22:49 : lost contact with nvcorrd. The daemon may have been
stopped
2003/01/15 07:22:49 : Terminating session number bayinterface.rs with
nvcorrd.
2003/01/15 07:22:49 : Terminating session number bayinterface.rs with
nvcorrd.
2003/01/15 07:22:49 : Terminating session number bayinterface.rs with
nvcorrd.
2003/01/15 07:22:49 : Terminating session number bayinterface.rs with
nvcorrd.

At this point I have to stop and restart the actionsvr to reload the 
rules.
The ruleset it fails on changes from time to time. I have made sure that 
the
rules are valid and all of them end in running a script.

Scott Bursik 
Event Systems Management 
Pepsico Business Solutions Group 
(972) 334-3757 
scott.bursik AT pbsg DOT com 

---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)





---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)


<Prev in Thread] Current Thread [Next in Thread>