HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- swinstall failure & backout (10.20)
Operating System - HP-UX
1833733
Members
2526
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
11-28-1999 06:17 AM
11-28-1999 06:17 AM
swinstall failure & backout (10.20)
What is the proper way to correct/fix the problem of a HP Patch or P.D.
Software that fails to install. This failure leaves an entry which is seen
using the swlist command even though it never installed. "swremove" refuses to
remove it since it fails analysis there also.
Reason for killing process:
It never got beyond the "preinstall" phase of install analysis. Had to be
killed for running too long and nothing happening. No errors are seen in the
analysis logs. Unable to find the process holding up the install.
Thank You
Rich
Software that fails to install. This failure leaves an entry which is seen
using the swlist command even though it never installed. "swremove" refuses to
remove it since it fails analysis there also.
Reason for killing process:
It never got beyond the "preinstall" phase of install analysis. Had to be
killed for running too long and nothing happening. No errors are seen in the
analysis logs. Unable to find the process holding up the install.
Thank You
Rich
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-1999 11:03 PM
11-28-1999 11:03 PM
Re: swinstall failure & backout (10.20)
If the product was installed but not properly configured, you'll be able to see
that with the following command:
swlist -l fileset -a state
The product will show either "installed" or "configured". If it shows just
"installed," you'll need to run swconfig to manually configure it, like so:
swconfig
If all else fails, you'll need to hack the directory structure under the
/var/adm/sw directory to "manually" remove the product, then rebuild the main
sd INDEX file, but this absolutely a last resort, and not recommended for the
weak-hearted.
MrNeil
that with the following command:
swlist -l fileset -a state
The product will show either "installed" or "configured". If it shows just
"installed," you'll need to run swconfig to manually configure it, like so:
swconfig
If all else fails, you'll need to hack the directory structure under the
/var/adm/sw directory to "manually" remove the product, then rebuild the main
sd INDEX file, but this absolutely a last resort, and not recommended for the
weak-hearted.
MrNeil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-1999 02:29 AM
12-01-1999 02:29 AM
Re: swinstall failure & backout (10.20)
If I understand properly, what you really want to be able to do is install the
product fully. The way to do this is to set the reinstall and reinstall_files
flags to true. This can be done from the command line or through an
interactive session.
Of course, this only helps if you can overcome the swinstall hang you
experienced the first time. Two things you may want to look at are measure and
your swinstall defaults. Measure can definitely interfere with swinstall.
Before any installation you should issue "mwa stop". Restart measurewear after
the installation with "mwa stop" (/opt/perf/bin/mwa if you require the full
path). I have also had installations hang with the out-of-the-box
/var/adm/sw/defaults file. I usually edit this with:
swinstall.rpc_binding_info = ncacn_ip_tcp:[2121] ncadg_ip_udp:[2121]
swinstall.rpc_timeout = 5
swinstall.retry_rpc = 9
swinstall.agent_timeout_minutes = 5
swinstall.polling_interval = 60
You may want to play with these values.
product fully. The way to do this is to set the reinstall and reinstall_files
flags to true. This can be done from the command line or through an
interactive session.
Of course, this only helps if you can overcome the swinstall hang you
experienced the first time. Two things you may want to look at are measure and
your swinstall defaults. Measure can definitely interfere with swinstall.
Before any installation you should issue "mwa stop". Restart measurewear after
the installation with "mwa stop" (/opt/perf/bin/mwa if you require the full
path). I have also had installations hang with the out-of-the-box
/var/adm/sw/defaults file. I usually edit this with:
swinstall.rpc_binding_info = ncacn_ip_tcp:[2121] ncadg_ip_udp:[2121]
swinstall.rpc_timeout = 5
swinstall.retry_rpc = 9
swinstall.agent_timeout_minutes = 5
swinstall.polling_interval = 60
You may want to play with these values.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-1999 09:20 AM
12-01-1999 09:20 AM
Re: swinstall failure & backout (10.20)
Neal,
I tried your suggestion & got a 'transient' state which verified that the
software didn't install. Good way to check that I never thought of. I do it
the hard way with examining the logs and /tmp location.
Anyhow, looked around for the main sd INDEX file. Looked in /var/adm/sw and
related spots. What's the name of the main Index file?? I could have missed it
somehow.
I seen a note from Alan Riggs here on mwa. Dang, I didn't know that it would
interfer with swinstall. Never thought of that one. Maybe HP would be good
enough to put a WARNING out. Don't install using swinstall while using the
Measureware Product.
I do have a problem with one other machine from quite awhile ago with an
aborted install so the name/location of the INDEX file helps.
Thanks both of you guys..
Rich
I tried your suggestion & got a 'transient' state which verified that the
software didn't install. Good way to check that I never thought of. I do it
the hard way with examining the logs and /tmp location.
Anyhow, looked around for the main sd INDEX file. Looked in /var/adm/sw and
related spots. What's the name of the main Index file?? I could have missed it
somehow.
I seen a note from Alan Riggs here on mwa. Dang, I didn't know that it would
interfer with swinstall. Never thought of that one. Maybe HP would be good
enough to put a WARNING out. Don't install using swinstall while using the
Measureware Product.
I do have a problem with one other machine from quite awhile ago with an
aborted install so the name/location of the INDEX file helps.
Thanks both of you guys..
Rich
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP