How do you know events are coming in if it is not logging?

The only reason that they might not be logged when they come in is because they
are being sent too fast.
When trapd is in a "trap storm" he has no time to do any thing but queue up the
incoming traps until the storm subsides and he has time to process.   When this
is the case, you should see trapd grow and grow in size.  But you can determine
what is happening better by starting the trapd trace.  Just type "trapd -T" from
the command line,  and this toggles the trace on and off.  If all you see in the
trapd.trace is that events are being queued, then that is your problem, and you
will have to turn off the sending of traps by some of your external agents,
until trapd can recover.

I would also plan on calling Support since there is something fundamentally
wrong with your network design if this is happening.

James Shanks
Tivoli (NetView for UNIX and NT) L3 Support


"Yean Tai Chew" <yeantai AT geocities DOT com> on 05/18/2000 09:57:29 PM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

To:   "IBM NetView Discussion" <nv-l AT tkg DOT com>
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  [NV-L] Trapd.log Stops Logging




Hi all,

My trapd.log just stops logging events a few days ago.  I've checked the
trapd daemon's options but everything looks fine there.  Restarted the
daemon, did an ovstop, ovstart - practically did everything that I could
think of except restarting the whole server.  Could someone shed some light
to this?  The events are still coming in but they are not logged at all due
to this problem.

Thanks for listening!

Warmest regards,
Kendra


_________________________________________________________________________

NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l