Re: ovtopmd not starting

1998-09-21 15:31:44
Subject: Re: ovtopmd not starting
From: James_Shanks AT TIVOLI DOT COM
To: nv-l AT lists.tivoli DOT com
Date: Mon, 21 Sep 1998 15:31:44 -0400
It is not obvious whether you have the same problem or not.  That depends
upon what version of NetView you are running and whether a reboot solves
the problem or not.  And also on the circumstances under which the daemons
Did they die?  Did they core?  You didn't say.   How did they get down?

What version of NetView are you running?  An exit code of 225 in V5
indicates that you have not sourced the Tivoli directory as required in the
Release Notes.    If you are running V5, then you must issue
   .   /etc/Tivoli/setup_env.sh
before you issue ovstart from the command line.  Note that there is a space
between the starting dot (.) and the rest of the command

By the way, ovtopofix requires ovtopmd to be running.  That is the source
of your second error.

If you require immediate personal assistance, then I recommend opening a
call to Support and making it Sev 1.  That is appropriate if you cannot get
the system started or re-started.

James Shanks
Tivoli (NetView for UNIX) L3 Support

"Brook, Bryan S" <bryan.s.brook AT LMCO DOT 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 AT UCSBVM.UCSB DOT EDU>

cc:    (bcc: James Shanks)
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!!


RS6000/AIX 4.2.1

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