- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- HP Software Assistant (SWA) process
Operating System - HP-UX
1754143
Members
3578
Online
108811
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО12-17-2009 06:06 AM
тАО12-17-2009 06:06 AM
I have this scenario, two hpux 11.23 servers , one production (apollo), the other test (artemis)
I ran the swa and all the way thru the swinstall process on the test server (artemis) without a problem. (swinstall -s /u04/swadepot/swadepot and i previously updated the swa.conf file swcache=/u04/swadepot)
I ran the same process on the production server,but not the swinstall yet.
I find that there is no .depot file on the test server, and all the patches are in the path /u04/swadepot/swadepot... ?
On the production server a .depot file was created in /u04/swadepot/patch_bundles/hp-ux/QUALITYPACK/QPK1123_B.11.23.0912.082.depot and all the patches are in /u04/swadepot..
My question is (1)why isn't there a .depot file on the test server, would the swinstall have run if it didn't find a .depot in the /u04/swadepot/swadepot directory. (2)The .depot file isn't automatically deleted after a swinstall ? (3)Would a "swa cleanup -c 2" command have removed the .depot file. I mention this because in my notes i have noted that command, and since it's a test server i wouldn't have been concerned with attempting to re-appply any patches that the cleanup process might have deleted?
(4) When i finally run the swinstall on apollo
should it look like:swinstall -s /u04/swadepot/patch_bundles/hp-ux/QUALITYPACK/
QPK1123_B.11.23.0912.082.depot
I ran the swa and all the way thru the swinstall process on the test server (artemis) without a problem. (swinstall -s /u04/swadepot/swadepot and i previously updated the swa.conf file swcache=/u04/swadepot)
I ran the same process on the production server,but not the swinstall yet.
I find that there is no .depot file on the test server, and all the patches are in the path /u04/swadepot/swadepot... ?
On the production server a .depot file was created in /u04/swadepot/patch_bundles/hp-ux/QUALITYPACK/QPK1123_B.11.23.0912.082.depot and all the patches are in /u04/swadepot..
My question is (1)why isn't there a .depot file on the test server, would the swinstall have run if it didn't find a .depot in the /u04/swadepot/swadepot directory. (2)The .depot file isn't automatically deleted after a swinstall ? (3)Would a "swa cleanup -c 2" command have removed the .depot file. I mention this because in my notes i have noted that command, and since it's a test server i wouldn't have been concerned with attempting to re-appply any patches that the cleanup process might have deleted?
(4) When i finally run the swinstall on apollo
should it look like:swinstall -s /u04/swadepot/patch_bundles/hp-ux/QUALITYPACK/
QPK1123_B.11.23.0912.082.depot
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2009 06:16 AM
тАО12-17-2009 06:16 AM
Solution
Shalom,
PSB
(1)why isn't there a .depot file on the test server, would the swinstall have run if it didn't find a .depot in the /u04/swadepot/swadepot directory.
The swa create process failed. There should be logs as to exactly what happened.
(2)The .depot file isn't automatically deleted after a swinstall ? (3)Would a "swa cleanup -c 2" command have removed the .depot file.
What if you want to use the same depots on multiple system. Auto delete of the .depot file would make me a little annoyed with 50 odd HP-UX hosts to update off a single swa configuration (all our servers are the same, we don't need to run swa 50 times). This is probably a configurable option.
(3)Would a "swa cleanup -c 2" command have removed the .depot file.
This is worth testing so long as you don't need the .depot file for another system.
(4) When i finally run the swinstall on apollo
should it look like:swinstall -x autoreboot=true -x reinstall=false -s /u04/swadepot/patch_bundles/hp-ux/QUALITYPACK/
QPK1123_B.11.23.0912.082.depot \*
You need that \* to avoid going into interactive mode, unless you want to.
The two -x commands permit auto reboot and damaging reinstall of software you don't want to reinstall.
SEP
PSB
(1)why isn't there a .depot file on the test server, would the swinstall have run if it didn't find a .depot in the /u04/swadepot/swadepot directory.
The swa create process failed. There should be logs as to exactly what happened.
(2)The .depot file isn't automatically deleted after a swinstall ? (3)Would a "swa cleanup -c 2" command have removed the .depot file.
What if you want to use the same depots on multiple system. Auto delete of the .depot file would make me a little annoyed with 50 odd HP-UX hosts to update off a single swa configuration (all our servers are the same, we don't need to run swa 50 times). This is probably a configurable option.
(3)Would a "swa cleanup -c 2" command have removed the .depot file.
This is worth testing so long as you don't need the .depot file for another system.
(4) When i finally run the swinstall on apollo
should it look like:swinstall -x autoreboot=true -x reinstall=false -s /u04/swadepot/patch_bundles/hp-ux/QUALITYPACK/
QPK1123_B.11.23.0912.082.depot \*
You need that \* to avoid going into interactive mode, unless you want to.
The two -x commands permit auto reboot and damaging reinstall of software you don't want to reinstall.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
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
тАО12-17-2009 02:38 PM
тАО12-17-2009 02:38 PM
Re: HP Software Assistant (SWA) process
SWA does not create a serial depot (.depot file), but it does download them. The SWA process is:
1. Run a report with your favorite analyzers:
# swa report
2. Review report
Look over the data, preferrably in the HTML report. You may decide to ignore some issues using ~/.swa/ignore and reanalyze. Many SEC issues will not be fixed by a patch.
3. Create a depot
# swa get -t /var/tmp/myDepot
This will run in 2 phases. The first will download serial depots of patches and QPK bundles to the software cache. After this they will be copied into the specified depot.
4. Review ODeps and SII
Some patches have "soft" dependencies documented in the Other Dependencies section. Others may require special handling during installation listed in Special Installation Instructions. SWA will summarize this content for the depot in a readBeforeInstall.txt file at the depot root.
5. Install
# swinstall -s /var/tmp/myDepot -x patch_match_target=true
Note that the system being analyzed and the location of the depot in step #5 can be other systems on the network.
1. Run a report with your favorite analyzers:
# swa report
2. Review report
Look over the data, preferrably in the HTML report. You may decide to ignore some issues using ~/.swa/ignore and reanalyze. Many SEC issues will not be fixed by a patch.
3. Create a depot
# swa get -t /var/tmp/myDepot
This will run in 2 phases. The first will download serial depots of patches and QPK bundles to the software cache. After this they will be copied into the specified depot.
4. Review ODeps and SII
Some patches have "soft" dependencies documented in the Other Dependencies section. Others may require special handling during installation listed in Special Installation Instructions. SWA will summarize this content for the depot in a readBeforeInstall.txt file at the depot root.
5. Install
# swinstall -s /var/tmp/myDepot -x patch_match_target=true
Note that the system being analyzed and the location of the depot in step #5 can be other systems on the network.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP