sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
Appendix A # Error Messages This appendix lists the error messages that are generated by the Foundation Services and provides a brief summary of the possible cause of each error. The error messages are grouped by those produced during installation, those produced during runtime, and those produced when using the command-line interface. Each list appears in alphabetical order of error message. For information about the error messages that are produced by the Foundation Services, see the following sections: Introduction to Error Messages Error Messages Written During Installation Error Messages Written During Runtime Error Messages Written by Command-Line Tools ## Introduction to Error Messages All of the Foundation Services log error and information messages to the system log files. These messages can be processed by client programs or by the Node Management Agent. For information about how to configure system log files, see the Netra High Availability Suite Foundation Services 2.1 6/03 Cluster Administration Guide. This appendix lists some of the error messages that are produced by the error scenarios described in this book. This appendix does not contain an exhaustive list of error messages produced by the Foundation Services. All error messages have the following format:
    <date><nodeid><PID><stack><failed service or daemon><message>
The following output shows some sample error messages:
    1:Nov  8 10:05:20 b14-netra-4 CMM[547]: [ID 191875 local0.error]
    	S-CMM [Membership] (no_master_role) Cluster becomes stale
    3:Oct 24 15:47:20 b14-netra-4 statd[3162]: [ID 514559 daemon.error]
    	svc_tp_create: Could not register prog 100024 vers 1 on udp
    3:Oct 24 15:47:20 b14-netra-4 nhcrfsd[591]: [ID 191875 local0.error]
    	S-CORE  nhcrfsd' failed to stay up
    3:Oct 24 15:47:25 b14-netra-4 nfs: [ID 609386 kern.warning] WARNING:
    	lockd: cannot contact statd (error 4), continuing
    3:Oct 24 15:53:43 b14-netra-4 CMM[546]: [ID 191875 local0.error]
    	S-CMM   [PROBE] Node 173 becomes DOWN
## Error Messages Written During Installation ### Error Messages Written During Manual Installation `[nhcmm] `/etc/opt/SUNWcgha/not_configured` present => no action taken` The installation or configuration process has failed. `[nhwdt] `/etc/opt/SUNWcgha/not_configured` present => no action taken` The installation or configuration process has failed. ### Error Messages Written During Installation Using the `nhinstall` Tool The `nhinstall` tool is a script that runs a series of commands. If the `nhinstall` tool encounters an error during the installation, it issues a message to the console and stops. The error message indicates which command has failed. If the failing command is a Solaris command, the `nhinstall` tool indicates which Solaris command has failed. The `nhinstall` tool does not produce its own error messages. When the `nhinstall` tool encounters an error, it does not continue to search for other errors. You must fix the error, then relaunch the `nhinstall` tool from the point at which it failed. If the `nhinstall` tool encounters another error, it stops again. ## Error Messages Written During Runtime ### Error Messages Written by the Cluster Membership Manager `[%s] port undefined in `/etc/services`` Confirm that the `nhfs.conf` and `cluster_nodes_table` files are correctly configured. See the man pages in the Netra High Availability Suite Foundation Services 2.1 6/03 Reference Manual. `[%s/%s] port undefined in `/etc/services`` Confirm that the `nhfs.conf` and `cluster_nodes_table` files are correctly configured. See the man pages in the Netra High Availability Suite Foundation Services 2.1 6/03 Reference Manual. `Another CMM is running => exit` A second instance of the `nhcmmd` daemon attempted to start on the node. `[Config] %s does not exist, could not recreate %s` A cluster configuration file or its backup is missing. The file cannot be created. Confirm that the directory in which the file should exist has the correct access permissions. `[Config] Could not initialize Cluster nodes table (local)` Confirm that the `cluster_nodes_table` file is correctly configured. See the `cluster_nodes_table`(4) man page. `[Config] Could not initialize Cluster nodes table (NFS)` Confirm that the `cluster_nodes_table` file is correctly configured. See the `cluster_nodes_table`(4) man page. `[Config] Could not initialize minimal config` Confirm that the `target.conf` file is correctly configured. See the `target.conf`(4) man page. `[Config] Could not load backup configuration file` A cluster configuration file or its backup is missing. The file cannot be created. Confirm that the directory in which the file should exist has the correct access permissions. `[Config] Could not read Cluster nodes table` Investigate whether the `cluster_nodes_table` file is missing or inaccessible. `[Config] Could not read minimal configuration file` Investigate whether the `target.conf` file is missing or inaccessible. `[Config] Invalid domain id in file %s` Confirm that the `nhfs.conf` and `cluster_nodes_table` files are correctly configured. See the man pages in the Netra High Availability Suite Foundation Services 2.1 6/03 Reference Manual. `[Config] Invalid node id in file %s` Confirm that the `nhfs.conf` and `cluster_nodes_table` files are correctly configured. See the man pages in the Netra High Availability Suite Foundation Services 2.1 6/03 Reference Manual. `[Config] Invalid node name in file %s` Confirm that the `cluster_nodes_table` files is correctly configured. See the `cluster_nodes_table`(4) man page. `[Config] Minimal configuration files %s and %s cannot be accessed` Investigate whether the `target.conf` file is missing or inaccessible. `[Candidates] No master-eligible node` See Chapter 4, Recovering From Startup Problems on Master-Eligible Nodes. `[Config] Nodes number exceed cluster capacities` For information about the supported cluster configuration, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide `CURRENT NODE HAS LEFT CLUSTER` The current node does not belong to the master node domain. Confirm that the following are true: The node `domainid` is correct in the `nhfs.conf` file and the `cluster_nodes_table` file. The node name is correct in the `cluster_nodes_table` file. The node `domainid` is the same in the `nhfs.conf` file and the `cluster_nodes_table` file. The master node `domainid` is correct. `[Election] Unable to extract the best choice` No node is eligible to become the master node. Verify that the vice-master node is qualified, and that it is synchronized with the master node. See The Vice-Master Node Remains Unsynchronized After Startup. `[Membership] Could not access Cluster nodes table` Investigate whether the `cluster_nodes_table` file is missing or inaccessible. `[PROBE] a probe is already executed` Confirm whether the following are true: The node is present in the `cluster_nodes_table` file. The node name is unique in the `cluster_nodes_table` file. The `nodeid` is unique in the `cluster_nodes_table` file.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems