Well, you're major problem is that trapd is not running. None of the
others will run until he does, so that's where you have to look.
Try starting /usr/OV/bin/trapd from the command line and see what you get.
Check /etc/services and make sure the nvtrapd entries for port 162 udp and
162 tcp are there. Is t possible you have something else running on the
box which has port 162? If anything else has trapd's port it will not
start. You could also try formatting the nettl logs
netfmt -f /usr/OV/log/nettl/LOG00 > "myfile"
and looking to see if there are trapd errors logged there.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Pretorius, Vynita" <VPretorius@fnb.co.za>@tkg.com on 01/24/2001 09:29:17
AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc:
Subject: RE: [NV-L] Upgrading nv6.0 to Nv6.0.1 more info
HI all
Sorry about the delay
I have attempted this again and again it has not worked but I have more
info.
I also have included the output from /usr/OV/bin/ovtopmd & trapd (my
LIBPATH
is set correctly) which follows the ovstart
I have checked to see that trapd and ovtopmd are not already running via ps
-ef
nvaix:/ # ovstop nvsecd
nvaix:/ # ovstop
ovstop: ovspmd is not running, use ovstart to start ovspmd
nvaix:/ # . /etc/Tivoli/setup_env.sh
nvaix:/ # ovstart nvsecd
nvaix:/ # ovstart
object manager name: trapd
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: 18860
last message:
exit status: exit(255)
object manager name: ovactiond
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: nvcorrd
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: actionsvr
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: nvserverd
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:
exit status: -
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: ovtopmd
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
nvaix:/ #
nvaix:/ # /usr/OV/bin/ovtopmd
Message Catalog System: Attempted to use TME message catalog software to
access
/usr/lib/nls/msg/En_US/ov_ip.cat which is not a valid TME message catalog.
Moving the TME message catalog directory to the front of NLSPATH
may correct this problem.
Message Catalog System: Attempted to use TME message catalog software to
access
/usr/lib/nls/msg/En_US/ov_ip.cat which is not a valid TME message catalog.
Moving the TME message catalog directory to the front of NLSPATH
may correct this problem.
ERROR: ovtopmd: Cannot connect to trapd
Closing databases.
Completed closing databases.
Closing event socket.
nvaix:/ # /usr/OV/bin/trapd
exec(): 0509-036 Cannot load program /usr/OV/bin/trapd because of the
following errors:
0509-130 Symbol resolution failed for trapd because:
0509-136 Symbol isNVEnterprise__FPUi (number 90) is not exported
from
dependent module
/usr/local/Tivoli/lib/aix4-r1/libems.a(libems.osh).
0509-136 Symbol isMLMEnterprise__FPUi (number 91) is not exported
from
dependent module
/usr/local/Tivoli/lib/aix4-r1/libems.a(libems.osh).
0509-192 Examine .loader section symbols with the
'dump -Tv' command.
Thanks
Vynita
-----Original Message-----
From: James_Shanks@tivoli.com [mailto:James_Shanks@tivoli.com]
Sent: Tuesday, December 19, 2000 1:02 AM
To: IBM NetView Discussion
Subject: Re: [NV-L] Upgrading nv6.0 to Nv6.0.1
I am sorry to hear about your difficulty but you haven't given us nearly
enough information to determine whta your problem was. This is the first
report of such a problem that I have heard, because the install part of
6.01 is the most exhaustively tested part of it. Verification installs and
re-installs dozens of times during system test.
What exit code or message was given for ovtopmd and trapd when you did
ovstatus? The others won't start if they don't. Are you sure there were
no other copies of them already running? What other daemons were running
at the time? Did you ovstop nvsecd and try again?
When you say you ran setupenv_sh did you ovstop nvsecd first? If you don't
bring down ovspmd and nvsecd, then re-running the environment scripts does
not good. All other daemons inherit their environment from ovspmd, so you
must get the environment right before he is started, and he is started by
the first ovstart command.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Pretorius, Vynita" <VPretorius@fnb.co.za>@tkg.com on 12/18/2000 03:09:28
PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "NV-L@tkg. com (E-mail)" <NV-L@tkg.com>
cc:
Subject: [NV-L] Upgrading nv6.0 to Nv6.0.1
Hi all
I have Netview 6.0 on AIX 4.3.3
I installed the netview server patch(6.0.1) onto my server, I did not
install the database patch because I presume from the ovtopmd configuration
it says use SQL database and it is set to no, and I did not install the
client as I don't have a client.
The patches installed successfully (just 2 warnings in the update.log).
However I could not start the daemons trapd, ovtopmd , ems* and a couple of
others.
I tried after running setupenv_sh to no avail , also reset_ci still
nothing.
I then backed out the change and the daemons came up without a problem on
6.0.
What is going wrong?.
Any help would be greatly appreciated.
Thanks
Vynita
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|