ovstatus netmon:
object manager name: netmon
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: 29776
last message: Initialization complete.
exit status: exited on signal 4
/usr/OV/log/netmon.trace has not been updated since May...
Jason Allison
Principal Engineer
ARINC Incorporated
Office: (410) 266-2006
FAX: (410) 573-3026
-----Original Message-----
From: reamd@Nationwide.com [mailto:reamd@Nationwide.com]
Sent: Wednesday, July 17, 2002 7:54 AM
To: Allison, Jason (JALLISON)
Cc: Allison, Jason (JALLISON); 'nv-l'
Subject: Re: [nv-l] netmon problem
When you do a "ovstatus netmon" does it give you an error? Does it tell you
to look at usr/OV/log/netmon.trace for the cause of the failure?
"Allison, Jason
(JALLISON)" To: "'nv-l'"
<nv-l@lists.tivoli.com>
<JALLISON@arinc.com> cc: "Allison, Jason
(JALLISON)" <JALLISON@arinc.com>
bcc:
Subject:
[nv-l] netmon problem
07/17/2002 07:18 AM
Having a bit of a problem with netmon.
When I start and stop the daemon, it will only run for ~5 minutes and then
die. Netview will then remind me with one of those gray popups saying
netmon is not running, would you like it to continue to check it.
The only thing that has changed in the past few weeks is the 'flood' script
I have been running using snmptrap. I will parse our entire trapd.conf for
each oid configured and send a trap for it. The app will send ~1000 traps
with our trapd.conf. I have noticed before that it would 'kill' netmon
after 700 or so (guess) traps. However, I would be able to restart netmon
with no problems. Now, it will not stay running. I have since cleared all
the events from all users from all workspaces for each nvevents thinking it
had something to do with our max 1000 events allowed in nvevents.
I cannot seem to find a log file to tell me about netmon's failure. nv6000
has nothing, trapd.log has nothing. When netmon dies, I perform a 'ls
-lrt'
on /usr/OV/log and ovevent.log has a timestamp change (we would expect
that). ovactiond.log contains:
07/15/02 14:52:55 ovactiond starting. Waiting up to 300 seconds for
command
to complete.
07/15/02 15:01:09 ovactiond: Closing at the request of OVsPMD (via ovstop).
07/15/02 17:41:37 ovactiond starting. Waiting up to 300 seconds for
command
to complete.
07/15/02 17:44:59 ovactiond: Closing at the request of OVsPMD (via ovstop).
07/15/02 17:45:29 ovactiond starting. Waiting up to 300 seconds for
command
to complete.
Any thoughts on my problem?
Thanks in advance,
Jason Allison
Principal Engineer
ARINC Incorporated
Office: (410) 266-2006
FAX: (410) 573-3026
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.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)
|