Veritas Storage Foundation 5.0.1 Cluster File System Administrator's Guide Extracts for the HP Serviceguard Storage Management Suite on HP-UX 11i v3

A Troubleshooting
This appendix contains the following topics:
• “Installation Issues” (page 35)
• “Cluster File System Problems” (page 36)
Installation Issues
If you encounter any issues installing CFS, refer to the following paragraphs for typical problems
and their solutions. You can also refer to the HP Serviceguard Storage Management Suite Release
Notes and the HP Serviceguard Storage Management Suite Read Before Installing document, if you
encounter an issue that is not included here.
Incorrect Permissions for Root on Remote System
The permissions are inappropriate. Make sure you have remote root access permission on each
system to which you are installing.
Checking communication with system01............... FAILED
Remote reams/rcp permissions not available on: system01
Correct permissions and continue
Continue? [Y/N]:
Suggested solution: You need to set up the systems to allow remote access using ssh or rsh.
NOTE: Remove remote shell permissions after completing the CFS installation and configuration.
Resource Temporarily Unavailable
If the installation fails with the following error message on the console:
fork() failed: Resource temporarily unavailable
The value of the nkthread tunable parameter may not be large enough. The nkthread tunable
requires a minimum value of 600 on all systems in the cluster. To determine the current value
of nkthread, enter:
# kctune –q nkthread
If necessary, you can change the value of nkthread using the System Management Homepage
(SMH) tool, or by running the kctune command. If you change the value of nkthread, the kernel
must be rebuilt for the new value to take effect. It is easier to change the value using SAM because
there is an option to process the new kernel immediately. See the kctune(1M) manual pages
for more information on tuning kernel parameters.
Inaccessible System
The system you specified is not accessible. This could be for a variety of reasons such as, the
system name was entered incorrectly, or the system is not available over the network.
Checking communication with system01................ FAILED
System not accessible : system01
Suggested solution: Verify that you entered the system name correctly; use the ping(1M)
command to verify accessibility of the host.If a system cannot access the software source depot,
either swagentd is not running on the target system or the swlist command cannot see the
source depot.
Correct /etc/{hosts, nsswitch.conf} and continue from here
Continue? [Y/N] :
Installation Issues 35