Thank you James. That was exactly it. The install proceeded without
incident after changing the file descriptors limit to 256 and restarting the
system. That's one that should be moved to the release notes.
By the way, when will NetView 6.0.2 be released?
Regis Ebersole
SRA International, Inc.
regis_ebersole@sra.com
---------------------------
From: owner-nv-l@tkg.com
Date: 03/01/2001 16:56:38
Subject: Re: [NV-L] NetView 6.0 installation problem on Solaris 2.6
Do a ulimit -a and check what the ulimits are for file descriptors
(nofiles(descriptors)). If this number exceeds 1024 then pmd will not
start on Solaris. This is covered by APAR IY14813. The APAR
circumvention recommends a ulimit 256 if you have problems with higher
numbers. The restriction is removed in 6.0.2 but that will not help you
now, of course.
The write up by the NetView Level 2 engineer (George deSocio) who worked on
this problem reads as follows:
To circumvent this problem, /etc/init.d/oserv.rc must be modified to
issue
the command "ulimit -n 256" prior to starting the oserv daemon (which
drives the NetView installation). oserv should then shutdown and
started
using the oserv.rc script. After NetView installation,
/etc/init.d/netnmrc
and /usr/OV/bin/netview should be changed to unconditionally set the
ulimit
to 256. Of course if the system default is changed to be 256, and the
box
rebooted, the oserv.rc and other changes are not necessary.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Ebersole, Regis" <Regis_Ebersole@sra.com>@tkg.com on 01/03/2001 04:23:25
PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'nv-l@tkg.com'" <nv-l@tkg.com>
cc:
Subject: [NV-L] NetView 6.0 installation problem on Solaris 2.6
On a fresh installation of NetView Server 6.0 on a Solaris 2.6 Managed Node
(Framework 3.7), the NetView script "run_customize" is running the script
"nv6000.base.obj.config", which is executing the following section of code:
if [ "$REGNAMES" != "" ] ; then # start newly-registered daemons
for name in $REGNAMES
do
dspmsg -s 5 nv6000.cat 9999 'Starting %s\n' $name >>$LOG
dspmsg -s 5 nv6000.cat 9999 'Starting %s\n' $name
ovstart $name || err_chk 1 bcfg_270 OVSTART "$name"
done
fi
As noted in "update.log", this runs successfully for awhile and then fails
on starting pmd:
NOTE: Configuring ovwdb
NOTE: Configuring nvsecd
NOTE: Starting nvsecd
NOTE: Starting ovwdb
mgragentd registered with snmpdx
* Making links....
* Running customize script for fileset OVCI-RUN.
NOTE: Registering pmd
NOTE: Registering OVORS_M
And fails for:
NOTE: Starting pmd
object manager name: pmd
behavior:OVs_WELL_BEHAVED
state:NOT_RUNNING
PID: 2242
last message:
exit status:exited on signal 11
ERROR: Unable to start pmd with ovstart.
ERROR: Unable to start pmd with ovstart.
ERR_0004_050
ERR_0004_050
.. at which point the installation stops. Has anyone seen this error?
Regis Ebersole
SRA International, Inc.
|