|
|
United States-English | |
|
|
 |
|
Software Distributor Administration Guide: HP-UX 11i v1, 11i v2, and 11i v3 > Appendix B Troubleshooting
Common Problems |
|
|
This section presents a selection of problems you might encounter and how to resolve them: Table B-2 Common Problems
If you see the following error message:
it means that the hostname you specified could not be found in the hosts database. Make sure you have typed the hostname correctly (you can use the nslookup command to verify hostnames). If the target hostname is not in the hosts database, but you know its network address, you can use it (in standard “dot” notation) in place of the hostname. If you see this error message:
it means SD-UX could not contact the daemon program on a specific target system. Note that this may occur even if you haven’t specified any targets, for example, if the daemon on your local host is not running. ResolutionIf the SD-UX daemon/agent is not installed on a given target system, you must install it before you can use SD-UX. If you’ve verified that the daemon/agent component has been installed on a target system and you still have trouble contacting it, check to see that the daemon is running:
Other possible causes for this problem are listed in the section “Connection Timeouts and Other WAN Problems ”. You can start the GUI in these ways:
When using the GUI, you might encounter these problems: ResolutionIf you have invoked the GUI on a remote system, you may see the following error messages:
Check that you have set the $DISPLAY environment variable correctly on the remote system to identify your display. If it is correct, you may have to enable the remote host to make connections to your X server via the xhost(1) command or by modifying your /etc/X*.hosts file.
the system is telling you that the file /usr/lib/sw/ui/smc_install_copy.ui must be installed on the system to run either swinstall or swcopy interactively or that the /usr/lib/sw/ui/smc_remove.ui file must be installed to run swremove. Make sure that the directory /usr/lib/sw/ui exists and includes the requested file. If the file does not exist, you must reinstall the SD-CMDS fileset from your OS media. Denial of access to SD-UX objects may have a number of causes, including: ResolutionGenerally, when SD-UX denies access to an object, a message tells you that you do not have the required access permission. Yet, it may be unclear which object is not accessible. For example, when you use swcopy to copy a product from system A to a depot, SD-UX checks these ACLs:
If any of these access permissions is absent, the whole operation is disallowed, and you must read the error message carefully to understanding the exact cause. To see more about what type of security or access problems exist, see the daemon log file on the target system: /var/adm/sw/swagentd.log The default ACLs make it fairly easy to administer ACLs, but do not always give the desired level of access control. When you change an ACL to restrict access, especially by removing the any_other read permission, you may restrict access in unexpected ways. Host entries are required for any destination systems for swcopy and swinstall operations. See Chapter 9: “SD-UX Security ” for a full discussion of the access tests performed or each operation. Since SD-UX stores ACLs in the file system as plain text files, you may try to edit them with a conventional editor. This can lead to unexpected corruption of the ACL. Most cases of this corruption simply result in a message indicating the corruption, but inserting additions to the ACL file without updating the num_entries value can result in unreported problems and cause SD-UX to deny access. A common failure could occur, for instance, if a you inserted user entry in the ACL file. This could push the any_otherentry down beyond the num_entries limit. The ACL manager would never read the any_other entry, and you would have access problems. The best guard against this situation is to always use the swacl command to manipulate ACLs. The default /var/adm/sw/security/secrets file contains a single entry:
If you wish to explicitly name all hosts from which controllers can be run, you must replace the -sdu- with a different default secret, or eliminate the entire entry. See Chapter 9: “SD-UX Security ” for a thorough discussion of the secrets file. The controller (for swinstall, swcopy, etc.) looks up the secret for the system on which it runs and passes it in an encrypted form to its agent. The agent receiving a request from the controller looks up the secret for the host from which the call comes, encrypts it, and compares the encryption to that provided by the controller. If the two secrets do not match, access is denied. If you have problems with this mechanism, make sure that all systems have matching entries. You can also revert to the old secrets file (/etc/newconfig/sd/secrets on 9.x and /usr/newconfig/var/adm/sw/security/secrets on 10.x) on all hosts, or simply copy a single secrets file to all hosts. You may encounter a problem in using cp, tar, cpio, dd, and other commands to copy images of depots for use on other systems. Depot and product ACLs in the image have built-in knowledge of the host on which the depot originated. In particular, an ACL default realm will be wrong and local users will be confused with users on the originating host. For example, attempts to add local users to the access list will, in fact, grant access to remote users. There is no way to alter the default realm of an ACL from that set when it is created. Another common problem with such images occurs if you import them to systems that cannot resolve all the hostnames (see resolver(4) and nslookup(1)) that exist in the ACLs. If your purpose is to create a “staged” installation, use swcopy to propagate the depot. This creates new ACLs, based on local templates, for each instance of the depot. If the sole intent of a depot is for such image distribution, you may wish to set the swpackage create_target_acls option to false to prevent ACL creation on the depot and products during the swpackage operation. This option creates tape and CD-ROM images. Depots and products without ACLs grant the local superuser all privileges, while all other users and systems have read access. Note that when you copy or install this ACL-less depot with swcopy or swinstall, the copies (installations) are automatically protected by ACLs based on templates on the destination host. When using swinstall or swcopy in an environment where network bandwidth is the “bottleneck,” the file transfer rate between source and target can become very slow. ResolutionThe compress_files=true option compresses files transferred from a source depot to a target. This can reduce network usage by approximately 50%; the exact amount of compression depends on the type of files. Binary files compress less than 50%, text files more. The greatest throughput improvements are seen when transfers are across a slow network (approximately 50kbyte/sec or less), and the source depot server is serving a few target hosts at a time.
If it is not clear that this option will help in your situation, compare the throughput of a few install or copy tasks (both with and without compression) before changing this option value. See Chapter 8: “Reliability and Performance ” for more information about performance options. Low-throughput, wide-area networks can cause SD-UX to encounter time-out problems when establishing and maintaining network connections with remote agents on other systems. If you see the following messages:
and you have verified that the system is up and the daemon program (swagentd) is running on it, it may be that network delays are causing the connection to time-out. ResolutionIncrease the time-out value used by SD-UX when performing Remote Procedure Calls (RPCs) by specifying a higher value for the rpc_timeout option, either via the command line or in the defaults file. RPC time-out values range from 0 to 9, with 9 being the longest time-out. The default RPC time-out value is 5. Note that these values do not represent any specific time units. See Appendix A for more information on the rpc_timeout option. Increasing the rpc_timeout can also help in situations where the target agents in an install or copy session are timing out when trying to contact the source agent. This problem is indicated by the following error messages in the agent log file:
Another factor that can affect RPC timeouts on a slow network is the choice of network protocol. SD-UX supports both UDP- and TCP-based communication (the default is TCP). TCP communication is more reliable on a WAN because it is connection-based. SD will fall back to a UDP connection if the TCP connection fails for some reason. The default binding can be set with the -x rpc_binding_info option. Note that the daemon program (swagentd) listens for both UDP- and TCP-based RPCs by default. See Appendix A for more information on the rpc_binding_info option. A final WAN-related issue may arise when using the interactive GUI. During the analysis and execution phases of an interactive session, each target agent is periodically polled for up-to-date status information. The polling_interval option can be used to control the number of seconds that elapse between successive status polls of a given target system. On networks where even this minor data transfer is a problem, you can increase this polling interval, thus decreasing the frequency of polling, and reducing an interactive session’s overall demands on the network. See Appendix A for more information on the polling_interval option. Your installation or copy operation runs out of space even though the disk space analysis succeeded. Upon further checking, you find that the results of the disk space analysis differ from the actual space available. ResolutionPossible causes of this problem:
A swpackage operation may fail because of the incorrect use of the end keyword in the Product Specification File (PSF). ResolutionThe end keyword marks the end of a depot, vendor, product, subproduct or fileset specification in a PSF. It requires no value and is optional. However, if you use it and it is incorrectly placed, the specification will fail. Check to make sure, if you use it, there is an end keyword for every object specification (especially the last one). If you want to reduce the contents of a SD-UX command logfile, follow this procedure: ResolutionTo reduce messages to a minimum, set the verbose command option to 0 in one of the option files or by using the -x option on the command line. For example, entering -x spackage.verbose=0 on the command line when you run swpackage would reduce the number of entries to the swpackage log to a minimum. See Appendix A for details about setting options. If you want to shorten (truncate) the SD-UX daemon logfile because it is getting too long, follow this procedure: ResolutionIf the daemon is currently running, DO NOT remove its logfile. The running daemon continues to log messages to its logfile even after you’ve removed it, causing any subsequent information to be lost. Also, the disk space used by the logfile will not be freed as long as the daemon is running. Instead, truncate the logfile by typing (as root): echo > /var/adm/sw/swagentd.log This replaces the previous data in the log with an empty string. If you inadvertently remove the daemon logfile while it is running, you must kill and restart the daemon if you want to see subsequent daemon log messages and free up the disk space used by the logfile. You can stop (kill) a daemon by typing: You can also kill and restart a currently running daemon by typing: If you are trying to access a tape depot and see the following error message in the daemon logfile, it means that the tape is either corrupt or is not in SD-UX format.
ResolutionMake sure that you have correctly specified the tape device and that the correct tape is in the drive. SD-UX only reads tapes that are in SD-UX format. For example, SD-UX does not read update format tapes. An installation may fail while only part way through the process. ResolutionSD-UX gives you several restart options:
swinstall or swremove fails with the following message:
ResolutionAnother SD command is running that prevents the swinstall or swremove command from running. Wait for that command to finish and try again. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
