nv-l

RE: [nv-l] daemon could not startup.....

2002-12-04 08:42:42
Subject: RE: [nv-l] daemon could not startup.....
From: "Davis, Donald" <donald.davis AT firstcitizens DOT com>
To: "'Fission CC Lin'" <flin AT tw.ibm DOT com>, nv-l AT lists.tivoli DOT com
Date: Wed, 4 Dec 2002 08:42:42 -0500

I think the key piece of information here is that netmon is unstartable.
This is usually caused by netmon not being able to communicate with the SNMP agent on the server.
Do this:

snmpwalk 127.0.0.1 system
snmpwalk `hostname` system
snmpwalk <real IP Address> system

All of these should display the system information from the agent on the NetView server.

Another test would be:
ps -ef | grep sleep
There should not be a sleep process running. A sleep process running is an indication that netmon is waiting (sleeping) for SNMP agent to respond.

It sounds to me like you have a community name problem.

Don Davis

-----Original Message-----
From: Fission CC Lin [mailto:flin AT tw.ibm DOT com]
Sent: Wednesday, December 04, 2002 6:22 AM
To: nv-l AT lists.tivoli DOT com
Subject: [nv-l] daemon could not startup.....


Dear all,
   Attached is the netmnrc.ovstart which is the log of ovstart command. It
seems ovtopmd could not successfully start after a long waiting startup
time, then netmon and some other daemons never run. Where and how can I
find the trace log to fix the problem? please advise, thanks a lot.

Netview 7.1, on AIX 4.3.3, Framework 371(on TMR server)


 object manager name: OVsPMD
 behavior:            OVs PMD
 state:               RUNNING
 PID:                 43294
 exit status:         -

 object manager name: nvsecd
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 34614
 last message:        Initialization complete.
 exit status:         -

 object manager name: pmd
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 15692
 last message:        pmd completed initialization
 exit status:         -

 object manager name: OVORS M
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 63084
 last message:        orsd completed initialization
 exit status:         -

 object manager name: webserver
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 60094
 last message:        Initialization complete
 exit status:         -

 object manager name: snmpserver
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 22846
 last message:        Initialization complete
 exit status:         -

 object manager name: trapgend
 behavior:            OVs NON WELL BEHAVED
 state:               RUNNING
 PID:                 53954
 exit status:         -

 object manager name: mgragentd
 behavior:            OVs NON WELL BEHAVED
 state:               RUNNING
 PID:                 40406
 exit status:         -

 object manager name: ovactiond
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 28676
 last message:        Initialization complete.
 exit status:         -

 object manager name: nvcorrd
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 21554
 last message:        Initialization complete
 exit status:         -

 object manager name: nvpagerd
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 47272
 last message:        PMD initialization complete
 exit status:         -

 object manager name: actionsvr
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 16316
 last message:        Initialization complete
 exit status:         -

 object manager name: nvserverd
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 42900
 last message:        Initialization complete.
 exit status:         -

 object manager name: nvcold
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 39848
 last message:        Initialization complete.
 exit status:         -

 object manager name: nvlockd
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 55656
 last message:        Initialization complete.
 exit status:         -

 object manager name: trapd
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 66176
 last message:        Initialization complete.
 exit status:         -

 object manager name: ovwdb
 behavior:            OVs WELL BEHAVED
 state:               RUNNING
 PID:                 41990
 last message:        Initialization complete.
 exit status:         -

 object manager name: snmpCollect
 behavior:            OVs WELL BEHAVED
 state:               UNSTARTABLE
 PID:                 (never run)
 last message:
 exit status:         -

 object manager name: ovtopmd
 behavior:            OVs WELL BEHAVED
 state:               NOT RUNNING
 PID:                 57828
 last message:
 exit status:         exit(1)

 object manager name: netmon
 behavior:            OVs WELL BEHAVED
 state:               UNSTARTABLE
 PID:                 (never run)
 last message:
 exit status:         -

 object manager name: ems sieve agent
 behavior:            OVs WELL BEHAVED
 state:               UNSTARTABLE
 PID:                 (never run)
 last message:
 exit status:         -

 object manager name: ems log agent
 behavior:            OVs WELL BEHAVED
 state:               UNSTARTABLE
 PID:                 (never run)
 last message:
 exit status:         -

Best Regards,
Fission Lin, 林倩全
I / T Specialist  , Tivoli Professional Services,
ITS/SMBU/NSM,  IBM Taiwan
206, Sec.1 Keelung Rd, Taipei, Taiwan, R.O.C.
Tel:886-2-2725-8872, Mobile:0935-558622
E-Mail: flin AT tw.ibm DOT com

------------------------------------------------------------------------------
This electronic mail and any files transmitted with it are confidential and are intended solely for the use of individual or entity to whom they are addressed. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.

==============================================================================

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