The problem is ovtopmd and the exit 255 means that the actual return code
was -1, which means that some library could not be loaded. Usually this is
the result of trying to do ovstart without having first sourced the Tivoli
environment. To fix it, you must stop all the daemons, source the
environment, and restart them.
As root,
(1) ovstop nvsecd
(2) . /etc/Tivoli/setup_env.sh (don't omit the "dot space" to start
with)
(3) ovstart
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Scott.Bursik@fritolay.com on 11/02/2000 12:16:37 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: nv-l@tkg.com
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Netview Daemon startup errors
I am attempting to start Netview (6.0.1 AIX 4.3.2) and I get the following
information in the netnmrc.ovstart log. I have attempted to stop and
restart
with serversetup, as well as with smit. Nothing seems to work. PLEASE HELP!
Thanks a million.
Scott
object manager name: ovtopmd
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: 18364
last message:
exit status: exit(255)
object manager name: ems_sieve_agent
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: ems_log_agent
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: snmpCollect
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: netmon
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|