Events History has nothing to do with trapd.log or current events being sent to
TEC. trapd maintains the trapd.log, and nvserverd sends the events to TEC,
after they have been processed by trapd and nvcorrd.
Events History is maintained by a separate process which registers for traps
from trapd, just like all the current event daemons do. That process is
ovesmd, the ems_sieve_agent. He formats them and passes them to the
ems_log_agent, ovelmd, who stores them in formatted form in
/usr/OV/log/ovevent.log. That's where they are read from.
And remember that Events History, unlike current Events, does not update
automatically. Once you have done your initial Query, the contents of the
window are fixed, until you refresh it by pulling down "Query" again and
clicking "Display Event".
Then they are updated with the current contents of the ovevent.log.
So if this isn't working, I would first check whether your ovevent.log is
growing and if not, whether the ems_log_agent and the ems_sieve_agent are still
running. ovstatus should tell you that.
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
"Tremblay, David A." <dtremblay@JHANCOCK.COM> on 06/06/2000 04:07:45 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc: "Lemire, Mark" <mlemire@JHANCOCK.COM> (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Question concerning Netview Event History Window???
Hello all,
I am currently working with support on this issue but I am wondering if
anyone else has experienced this problem.
Has anyone ever had their Event History Window stop taking in events but
their trapd.log continue to run ok and even continue forwarding events to
TEC?? All the Netview Daemons look ok for the exception of one that pegs
the CPU at 50% which is nvserverd. After a reboot everything is ok for a
day or so and then we are back into the same problem with the Event Viewer
not picking up events anymore.
This is the situation we are currently experiencing but their weird part is
that our test/staging server which is supposed to be identical has not
exhibited any of the symptoms I have mentioned above. The test/staging
server even uses the exact same database that is copied over nightly!!!
We are running NetView 5.1.1 (on purpose) with integration forwarding events
to Tivoli/TEC on a Solaris 2.5.1 box with over 2 gig of memory.
If anyone has any ideas, please reply.
Thank you.
David A. Tremblay John Hancock Financial Services
Lead Systems Analyst Information Technology Services
Enterprise Management Tools Technology Shared Services
E-Mail: dtremblay@jhancock.com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|