Symantec HP-UX Storage Foundation Cluster File System problems, Resource temporarily unavailable

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.

Image 62
Contents HP-UX Sfcfs Licensing and registration Technical supportPage Contents Chapter Upgrading the product Adding a node to a clusterInstalling and configuring the product Hardware overview Cluster platforms Fibre channel switchShared storage Packages installed with Sfcfs only Software componentsPackage Contents Packages Contents Optional packages for Sfcfs and Sfcfs HARequired HP-UX patches PHKL32272HP-UX Patch ID Description PHKL32430Product licensing PreinstallationRelease Notes Setting Path and Manpath environment variables Secure communicationRequirements Veritas Enterprise AdministratorPrerequisites Alternatively, remove the file /sbin/init.d/vmsa-serverInstalling the product Enter 1, 2 or 3 to be installed on all systems If you want to use rsh you must specify on the command lineEnter one or more system names to install Sfcfs Change directory to /dvdromConfiguring the Components Do you want to add another user to the cluster? y,n,q y Response file Using the log filesInstallation log file Summary fileEtc/llthosts Verifying the configuration filesLow Latency Transport configuration files Etc/llttabLog into system02 Checking Low Latency Transport operationOutput resembles # lltstat -p Etc/gabtab Group Membership and Atomic Broadcast configuration filesChecking Group Membership and Atomic Broadcast operation Checking cluster operation Output for an Sfcfs HA installation resemblesEnter the following command on any systems See the hastatus1M manualVerifying the configuration files #System Attribute Value Synchronizing time on Cluster File Systems Verifying agent configurationConfiguring VCS Typical VCS configuration file for Sfcfs file resembles Main.cf fileVCS application failover services Sfcfs HA OnlyVCS application failover services Upgrading the product Upgrade paths Preparing to upgrade the productPlanning the upgrade Complete the following tasks in advance of upgradingMP1 Full upgrade Upgrade OverviewPhased upgrade Upgrading from 3.5 to Change to the top-level directory on the disc# hastart Remove VRTSweb Replace it withRun through , , , and on rest of the nodes to be upgraded See the Veritas Cluster Server Installation Guide Run the following command on all the nodes to start VCS Upgrading from 4.1 to Install all the prerequisite patches and reboot the machines Etc/VRTSvcs/conf/config/main.cf file Full upgrade Etc/VRTSvcs/conf/config/main.cf file Upgrading the disk layout versions # umount /mnt1 Upgrading the disk layout versions Adding and removing a node Adding a node to a cluster Enter y to install Sfcfs on these systemsEnter the system name of the new node to install Sfcfs Change to the Sfcfs directoryEnter 1 or 2 to be installed on all systems Start VxVM on the system that has been addedOpen the VCS configuration for writing Configuring Sfcfs and CVM agents on the new nodeRun the following command Write the new VCS configuration to diskRemoving a node from a cluster Add shared disk groups to the cluster configurationCreate a /mnt on system03 and run the following commands Put the CVM resources back online, in the following order# rm /etc/vxfentab # rm /etc/vxfendg # ./uninstallsfcfs Removing a node from a cluster Enter the system names to uninstall Sfcfs Enter y to uninstall SfcfsUninstalling the product Installation issues Incorrect permissions for root on remote systemResource temporarily unavailable Storage Foundation Cluster File System problemsInaccessible system Unmount failures Mount failuresIf this error message displays Command failuresPerformance issues Following error message displaysHigh availability issues Network partition/jeopardyLow memory