Sun Cluster Error Messages Guide for Solaris OS

Message IDs 700000–799999

This section contains message IDs 700000–799999.

700123 first probe for N1 Grid Service Provisioning Systems Tomcat was unsuccessful, try again in 5 seconds

Description:

The first probe for the Tomcat will be rescheduled in 5 seconds

Solution:

None

700161 Fault monitor is already running.

Description:

The resource's fault monitor is already running.

Solution:

This is an internal error. Save the /var/adm/messages file from all the nodes. Contact your authorized Sun service provider.

700321 exec() of %s failed: %m.

Description:

The exec() system call failed for the given reason.

Solution:

Verify that the pathname given is valid.

700425 WebSphere MQ Broker RDBMS not available

Description:

The WebSphere MQ Broker is dependent on a WebSphere MQ Broker RDBMS, which is currently not available.

Solution:

No user action is needed. The fault monitor detects that the WebSphere MQ Broker RDBMS is not available and will restart the Resource Group.

701136 Failed to stop monitor server.

Description:

Sun Cluster HA for Sybase failed to stop monitor server using KILL signal.

Solution:

Please examine whether any Sybase server processes are running on the server. Please manually shutdown the server.

701567 Unable to bind door %s: %s

Description:

The cl_apid was unable to create the channel by which it receives sysevent messages. It will exit.

Solution:

Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

702094 HA: Secondary version %u does not support checkpoint method%d on interface %s.

Description:

One of the components is running at an unsupported older version.

Solution:

Ensure that same version of Sun Cluster software is installed on all cluster nodes.

702673 :Function: stop_sczsh - %s does not exist or is not executable in zone %s - early End

Description:

The command specified for variable ServiceStopCommand within the /opt/SUNWsczone/sczsh/util/sczsh_config configuration file is not executable or does not exist in the specified zone.

Solution:

Make sure that the command specified for variable ServiceStopCommand within the /opt/SUNWsczone/sczsh/util/sczsh_config configuration file is existing and executable for user root in the specified zone. If you do not want to re-register the resource, make sure the variable ServiceStopCommand is properly set within the ${PARAMETERDIR}/sczsh_${RS} parameterfile.

702748 Maxdelay = %lld Mindelay = %lld Avgdelay = %lld NumEv = %d\nMaxQlen = %d CurrQlen = %d\n

Description:

The cl_eventd is receiving and delivering messages with the specified delays, as calculated empirically during the lifetime of the daemon.

Solution:

This message is informational only, and does not require user action.

703156 scha_control GIVEOVER failed with error code: %s

Description:

Fault monitor had detected problems in Oracle listener. Attempt to switchover resource to another node failed. Error returned by API call scha_control is indicated in the message.

Solution:

Check Oracle listener setup. Please make sure that Listener_name specified in the resource property is configured in listener.ora file. Check 'Host' property of listener in listener.ora file. Examine log file and syslog messages for additional information.

703450 Despite the warnings, the validation of the hostname list succeeded

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

703476 clcomm: unable to create desired unref threads

Description:

The system was unable to create threads that deal with no longer needed objects. The system fails to create threads when memory is not available. This message can be generated by the inability of either the kernel or a user level process. The kernel creates unref threads when the cluster starts. A user level process creates threads when it initializes.

Solution:

Take steps to increase memory availability. The installation of more memory will avoid the problem with a kernel inability to create threads. For a user level process problem: install more memory, increase swap space, or reduce the peak work load.

703553 Resource group name or resource name is too long.

Description:

Process monitor facility is failed to execute the command. Resource group name or resource name is too long for the process monitor facility command.

Solution:

Check the resource group name and resource name. Give short name for resource group or resource .

703744 reservation fatal error(%s) - get_cluster_state() exception

Description:

The device fencing program has suffered an internal error.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available. Copies of /var/adm/messages from all nodes should be provided for diagnosis. It may be possible to retry the failed operation, depending on the nature of the error. If the message specifies the 'node_join' transition, then this node may be unable to access shared devices. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access shared devices. In either case, it may be possible to reacquire access to shared devices by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on all cluster nodes. If the failure occurred during the 'make_primary' transition, then a device group has failed to start on this node. If another node was available to host the device group, then it should have been started on that node. If desired, it may be possible to switch the device group to this node with the scswitch command. If no other node was available, then the device group will not have been started. The scswitch command may be used to retry the attempt to start the device group. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group has failed. The desired action may be retried.

704567 UNRECOVERABLE ERROR: Sun Cluster boot: Could not initialize cluster framework

Description:

Internal error.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

704710 INTERNAL ERROR: invalid failover delegate <%s>

Description:

A non-fatal internal error was detected by the rgmd. The target resource group for a strong positive affinity with failover delegation (+++ affinity) is invalid.

Solution:

Since this problem might indicate an internal logic error in the rgmd, please save a copy of the /var/adm/messages files on all nodes, the output of an scstat -g command, and the output of a scrgadm -pvv command. Report the problem to your authorized Sun service provider.

704731 Retrying retrieve of cluster information: %s.

Description:

An update to cluster configuration occured while cluster properties were being retrieved

Solution:

This is an informational message, no user action is needed.

705163 load balancer thread failed to start for %s

Description:

The system has run out of resources that is required to create a thread. The system could not create the load balancer thread.

Solution:

The service group is created with the default load balancing policy. If rebalancing is required, free up resources by shutting down some processes. Then delete the service group and re-create it.

705629 clutil: Can't allocate hash table

Description:

The system attempted unsuccessfully to allocate a hash table. There was insufficient memory.

Solution:

Install more memory, increase swap space, or reduce peak memory consumption.

705693 listen: %s

Description:

The cl_apid received the specified error while creating a listening socket. This error may prevent the cl_apid from starting up.

Solution:

Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

706159 Failed to switchover resource group %s: %s

Description:

An attempt to switchover the specified resource group failed. The reason for the failure is logged.

Solution:

Look for the message indicating the reason for this failure. This should help in the diagnosis of the problem.

706314 clexecd: Error %d from open(/dev/zero). Exiting.

Description:

clexecd program has encountered a failed open(2) system call. The error message indicates the error number for the failure.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

706550 start_sap_j2ee - Failed to start J2EE instance %s returned %s

Description:

The agent failed to start the specified J2EE instance.

Solution:

Check the logfile produced by the startsap script.

707421 %s: Cannot create a thread.

Description:

Solaris has run out of its limit on threads. Either too many clients are requesting a service, causing many threads to be created at once or system is overloaded with processes.

Solution:

Reduce system load by reducing number of requestors of this service or halting other processes on the system.

707863 :Function: validate - ServiceStopCommand (%s) not a fully qualified path.

Description:

The command specified for variable ServiceStopCommand within the /opt/SUNWsczone/sczsh/util/sczsh_config configuration file is not containing the full qualified path to it.

Solution:

Make sure the full qualified path is specified for the ServiceStopCommand, e.g. "/full/path/to/mycommand" rather than just "mycommand". This full qualified path must be accessible within the zone that command is being called.

707881 clcomm: thread_create failed for autom_thread

Description:

The system could not create the needed thread, because there is inadequate memory.

Solution:

There are two possible solutions. Install more memory. Alternatively, reduce memory usage. Since this happens during system startup, application memory usage is normally not a factor.

707948 launching method <%s> for resource <%s>, resource group <%s>, timeout <%d> seconds

Description:

RGM has invoked a callback method for the named resource, as a result of a cluster reconfiguration, scha_control GIVEOVER, or scswitch.

Solution:

This is an informational message, no user action is needed.

708422 Command {%s} failed: %s.

Description:

The command noted did not return the expected value. Additional information may be found in the error message after the ":", or in subsequent messages in syslog.

Solution:

This message is issued from a general purpose routine. Appropriate action may be indicated by the additional information in the message or in syslog.

708719 check_mysql - mysqld server <%s> not working, failed to connect to MySQL

Description:

The fault monitor can't connect to the specified MySQL instance.

Solution:

This is an error message from MySQL fault monitor, no user action is needed.

708825 Failed to validate IPMP group name <%s> pnm errorcode <%d>.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

709082 "pmfadm -k": Can not signal <%s>: Monitoring is not resumed on pid %d

Description:

The command 'pmfadm -k' can not be executed on the given tag because the monitoring is suspended on the indicated pid.

Solution:

Resume the monitoring on the indicated pid with the 'pmfctl -R' command.

709833 INITUCMM Warning: ucmmstate printmembers returned: ${exitcode}

Description:

The ucmmstate program returned error when checking membership.

Solution:

This message is informational; no user action is needed.

710143 Failed to add node %d to scalable service group %s: %s.

Description:

A call to the underlying scalable networking code failed.

Solution:

Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

711010 ERROR: start_mysql Option -R not set

Description:

The -R option is missing for start_mysql command.

Solution:

Add the -R option for start_mysql command.

711956 open /dev/ip failed: %s.

Description:

System was attempting to open the specified device, but was unable to do so.

Solution:

This might be the result of lack of the system resources. Check whether the system is low in memory and take appropriate action. For specific error information check the syslog message.

712367 clcomm: Endpoint %p: deferred task not allowed in state %d

Description:

The system maintains information about the state of an Endpoint. A deferred task is not allowed in this state.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

712437 Ignoring %s in custom action file.

Description:

This is an informational message indicating that an entry with an invalid value was found in the custom action file and will be ignored.

Solution:

Remove the invalid entry from the custom action file.

712591 Validation failed. Resource group property FAILBACK must be FALSE

Description:

The resource being created or modified must belong to a group that must have a value of FALSE for it's FAILBACK property.

Solution:

Specify FALSE for the FAILBACK property.

712665 ERROR: probe_mysql Option -U not set

Description:

The -U option is missing for probe_mysql command.

Solution:

Add the -U option for probe_mysql command.

713120 CMM: Reading reservations from quorum device %s failed.

Description:

An error was encountered while trying to read reservations on the specified quorum device.

Solution:

There may be other related messages on this and other nodes connected to this quorum device that may indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.

713428 Confdir_list must be an absolute path.

Description:

The entries in Confdir_list must be an absolute path (start with '/').

Solution:

Create the resource with absolute paths in Confdir_list.

714002 Warning: death_ff->disarm failed

Description:

The daemon specified in the error tag was unable to disarm the failfast device. The failfast device kills the node if the daemon process dies either due to hitting a fatal bug or due to being killed inadvertently by an operator. This is a requirement to avoid the possibility of data corruption. The daemon will produce a core file and will cause the node to halt or reboot

Solution:

Save a copy of the /var/adm/messages files on all nodes, and of the core file generated by the daemon. Contact your authorized Sun service provider for assistance in diagnosing the problem.

714123 Stopping the backup server.

Description:

The backup server is about to be brought down by Sun Cluster HA forSybase.

Solution:

This is an information message, no user action is needed.

714173 Load balancer setting distribution.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

714208 Starting liveCache timed out with command %s.

Description:

Starting liveCache timed out.

Solution:

Look for syslog error messages on the same node. Save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.

715958 Method <%s> on resource <%s> stopped due to receipt of signal <%d>

Description:

A resource method was stopped by a signal, most likely resulting from an operator-issued kill(1). The method is considered to have failed.

Solution:

The operator must kill the stopped method. The operator may then choose to issue an scswitch(1M) command to bring resource groups onto desired primaries, or re-try the administrative action that was interrupted by the method failure.

716253 launch_fed_prog: fe_set_env_vars() failed for program <%s>, step <%s>

Description:

The ucmmd server was not able to get the locale environment. An error message is output to syslog.

Solution:

Investigate if the host is running out of memory. If not save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

717827 error in configuration of SAA

Description:

Could not start SAA because of SAA configuration problems.

Solution:

Correct configuration of SAA, try manual start, and stop, re-enable in cluster.

718130 NFS daemon %s did not start. Will retry in 2 seconds.

Description:

While attempting to start the specified NFS daemon, the daemon did not start.

Solution:

This is an informational message. No action is needed. HA-NFS would attempt to correct the problem by restarting the daemon again. To avoid spinning, HA-NFS imposes a delay of 2 seconds between restart attempts.

718325 Failed to stop development system within %d seconds. Will continue to stop the development system in the background. Meanwhile, the production system Central Instance is started up now.

Description:

Failed to shutdown the development system within the timeout period. It will be continuously shutting down in the background. Meanwhile, the Central instance will be started up.

Solution:

No action needed. You might consider increasing the Dev_stop_pct property or Start_timeout property.

718457 Dispatcher Process is not running. pid was %d

Description:

The main dispatcher process is not present in the process list indicating the main dispatcher is not running on this node.

Solution:

No action needed. Fault monitor will detect that the main dispatcher process is not running, and take appropriate action.

718913 There is no SAP replica resource in the weak positive affinity resource group %s.

Description:

The weak positive affinity is set on the specified resource group (from the SAP enqueue server resource group). However, the specified resource group does not contain any SAP replica server resources.

Solution:

Create SAP replica server resource in the resource group specified in the error message.

719114 Failed to parse key/value pair from command line for %s.

Description:

The validate method for the scalable resource network configuration code was unable to convert the property information given to a usable format.

Solution:

Verify the property information was properly set when configuring the resource.

719497 clcomm: path_manager using RT lwp rather than clock interrupt

Description:

The system has been built to use a real time thread to support path_manager heart beats instead of the clock interrupt.

Solution:

No user action is required.

719997 Failed to pre-allocate swap space

Description:

The pmfd, fed, or other program was not able to allocate swap space. This means that the machine is low in swap space. The server does not come up, and an error message is output to syslog.

Solution:

Investigate if the machine is running out of swap. If this is not the case, save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

720239 Extension property <Stop_signal> has a value of <%d>

Description:

Resource property stop_signal is set to a value or has a default value.

Solution:

No user action is needed.

720746 Global service %s associated with path %s is unavailable. Retrying...

Description:

Self explanatory.

Solution:

This is an informational message, no user action is needed.

721252 cm2udlm: cm_getclustmbyname: %s

Description:

Could not create a structure for communication with the cluster monitor process.

Solution:

This is an internal error. Save the contents of /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log and /var/cluster/ucmm/dlm*/*logs/* from all the nodes and contact your Sun service representative.

721263 Extension property <stop_signal> has a value of <%d>

Description:

Resource property stop_signal is set to a value or has a default value.

Solution:

This is an informational message, no user action is needed.

721341 Service failed and the fault monitor is not running on this node.

Description:

The PMF action script supplied by the DSDL could not contact the monitor. The resource will be restarted by PMF if the following three conditions are true: Retry_interval has been defined, the current number of restart does is lower than RETRY_COUNT, and the resource is not in the START_FAILED state.

Solution:

Check if this is normal for the probe to not be running.

721396 Error modifying CRNP CCR table: unable to update client registrations.

Description:

The cl_apid experienced an error with the CCR table that prevented it from modifying the client registrations as requested.

Solution:

721490 Validate - 32 bit libloghost_32.so.1 is not secure

Description:

libloghost_32.so.1 is not found within /usr/lib/secure/libloghost_32.so.1

Solution:

Ensure that libloghost_32.so.1 is placed within /usr/lib/secure/libloghost_32.so.1 as documented within the Sun Cluster Data Service for Oracle Application Server for Solaris OS

721650 Siebel server not running.

Description:

Siebel server may not be running.

Solution:

This is an informative message. Fault Monitor should either restart or failover the Siebel server resource. This message may also be generated during the start method while waiting for the service to come up.

721881 dl_attach: kstr_msg failed %d error

Description:

Could not attach to the private interconnect.

Solution:

Reboot of the node might fix the problem.

722025 Function: stop_mysql - Sql-command SLAVE STOP returned error (%s)

Description:

Couldn't stop slave instance.

Solution:

Examine the returned Sql-status message and consult MySQL documentation.

722270 fatal: cannot create state machine thread

Description:

The rgmd was unable to create a thread upon starting up. This is a fatal error. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution:

Make sure that the hardware configuration meets documented minimum requirements. Save a copy of the /var/adm/messages files on all nodes, and of the rgmd core file. Contact your authorized Sun service provider for assistance in diagnosing the problem.

722332 Check SAPDB state with command %s.

Description:

Checking the state of the SAPDB database instance with the command which is listed.

Solution:

Informational message. No action is needed.

722368 node %s vm_on_node is %s

Description:

This is informational message indicating volume manager mode on this node.

Solution:

None

722439 Restarting using scha_control RESOURCE_RESTART

Description:

Fault monitor has detected problems in RDBMS server. Attempt will be made to restart RDBMS server on the same node.

Solution:

Check the cause of RDBMS failure.

722768 %s: could not get network addresses.

Description:

The daemon is unable to get net addresses of itself and caller.

Solution:

Need a user action for this message.

722904 Failed to open the resource group handle: %s.

Description:

An API operation has failed while retrieving the resource group property. Low memory or API call failure might be the reasons.

Solution:

In case of low memory, the problem will probably cured by rebooting. If the problem reoccurs, you might need to increase swap space by configuring additional swap devices. Otherwise, if it is API call failure, check the syslog messages from other components. For resource group name and the property name, check the current syslog message.

722984 call to rpc.fed failed for resource <%s>, resource group <%s>, method <%s>

Description:

The rgmd failed in an attempt to execute a method, due to a failure to communicate with the rpc.fed daemon. Depending on which method was being invoked and the Failover_mode setting on the resource, this might cause the resource group to fail over or move to an error state. If the rpc.fed process died, this might lead to a subsequent reboot of the node.

Solution:

723206 SAP is already running.

Description:

SAP is already running either locally on this node or remotely on a different node in the cluster outside of the control of the Sun Cluster.

Solution:

Need to shut down SAP first, before start up SAP under the control of Sun Cluster.

724035 Failed to connect to %s secure port %d.

Description:

An error occured while the fault monitor was trying to connect to a secure port specified in the Port_list property for this resource.

Solution:

Check to make sure that the Port_list property is correctly set to the same port number that the Netscape Directory Server is running on.

725027 ERROR: start_mysql Option -D not set

Description:

The -D option is missing for start_mysql command.

Solution:

Add the -D option for start_mysql command.

725087 CMM: Aborting due to stale sequence number. Received a message from node %ld indicating that node %ld has a stale sequence

Description:

After receiving a message from the specified remote node, the local node has concluded that it has stale state with respect to the remote node, and will therefore abort. The state of a node can get out-of-date if it has been in isolation from the nodes which have majority quorum.

Solution:

Reboot the node.

725933 start_samba - Could not start Samba server %s smb daemon

Description:

The Samba resource could not start the Samba server smbd process.

Solution:

The Samba resource will be restarted, however examine the other syslog messages occurring at the same time on the same node, to see if the cause of the problem can be identified.

726004 Invalid timeout value %d passed.

Description:

Failed to execute the command under the specified timeout. The specified timeout is invalid.

Solution:

Respecify a positive, non-zero timeout value.

726417 read %d for %sport

Description:

Could not get the port information from config file udlm.conf.

Solution:

Check to make sure udlm.conf file exist and has entry for udlm.port. If everything looks normal and the problem persists, contact your Sun service representative.

726682 ERROR: probe_mysql Option -G not set

Description:

The -G option is missing for probe_mysql command.

Solution:

Add the -G option for probe_mysql command.

727160 msg of wrong version %d, expected %d

Description:

udlmctl received an illegal message.

Solution:

None. udlm will handle this error.

728216 reservation error(%s) - did_get_path() error

Description:

The device fencing program has suffered an internal error.

Solution:

728425 INTERNAL ERROR: bad state <%s> (%d) for resource group <%s> in rebalance()

Description:

An internal error has occurred in the rgmd. This may prevent the rgmd from bringing the affected resource group online.

Solution:

Look for other syslog error messages on the same node. Save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.

728840 get_resource_dependencies - Resource_dependencies does not have a RDBMS resource

Description:

The WebSphere MQ Broker is dependent on the WebSphere MQ Broker RDBMS resource, which is not available. So the WebSphere MQ Broker will terminate.

Solution:

Ensure that the WebSphere MQ Broker RDBMS resource is defined within resource_dependencies when registering the WebSphere MQ Broker resource.

728881 Failed to read data: %s.Explanation Failed to read the data from the socket. The reason might be expiration of timeout, hung application or heavy load.

Solution:

Check if the application is hung. If this is the case, restart the appilcation.

728928 CCR: Can't access table %s on node %s errno = %d.

Description:

The indicated error occurred when CCR was tried to access the indicated table on the nodes in the cluster. The errno value indicates the nature of the problem. errno values are defined in the file /usr/include/sys/errno.h. An errno value of 28(ENOSPC) indicates that the root files system on the node is full. Other values of errno can be returned when the root disk has failed(EIO).

Solution:

There may be other related messages on the node where the failure occurred. They may help diagnose the problem. If the root file system is full on the node, then free up some space by removing unnecessary files. If the root disk on the afflicted node has failed, then it needs to be replaced. If the indicated table was accidently removed, boot the indicated node in -x mode to restore the indicated table from backup. The CCR tables are located at /etc/cluster/ccr/.

729152 clexecd: Error %d from F_SETFD. Exiting.

Description:

clexecd program has encountered a failed fcntl(2) system call. The error message indicates the error number for the failure.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

730190 scvxvmlg error - found non device-node or non link %s, directory not removed

Description:

The program responsible for maintaining the VxVM namespace had detected suspicious entries in the global device namespace.

Solution:

The global device namespace should only contain diskgroup directories and volume device nodes for registered diskgroups. The specified path was not recognized as either of these and should be removed from the global device namespace.

730685 PCSTATUS: %s

Description:

The rpc.pmfd server was not able to monitor a process, and the system error is shown. An error message is output to syslog.

Solution:

Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

730782 Failed to update scalable service: Error %d.

Description:

Update to a property related to scalability was not successfully applied to the system.

Solution:

Use scswitch to try to bring resource offline and online again on this node. If the error persists, reboot the node and contact your Sun service representative.

730956 %d entries found in property %s. For a nonsecure Netscape Directory Server instance %s should have exactly one entry.

Description:

Since a nonsecure Netscape Directory Server instance only listens on a single port, the list property should only have a single entry. A different number of entries was found.

Solution:

Change the number of entries to be exactly one.

731228 validate_options: $COMMANDNAME Option -G not set

Description:

The option -G of the Apache Tomcat agent command $COMMANDNAME is not set, $COMMANDNAME is either start_sctomcat, stop_sctomcat or probe_sctomcat.

Solution:

Look at previous error messages in the syslog.

731263 %s: run callback had a NULL event The run_callback() routine is called only when an IPMP group's state changes from OK to DOWN and also when an IPMP group is updated (adapter added to the group).

Solution:

Save a copy of the /var/adm/messages files on the node. Contact your authorized Sun service provider for assistance in diagnosing the problem.

731616 No memory.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

732069 dl_attach: DL_ERROR_ACK protocol error

Description:

Could not attach to the physical device.

Solution:

Check the documentation for the driver associated with the private interconnect. It might be that the message returned is too small to be valid.

732569 reservation error(%s) error. Not found clexecd on node %d.

Description:

The device fencing code was unable to cimmunicate with another cluster node.

Solution:

732643 scha_control: warning: cannot store %s restart timestamp for resource group <%s> resource <%s>: time() failed, errno <%d> (%s)

Description:

A time() system call has failed. This prevents updating the history of scha_control restart calls. This could cause the scha_resource_get (NUM_RESOURCE_RESTARTS) or (NUM_RG_RESTARTS) query to return an inaccurate value on this node. This in turn could cause a failing resource to be restarted continually rather than failing over to another node. However, this problem is very unlikely to occur.

Solution:

If this message is produced and it appears that a resource or resource group is continually restarting without failing over, try switching the resource group to another node. Other syslog error messages occurring on the same node might provide further clues to the root cause of the problem.

732787 bv1to1.conf.sh file is not found in the %s/etc directory

Description:

The bv1to1.conf .sh file is not accessible.

Solution:

Check if the file exists in $BV1TO1_VAR/etc/bv1to1.conf.sh.If the file exists in this directory check if the BV1TO1_VAR extension property is correctly set.

732822 clconf: Invalid group name

Description:

An invalid group name has been encountered while converting a group name to clconf_obj type. Valid group names are "cluster", "nodes", "adapters", "ports", "blackboxes", "cables", and "quorum_devices".

Solution:

This is an unrecoverable error, and the cluster needs to be rebooted. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.

732975 Error from scha_control() cannot bail out.

Description:

scha_control() failed to set resource to SCHA_IGNORE_FAILED_START.

Solution:

No user action needed.

733367 lkcm_act: %s: %s cm_reconfigure failed

Description:

ucmm reconfiguration failed.

Solution:

None if the next reconfiguration succeeds. If not, save the contents of /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log and /var/cluster/ucmm/dlm*/*logs/* from all the nodes and contact your Sun service representative.

734057 clcomm: Duplicate TypeId's: %s : %s

Description:

The system records type identifiers for multiple kinds of type data. The system checks for type identifiers when loading type information. This message identifies two items having the same type identifiers. This checking only occurs on debug systems.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

734832 clutil: Created insufficient threads in threadpool

Description:

There was insufficient memory to create the desired number of threads.

Solution:

Install more memory, increase swap space, or reduce peak memory consumption.

734890 pthread_detach: %s

Description:

The rpc.pmfd server was not able to detach a thread, possibly due to low memory. The message contains the system error. The server does not perform the action requested by the client, and an error message is output to syslog.

Solution:

Investigate if the machine is running out of memory. If all looks correct, save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

735336 Media error encountered, but Auto_end_bkp is disabled.

Description:

The HA-Oracle start method identified that one or more datafiles is in need of recovery. The Auto_end_bkp extension property is disabled so no further recovery action was taken.Action: Examine the log files for the cause of the media error. If it's caused by datafiles being left in hot backup mode, the Auto_end_bkp extension property should be enabled or the datafiles should be recovered manually.

735585 The new maximum number of clients <%d> is smaller than the current number of clients <%d>.

Description:

The cl_apid has received a change to the max_clients property such that the number of current clients exceeds the desired maximum.

Solution:

If desired, modify the max_clients parameter on the SUNW.Event resource so that it is greater than the current number of clients.

735753 INITUCMM Warning: all retries unsucessful, starting anyway

Description:

The ucmmd daemon was started after exhausting all the attempts to contact other cluster nodes and query their ucmm membership status. The ucmmd daemon will started on this node.

Solution:

Examine other syslog messages occurring at about the same time to determine whether there is any network problem. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

736390 method <%s> completed successfully for resource <%s>, resource group <%s>, time used: %d%% of timeout <%d seconds>

Description:

RGM invoked a callback method for the named resource, as a result of a cluster reconfiguration, scha_control GIVEOVER, or scswitch. The method completed successfully.

Solution:

This is an informational message, no user action is needed.

736551 File system checking is disabled for %s file system %s.

Description:

The FilesystemCheckCommand has been specified as '/bin/true'. This means that no file system check will be performed on the specified file system of the specified type. This is not advised.

Solution:

This is an informational message, no user action is needed. However, it is recommended to make HA Storage Plus check the file system upon switchover or failover, in order to avoid possible file system inconsistencies.

737104 Received unexpected result <%d> from rpc.fed, aborting node

Description:

This node encountered an unexpected error while communicating with other cluster nodes during a cluster reconfiguration. The ucmmd will produce a core file and will cause the node to halt or reboot.

Solution:

Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

737572 PMF error when starting Sybase %s: %s. Error: %s

Description:

Sun Cluster HA for Sybase failed to start sybase server using Process Monitoring Facility (PMF). Other syslog messages and the log file will provide additional information on possible reasons for the failure.

Solution:

Please whether the server can be started manually. Examine the HA-Sybase log files, sybase log files and setup.

738197 sema_wait child: %s

Description:

The rpc.pmfd server was not able to act on a semaphore. The message contains the system error. The server does not perform the action requested by the client, and an error message is output to syslog.

Solution:

Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

738847 clexecd: unable to create failfast object.

Description:

clexecd problem could not enable one of the mechanisms which causes the node to be shutdown to prevent data corruption, when clexecd program dies.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

739356 warning: cannot store start_failed timestamp for resource group <%s>: time() failed, errno <%d> (%s)

Description:

The specified resource group failed to come online on some node, but this node is unable to record that fact due to the failure of the time(2) system call. The consequence of this is that the resource group may continue to pingpong between nodes for longer than the Pingpong_interval property setting.

Solution:

Examine other syslog messages occurring around the same time on the same node, to see if the cause of the problem can be identified. If the same error recurs, you might have to reboot the affected node.

739653 Port number %d is listed twice in property %s, at entries %d and %d.

Description:

The port number in the message was listed twice in the named property, at the list entry locations given in the message. A port number should only appear once in the property.

Solution:

Specify the property with only one occurrence of the port number.

739997 endmqcsv - %s"

Description:

The following output was generated from the endmqcsv command.

Solution:

No user action is required if the command was successful. Otherwise, examine the other syslog messages occurring at the same time on the same node to see if the cause of the problem can be identified.

740373 Failed to get the scalable service related properties for resource %s.

Description:

An unexpected error occurred while trying to collect the properties related to scalable networking for the named resource.

Solution:

Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

740972 in fe_set_env_vars setlocale failed

Description:

The rgmd server was not able to get the locale environment, while trying to connect to the rpc.fed server. An error message is output to syslog.

Solution:

Investigate if the host is running out of memory. If not save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

741384 Failed to stop %s with SIGINT. Will try to stop it with SIGKILL.

Description:

The attempt to stop the specified application with signal SIGINT failed. Will attempt to stop it with signal SIGKILL.

Solution:

No user action is needed.

741451 INTERNAL ERROR: usage: `basename $0` <dbmcli-command> <User_Key> <Pid_Dir_Path> <DB_Name>

Description:

An internal error has occurred.

Solution:

Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

741561 Unexpected - test_qmgr_pid<%s>

Description:

The WebSphere MQ Broker is dependent on the WebSphere MQ Broker Queue Manager, however an unexpected error was found while checking the WebSphere MQ Broker Queue Manager.

Solution:

Examine the other syslog messages occurring at the same time on the same node to see if the cause of the problem can be identified.

742307 Got my own event. Ignoring...

Description:

the cl_eventd received an event that it generated itself. This behavior is expected.

Solution:

This message is informational only, and does not require user action.

742337 Node %d is in the %s for resource %s, but property %s identifies resource %s which cannot host an address on node %d.

Description:

All IP addresses used by this resource must be configured to be available on all nodes that the scalable resource can run on.

Solution:

Either change the resource group nodelist to exclude the nodes that cannot host the SharedAddress IP address, or select a different network resource whose IP address will be available on all nodes where this scalable resource can run.

742807 Ignoring command execution `<command>`

Description:

HA-Oracle reads the file specified in USER_ENV property and exports the variables declared in the file. Syntax for declaring the variables is : VARIABLE=VALUE If a command execution is attempted using `<command>`, the VARIABLE is ignored.

Solution:

Please check the environment file and correct the syntax errors by removing any entry containing a back-quote (`) from it.

743362 could not read failfast mode, using panic

Description:

/opt/SUNWudlm/etc/udlm.conf did not have an entry for failfast mode. Default mode of 'panic' will be used.

Solution:

None.

743571 Failed to configure sci%d adapter

Description:

The Sun Cluster Topology Manager (TM) has failed to add or remove a path using the SCI adapter.

Solution:

Make sure that the SCI adapter is installed correctly on the system. Also ensure that the cables have been setup correctly. If required please contact your authorized Sun service provider for assistance.

743923 Starting server with command %s.

Description:

Sun Cluster is starting the application with the specified command.

Solution:

This is an informational message, no user action is needed.

743995 Mismatch between the Failback policies for the resource group %s (%s) and global service %s (%s) detected.

Description:

HA Storage Plus detected a mismatch between the Failback setting for the resource group and the Failback setting for the specified DCS global service.

Solution:

Correct either the Failback setting of the resource group -or- the Failback setting of the DCS global service.

744544 Successfully stopped the local HADB nodes.

Description:

The resource was able to successfully stop the HADB nodes running on the local Sun Cluster node.

Solution:

This is an informational message, no user action is needed.

744866 Failed to check status of SUNW.HAStoragePlus resource.

Description:

An error occured while checking the status of the SUNW.HAStoragePlus resource that this resource depends on.

Solution:

Check syslog messages and correct the problems specified in prior syslog messages. If the error still persists, please report this problem.

745275 PNM daemon system error: %s

Description:

A system error has occured in the PNM daemon. This could be because of the resources on the system being very low. eg: low memory.

Solution:

If the message is: out of memory - increase the swap space, install more memory or reduce peak memory consumption. Otherwise the error is unrecovarable, and the node needs to be rebooted. can't open file - check the "open" man page for possible error. fcntl error - check the "fcntl" man page for possible errors. poll failed - check the "poll" man page for possible errors. socket failed - check the "socket" man page for possible errors. SIOCGLIFNUM failed - check the "ioctl" man page for possible errors. SIOCGLIFCONF failed - check the "ioctl" man page for possible errors. wrong address family - check the "ioctl" man page for possible errors. SIOCGLIFFLAGS failed - check the "ioctl" man page for possible errors. SIOCGLIFADDR failed - check the "ioctl" man page for possible errors. rename failed - check the "rename" man page for possible errors. SIOCGLIFGROUPNAME failed - check the "ioctl" man page for possible errors. setsockopt (SO_REUSEADDR) failed - check the "setsockopt" man page for possible errors. bind failed - check the "bind" man page for possible errors. listen failed - check the "listen" man page for possible errors. read error - check the "read" man page for possible errors. SIOCSLIFGROUPNAME failed - check the "ioctl" man page for possible errors. SIOCSLIFFLAGS failed - check the "ioctl" man page for possible errors. SIOCGLIFNETMASK failed - check the "ioctl" man page for possible errors. SIOCGLIFSUBNET failed - check the "ioctl" man page for possible errors. write error - check the "write" man page for possible errors. accept failed - check the "accept" man page for possible errors. wrong peerlen %d - check the "accept" man page for possible errors. gethostbyname failed %s - make sure entries in /etc/hosts, /etc/nsswitch.conf and /etc/netconfig are correct to get information about this host. SIOCGIFARP failed - check the "ioctl" man page for possible errors. Check the arp cache to see if all the adapters in the node have their entries. can't install SIGTERM handler - check the man page for possible errors. posting of an IPMP event failed - the system is out of resources and hence sysevents cannot be posted.

745455 %s: Could not call Disk Path Monitoring daemon to cleanup path(s)

Description:

scdidadm -C was run and some disk paths may have been cleaned up, but DPM daemon on the local node may still have them in its list of paths to be monitored.

Solution:

This message means that the daemon may declare one or more paths to have failed even though these paths have been removed. Kill and restart the daemon on the local node. If the status of one or more paths is shown to be "Failed" although those paths have been removed, it means that those paths are still present in the persistent state maintained by the daemon in the CCR. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

746255 Failed to obtain list of IP addresses for this resource

Description:

There was a failure in obtaining a list of IP addresses for the hostnames in the resource. Messages logged immediately before this message may indicate what the exact problem is.

Solution:

Check the settings in /etc/nsswitch.conf and verify that the resolver is able to resolve the hostnames.

747268 strmqcsv - %s

Description:

The following output was generated from the strmqcsv command.

Solution:

747567 Unable to complete any share commands.

Description:

None of the paths specified in the dfstab.<resource-name> file were shared successfully.

Solution:

The prenet_start method would fail. Sun Cluster resource management would attempt to bring the resource on-line on some other node. Manually check that the paths specifed in the dfstab.<resource-name> file are correct.

748729 clconf: Failed to open table infrastructure in unregister_infr_callback

Description:

Failed to open table infrastructure in unregistered clconf callback with CCR. Table infrastructure not found.

Solution:

Check the table infrastructure.

749409 clcomm: validate_policy: high not enough. high %d low %d in c %d nodes %d pool %d

Description:

The system checks the proposed flow control policy parameters at system startup and when processing a change request. For a variable size resource pool, the high server thread level must be large enough to allow all of the nodes identified in the message join the cluster and receive a minimal number of server threads.

Solution:

No user action required.

749681 The action to be taken as determined by scds_fm_action is failover. However the application is not being failed over because the failover_enabled extension property is set to false. The application is left as-is. Probe quitting ...

Description:

The application is not being restarted because failover_enabled is set to false and the number of restarts has exceeded the retry_count. The probe is quitting because it does not have any application to monitor.

Solution:

This is an informational message, no user action is needed.

749958 CMM: Unable to create %s thread.

Description:

The CMM was unable to create its specified thread and the system can not continue. This is caused by inadequate memory on the system.

Solution:

Add more memory to the system. If that does not resolve the problem, contact your authorized Sun service provider to determine whether a workaround or patch is available.

751079 scha_cluster_open failed

Description:

A call to initialize a handle to obtain cluster information failed. As a result, the incoming connection to the PNM daemon will not be accepted.

Solution:

There could be other related error messages which might be helpful. Contact your authorized Sun service provider to determine whether a workaround or a patch is available.

751205 Validate - WebSphere MQ Broker file systems not defined

Description:

The WebSphere MQ Broker file systems (/opt/mqsi and /var/mqsi) are not defined.

Solution:

Ensure that the WebSphere MQ Broker file systems are defined correctly.

751934 scswitch: rgm_change_mastery() failed with NOREF, UNKNOWN, or invalid error on node %d

Description:

An inter-node communication failed with an unknown exception while the rgmd was attempting to execute an operator-requested switch of the primaries of a resource group, or was attempting to "fail back" a resource group onto a node that just rejoined the cluster. This will cause the attempted switching action to fail.

Solution:

Examine other syslog messages occurring around the same time on the same node, to see if the cause of the problem can be identified. If the switch was operator-requested, retry it. If the same error recurs, you might have to reboot the affected node. Since this problem might indicate an internal logic error in the clustering software, please save a copy of the /var/adm/messages files on all nodes, the output of an scstat -g command, and the output of a scrgadm -pvv command. Report the problem to your authorized Sun service provider.

751966 IPMP group %s has tagged VLAN adapter(s) as well as untagged adapter(s). Can not verify if they belong to the same VLAN.

Description:

All adapters that participate in an IPMP group must host IP addresses from the same subnet. Sun Cluster has detected that the named IPMP group has both tagged VLAN adapters and untagged adapters that participate in the IPMP group. Sun Cluster can not determine if the are in the same VLAN.

Solution:

Make sure that the untagged adapters participate in the same VLAN as the tagged VLAN adapters.

752204 Cannot fork: %s

Description:

The cl_eventd was unable to start because it could not daemonize.

Solution:

752212 Failed to retrieve the resource handle: %s

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

752289 ERROR: sort_candidate_nodes: duplicate nodeid <%d> in Nodelist of resource group <%s>; continuing

Description:

The same nodename appears twice in the Nodelist of the given resource group. Although non-fatal, this should not occur and may indicate an internal logic error in the rgmd.

Solution:

Use scrgadm -pv to check the Nodelist of the affected resource group. Save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.

753155 Starting fault monitor. pmf tag %s.

Description:

The fault monitor is being started under control of the Process Monitoring Facility (PMF), with the tag indicated in the message.

Solution:

This is an information message, no user action is needed.

754046 in libsecurity: program %s (%lu); file %s not readable or bad content

Description:

The specified server was not able to read an rpcbind information cache file, or the file's contents are corrupted. The affected component should continue to function by calling rpcbind directly.

Solution:

Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

754283 pipe: %s

Description:

The rpc.fed server was not able to create a pipe. The message contains the system error. The server will not capture the output from methods it runs.

Solution:

Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

754521 Property %s does not have a value. This property must have exactly one value.

Description:

The property named does not have a value specified for it.

Solution:

Set the property to have exactly one value.

754848 The property %s must contain at least one SharedAddress network resource.

Description:

The named property must contain at least one SharedAddress.

Solution:

Specify a SharedAddress resource for this property.

755022 scf_value_create failed: %s

Description:

An API call failed.

Solution:

Examine log files and syslog messages to determine the cause of the failure. Take corrective action based on any related messages. If the problem persists, report it to your Sun support representative for further assistance.

755051 Unable to create %s service class

Description:

The specified entry could not be added to the dcs_service_classes table.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

755495 No reply from message server.

Description:

Probe did not get a response from the SAP message server.

Solution:

No user action needed.

756033 No hostname address found in resource group.

Description:

The resource requires access to the resource group's hostnames to perform its action

Solution:

Investigate if the hamasa resource type is correctly configured. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

756082 clcomm:Cannot fork() after ORB server initialization.

Description:

A user level process attempted to fork after ORB server initialization. This is not allowed.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

756517 Sent HUP signal to ucmmd

Description:

This is informational message. Signal was sent to ucmmd process.

Solution:

None

756650 Failed to set the global interface node to %d for IP %s: %s.

Description:

A call to the underlying scalable networking code failed.

Solution:

Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

757236 Error initializing LDAP library to probe %s port %d for non-secure resource %s: %s

Description:

An error occurred while initializing the LDAP library. The error message will contain the error returned by the library.

Solution:

Investigate if the machine is running out of memory. If this is not the case, save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

757581 Failed to stop daemon %s.

Description:

The HA-NFS implementation was unable to stop the specified daemon.

Solution:

The resource could be in a STOP_FAILED state. If the failover mode is set to HARD, the node would get automatically rebooted by the SunCluster resource management. If the Failover_mode is set to SOFT or NONE, please check that the specified daemon is indeed stopped (by killing it by hand, if necessary). Then clear the STOP_FAILED status on the resource and bring it on-line again using the scswitch command.

757758 scvxvmlg error - getminor called with a bad filename: %s

Description:

The program responsible for maintaining the VxVM namespace has suffered an internal error. If configuration changes were recently made to VxVM diskgroups or volumes, this node may be unaware of those changes. Recently created volumes may be unaccessible from this node.

Solution:

If no configuration changes have been recently made to VxVM diskgroups or volumes and all volumes continue to be accessible from this node, then no action is required. If changes have been made, the device namespace on this node can be updated to reflect those changes by executing '/usr/cluster/lib/dcs/scvxvmlg'. If the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.

757908 Failed to stop the application using %s: %s

Description:

An attempt to stop the application failed with the failure specified in the message.

Solution:

Save the syslog and contact your authorized Sun service provider.

759873 HA: exception %s (major=%d) sending checkpoint.

Description:

An unexpected return value was encountered when performing an internal operation.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

760001 (%s) netconf error: cannot get transport info for 'ticlts' %s

Description:

Call to getnetconfigent failed and udlmctl could not get network information. udlmctl will exit.

Solution:

Make sure the internconnect does not have any problems. Save the contents of /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log and /var/cluster/ucmm/dlm*/*logs/* from all the nodes and contact your Sun service representative.

760086 Could not find clexecd in nameserver.

Description:

There were problems making an upcall to run a user-level program.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

760337 Error reading %s: %s

Description:

The rpc.pmfd server was unable to open the specified file because of the specified error.

Solution:

Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

760354 modinstall of cldlpihb failed

Description:

The streams module that intercepts heartbeat messages could not be installed.

Solution:

Need a user action for this message.

760649 %s data services must have exactly one value for extension property %s.

Description:

One and only value may be specified in the specified extension property.

Solution:

Specify only one value for the specified extension property.

761076 dl_bind: DL_ERROR_ACK protocol error

Description:

Could not bind to the physical device. We are trying to open a fast path to the private transport adapters.

Solution:

Reboot of the node might fix the problem.

761122 INITUCMM ${UCMMSTATE} usage error : ${msg}

Description:

The ucmmstate program was invoked with incorrect options. This error message indicates that there can be a problem in installation of SUNWscucm package or patches.

Solution:

Check installation of SUNWscucm package using pkgchk command. Correct the installation problems and reboot the cluster node. Save a copy of the /var/adm/messages files on this node and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

761677 Cannot connect to message server.

Description:

Probe could not connect to the SAP message server.

Solution:

No user action needed.

762729 Some information from the CCR couldn't be cached. RGM performance will suffer.

Description:

Due to a previous error, the rgmd daemon was not able to initialize its configuration cache. As a result, the rgmd can still run, but slower than normal.

Solution:

Even though it is not fatal, the error is not supposed to happen and needs to be root-caused. Check the log for previous errors and report the problem to your authorized Sun service provider.

762902 Failed to restart fault monitor.

Description:

The resource property that was updated needed the fault monitor to be restarted inorder for the change to take effect, but the attempt to restart the fault monitor failed.

Solution:

Look at the prior syslog messages for specific problems. Correct the errors if possible. Look for the process <dataservice>_probe operating on the desired resource (indicated by the argument to "-R" option). This can be found from the command: ps -ef | egrep <dataservice>_probe | grep "\-R <resourcename>" Send a kill signal to this process. If the process does not get killed and restarted by the process monitor facility, reboot the node.

763570 can't start pnmd due to lock

Description:

An attempt was made to start multiple instances of the PNM daemon pnmd(1M), or pnmd(1M) has problem acquiring a lock on the file (/var/cluster/run/pnm_lock).

Solution:

Check if another instance of pnmd is already running. If not, remove the lock file (/var/cluster/run/pnm_lock) and start pnmd by sending KILL (9) signal to pnmd. PMF will restart pnmd automatically.

763781 For global service <%s> of path <%s>, local node is less preferred than node <%d>. But affinity switch over may still be done.

Description:

A service is switched to a less preferred node due to affinity switchover of SUNW.HAStorage prenet_start method.

Solution:

Check which configuration can gain more performance benefit, either to leave the service on its most preferred node or let the affinity switchover take effect. Using scswitch(1m) to switch it back if necessary.

763929 HA: rm_service_thread_create failed

Description:

The system could not create the needed thread, because there is inadequate memory.

Solution:

There are two possible solutions. Install more memory. Alternatively, reduce memory usage.

764662 Listener security is ON for %s. Using kill.

Description:

Informational message. HA-Oracle will kill listener rather than use 'lsnrctl stop'.

Solution:

None

764923 Failed to initialize the DCS.

Description:

HA Storage Plus was not able to connect to the DCS.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

765087 uname: %s

Description:

The rpc.fed server encountered an error with the uname function. The message contains the system error.

Solution:

Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

765395 clcomm: RT class not configured in this system

Description:

Sun Cluster requires that the real time thread scheduling class be configured in the kernel.

Solution:

Configure Solaris with the RT thread scheduling class in the kernel.

766093 IP address (hostname) and Port pairs %s%c%d%c%s and %s%c%d%c%s in property %s, at entries %d and %d, effectively duplicate each other. The port numbers are the same and the resolved IP addresses are the same.

Description:

The two list entries at the named locations in the named property have port numbers that are identical, and also have IP address (hostname) strings that resolve to the same underlying IP address. An IP address (hostname) string and port entry should only appear once in the property.

Solution:

Specify the property with only one occurrence of the IP address (hostname) string and port entry.

766316 Started saposcol process under PMF successfully.

Description:

The SAP OS collector process is started successfully under the control of the Process monitor facility.

Solution:

Informational message. No user action needed.

766385 Configuration file %s written from template file %s.

Description:

This is informational message. Configuration file specified in the message is written from template file to synchronize it with resource properties.

Solution:

None

766977 Error getting cluster state from CMM.

Description:

The cl_eventd was unable to obtain a list of cluster nodes from the CMM. It will exit.

Solution:

767363 CMM: Disconnected from node %ld; aborting using %s rule.

Description:

Due to a connection failure between the local and the specified node, the local node must be halted to avoid a "split brain" configuration. The CMM used the specified rule to decide which node to fail. Rules are: rebootee: If one node is rebooting and the other was a member of the cluster, the node that is rebooting must abort. quorum: The node with greater control of quorum device votes survives and the other node aborts. node number: The node with higher node number aborts.

Solution:

The cause of the failure should be resolved and the node should be rebooted if node failure is unexpected.

767488 reservation fatal error(UNKNOWN) - Command not specified

Description:

The device fencing program has suffered an internal error.

Solution:

767629 lkcm_reg: Unix DLM version (%d) and the OSD library version (%d) are not compatible. Unix DLM versions accepatble to this library are: %d

Description:

Unix DLM and Oracle DLM are not compatibale. Compatible versions will be printed as part of this message.

Solution:

Check installation procedure to make sure you have the correct versions of Oracle DLM and Unix DLM. Contact Sun service representative if versions cannot be resolved.

767858 in libsecurity unknown security type %d

Description:

This is an internal error which shouldn't occur. An error message is output to syslog.

Solution:

Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

768676 Failed to access <%s>: <%s>

Description:

The validate method for the SUNW.Event service was unable to access the specified command. Thus, the service could not be started.

Solution:

769000 Mount of %s failed. Trying an overlay mount.

Description:

HA Storage Plus was not able to mount the specified file system, but will retry with the Overlay flag.

Solution:

This is an informational message, no user action is needed.

769448 Unable to access the executable %s: %s.

Description:

Self explanatory.

Solution:

Check and correct the rights of the specified filename by using the chown/chmod commands.

769573 dl_info: bad ACK header %u

Description:

An unexpected error occurred. The acknowledgment header for the info request (to bind to the physical device) is bad. We are trying to open a fast path to the private transport adapters.

Solution:

Reboot of the node might fix the problem.

769687 Error: unable to initialize ORB.

Description:

The cl_apid or cl_eventd was unable to initialize the ORB during start-up. This error will prevent the daemon from starting.

Solution:

769999 Number of errors found: %ld

Description:

Indicates the number of errors detected before the processing of custom monitor action file stopped. The filename and type of errors would be indicated in a prior message.

Solution:

Please ensure that all entries in the custom monitor action file are valid and follow the correct syntax. After the file is corrected, validate it again to verify the syntax.

770355 fatal: received signal %d

Description:

The daemon indicated in the message tag (rgmd or ucmmd) has received a SIGTERM signal, possibly caused by an operator-initiated kill(1) command. The daemon will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution:

The operator must use scswitch(1M) and shutdown(1M) to take down a node, rather than directly killing the daemon.

770415 Extension properties %s and %s are both empty.

Description:

HA Storage Plus detected that no devices are to be managed.

Solution:

This is an informational message, no user action is needed.

770675 monitor_check: fe_method_full_name() failed for resource <%s>, resource group <%s>

Description:

During execution of a scha_control(1HA,3HA) function, the rgmd was unable to assemble the full method pathname for the MONITOR_CHECK method. This is considered a MONITOR_CHECK method failure. This in turn will prevent the attempted failover of the resource group from its current master to a new master.

Solution:

770776 INTERNAL ERROR: process_resource: Resource <%s> is R_BOOTING in PENDING_ONLINE resource group

Description:

The rgmd is attempting to bring a resource group online on a node where BOOT methods are still being run on its resources. This should not occur and may indicate an internal logic error in the rgmd.

Solution:

Look for other syslog error messages on the same node. Save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.

770790 failfastd: thr_sigsetmask returned %d. Exiting.

Description:

Internal error.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

771151 WebSphere MQ Queue Manager available

Description:

The WebSphere MQ Broker is dependent on the WebSphere MQ Broker Queue Manager. This message simple informs that the WebSphere MQ Broker Queue Manager is available.

Solution:

No user action is needed.

771340 fatal: Resource group <%s> update failed with error <%d>; aborting node

Description:

Rgmd failed to read updated resource group from the CCR on this node.

Solution:

Save a copy of the /var/adm/messages files on all nodes, and of the rgmd core file. Contact your authorized Sun service provider for assistance in diagnosing the problem.

772123 In J2EE probe, failed to determine Content-Length: in %s.

Description:

The reply from the J2EE engine did not contain a detectable contrnt length value in the http header.

Solution:

Informational message. No user action is needed.

772157 Failed to start the Node Agent %s using the command %s.

Description:

The Start method failed to start the Node Agent.

Solution:

Try starting the Node Agent manually using the asadmin command listed in the error message. If the Node Agent fails to start, check your configuration and try again. If Node Agent starts properly when started manually but the Sun Cluster agent cannot start it, report the problem.

772294 %s requests reconfiguration in step %s

Description:

Return status at the end of a step execution indicates that a reconfiguration is required.

Solution:

None.

772395 shutdown immediate did not succeed. (%s)

Description:

Failed to shutdown Oracle server using 'shutdown immediate' command.

Solution:

Examine 'Stop_timeout' property of the resource and increase 'Stop_timeout' if Oracle server takes long time to shutdown. and if you don't wish to use 'shutdown abort' for stopping Oracle server.

772658 INITRGM Error: ${PROCESS} is not started.

Description:

the rgmd depends on a server which is not started. The specified server probably failed to start. This error will prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.User Action Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

772953 Stop command %s returned error, %d.

Description:

The command for stopping the data service returned an error.

Solution:

No user action needed.

773078 Error in configuration file lookup (%s, ...): %s

Description:

Could not read configuration file udlm.conf.

Solution:

Make sure udlm.conf exists under /opt/SUNWudlm/etc and has the correct permissions.

773226 Server_url %s probe failed

Description:

The probing of the url set in the Server_url extension property failed. The agent probe will take action.

Solution:

None. The agent probe will take action. However, the cause of the failure should be investigated further. Examine the log file and syslog messages for additional information.

773366 thread create for hb_threadpool failed

Description:

The system was unable to create thread used for heartbeat processing.

Solution:

773690 clexecd: wait_for_ready worker_process. clexecd program has encountered a problem with the worker_process thread at initialization time.

Solution:

clexecd program will exit and node will be halted or rebooted to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

774752 reservation error(%s) - do_scsi3_inresv() error for disk %s

Description:

The device fencing program has encountered errors while trying to access a device. All retry attempts have failed.

Solution:

This may be indicative of a hardware problem, which should be resolved as soon as possible. Once the problem has been resolved, the following actions may be necessary: If the message specifies the 'node_join' transition, then this node may be unable to access the specified device. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access the device. In either case, access can be reacquired by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on all cluster nodes. If the failure occurred during the 'make_primary' transition, then a device group may have failed to start on this node. If the device group was started on another node, it may be moved to this node with the scswitch command. If the device group was not started, it may be started with the scswitch command. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group may have failed. If so, the desired action may be retried.

774767 Start of HADB node %d failed with exit code %d.

Description:

The resource encountered an error trying to start the HADB node.

Solution:

Examine other syslog messages occurring around the same time on the same node, to see if the source of the problem can be identified.

775342 Failed to obtain replica information for global service %s associated with path %s: %s.

Description:

The DCS was not able to obtain the replica information for the specified global service.

Solution:

Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.

775696 Unable to unlock file: %s.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

776074 INITUCMM Error: ucmmstate ucmm_membership returned: ${exitcode}

Description:

The ucmmstate program returned error when checking membership. If the message appears continuously and the ucmmd daemon fails to start, this node will not be able to run OPS/RAC.

Solution:

Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

776199 (%s) reconfigure: cm error %s

Description:

ucmm reconfiguration failed.

Solution:

776339 INTERNAL ERROR: postpone_stop_r: meth type <%d>

Description:

A non-fatal internal error has occurred in the rgmd state machine.

Solution:

777984 INITFED Error: Can't start ${SERVER}.

Description:

An attempt to start the rpc.fed server failed. This error will prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.

Solution:

778629 ERROR: MONITOR_STOP method is not registered for ONLINE resource <%s>

Description:

A non-fatal internal error has occurred in the rgmd state machine.

Solution:

778674 start_mysql - Could not start mysql server for %s

Description:

GDS couldn't start this instance of MySQL.

Solution:

Look at previous error messages.

779073 in fe_set_env_vars malloc of env_name[%d] failed

Description:

The rgmd server was not able to allocate memory for an environment variable, while trying to connect to the rpc.fed server, possibly due to low memory. An error message is output to syslog.

Solution:

Investigate if the host is running out of memory. If not save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

779089 Could not start up DCS client because we could not contact the name server.

Description:

There was a fatal error while this node was booting.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

779511 SAPDB is down.

Description:

SAPDB database instance is not available. The HA-SAPDB will restart it locally or fail over it to another available cluster node. Messages in the SAPDB log might provide more information regarding the failure.

Solution:

Informational message. No action is needed.

779544 "pmfctl -R": Error resuming pid %d for tag <%s>: %d

Description:

An error occured while rpc.pmfd attempted to resume the monitoring of the indicated pid, possibly because the indicated pid has exited while attempting to resume its monitoring.

Solution:

Check if the indicated pid has exited, if this is not the case, Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

779953 ERROR: probe_mysql Option -R not set

Description:

The -R option is missing for probe_mysql command.

Solution:

Add the -R option for probe_mysql command.

780204 Property %s not set to '%s' for %s. INIT method was not run or has failed on this node.

Description:

A property of the specified SMF service was not set to the expected value. This could cause unpredictable behavior of the service and failure to detect faults.

Solution:

If possible, update the property value manually using 'svccfg' commands. This could also be done by running the INIT method manually or re-creating the resource. If problem persists, please contact your Sun support representative for further assistance.

780283 clcomm: Exception in coalescing region - Lost data

Description:

While supporting an invocation, the system wanted to combine buffers and failed. The system identifies the exception prior to this message.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

780298 INITPMF Error: Can't start ${SERVER}.

Description:

An attempt to start the rpc.pmfd server failed. This error will prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.

Solution:

780539 Stopping fault monitor: %s:%ld:%s

Description:

Fault monitor has detected an error. Fault monitor will be stopped. Error detected by fault monitor and action taken by fault monitor is indicated in message.

Solution:

None

780792 Failed to retrieve the resource type information.

Description:

A Sun cluster dataservice has failed to retrieve the resource type's property information. Low memory or API call failure might be the reasons.

Solution:

781114 ERROR: probe_sap_j2ee Option -L not set

Description:

The -L option is missing for the probe_command.

Solution:

Add -L option to the probe-command.

781445 kill -0: %sExplanation The rpc.fed server is not able to send a signal to a tag that timed out, and the error message is shown. An error message is output to syslog.

Solution:

Save the syslog messages file. Examine other syslog messages occurring around the same time on the same node, to see if the cause of the problem can be identified.

781731 Failed to retrieve the cluster handle: %s.

Description:

An API operation has failed while retrieving the cluster information.

Solution:

This may be solved by rebooting the node. For more details about API failure, check the messages from other components.

782111 This list element in System property %s is missing a protocol: %s.

Description:

The system property that was named does not have a valid format. The value of the property must include a protocol.

Solution:

Add a protocol to the property value.

782497 Ignoring command execution $(command)

Description:

Solution:

Please check the environment file and correct the syntax errors by removing any entry containing a $(command) construct from it.

782603 INITUCMM Error: ${UCMMSTATE} not an executible.

Description:

The /usr/cluster/lib/ucmm/ucmmstate program does not exist on the node or is not executable. This file is installed as a part of SUNWscucm package. This error message indicates that there can be a problem in installation of SUNWscucm package or patches.

Solution:

Check installation of SUNWscucm package using pkgchk command. Correct the installation problems and reboot the cluster node. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

782694 The value returned for property %s for resource %s was invalid.

Description:

An unexpected value was returned for the named property.

Solution:

Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

782871 Not attempting to start Resource Group <%s> on node <%s>, because one or more Resource Groups for which it has Resource Group dependencies are not online.

Description:

The rgmd is enforcing the resource group dependencies. This behavior is normal and expected.

Solution:

No action required. If desired, use scrgadm(1M) to change the resource group dependencies.

783130 Failed to retrieve the node id for node %s: %s.

Description:

API operation has failed while retrieving the node id for the given node.

Solution:

Check whether the node name is valid. For more information about API call failure, check the messages from other components.

783199 INTERNAL ERROR CMM: Cannot bind device type registry object to local name server.

Description:

This is an internal error during node initialization, and the system can not continue.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

783581 scvxvmlg fatal error - clconf_lib_init failed, returned %d

Description:

Solution:

784157 clq_netapp: thread_create failed for door_call_thread. Quorum Device will be unavailable.

Description:

An internal error occurred when creating a thread to communicate with the NetApp NAS quorum device. The device will be in failed state.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

784311 Network_resources_used property not set properly

Description:

There are probably more than 1 logical IP addresses in thisresource group and the Network_resources_used property is not properly set to associate the Resources to the appropriatebackend hosts.

Solution:

Set the Network_resources_used property for each resource in the RG to the logical IP address in the RG that is actually configured to run BV backend processes.

784499 validate_options: $COMMANDNAME Option -R not set

Description:

The option -R of the Apache Tomcat agent command $COMMANDNAME is not set, $COMMANDNAME is either start_sctomcat, stop_sctomcat or probe_sctomcat.

Solution:

Look at previous error messages in the syslog.

784560 resource %s status on node %s change to %s

Description:

This is a notification from the rgmd that a resource's fault monitor status has changed.

Solution:

This is an informational message, no user action is needed.

784571 %s open error: %s Continuing with the scdpmd defaults values

Description:

Open of scdpmd config file (/etc/cluster/scdpm/scdpmd.conf) has failed. The scdpmd deamon uses default values.

Solution:

Check the config file.

784607 Couldn't fork1.

Description:

The fork(1) system call failed.

Solution:

Some system resource has been exceeded. Install more memory, increase swap space or reduce peak memory consumption.

785003 clexecd: priocntl to set ts returned %d. Exiting. clexecd program has encountered a failed priocltl(2) system call. The error message indicates the error number for the failure.

Solution:

clexecd program will exit and node will be halted or rebooted to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

785101 transition '%s' failed for cluster '%s': unknown code %d

Description:

The mentioned state transition failed for the cluster because of an unexpected command line option. udlmctl will exit.

Solution:

This is an internal error. Save the contents of /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log and /var/cluster/ucmm/dlm*/*logs/* from all the nodes and contact your Sun service representative.

785154 Could not look up IP because IP was NULL.

Description:

The mapping for the given ip address in the local host files can't be done: the specified ip address is NULL.

Solution:

Check whether the ip address has NULL value. If this is the case, recreate the resource with valid host name. If this is not the reason, treat it as an internal error and contact Sun service provider.

785213 reservation error(%s) - IOCDID_ISFIBRE failed for device %s, errno %d

Description:

The device fencing program has suffered an internal error.

Solution:

785841 %s: Could not register DPM daemon. Daemon will not start on this node

Description:

Disk Path Monitoring daemon could not register itself with the Name Server.

Solution:

This is a fatal error for the Disk Path Monitoring daemon and will mean that the daemon cannot start on this node. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

786114 Cannot access file: %s (%s)

Description:

Unable to access the file because of the indicated reason.

Solution:

Check that the file exists and has the correct permissions.

786127 Failed to start mddoors under PMF tag %s

Description:

The mddoors program of Solaris Volume Manager could not start under Sun Cluster Process Monitoring Facility.

Solution:

Solaris Volume Manager will not be able to support Oracle Real Application Clusters, is mddoors program failed on the node. Verify installation of Solaris Volume Manager and Solaris version. Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Refer to the documentation of Solaris Volume Manager for more information on Solaris Volume Manager components. If problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.

786412 reservation fatal error(UNKNOWN) - clconf_lib_init() error, returned %d

Description:

The device fencing program has suffered an internal error.

Solution:

786765 Failed to get host names from resource %s.

Description:

The networking information for the resource could not be retrieved.

Solution:

Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

787063 Error in getting parameters for global service <%s> of path <%s>: %s

Description:

Can not get information of global service.

Solution:

Save a copy of /var/adm/messages and contact your authorized Sun service provider to determine what is the cause of the problem.

787276 INITRGM Error: Can't start ${SERVER}.

Description:

An attempt to start the rgmd server failed. This error will prevent this node from participating as a full member of the cluster.

Solution:

787616 Adapter %s is not a valid IPMP group on this node.

Description:

Validation of the adapter information has failed. The specified IPMP group does not exist on this node.

Solution:

Create appropriate IPMP group on this node or recreate the logical host with correct IPMP group.

787938 stopped dce rc<>

Description:

Informational message stop of dced.

Solution:

No user action is needed.

788145 gethostbyname() failed: %s.

Description:

gethostbyname() failed with unexpected error.

Solution:

Check if name servcie is configured correctly. Try some commands to query name serves, such as ping and nslookup, and correct the problem. If the error still persists, then reboot the node.

788624 File system checking is enabled for %s file system %s.

Description:

Self explanatory.

Solution:

This is an informational message, no user action is needed.

789135 The Data base probe %s failed.The WLS probe will wait for the DB to be UP before starting the WLS

Description:

The Data base probe (set in the extension property db_probe_script) failed. The start method will not start the WLS. The probe method will wait till the DB probe succeeds before starting the WLS.

Solution:

Make sure the DB probe (set in db_probe_script) succeeds. Once the DB is started the WLS probe will start the WLS instance.

789223 lkcm_sync: caller is not registered

Description:

udlm is not registered with ucmm.

Solution:

This is an internal error. Save the contents of /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log and /var/cluster/ucmm/dlm*/*logs/* from all the nodes and contact your Sun service representative.

789392 Validate - MySQL basedirectory %s does not exist

Description:

The defined basedirectory (-B option) doesn't exist.

Solution:

Make sure that defined basedirectory exists.

789460 monitor_check: call to rpc.fed failed for resource <%s>, resource group <%s>, method <%s>

Description:

A scha_control(1HA,3HA) GIVEOVER attempt failed, due to a failure of the rgmd to communicate with the rpc.fed daemon. If the rpc.fed process died, this might lead to a subsequent reboot of the node. Otherwise, this will prevent a resource group on the local node from failing over to an alternate primary node

Solution:

Examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.

790080 The global service %s associated with path %s is unable to become a primary on node %d.

Description:

HA Storage Plus was not able to switchover the specified global service to the primary node.

Solution:

Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.

790758 Unable to open /dev/null: %s

Description:

While starting up, one of the rgmd daemons was not able to open /dev/null. The message contains the system error. This will prevent the daemon from starting on this node.

Solution:

790899 Starting %s with command %s failed.

Description:

An attempt to start the application by the command that is listed failed.

Solution:

Check the SAPDB log file for potential cause. Try to start the application manually using the command that is listed in the message. Consult other syslog messages that occur shortly before this message for more information about this failure.

791495 Unregistered syscall (%d)

Description:

An internal error has occured. This should not happen. An error message is output to syslog.

Solution:

Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

791959 Error: reg_evt missing correct names

Description:

The cl_apid was unable to find cached events to deliver to the newly registered client.

Solution:

No action required.

792109 Unable to set number of file descriptors.

Description:

rpc.pmfd was unable to set the number of file descriptors used in the RPC server.

Solution:

Look for other syslog error messages on the same node. Save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.

792295 Some shared paths in file %s are invalid.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

792338 The property %s must contain at least one value.

Description:

The named property does not have a legal value.

Solution:

Assign the property a value.

792683 clexecd: priocntl to set rt returned %d. Exiting. clexecd program has encountered a failed priocltl(2) system call. The error message indicates the error number for the failure.

Solution:

clexecd program will exit and node will be halted or rebooted to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

792848 ended host rename

Description:

Housekeeping has been performed after a successful failover.

Solution:

No user action is needed.

792916 CMM: Preempting node %d from quorum device %s failed.

Description:

This node was unable to preempt the specified node from the quorum device, indicating that the partition to which the local node belongs has been preempted and will abort. If a cluster gets divided into two or more disjoint subclusters, exactly one of these must survive as the operational cluster. The surviving cluster forces the other subclusters to abort by grabbing enough votes to grant it majority quorum. This is referred to as preemption of the losing subclusters.

Solution:

There may be other related messages that may indicate why the partition to which the local node belongs has been preempted. Resolve the problem and reboot the node.

792967 Unable to parse configuration file.

Description:

While parsing the Netscape configuration file an error occured in while either reading the file, or one of the fields within the file.

Solution:

Make sure that the appropriate configuration file is located in its default location with respect to the Confdir_list property.

793575 Adaptive server terminated.

Description:

Graceful shutdown did not succeed. Adaptive server processes were killed in STOP method.

Solution:

Please check the permissions of file specified in the STOP_FILE extension property. File should be executable by the Sybase owner and root user.

793651 Failed to parse xml for %s: %s

Description:

The cl_apid was unable to parse the specified xml message for the specified reason. Unless the reason is "low memory", this message probably represents a CRNP client error.

Solution:

If the specified reason is "low memory", increase swap space, install more memory, or reduce peak memory consumption. Otherwise, no action is needed.

793801 Validate - checkprog file does not exist or is not executable at %s/checkprog

Description:

The binary file ${SGE_ROOT}/utilbin/<arch>/checkprog does not exist, or is not executable.

Solution:

Confirm the binary file ${SGE_ROOT}/utilbin/<arch>/checkprog both exists in that location, and is executable.

793831 Waiting for %s to run stop command.

Description:

When the database is being stopped only one node can run the stop command. The other nodes will just wait for the database to finish stopping.

Solution:

This is an informational message, no user action is needed.

793970 ERROR: probe_mysql Option -D not set

Description:

The -D option is missing for probe_mysql command.

Solution:

Add the -D option for probe_mysql command.

794535 clcomm: Marshal Type mismatch. Expecting type %d got type %d

Description:

When MARSHAL_DEBUG is enabled, the system tags every data item marshalled to support an invocation. This reports that the current data item in the received message does not have the expected type. The received message format is wrong.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

795047 Stop fault monitor using pmfadm failed. tag %s error=%d

Description:

Failed to stop fault monitor will be stopped using Process Monitoring Facility (PMF), with the tag indicated in message. Error returned by PMF is indicated in message.

Solution:

Stop fault monitor processes. Please report this problem.

795062 Stop fault monitor using pmfadm failed. tag %s error=%s

Description:

Failed to stop fault monitor will be stopped using Process Monitoring Facility (PMF), with the tag indicated in message. Error returned by PMF is indicated in message.

Solution:

Stop fault monitor processes. Please report this problem.

795311 CMM: Issuing a NULL Preempt failed on quorum device %s with error %d.

Description:

This node encountered an error while trying to release exclusive access to the specified quorum device. The quorum code will either retry this operation or will ignore this quorum device.

Solution:

There may be other related messages that may provide more information regarding the cause of this problem.

795360 Validate - User ID %s does not exist

Description:

The WebSphere MQ UserNameServer resource could not validate that the UserNameServer userid exists.

Solution:

Ensure that the UserNameServer userid has been correctly entered when registering the WebSphere MQ UserNameServer resource and that the userid really exists.

795381 t_open: %s

Description:

Call to t_open() failed. The "t_open" man page describes possible error codes. udlm exits and the node will abort and panic.

Solution:

This is an internal error. Save the contents of /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log and /var/cluster/ucmm/dlm*/*logs/* from all the nodes and contact your Sun service representative.

795754 scha_control: resource <%s> restart request is rejected because the resource type <%s> must have START and STOP methods

Description:

A resource monitor (or some other program) is attempting to restart the indicated resource by calling scha_control(1ha),(3ha). This request is rejected because the resource type fails to declare both a START method and a STOP method. This represents a bug in the calling program, because the resource_restart feature can only be applied to resources that have STOP and START methods. Instead of attempting to restart the individual resource, the programmer may use scha_control(RESTART) to restart the resource group.

Solution:

The resource group may be restarted manually on the same node or switched to another node by using scswitch(1m) or the equivalent GUI command. Contact the author of the data service (or of whatever program is attempting to call scha_control) and report the error.

796536 Password file %s is not readable: %s

Description:

For the secure server to run, a password file named keypass is required. This file could not be read, which resulted in an error when trying to start the Data Service.

Solution:

Create the keypass file and place it under the Confdir_list path for this resource. Make sure that the file is readable.

796592 Monitor stopped due to setup error or custom action.

Description:

Fault monitor detected an error in the setup or an error specified in the custom action file for which the specified action was to stop the fault monitor. While the fault monitor remains offline, no other errors will be detected or acted upon.

Solution:

Please correct the condition which lead to the error. The information about this error would be logged together with this message.

796771 check_for_ccrdata failed malloc of size %d

Description:

Call to malloc failed. The "malloc" man page describes possible reasons.

Solution:

Install more memory, increase swap space or reduce peak memory consumption.

796998 Validate - The Sap id %s is invalid

Description:

The defined SAP Systemname does not exist in /usr/sap.

Solution:

Correct the defined SAP Systemname in /opt/SUNWscswa/util/ha_sap_j2ee_config and re-register the agent.

797292 Starting the Node Agent %s and all its Application Server instances under PMF

Description:

This is an informational message. The Start method is starting the Node Agent and all the Application Server Instances under PMF.

Solution:

None.

797486 Must be root to start %s.

Description:

A non-root user attempted to start the cl_eventd.

Solution:

Start the cl_event as root.

798060 Error opening procfs status file <%s> for tag <%s>: %s

Description:

The rpc.pmfd server was not able to open a procfs status file, and the system error is shown. procfs status files are required in order to monitor user processes.

Solution:

798318 Could not verify status of %s.

Description:

A critical method was unable to determine the status of the specified service or resource.

Solution:

Please examine other messages in the /var/adm/messages file to determine the cause of this problem. Also verify if the specified service or resource is available or not. If not available, start the service or resource and retry the operation which failed.

798514 Starting fault monitor. pmf tag %s

Description:

Informational message. Fault monitor is being started under control of Process Monitoring Facility (PMF), with the tag indicated in message.

Solution:

None

798658 Failed to get the resource type name: %s.

Description:

While retrieving the resource information, API operation has failed to retrieve the resource type name.

Solution:

This is internal error. Contact your authorized Sun service provider. For more error description, check the syslog messages.

798913 Validate - The profile for SAP J2EE instance %s does not exist

Description:

One of the defined J2EE instancies don't exist.

Solution:

Correct the defined J2EE instancies in /opt/SUNWscswa/util/ha_sap_j2ee_config and re-register the agent.

798928 CMM: Connectivity of quorum device %d (%s) has been changed from 0x%llx to 0x%llx.

Description:

The number of configured paths to the specified quorum device has been changed as indicated. The connectivity information is depicted as bitmasks.

Solution:

This is an informational message, no user action is needed.

799348 INTERNAL ERROR: MONITOR_START method is not registered for resource <%s>

Description:

A non-fatal internal error has occurred in the rgmd state machine.

Solution:

799426 clcomm: can't ifkconfig private interface: %s:%d cmd %d error %d

Description:

The system failed to configure private network device for IP communications across the private interconnect of this device and IP address, resulting in the error identified in the message.

Solution:

Ensure that the network interconnect device is supported. Otherwise, Contact your authorized Sun service provider to determine whether a workaround or patch is available.

799817 Failed to stop the application using SIGTERM. Will try to stop using SIGKILL

Description:

The Application could not be stopped by sending SIGTERM. The STOP method will try to stop the application by sending SIGKILL with infinite timeout.

Solution:

None.