This looks interesting...AIX 4.3.3
Any thoughts?
`errpt -a`
---
---------------------------------------------------------------------------
LABEL: CORE_DUMP
IDENTIFIER: C60BB505
Date/Time: Tue Jul 16 20:04:49
Sequence Number: 3633
Machine Id: 000470324C00
Node Id: etb2_dms3
Class: S
Type: PERM
Resource Name: SYSPROC
Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED
Probable Causes
SOFTWARE PROGRAM
User Causes
USER GENERATED SIGNAL
Recommended Actions
CORRECT THEN RETRY
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
RERUN THE APPLICATION PROGRAM
IF PROBLEM PERSISTS THEN DO THE FOLLOWING
CONTACT APPROPRIATE SERVICE REPRESENTATIVE
Detail Data
SIGNAL NUMBER
4
USER'S PROCESS ID:
29776
FILE SYSTEM SERIAL NUMBER
12
INODE NUMBER
14349
PROGRAM NAME
netmon
ADDITIONAL INFORMATION
??
send_snmp 5B4
NetmonLoo 2F4
main 1350
??
Symptom Data
REPORTABLE
1
INTERNAL ERROR
0
SYMPTOM CODE
PCSS/SPI2 FLDS/netmon SIG/4 FLDS/send_snmp VALU/5b4
---
Jason Allison
Principal Engineer
ARINC Incorporated
Office: (410) 266-2006
FAX: (410) 573-3026
-----Original Message-----
From: Caputo, Thomas [mailto:TCaputo@kmart.com]
Sent: Wednesday, July 17, 2002 8:56 AM
To: 'Allison, Jason (JALLISON)'
Subject: RE: [nv-l] netmon problem
I assume you are running Unix(?)
If NT, check event logs. If AIX, check errpt -a for traces of a core. Not
sure about other flavours.
It would make it easier on you to check for cores by netmon &/or trapd
first.
-----Original Message-----
From: Allison, Jason (JALLISON) [mailto:JALLISON@arinc.com]
Sent: Wednesday, July 17, 2002 7:19 AM
To: 'nv-l'
Cc: Allison, Jason (JALLISON)
Subject: [nv-l] netmon problem
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)
|