Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)
Table Of Contents
- Software Distributor Administration Guide
- Contents
- HP secure development lifecycle
- About This Document
- 1 Introduction to Software Distributor
- SD-UX Overview
- SD-UX Concepts
- Using the GUI and TUI Commands
- The Terminal User Interface
- Starting the GUI/TUI Commands
- Window Components
- Opening and closing items in the object list
- Marking Items in the Object List
- Preselecting Host Files
- Software Selection Window
- Session and File Management—The File Menu
- Changing Software Views—The View Menu
- Changing Options and Refreshing the Object List—The Options Menu
- Performing Actions—The Actions Menu
- Getting Help—The Help Menu
- XToolkit Options and Changing Display Fonts
- Working from the Command Line
- 2 Installing Software
- Installation with swinstall
- Features and Limitations
- Installing with the GUI
- Installing from the Command Line
- Installation Tasks and Examples
- Updating to HP-UX 11i
- Installing Patches
- Recovering Updated Files
- Installing Software That Requires a System Reboot
- Using Software Codewords and Customer IDs
- Re-installing Software Distributor
- Installing Multiple Versions
- Installing to an Alternate Root
- Compatibility Filtering and Checking
- Software Selection Checking
- Configuring Your Installation (swconfig)
- Verifying Your Installation (swverify)
- Installation with swinstall
- 3 Managing Installed Software
- 4 Managing Software Depots
- Depot Management Commands and Concepts
- Copying Software Depots
- Registering and Unregistering Depots (swreg)
- Verifying Signed Software Signatures
- Additional Depot Management Tasks and Examples
- Combining Patch Depots
- Creating a Tape Depot for Distribution
- Setting Depot Attributes
- Creating a Network Depot
- Managing Multiple Versions of HP-UX
- Listing Registered Depots
- Listing the Contents of a Depot (swlist -d)
- Source Depot Auditing
- Verifying a Depot (swverify -d)
- Removing Software from Depots
- Removing a Depot
- 5 HP-UX Patching and Patch Management
- 6 Using Jobs and the Job Browser
- 7 Remote Operations Overview
- 8 Reliability and Performance
- 9 SD-UX Security
- 10 Creating Software Packages
- Overview of the Packaging Process
- Identifying the Products to Package
- Adding Control Scripts
- Creating a Product Specification File (PSF)
- Product Specification File Examples
- PSF Syntax
- PSF Object Syntax
- Selecting the PSF Layout Version
- PSF Value Types
- Product Specification File Semantics
- Re-Specifying Files
- Packaging the Software (swpackage)
- Packaging Tasks and Examples
- Registering Depots Created by swpackage
- Creating and Mastering a CD-ROM Depot
- Compressing Files to Increase Performance
- Packaging Security
- Repackaging or Modifying a Software Package
- Packaging In Place
- Following Symbolic Links in the Source
- Generating File Revisions
- Depots on Remote File Systems
- Verifying the Software Package
- Packaging Patch Software
- Writing to Multiple Tapes
- Making Tapes from an Existing Depot
- 11 Using Control Scripts
- Introduction to Control Scripts
- General Script Guidelines
- Packaging Control Scripts
- Using Environment Variables
- Execution of Control Scripts
- Execution of Other Commands by Control Scripts
- Control Script Input and Output
- File Management by Control Scripts
- Testing Control Scripts
- Requesting User Responses (swask)
- Request Script Tasks and Examples
- 12 Nonprivileged SD
- A Command Options
- B Troubleshooting
- Error Logging
- Common Problems
- Cannot Contact Target Host’s Daemon or Agent
- GUI Won’t Start or Missing Support Files
- Access To An Object Is Denied
- Slow Network Performance
- Connection Timeouts and Other WAN Problems
- Disk Space Analysis Is Incorrect
- Packager Fails
- Command Logfile Grows Too Large
- Daemon Logfile Is Too Long
- Cannot Read a Tape Depot
- Installation Fails
- swinstall or swremove Fails With a Lock Error
- Use of Square Brackets ([ and ]) Around an IPv6 Address Causes an Error
- Some SD commands do not work after network configuration changes
- C Replacing or Updating SD-UX
- D Software Distributor Files and File System Structure
- Glossary
- Index

B Troubleshooting
This appendix explains how SD-UX error messages are used, reviews the SD-UX error logging
process, lists common problems you might encounter, and suggests how to resolve them.
Table 56 Chapter Topics
Topics:
“Error Logging ” (page 253)
“Common Problems ” (page 254)
Error Logging
All SD-UX commands (except swlist and swacl) log error messages, summary information about
the session, and operation details to a command-specific logfile located (by default) in
/var/adm/sw/<command>.log. For example, if you wanted to examine the logfile for
swinstall, you would look in the file /var/adm/sw/swinstall.log. You can also examine
target agent logfiles for a current session from the swinstall, swcopy, or swremove GUIs.
If you have log-in access to a target host, you can see its agent logfile(s) directly. The location of
the agent logfile varies, depending on the type of target:
• /var/adm/sw/swagent.log when operating on a host’s primary root.
• /<root_path>/var/adm/sw/swagent.log for an alternate root.
• /<depot_path>/swagent.log for a target or source depot.
The default location of a host’s daemon logfile is /var/adm/sw/swagentd.log. This logfile
contains information for problems starting agents, particularly for problems where you have access
denied to a depot or root.
NOTE: When both the source and target machine are updated to HP-UX 10.30 or later, the
system administrator at the source depot machine can track which user pulls which software from
a depot and when the software is pulled. Refer to the source_depot_audit option in Appendix A
(page 227) or “Source Depot Auditing” (page 100).
Error Messages
SD-UX error messages indicate that a problem occurred that will influence the overall outcome of
an operation.
For example, if a target in an install session fails the analysis phase due to insufficient disk space,
you would find the following error message in the agent log file:
ERROR: The estimated disk space used on filesystem "/" is
14104 Kbyte blocks. This operation will exceed the
minimum free space for this disk. You should free up at
least 2280 Kbyte blocks to avoid installing beyond this
threshold of available user disk space. If you are
running interactive "swinstall", you must return to the
Selection Window and Unmark this target before using
"swremove" to free disk space.
Warning Messages
Warning messages let you know that something unexpected and potentially undesirable occurred.
A warning does not prevent the SD session from continuing. Warning messages during analysis
of an interactive session give you the chance to continue or stop.
For example, if the fileset SD-DATABASE.SD-DATABASE2 is being installed in multiple locations
on a target system, you would find the following warning message in the agent log file:
Error Logging 253