A signal 11 is indicates a segmentation violation. Usually a core file is
produced. There is probably nothing you can do about this except to call
Support and get some help from them with it. Typically you would be asked
to run /usr/OV/service/readcore against the core file (which is in
/usr/OV/PD/cores/netmon) and send them the core.report output along with
the nettl logs and the netmon.trace file, and perhaps other documentation.
Since they will have to match up what is going on in the core with the code
internally there is little you can do to solve this on your own.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
KOCH François Athesa <KOCH@ulysse.cea.fr> on 10/25/2000 03:08:07 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "Liste NetView (E-mail)" <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Problem with netmon in 6.0.1
Hi,
Since I upgraded netview from 6.0 to 6.0.1, the netmon daemon permanently
crashes (after less than 1 minute). There are no errors in the trace file,
and ovstatus just tells 'exited on signal 11'.
Is there something special to do when upgrading in 6.0.1 ? How can I debug
the problem ?
Thank you for your help.
________________________________________________________________
Francois KOCH
CS SI - Athesa / CEA Saclay
Tel: 01 69 08 67 53 Fax: 01 69 08 87 55
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|