test

Sun Cluster 2.2 7/00 Release Notes

Undocumented Error Messages

The following error messages may be generated by Sun Cluster 2.2 7/00 Release, but are not included in the Sun Cluster 2.2 Error Messages Manual.

Sun Cluster HA for SAP Error Messages

The following error messages for Sun Cluster HA for SAP were omitted from the Sun Cluster 2.2 Error Messages Manual. 


SUNWcluster.ha.sap.stop_net.2076: proha:SUNWscsap_PRO: Found 2 leftover IPC objects for SAP instance, removing via cleanipc

This message indicates that during shutdown of the SAP central instance by the stop_net method, two IPC segments from the central instance were found. The stop_net code uses the SAP-supplied utility cleanipc to remove all IPC segments of the central instance during shutdown (and also before startup). This is to ensure a thorough shutdown as well as a clean startup. The error message is an informational message only, and is expected. No user action is required.


Graceful shutdown failed for oracle instance PRO, starting abort

This message indicates that the HA-Oracle oracle_db_shutdown script did not complete a graceful shutdown of the database within the timeout limit (30 seconds, by default). If the normal shutdown does not complete during the allowed time, then a shutdown abort is issued. This is an informational message and no user action is required.


SUNWcluster.ccd.ccdctl.4403: (error) checkpoint, ccdd, ticlts: RPC: Program not registered

This message indicates that the ccdadm command could not contact the ccdd demon for the requested operation--the RPC call clnt_create() failed. Verify that the cluster has been started on the current node, and the ccdd daemon is running.


SUNWcluster.clustd.transition.4010: cluster aborted on this node nodename

This message indicates that the current node is being aborted. Other error messages should indicate why this is occurring; check the scadmin.log log file in /var/opt/SUNWcluster.


reconf.pnm.3009: pnminit faced problems

This message is generated by the script /opt/SUNWcluster/bin/pnm. This script is called during step 1 of cluster reconfiguration, when PNM is initialized with pnminit. The error message appears if the execution of pnminit resulted in a non-zero exit. Reasons for a non-zero exit of pnminit include:

Check for any error messages logged to /var/opt/SUNWcluster/ccd/ccd.log, then restart the cluster reconfiguration.


SUNWcluster.reconfig.4018: Aborting--received abort request from nodename

This message indicates a request from a remote node to abort the current node. Use checksum to verify that the /etc/opt/SUNWcluster/conf/clustername.cdb files are identical on all nodes. If necessary, manually copy the most recent clustername.cdb file to all nodes, and then restart the cluster.

monitor_rpcbind Error Messages

The following error messages potentially produced by monitor_rpcbind were omitted from the Sun Cluster 2.2 Error Messages Manual.


SUNWcluster.monitor_rpcbind.1001: Invalid daemon:

This message indicates that the daemon name is set incorrectly. To remedy this, contact your Sun representative.


SUNWcluster.monitor_rpcbind.3001: Failed to restart rpcbind -w. Aborting this node.

This message indicates that rpcbind is not running on this node, and the system attempted unsuccessfully to restart it. The system will be aborted automatically. 


SUNWcluster.monitor_rpcbind.4502: rpcbind is not running -- manual reboot may be needed

This message indicates that rpcbind is not running on this node and could not be restarted automatically by the system. The system will be aborted automatically.


SUNWcluster.monitor_rpcbind.5001: rpcbind is not running but warm restart seems to be possible. Will attempt to restart.

This message indicates that rpcbind is not running on this node and an attempt will be made by the system to restart it. This is an informational message only; no user action is necessary.


SUNWcluster.monitor_rpcbind.5002: rpcinfo failed - no rpcbind.

This message indicates that the test for an active rpcbind failed, for whatever reason is specified in the message. This is an informational message only; no user action is necessary.


SUNWcluster.monitor_rpcbind.5003: rpcbind in process list but has not responded.

This message indicates that although rpcbind appears in the process table for the system, it has failed to respond to the fault monitor in the required time. The fault probe will be retried automatically. This is an informational message only; no user action is required. 


SUNWcluster.monitor_rpcbind.5010: rpcbind is not running on this node and cannot be restarted. This node will be aborted.

This message indicates that rpcbind is not running on this node and an unsuccessful attempt was made by the system to restart it. As a result this node will abort automatically. No user action is required.


SUNWcluster.monitor_rpcbind.5011: rpcbind is not running on this node and cannot be restarted. Selected action is to continue operation.

This message indicates that rpcbind is not running on this node and the system was unable to restart it. Because the fault monitor has been told not to abort the node, operation will continue. However, the Sun Cluster framework will not be able to reconfigure without operator intervention. Reboot the node manually to ensure correct operation. 


SUNWcluster.monitor_rpcbind.6000: Restarted the daemon rpcbind, pid= <pid>

This message indicates that rpcbind was not running on this node and was successfully restarted by Sun Cluster. No user action is required.

Framework Error Messages

The following error messages are potentially produced by the Sun Cluster process monitor facility. These messages were omitted from the Sun Cluster 2.2 Error Messages Manual.


SUNWcluster.pmf.1030: failfast_open: running with failfast in debug/disabled mode

This message indicates that the pmf daemon, pmfd, is running in debug mode. A non-responsive pmfd will not trigger a failfast panic while running in this mode. This is a notification message only. No action is required.


SUNWcluster.pmf.1031: pmfd_failfast_thread: re-armed in %lld ms, was expecting %lld ms with variance of %lld ms

The rpc.pmfd daemon registers with the failfast timer on startup, and then a reset thread is spawned to rearm the failfast timeout continuously. This warning message is printed when this reset thread is scheduled past the expected time plus some padding or variance time. The variance is set at 10% of rearm time initially (5.5 seconds), and then is incremented to twice the rearm time (10 seconds). This only affects the rate at which messages are printed, not the rearm time or the timeout. This warning message indicates an excessive workload on this node, which in turn is causing a delay in the scheduling of the pmfd failfast reset thread. Further delay of this thread could result in a failfast timeout. 


in.rdiscd[517]: setsockopt
(IP_DROP_MEMBERSHIP): Cannot assign requested address

This error message might be displayed when you stop a cluster node. The error is caused by a timing issue between the in.rdiscd daemon and the IP module. It is harmless and can be ignored safely.


WARNING: lockd: cannot contact statd (error 4), continuing.

On clusters using Sun Cluster HA for NFS on Solaris 7, this error message is displayed if the lockd daemon is killed before the statd daemon is fully running. This error message can be ignored safely.