If you have a core then you should call Support, because short of not
running the ruleset you are, there is NOTHING you can do to solve it.
The Support folks will advise you to run the /usr/OV/service/readcore
program and send them the core file, the report from readcore, and the
ruleset you are running. They may also ask that you turn on the nvcorrd
trace and let the problem happen again, since as you say, it does
frequently anyway., They will probably also want the trapd.log.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Gruner Mike" <mike.gruner@rfv.sfa.se> on 11/10/2000 02:14:00 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: nv-l@tkg.com
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] nvcorrd dies on signal 11
Have NetView V6.0.1 and Aix 4.3.3 and have a "little" problem with nvcorrd
which
dies on us randomly with signal 11. We have rulesets which we are using for
correlation
and a script which takes away some traps ( eg ISDN BRI ). Has someone
experienced
the same problems as we have ? Any suggestions appreciated ....
Mike Gruner
RFV Sweden
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|