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

["Fission CC Lin" <flin@tw.ibm.com>]

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@tw.ibm.com