Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

hp extensible snmp agent installation problems

Status
Not open for further replies.

patlv23

Programmer
May 23, 2002
31
PH
I'm not sure if i'm in the right place but here goes, thanks in advance:

I'm trying to install the hp extensible snmp agent A.04.01. I'm using Sun Solaris 2.6. Installation was done from cdrom. I was able to get this far:
************************************************************
# ./install

Do you want to install the manpages? (y|n): y
This installation will put the following software on your system:

SNMP Extensible Agent - SUNOS5.x version
SNMP Extensible Agent man pages


There are many factors that can affect the amount of time
this installation could take. However, it averages around
30 to 45 minutes.

Do you want to continue with this installation? (y|n): y
The installation should complete without further interaction.

WARNING: do NOT use the kill command or Control-C to get out
of this installation because that could leave your system in
a corrupt state.

If you want to closely track the progress of the installation,
open a separate terminal window and give the command:
tail -f /var/adm/sw/swagent.log
Notes and warnings will be written to this log as well as
indications of the installation's progress.


======= 07/24/02 18:38:37 HKT BEGIN swinstall SESSION (setup mode)

* The target "/" does not exist and will be created.

************************************************************

It stops right there, seems to hang. The log(/var/adm/sw/swagent.log) looks like this:

************************************************************

======= 07/24/02 18:38:37 HKT BEGIN install AGENT SESSION (pid=2345)
(jobid=setup-0001)

* Agent session started for user "root@pgsun02". (pid=2345)

* Beginning Analysis Phase.
* Source: pgsun02:/cdrom/extensible_agent_401/OVDEPOT
* Target: pgsun02:/
* Target logfile: pgsun02:/var/adm/sw/swagent.log
* Options:
loglevel 1
agent_auto_exit false
agent_timeout_minutes 10000
create_target_path true
use_alternate_source false
mount_all_filesystems true
autoreboot false
enforce_dsa true
install_setup_cmd /usr/lbin/sw/install_setup
system_prep_cmd /usr/lbin/sysadm/system_prep
system_file_path /stand/system
kernel_build_cmd /usr/lbin/kernel_build
kernel_path /stand/vmunix
install_cleanup_cmd /usr/lbin/sw/install_clean
uncompress_cmd /usr/contrib/bin/gunzip
retry_rpc 1

autorecover_product false
reinstall true
allow_downdate false
allow_multiple_versions false
allow_incompatible false
enforce_dependencies true
enforce_scripts true
enforce_kernbld_failure true
defer_configure false

reinstall_files true
reinstall_files_use_cksum true
write_remote_files true
compress_files false

* Reading source for product information.
* Reading source for file information.
* Checking mounted filesystems.

************************************************************

It seems to hang right there after the last line. no errors are displayed. it stays like this for over an hour then we have to kill it(even though they discourage it)
 
annoying....

Ok -- if you run mount or df does it have any trouble displaying any mounted filesystems? Are you using NFS to mount anything remote for instance? Mike
________________________________________________________________

"Experience is the comb that Nature gives us, after we are bald."

Is that a haiku?
I never could get the hang
of writing those things.
 
nope, no problems running those commands. there also aren't any remote file systems mounted. it used to but we recently reinstalled.

the server actually run into some major problems(panic). got it fixed a few days back with some patches. it screwed up again deleting /usr so a reinstall was done and the patches were reapplied. the agent was the first extra app we tried to install.
 
hmmmm doesn't look like you're out of the woods yet...

you sure you installed all of the patches you should need?

did you reinstall the same version of the OS or did you take the opportunity to install the latest and greatest? Mike
________________________________________________________________

"Experience is the comb that Nature gives us, after we are bald."

Is that a haiku?
I never could get the hang
of writing those things.
 
well, we installed the patches we had before. maybe we need another one. i'm not really sure how it works. not really a true admin. our unix gurus already left the company. o well...

we reinstalled the same version(2.6). Our client won't let us move up to the latest. have to be the same with their environment. really wish we would though.

hey btw, thanks a lot for your time. i'll give you a vote no matter how this turns out
 
Hi there patlv23, could you please post the script you are running for the installation?To check what is exactly trying to do or expecting to find...

Are you using a depot for the installation?Don´t you have a package compiled already for Solaris instead?

Regards,
vlan52
[sunshine] vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.
 
hello vlan52, actually i'm installing from cdrom. the installation is for solaris 2.5 but this is the same cd that was used to install some years back (i wasn't here yet). hmm, not sure what a depot is, sorry. read something about that in the script though. anyway, thanks for your help, heres the script:

############################################################################
# Conditions assumed for this installation to work smoothly.
# 1. The name of the depot that is being installed is OVDEPOT
# 2. The portion of SD that we are using is on the CD ROM and is under
# a directory named SD-SETUP-HP9, SD-SETUP-SUNOS or SD-SETUP-SOLARIS
# and that directory is located in the same place as this script.
############################################################################

. ./allcommon # This is a file of functions that are intended to be
# used by all product's install and remove scripts.

. ./common.nnm # This is a file of functions that are used by the NNM
# install and remove scripts. If you are modifying
# this file to acommodate a product other than NNM, you
# should replace this line with one that sources your
# common functions if there are any.

GetInstallBundles () {
########################################################################
#
# Purpose:
# Find out what bundle is being installed here
#
# Parameters:
# None
#
# Assumptions:
# The possible bundles are:
# NNMEngHP9full NNMEngHP9entry NNMEngHP9man
# NNMEngHP10full NNMEngHP10entry NNMEngHP10man
# NNMEngSun4full NNMEngSun4entry NNMEngSun4man
# NNMEngSun5full NNMEngSun5entry NNMEngSun5man
# NNMJpnHP9full NNMJpnHP9entry
# NNMJpnHP10full NNMJpnHP10entry
# NNMJpnSun5full NNMJpnSun5entry
# OVLicenseSvrHP9
# OVLicenseSvrHP10
# OVLicenseSvrSun4
# OVLicenseSvrSun5
#
# We install the OVLicenseSvr* bundle by default along with the
# other bundle(s).
#
# The only 2 languages offered are English and Japanese.
#
# If the user supplied bundle(s) to be installed, this function
# will not be called.
#
# Algorithm:
# Ask if the user wants English or Japanese
# Ask if the user ordered the full or entry product
# Ask if the user wants to install the man pages
# Use the results of all of these questions to formulate the
# bundle name(s)
# Also form the bundle description that will be used later to
# verify that this is what the user wants to install
#
# How to modify this function for other products:
# To make these modifications, you will need to know the full set of
# bundle names which make up your product offering.
#
# Determine what languages you will be supporting. If there is only
# one, remove the language question.
#
# I think that the full/entry question is only applicable for NNM
# so you will want to remove it.
#
# Add any other questions necessary to determine what the bundle
# name(s) will be. NOTE: do not ask any question of the user for
# which you could find an answer by interrogating the system.
#
# Assuming that you chose to bundle your man pages separately from
# your software, I would leave the man page question in.
#
# Modify the last case statement in this function to include cases
# for only those platforms you are supporting. For each of those
# platforms, do the correct string manipulation to form the bundle
# name(s) the user wants to install.
#
# Also, create the BUNDLEDESC string to specify in a more user
# readable form what is being installed.
#
########################################################################

case $OS in
HP9) NAME=HP9full
;;
HP10) NAME=HP10full
;;
SOLARIS) NAME=Sun5full
;;
esac
NUM_LANGS=0

while test 1
do
$ECHO
$ECHO "Do you want to install the manpages? (y|n): \c"
read INSTALL_MAN
case "$INSTALL_MAN" in
n*|N*)
INSTALL_MAN=noman
break
;;
y*|Y*)
INSTALL_MAN=man
break
;;
*) $ECHO "Incorrect response. Please enter either y or n."
;;
esac
done

case $OS in
HP9) BUNDLE=SNMPEAgntHPUX9x
BUNDLEDESC=" SNMP Extensible Agent - HPUX9.x version \n"
if [ "$INSTALL_MAN" = man ]; then
BUNDLEADDON=" SNMPEAgntHP9man"
BUNDLE=$BUNDLE$BUNDLEADDON
BUNDLEDESC="${BUNDLEDESC} SNMP Extensible Agent man pages \n"
fi
;;
HP10)
BUNDLE=SNMPEAgntHPUX10x
BUNDLE=$BUNDLE$BUNDLEADDON
BUNDLEDESC=" SNMP Extensible Agent - HPUX10.x version \n"
if [ "$INSTALL_MAN" = man ]; then
BUNDLEADDON=" SNMPEAgntHP10man"
BUNDLE=$BUNDLE$BUNDLEADDON
BUNDLEDESC="${BUNDLEDESC} SNMP Extensible Agent man pages \n"
fi
;;
SUNOS) BUNDLE=SNMPEAgntSunOS4x
BUNDLE=$BUNDLE$BUNDLEADDON
BUNDLEDESC=" SNMP Extensible Agent - SUNOS4.x version \n"
if [ "$INSTALL_MAN" = man ]; then
BUNDLEADDON=" SNMPEAgntSun4man"
BUNDLE=$BUNDLE$BUNDLEADDON
BUNDLEDESC="${BUNDLEDESC} SNMP Extensible Agent man pages \n"
fi
;;
SOLARIS) BUNDLE=SNMPEAgntSunOS5x
BUNDLE=$BUNDLE$BUNDLEADDON
BUNDLEDESC=" SNMP Extensible Agent - SUNOS5.x version \n"
if [ "$INSTALL_MAN" = man ]; then
BUNDLEADDON=" SNMPEAgntSun5man"
BUNDLE=$BUNDLE$BUNDLEADDON
BUNDLEDESC="${BUNDLEDESC} SNMP Extensible Agent man pages \n"
fi
;;
esac
} # GetInstallBundles


########################################################################
# main() starts here
#
# We have included the reinstall options on the swinstall command line
# because if there are problems, we want the user to be able to fix the
# problems and just run ./install again (rather than making them remove
# the product first).
#
# The write_remote_files option is set to true so that users can install
# files across an NFS mount to another system. One example for this is
# when the man pages for installed software are kept in one central
# location for several machines.
#
########################################################################

CMD=$0
CMDLINE=$*
BUNDLE=""
BUNDLEDESC=""
SWOPTIONS="-x reinstall=true -x reinstall_files=true -x write_remote_files=true -x logdetail=true"
OVDEPOT=""
DEPOT_NAME="OVDEPOT"
CDROM_PATH=""

CheckForRoot # See if the user is running as root

ParseInstallCommandLine $CMDLINE
# Determine what options are set

FindOS # Determine which platform we are
# installing on


FindSD # Determine where the SD bits are


FindDepot # Determine where the software depot is

if [ "$BUNDLESUPPLIED" != "true" ]; then
GetInstallBundles # If the user did not specify a bundle,
fi # then find out which one(s) to install

VerifyInstallContinue # Once the bundles are determined,
# show the user what will be installed
# and give them the chance to back out

if [ "$OS" = SUNOS ]; then # This is a workaround for a SunOS kernel
WorkaroundSunOSCrash # bug that we found. It does a dynamic
fi # kernel modification by loading a kernel
# module that we got from Sun. If this
# precaution is not taken, installing
# from a CD ROM will crash a SunOS system.

$SD_SETUP_PATH/swinstall $SWOPTIONS -s $OVDEPOT $BUNDLE

GiveInstallFeedback $? # Using the result of the swinstall
# command, let the user know what
# happened and what they should do next
 
tried again. system now has openview nnm 6.1 installed. same result except for a different message at the end

************************************************************
3 pgsun02:/cdrom/extensible_agent_401/>./install

Do you want to install the manpages? (y|n): y
This installation will put the following software on your system:

SNMP Extensible Agent - SUNOS5.x version
SNMP Extensible Agent man pages


There are many factors that can affect the amount of time
this installation could take. However, it averages around
30 to 45 minutes.

Do you want to continue with this installation? (y|n): y
The installation should complete without further interaction.

WARNING: do NOT use the kill command or Control-C to get out
of this installation because that could leave your system in
a corrupt state.

If you want to closely track the progress of the installation,
open a separate terminal window and give the command:
tail -f /var/adm/sw/swagent.log
Notes and warnings will be written to this log as well as
indications of the installation's progress.


======= 08/08/02 15:33:46 HKT BEGIN swinstall SESSION (setup mode)

* Target connection succeeded for "/".

************************************************************

'Target connection succeeded for "/".' used to be 'The target "/" does not exist and will be created.'

swagent.log still the same.
 
Hi patlv23,
Wondering if you ever got this resolved. I am running into the same problem.
Installing OpenView to get to NavisCore.
Regards,
twinemiller
 
Found it!
In case anyone else runs into this.
=========================================
This is due to the recent SunOS cluster patches.



Issue Symptoms:

./install_cvux script hangs after the below message

* Target connection succeeded for "/".

!!!!!!!!!!!!!!Hangs !!!!!!!!!!!!!!!!!!!!





Cause:

Recent SunOS cluster patches are conflicting with the install_cvux.


uranus# uname -a

SunOS uranus 5.6 Generic_105181-25 sun4u sparc SUNW,Ultra-60

uranus# ^^ Recent Cluster Patch Reference





Solution:

Remove the cluster patch. Need to do this one patch at a time.
======================================================

Troy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top