Symantec VERITAS STORAGE FOUNDATION HP-UX - Manual (Page 62)

64
Storage Foundation Cluster File System problems
Resource temporarily unavailable
If the installation fails with the following error message on the console:
fork() failed: Resource temporarily unavailable
The value of
nkthread
tunable parameter nay 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 SAM (System
Administration Manager) interface, 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) and
sam
(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 the 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] :
Suggested solutions: check that
swagentd
is running. Check whether there is
an entry for the target system in
/etc/hosts
. If there is no entry, then ensure
the hosts file is not the primary lookup for the “hosts” entry.
Storage Foundation Cluster File System problems
If there is a device failure or controller failure to a device, the file system may
become disabled cluster-wide. To address the problem, unmount file system on
all the nodes, then run a full
fsck
. When the file system check completes, mount
all nodes again.