nv-l

[nv-l] Netview 6.0 Installation Problem on Solaris 2.7

2002-04-02 06:50:47
Subject: [nv-l] Netview 6.0 Installation Problem on Solaris 2.7
From: Kottos Kostas <K.Kottos AT asyk.ase DOT gr>
To: nv-l AT lists.tivoli DOT com
Date: Tue, 2 Apr 2002 14:50:47 +0300

Dear all, 

On a fresh installation of NetView Server 6.0 (we want to install 6.0.3
actually) on a Solaris 2.7 Managed Node
 (Framework 3.6.2B), installation stops with errors in FILE43.PKT. More
specifically, ovwdb crashes on signal 11. 
The output  of "update.log" is as  following:

-------------------------------------------------------------------- Start
update.log---------------------------------------------------

Mon Apr 1 18:58:17 EET DST 2002
Initializing the Tracing and Logging...
Done. 
=======  Mon Apr  1 18:58:19 EET DST 2002  BEGINNING NVCONFIGURE 
       * Running customize script for fileset OVMIN-LICENSE.
       *   Making links....
       * Running customize script for fileset OVMIN.
       *   Making links....
       * Running customize script for fileset OVWIN.
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
NOTE:    Starting pmd
NOTE:    Starting OVORS_M
       *   Making links....
       * Running customize script for fileset OVSNMP-RUN.
NOTE:    Stopping trapd
NOTE:    Starting trapd
       *   Making links....
       * Running customize script for fileset OVIPMAP.
NOTE:    Starting ovtopmd
 object manager name: ovtopmd
 behavior:            OVs_WELL_BEHAVED
 state:               UNSTARTABLE
 PID:                 (never run)
 last message:        
 exit status:         -

 object manager name: ovwdb
 behavior:            OVs_WELL_BEHAVED
 state:               NOT_RUNNING
 PID:                 3906
 last message:        Exited due to user request
 exit status:         exited on signal 11

ERROR:   Cannot start ovtopmd with ovstart.
ERROR:   Cannot start ovtopmd with ovstart.
ERR_0006_074
ERR_0006_074
+ dspmsg -s 5 nv6000.cat 9999 customize:    Failing customize with exit code
%s\n 2
+ 1>> /tmp/update.log
customize:    Failing customize with exit code 2
ERROR:     Customize script for fileset OVIPMAP exited with code 2.
ERR_cfgbf_001
nvconfigbf:    Failing doing configuration with exit code 2
base:    Failure running script or command
'/usr/OV/install/tools/nvconfigbf'
ERR_bcfg_210
base:    Failing base.config with exit code 2

------------------------------------------------------------- End
update.log-------------------------------------------------


 At this point the installation stops. Ovwdb crashes, producing a core file.
>From what I saw
in the list, a similar thing was happening with pmd and the answer given by
James Shanks
was to check on ulimits (system resources) for the number of  file
descriptors.

An output of ulimit -a on my Solaris produces:

 time(seconds)        unlimited
 file(blocks)         unlimited
 data(kbytes)         unlimited
 stack(kbytes)        8192
 coredump(blocks)     unlimited
 nofiles(descriptors) 64
 vmemory(kbytes)      unlimited

 Could this be a similar problem? Could someone please give me any hints?


 Thank you,

  Kostas Kottos
Athens Stock Exchange
K.Kottos AT asyk.ase DOT gr








 

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