Re: nvcorrd exit on signal No. 9

[Geoffrey Cheng <gcheng@CA.IBM.COM>]

James,

     Yes, it's the only info. I've attached the ovstatus output as follows.
Thanks.

 
=============================================================================================
ovstatus: sent STATUS request to ovspmd
 object manager name: OVsPMD
 behavior:            OVs_PMD
 state:               RUNNING
 PID:                 19754
 exit status:         -

 object manager name: nvsecd
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 9788
 last message:        Initialization complete.
 exit status:         -

 object manager name: pmd
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 22406
 last message:        pmd completed initialization
 exit status:         -

 object manager name: OVORS_M
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 23480
 last message:        orsd completed initialization
ovstatus:: EOF from ovspmd, exiting
 exit status:         -

 object manager name: trapgend
 behavior:            OVs_NON_WELL_BEHAVED
 state:               RUNNING
 PID:                 20872
 exit status:         -

 object manager name: mgragentd
 behavior:            OVs_NON_WELL_BEHAVED
 state:               RUNNING
 PID:                 22154
 exit status:         -

 object manager name: nvpagerd
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 20364
 last message:        PMD initialization complete
 exit status:         -

 object manager name: nvserverd
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 21712
 last message:        Initialization complete.
 exit status:         -

 object manager name: nvcold
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 24034
 last message:        Initialization complete.
 exit status:         -

 object manager name: snmpCollect
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 25070
 last message:        Initialization complete.
 exit status:         -

 object manager name: nvlockd
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 19086
 last message:        Initialization complete.
 exit status:         -

 object manager name: gtmd
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 25844
 last message:        Initialization complete.
 exit status:         -

 object manager name: nvcorrd
 behavior:            OVs_WELL_BEHAVED
 state:               NOT_RUNNING
 PID:                 -
 last message:        Initialization complete
 exit status:         exited on signal 9

 object manager name: ovactiond
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 22990
 last message:        Initialization complete.
 exit status:         -

 object manager name: actionsvr
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 24274
 last message:        Initialization complete
 exit status:         -

 object manager name: netmon
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 25328
 last message:        Initialization complete.
 exit status:         -

 object manager name: trapd
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 23738
 last message:        Initialization complete.
 exit status:         -

 object manager name: ovtopmd
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 22756
 last message:        Initialization complete.
 exit status:         -

 object manager name: ems_sieve_agent
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 25586
 last message:
 exit status:         -

 object manager name: ems_log_agent
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 26102
 last message:
 exit status:         -

 object manager name: nvot_server
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 26360
 last message:        Initialization succeeded.
 exit status:         -

 object manager name: cmld
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 26450
 last message:        Initialization completed
 exit status:         -

 object manager name: JMAintegrator
 behavior:            OVs_NON_WELL_BEHAVED
 state:               RUNNING
 PID:                 24806
 exit status:         -

 object manager name: ahmclp
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 29078
 last message:        Initialization succeeded.
 exit status:         -

 object manager name: ahmdbserver
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 28824
 last message:        Initialization succeeded.
 exit status:         -

 object manager name: ovwdb
 behavior:            OVs_WELL_BEHAVED
 state:               RUNNING
 PID:                 16784
 last message:        Initialization complete.
 exit status:         -

Best Regards

Geoffrey Cheng
Senior Network Management Specialist
IBM Global Services
Tel: 905-316-5820
Fax: 905-316-4525
e-mail: gcheng@ca.ibm.com



James Shanks <James_Shanks@TIVOLI.COM> on 07/09/99 11:44:46 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L@UCSBVM.UCSB.EDU>

To:   NV-L@UCSBVM.UCSB.EDU
cc:
Subject:  Re: nvcorrd exit on signal No. 9





Hmmm.  A signal 9 is just that.  You can find out the meaning of any signal by
doing "man signal".  They are non-standard exits from UNIX.  Signal 9 is the
process being killed by the operating system or another process for some reason.

Is that the only info you get from doing ovstatus?

If so, I'd call Support and open a problem so someone can help figure this out.


James Shanks
Tivoli (NetView for UNIX) L3 Support



Geoffrey Cheng <gcheng@CA.IBM.COM> on 07/09/99 11:07:49 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L@UCSBVM.UCSB.EDU>

To:   NV-L@UCSBVM.UCSB.EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  nvcorrd exit on signal No. 9





Hi,

     I've met a problem with nvcorrd, when doing a ovstart, nvcorrd started for
a few seconds and then
     died silently, on signal no. 9. I've commented out all the rules in
ESE.automation, but the problem still
     exists. There is nothing shown up in nv6000.log file and nettl trace file.
Nobody is using the 1666 port
     either.

     Has anyone met the similar problem? meanwhile, the only sympton I can see
is the "exit on
     signal no.9. And I notice from time to time that some daemons do exit on
certain numbers, where
     I could find the definition of these exit code? There seems not in the
diagnostics guide or
     programmer's references.

     Thanks.

Best Regards

Geoffrey Cheng