This is a multipart message in MIME format.

I have open the problem last week. We have NetView 6.0.0 and AIX 4.3.3.
The Problem is in rules with "Reset on match" by closing nvevents (or 
netview). The result is a core with signal 11. I have deleted the "Reset 
on Match" in this week, an now the nvcorrd is running after close the 
netview.
 
I can test the rules in next week with 6.0.1, but i think the nvcorrd 
isn't changed.

Best Regards 
Uwe 


E-Mail: Uwe.Richter AT synthesis DOT de

Tel.:      0711/90680-27
Fax:      0711/90680-66
Handy: 0172/9531201




James_Shanks AT tivoli DOT com
Gesendet von: owner-nv-l AT tkg DOT com
10.11.2000 17:39
Bitte antworten an IBM NetView Discussion

 
        An:     IBM NetView Discussion <nv-l AT tkg DOT com>
        Kopie:  (Blindkopie: Uwe Richter/Synthesis)
        Thema:  RE: [NV-L] nvcorrd dies on signal 11

Joel -
Are you opening problems with Support on these?  I see no APARs taken for
you regarding cores in nvcorrd.
And you may have had a core in nvcorrd in 5.1.2 and 5.1.3 but it may not 
be
the same problem by 6.0.1. The same symptom may have radically different
causes.  All known cores in 5.1.2 were resolved in 5.1.3, and  there were
no new ons reported by the time 5.1.3 shipped.   And 6.0.1 is ahead of
5.1.3.  I know this because I fixed them.  A new APAR was opened yesterday
for a core which occurs when a dynamic window containing a ruleset that
thas two or more Reset-On-Match nodes is closed, but that is first
documented report of an nvcorrd core since 5.1.3 was completed in January.
 By "documented" I mean that the person who had it called Support and gave
them the core file, core report, ruleset, and logs to show what was going
on. I don't know how to fix what I don't get doc on .

But your circumvention is a good one while you wait for a fix.  Still it
would be better if you also calling Support so we cn get t work on it.

James Shanks
Team Leader, Level 3 Support
 Tivoli NetView for UNIX and NT



"Joel A. Gerber" <joel.gerber AT usaa DOT com> on 11/10/2000 11:14:25 AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

To:   "'IBM NetView Discussion'" <nv-l AT tkg DOT com>
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  RE: [NV-L] nvcorrd  dies on signal  11




We also have the same problem with nvcorrd on both NetView 5.1.2 and 
5.1.3.
We're still testing 6.0.1, so I'm not sure we still have the problem in
that
version.  I can't offer any help with the root cause or a fix, but if
you're
interested I can send you a script that will monitor nvcorrd, and restart
it.  We run the script out of root's crontab every minute.  It checks if
nvcorrd is running.  If it's not, then it stops the actionsvr daemon, and
restarts them both.

Joel A. Gerber - USAA Information Technology Co. - San Antonio, TX
* (210)913-4231  * mailto:Joel.Gerber AT USAA DOT com  " http://www.usaa.com

-----Original Message-----
From:     Gruner Mike [SMTP:mike.gruner AT rfv.sfa DOT se]
Sent:     Friday, November 10, 2000 01:14
To:  nv-l AT tkg DOT com
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
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l


_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l