The procedure for any daemon problem is the same. Look for cores, look in
the logs for error messages and call Support. If your daemon stops on
some signal, there is probably very little you can do about it without
help.
Sig 4 is an invalid instruction, most likely the result of an overlay
(memory) problem.
I'll bet you got a core. Did you look in /usr/OV/PD/cores/snmpCollect? If
so, run /usr/OV/service/readcore and call Support.
If you haven't been running the trace, I suggest you start. That way one
can tell what snmpCollect was doing before he died.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
reamd@Nationwide.com
07/12/2002 08:55 AM
To: nv-l@lists.tivoli.com
cc:
Subject: [nv-l] snmpCollect
Hi All,
My snmpCollect receives an exited on signal 4.. How can I find
out what's causing it to stop running.
Thanks, Dave
AIX 4.3.3
6.0.3
---------------------------------------------------------------------
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)
|