- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Issue during HP-UX boot phase
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 03:31 AM
тАО06-04-2007 03:31 AM
Issue during HP-UX boot phase
I'm installing a couple of rx2620 with HP-UX 11.23 March 06 and having a trouble on one of them (whereas they have been installed the same way).
During boot, the following service is started: /sbin/rc2.d/S910rstEMSlistener start
It fails, saying that Support Tool Manager is not installed, but in fact it is.
The problem is that this script is checking that a given fileset is present and then the version.
To do that, it redirects a swlist -l fileset to a file (that's ok) and then check the versions by retrieving field nb 3 (cut -f 3). But on the faulty system, version is in field 7 due to additional ^I in the file.
What is making the swlist l fileset output different?
Can this be fixed without fully reinstalling the server?
This is for an urgent deal ... if you have any clue !
Thanks,
Gerard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 03:34 AM
тАО06-04-2007 03:34 AM
Re: Issue during HP-UX boot phase
The EMSlistener requires inetd.conf entries. Make sure they are the same as a working server and then inetd -c
If that does not work, remove and reinstall the software.
I doubt full reinstallation is necessary.
swremove of the support tools and reinstallation should be sufficient if the ientd.conf chagnes don't fix it.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 03:44 AM
тАО06-04-2007 03:44 AM
Re: Issue during HP-UX boot phase
# Check for Sup-Tool-Mgr is added to support AR Media.
/usr/sbin/swlist -l fileset | grep -i Sup-Tool-Mgr.STM-SHLIBS > tmp$$
if [ $? -ne 0 ]; then
echo "WARNING: Support Tools Manager for HPUX systems is required "
echo " by ISEE to work properly. Install Support Tools Manager "
echo " for HPUX systems (version B.11.11.05.00 or higher) "
echo " before start using ISEE. "
rm -f tmp$$ > /dev/null
exit $ERROR
fi
VERSION_SUP=`cat tmp$$ | cut -f 3 | cut -f 1 -d ' '`
rm -f tmp$$ > /dev/null
if [[ "$VERSION_SUP" < "B.11.11.05.00" ]] ; then
echo "WARNING: Support Tools Manager for HPUX systems is required "
echo " by ISEE to work properly. Install Support Tools Manager "
echo " for HPUX systems (version B.11.11.05.00 or higher) "
echo " before start using ISEE. "
exit $ERROR
fi
First test is ok (swlist -l fileset finds an installed fileset) but second one is failing as it does a "cut -f 3" which returns nothing...
tmp$$ file contains:
Sup-Tool-Mgr.STM-SHLIBS^I^I^I^I^I^IB.11.23.06.07 HPUX Support Tools Manager Share Libraries $
with 6 ^I that I don't have on the working system where there are only 2
This results in the version field to be detected in field 7 instead of 3...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 04:00 PM
тАО06-04-2007 04:00 PM
Re: Issue during HP-UX boot phase
Hmm, why should grep be used when they can just put the fileset on the swlist.
>but second one is failing as it does a "cut -f 3" which returns nothing...
This is why you should use awk vs cut. awk would say it is always field 2.
>with 6 ^I that I don't have on the working system where there are only 2
Then there is a real problem. I have 3 tabs.
It appears that swlist is trying to be user friendly and align the version field based on the longest fileset name.
Running the following script gives:
$ itrc_awk_swlist.sh swlist.out
The longest is (30): Isee_EmsListener.ISEE-EMSLSTNR
When I give it the product, I get only 2 tabs:
$ swlist -l fileset Sup-Tool-Mgr | itrc_awk_swlist.sh -
The longest is (26): Sup-Tool-Mgr.STM-REL-NOTES
So as I said above, Sup-Tool-Mgr should be using awk and specify the exact fileset.
When you contact the Response Center you should mention this.
============
#!/usr/bin/ksh
# compute longest field1 in swlist output.
awk '
BEGIN { NAME=""; len=0 }
{
if (length($1) > len) {
len = length($1)
NAME=$1
}
}
END { print "The longest is (" len "):", NAME; }
' $1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 09:24 PM
тАО06-04-2007 09:24 PM
Re: Issue during HP-UX boot phase
thnks for your feedback, you're perfectly right.
And the latest version of OnlineDiag for HP-UX 11.23 have fixed this issue making the chage you suggested ;-)
However, I need to find out the right patch for this as we're building systems with a frozen HP-UX version as per customer requests and I can't roll to December 06 :-(
Gerard