Yepper that certainly seems like it is the problem we had. And it was a
problem at your NetView level.
James can probably verify, but I believe the symptoms for this bug were if you
have forwarding turned on to TEC, and bring down TEC (or TEC experiences a
problem causing a communications disruption (socket closed), nvserverd will
sometimes start consuming hugh quantities of CPU and nvcorrd will become
idle. No events are processed through rulesets.
"Lemire, Mark" wrote:
> Thanks for your suggestions, James -- I think we're getting closer.
>
> >> You said you said turned off TEC forwarding. How did you do that?
>
> I had *thought* we had turned TEC event forwarding off. In fact, not the
> case. We control this through the Tivoli/Netview Policy Region, by
> right-clicking the Netview icon/Configure/Configure Event Forwarding to
> Tivoli. It was set to 'On" with a rule defined!! Both Netview's have this
> feature enabled with different Tivoli Event Servers. However, I suspect one
> of the Tivoli servers may have had changes recently and perhaps the events
> had nowhere to go. There was data in the cache file -- although since we
> recently restarted Netview, it was small. We're going to turn event
> forwarding off and see if the problem recurs...feeling positive about this.
> Thanks VERY much for your help on this, James. I'll send an update if
> nothing further happens in a few days so the group knows the outcome.
>
> Mark
>
> -----Original Message-----
> From: James_Shanks@TIVOLI.COM [SMTP:James_Shanks@TIVOLI.COM]
> Sent: Wednesday, June 07, 2000 10:26 AM
> To: IBM NetView Discussion
> Subject: RE: [NV-L] Question concerning Netview Event History
> Window???
>
> Dollars to donuts, that is your problem. The presence of
> tecint.conf is how
> nvserverd knows to forward to TEC. So yours is spending a lot of
> worthless time
> trying to do just that, even if there is no TEC on the box he is
> sending to.
> I'll bet you have a nice big /etc/Tivoli/tec/cache file too. These
> files should
> be deleted. As for recycling the daemon, that is the sure way to
> make sure no
> attempts at TEC forwarding are going on. There is the nvtecia -stop
> command,
> but I don't know for certain how well it works at your level, since
> I just fixed
> a major bug in it for 5.1.3. You could try it and see if your
> problem goes
> away. But you must delete or rename those tecint.conf files so this
> does not
> re-occur.
>
> You said you said turned off TEC forwarding. How did you do that?
>
> James Shanks
> Tivoli (NetView for UNIX and NT) L3 Support
>
> : http://www.tkg.com/nv-l
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
--
Ray Schafer | schafer@tkg.com
The Kernel Group | Distributed Systems Management
http://www.tkg.com
|