Re: [nv-l] having problems starting ovtopmd

[George deSocio <desocio@us.ibm.com>]

NetView daemons are ALL stopped via
"/usr/OV/bin/ovstop nvsecd".  If you have another daemon
such as the tdwdaemon or another 3rd part daemon registered in ovsuf, you
will have to stop that too.  Basically when the last daemon is stopped
(normally nvsecd because all others are dependent), ovspmd will shut itself
down.


Regards,
Geo.

George deSocio
IBM Americas Support - Distributed Network Management
Dept 46-E1ZA
IBM B660  CC102
HWY 54 & 600 Park Offices
Research Triangle Park, NC  27709

919-254-2259 (T/L 444)  Fax: 919-543-7936 (T/L 441)

E-Mail:  desocio@us.ibm.com

Expand your IBM Tivoli product knowledge by participating in Support Technical
Exchange:
http://www-3.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html

Stephen Hochstetler/Austin/IBM@IBMUS Sent by: owner-nv-l@lists.us.ibm.com 01/23/2004 02:43 PM Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:                 Subject:        Re: [nv-l] having problems starting ovtopmd

Kevin,

There is an environment created when you do /etc/netnmrc that the programs
run in. Finding the right libraries is part of that. If you do the command
'ovstart ovtopmd', it is actually telling ovspmd to start ovtopmd. However,
if ovspmd was not started the right way, it will not have the proper environment
to pass onto ovtopmd. ovtopmd will die with the message that you see

Let's try to fix this by doing:

ovstop (this should stop all the daemons)

/etc/netnmrc (this should start all the daemons with the right environment
)


Stephen Hochstetler shochste@us.ibm.com
International Technical Support Organization at IBM
Office - 512-838-6198 (t/l 678) FAX - 512-838-6931
http://www.redbooks.ibm.com