Vince Rosso@TRANSALTA
11/12/98 01:29 PM

James ... after some digging I found an entry in the snmpCol.conf file for
a node that was deleted about a month ago.   I removed the  entry started
the snmpCollect daemon and it now seems to be okay.   At this point I'm
assuming that was our problem ... just thought I would pass it on.




 (Embedded
 image moved   James Shanks <James_Shanks AT TIVOLI DOT COM>
 to file:      12/11/98 09:48 AM
 pic19300.pcx)




Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.ucsb DOT edu>

To:   NV-L AT UCSBVM.ucsb DOT edu
cc:    (bcc: Vince Rosso)
Subject:  Re: SNMPCollector Dies Ungracefully




Unfortunately, the Digital platform does not gives us any tools which will
read a core file from a stripped executable.  You will have to call Support
and see what they can tell you.  If you are not on the latest version of
code, they will recommend that you get there.  The only way we have found
to shoot a core on Digital is to give the user a fully debuggable version
of what is coring, wait for it to core again, and this time we can read the
core file and get a stack trace and data.  And what they would send (you
would ftp) would be the very latest level.



James Shanks
Tivoli (NetView for UNIX) L3 Support



Vince Rosso <Vince_Rosso AT TRANSALTA DOT COM> on 12/11/98 11:33:50 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks)
Subject:  SNMPCollector Dies Ungracefully





Vince Rosso@TRANSALTA
11/12/98 09:33 AM

We are running Netview 4.1 on a Digital Unix platform.   Last night the
SNMP Collector died and created a core dump ... also earlier in the evening
the server itself auto booted for no apparent reason  ... this may be
unrelated.    I stopped and restarted all daemons and restarted Netview.
Things are fine for about an hour and then the SNMP Collector crashes again
with a resulting core file.   I'm not sure of the best approach to trouble
shoot this ie. can I run in a debug mode that will create log files etc.
Also is there some way of viewing the core file where you can actually get
useful information from it.   Any help  or suggestions would be greatly
appreciated.

pic19300.pcx
Description: Binary data