[Top] [All Lists]

RE: [nv-l] nvcorrd restarts

To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] nvcorrd restarts
From: James Shanks <jshanks@us.ibm.com>
Date: Tue, 5 Apr 2005 13:30:30 -0400
Delivery-date: Tue, 05 Apr 2005 18:31:05 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <9C75C49D7A005448A54CA00EA589CEE805E30F@nyhcbmsg3.na.ngrid.net>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

The core file in /usr/OV/PD/cores may have been swept up into an First
Failure Data Capture directory, if you have space for it.  That was a new
feature in 7.1.4.  Check /usr/OV/PD/FFDC for any subdirectories.  They will
be named by date, and inside them will be gzip'd tar files which are
gathered automatically if a daemon exits unexpected.  If you find some,
you'll want to contact Support, or as you suggested, install FP03.

Since you are on AIX, you could also be looking in errpt for daemon
failures.  The error logging facility will write a core dump record there
as well.
Try  errpt -a  | more

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

             "Zoeckler, Eric                                               
             <Eric.Zoeckler@us                                          To 
             .ngrid.com>               <nv-l@lists.us.ibm.com>             
             Sent by:                                                   cc 
             us.ibm.com                                            Subject 
                                       RE: [nv-l] nvcorrd restarts         
             04/05/2005 08:35                                              
             Please respond to                                             

Thanks for the feedback.  There have not been any ruleset changes and there
is no core file in /usr/OV/PD/cores/nvcorrd.  I'm running 7.1.4 at Fixpack
1 and ovw_binary-testfix.  This has been very stable for a year since my
last upgrade.  Maybe its time to review the release notes for FP3.
Thanks again,
Eric Zoeckler
Data Center Operations
National Grid USA

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On
Behalf Of Gareth Holl
Sent: Monday, April 04, 2005 5:03 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] nvcorrd restarts

The "Remote Monitor and Control" (ctrmc) daemon is a part of the "Reliable
Scalable Cluster Technology (RSCT) product. This is not related to the
NetView product and thus the error should have nothing to do with the
nvcorrd daemon.

If nvcorrd dies, it is automatically restarted....thats what the popup is
telling you. What you need to do is look for a core file in the
/usr/OV/PD/cores/nvcorrd directory. Have you changed any rulesets recently
? Have you added any rulesets to the ESE.automation file ? If you don't
have any 7.1.4 fixpacks installed, I'd recommend applying Fixpack 3 in case
there is a fix included for this kind of problem.

Gareth Holl
Staff Software Engineer

ITIL Foundations Certified
IBM Certified Deployment Professional
       --Tivoli Data Warehouse v1.2
       --Tivoli Enterprise Console v3.8 Network Management

IBM Software Group - Tivoli Software
Research Triangle Park,  North Carolina.

 "Zoeckler, Eric A."                                                       
 Sent by: owner-nv-l@lists.us.ibm.com                                      
 04/04/2005 04:45 PM                                       ibm.com>        
                Please respond to                                  Subject 
                       nv-l                                [nv-l] nvcorrd  

AIX 5.2 NV 7.1.4

On two occassions our NOC has seen a popup saying that nvcorrd daemon
has restarted.  When this happens the Events Display stops logging
events and they restart netview to resolve the problem.  I believe the
following error occurred each time.  Has anyone seen this before?

A6DF45AA   0401120905 I O RMCdaemon      The daemon is started.

Resource Name:   RMCdaemon
Description: The daemon is started.
Probable Causes: The Resource Monitoring and Control daemon has been

User Causes
The startsrc -s ctrmc command has been executed or
the rmcctrl -s command has been executed.

       Recommended Actions
       Confirm that the daemon should be started.

Eric Zoeckler
Data Center Operations
National Grid USA

This e-mail and any files transmitted with it, are confidential to National
Grid and are intended solely for the use of the individual or entity to
whom they are addressed.  If you have received this e-mail in error, please
reply to this message and let the sender know.

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web