nv-l

Re: ovtopmd exit on signal 255?

2000-02-14 08:59:06
Subject: Re: ovtopmd exit on signal 255?
From: James Shanks <James_Shanks AT TIVOLI DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Mon, 14 Feb 2000 08:59:06 -0500
Signal 255 means you got a negative one (-1) return code trying to start that
daemon.
The usual cause for this is that the Tivoli environment is not sourced when
ovspmd is started, so when he start ovtopmd, ovtopmd cannot find the $LIBDIR
libraries to load.

You can fix this problem in the short run by stopping all the daemons, sourcing
the Tivoli enviornment, and then starting them
(1) ovstop nvsecd
(2)  .  /etc/Tivoli/setup_env.sh
(3) ovstart  -v

If don't want to source the Tivoli enviornment, then you can just stop all the
daemons (ovstop nvsecd) and start them with /etc/netnmrc.

Are you starting NetView out of cron?  use /etc/netnmrc

James Shanks
Tivoli (NetView for UNIX) L3 Support



Sean Davidson <sean.davidson AT MAIL.PUBLIX DOT COM> on 02/14/2000 08:30:21 AM

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

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  ovtopmd exit on signal 255?




Running NetView v5.1.1 on AIX 4.2.1 and Tiv 3.6.1. Any idea what would cause
ovtopmd to exit on signal 255 or what it means? Check
/usr/OV/PD/cores/ovtopmd and the other directories here for core dump files,
found nothing. Searched the rest of the system for a core dump, nothing.

Based on some stuff I've got running in cron, it looks like this problem is
occuring after a reboot of the system. I've had this same problem the past 3
weeks after
system reboots.

Anyways, here's what ovstatus shows for netmon and ovtopmd:

 object manager name: netmon
 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:                 15606
 last message:
 exit status:         exit(255)

To resolve the problem, I end up doing:

ovstop
ovstop nvsecd
ovstart nvsecd
ovstart

All the daemons come up and everything is fine. Any ideas???

__________________________
Thanks,
Sean Davidson

Sr. Network Systems Engineer
Publix Super Markets, Inc.
P.O. Box 32015
Lakeland, Fl. 33802-2015
Email - sean.davidson AT publix DOT com
Voice - (863) 686-8754 x6889
Fax - (863)616-5895


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