Bryan,
If this is NetView 5.x, make sure that the Tivoli environment is sourced
before starting the daemons.
ovtopmd will not start, and will give you an exit code of 255, if the
Tivoli environment is not sourced when ovspmd is started.
Try this:
ovstop
ovstop nvsecd
. /etc/Tivoli/setup_env.sh (or whereever this script is on your system)
ovstart
If that does not solve the problem, you should open a pmr with support.
Scott Donohoo
Tivoli Customer Support Team (NetView for Unix)
"Brook, Bryan S" <bryan.s.brook@LMCO.COM> on 09/21/98 02:24:43 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Scott Donohoo/Tivoli Systems)
Subject: Re: ovtopmd not starting
We are having the same problem right now! Ovtopmd fails (with an exit code
of 255) which prevents netmon from starting which prevents the ovw (GUI)
from starting. Heres the details:
#ovstop everything shuts down but nvsecd
#ovstop nvsecd /usr/OV/service/nvstat shows all
Netview daemons are down
(Verified /usr/OV/sockets is emptied)
#ovstart This is where we get the
exit code of 255 for ovtopmd. No other messages are available. Then some
other daemons fail to even attempt starting.
If I try an ovtopfix, I get: "ERROR Couldnt open topology database: Cannot
connect to server: sys2: No such file or directory". I checked the
diagnosis guide for ovtopmd and nothing helped. We get a fair amount of
traps (~=4MB/ day) but I dont think that is beyond the realm of manageable.
We have cleaned out our topology database and still have the same problems.
Any questions, suggestions, or divine intervention requested!!
Thanks,
Bryan
RS6000/AIX 4.2.1
|