Sun Cluster Error Messages Guide for Solaris OS

Message IDs 700000–799999

This section contains message IDs 700000–799999.

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.

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.

701982 Waiting for the PNM to stop

Description:

The PNM service is being stopped.

Solution:

Please wait. No action is required. This is an informational message.

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.

702911 %s

Description:

Print the message as is.

Solution:

Whenever hadbm fails to even start off, it prints messages first line starting with "Error:". The messages should be obvious enough to take corrective action. NOTE: Though the error messages printed explicitly call out JAVA_HOME, make sure that the corrective action applies to java in /usr/bin directory. Unfortunately, our agent is JAVA_HOME ignorant.

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.

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 might be possible to switch the device group to this node by using the cldevicegroup command. If no other node was available, then the device group will not have been started. You can use the cldevicegroup command 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.

704082 reservation warning(%s) - MHIOCENFAILFAST error(%d) will retry in %d seconds

Description:

The device fencing program has encountered errors while trying to access a device. The failed operation will be retried

Solution:

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

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.

704639 dl_attach: DL_ERROR_ACK bad PPA

Description:

Could not attach 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.

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, save a copy of the /var/adm/messages files on all nodes, and the output of clresourcetype show -v, clresourcegroup show -v +, and clresourcegroup status +. 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.

705254 reservation notice(%s) - USCSI_RESET success for device %s, during retry attempt: %d

Description:

Informational message from reserve on ioctl success during retry.

Solution:

No user action required.

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.

705843 pclose failed with error: %s

Description:

pclose failed with an error.

Solution:

Contact your authorized Sun service provider for assistance in diagnosing the problem.

706101 CMM: Connection to quorum server %s failed with error %d.

Description:

This node encountered an error while trying to connect to a quorum server host.

Solution:

Check Sun Cluster quorum server administration documentation. Make sure that all Sun Cluster nodes can communicate with the Sun Cluster Quorum Server.

706216 SCSLM lockf <%s> error <%s>

Description:

Should never occur.

Solution:

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

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.

706881 Validation Failed. Dependency on resource %s should be of type offline restart

Description:

The resource that you are creating or modifying does not specify the required offline-restart resource dependency on the resource that is stated in the message.

Solution:

Repeat the attempt to create or modify the resource, ensuring that the Resource_dependencies_offline_restart resource property specifes the resource that is stated in the message.

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.

708234 "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.

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 faultmonitor can't connect to the specified MySQL instance.

Solution:

None

708901 Error in abandoning Contract:%d

Description:

Cannot abandon the displayed contract.

Solution:

Check the contract manpage to know more about the error.Also make sure the basic contract functionalities are working fine.Contact SUN vendor for more help.This will not trouble the functioning of the delegated restarter, can continue working.

708975 Error deleting PidFile <%s> (%s) for Apache service with apachectl file <%s>.

Description:

The data service was not able to delete the specified PidFile file.

Solution:

Delete the PidFile file manually and start the resource group.

709637 Diskgroup (%s)'s health degraded

Description:

The disk set or disk group is only partially available.

Solution:

Verify the status of the disk set or disk group and perform maintenance if required.

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.

710145 Error: Can't start ${LOGGER}.

Description:

An attempt to start the cl_eventlogd server failed.

Solution:

710449 Could not restart telemetry data service, placed in FAULTED state

Description:

The Telemetry data service could be restarted and was placed to FAULTED state.

Solution:

Save a copy of the log file /var/cacao/instances/default/logs/cacao.0, and contact your authorized Sun service provider to determine whether a workaround or patch is available.

710562 The pool '%s' is erroneously found to be exported.

Description:

HAStoragePlus determined that the zpool that you specified is exported but should not have been.

Solution:

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

711470 One or more of the SUNW.HAStoragePlus resources that this resource depends on is not online. Failing validate method.

Description:

The data service depends on one or more SUNW.HAStoragePlus resources that are not online.

Solution:

Put the SUNW.HAStoragePlus resources online.

711860 Failed to create contract template

Description:

The previous messages will tell the reason for the failure.

Solution:

Make sure the basic contract functionality is working fine.Contact SUN vendor for more help.

712233 Invalid resource or resource group name

Description:

Specified resource group or resource name that was asked to be managed by delegated restarter is not valid

Solution:

check for the validy of names

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.

712371 Extension property "%s" of MDS Resource %s is empty !!

Description:

The property 'QFSFileSystem' should contain at least one entry.

Solution:

Ensure that the metadata server resource was created properly. For information about how to configure the shared QFS file system with Sun Cluster, see your Sun Cluster documentation and your Sun StorEdge QFS documentation.

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.

712442 Proxy Daemon is already running. pmf tag %s

Description:

The Monitor module of the SUNW.scalable_rac_server_proxy is already running. Its internal id is as indicated.

Solution:

None required. Informational message.

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.

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 for Sybase.

Solution:

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

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.

715086 low memory

Description:

Unable to allocate memory. The program will be terminated and this zone will not be able to host applications.

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.

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:

Determine 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.

716318 SCSLM <%s> pool_conf_commit dynamic error <%s>

Description:

Should never occur.

Solution:

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

716731 Failed to set POSIX environment.

Description:

There was an failure in switching to POSIX locale

Solution:

Contact your authorized Sun service provider for assistance in diagnosing the problem.

716840 Method <%s> on resource <%s>, node <%s> killed to achieve user-initiated fast quiesce of the resource group <%s>.

Description:

The system administrator has requested a fast quiesce of the reosurce group. The specified callback method for the given resource was killed to speed its completion so that the resource group can be quiesced.

Solution:

This is just an informational message generated by a quiesce operation initiated by the user.

717344 SCSLM <%s> not found

Description:

Should never occur.

Solution:

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

717570 SCSLM file <%s> corrupted

Description:

Should never occur.

Solution:

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

717571 reservation notice(%s) - MHIOCGRP_REGISTERANDIGNOREKEY success during retry attempt: %d

Description:

Informational message from reserve on ioctl success during retry.

Solution:

No user action required.

718003 Invalid Client Handle

Description:

An internal error has occurred in the inter-process communication between cluster processes.

Solution:

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

718095 Lock on device %s obtained. Proceeding.

Description:

Sun Cluster successfully obtained a lock on a device to perform fsck/mount.

Solution:

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

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.

718526 Failed to take derby data service out of PMF control; trying to send SIGKILL now

Description:

The data service was not able to take derby out of the PMF control.

Solution:

This message is informational; no user action is needed. Automatic recovery kills the data service processes. Verify if other messages followed this one.

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.

719580 WebSphere MQ Queue Manager available

Description:

The Queue Manager is now available.

Solution:

None required. Informational message.

719890 Error stopping the RGM

Description:

The RGM service fails to stop.

Solution:

Please reboot the node,

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:

Determine 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.

720119 Invalid command line %s %s

Description:

An invalid command line argument was received by a callback method. The arguments are as indicated.

Solution:

Contact your Sun support representative for further assistance.

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.

720247 DNS domain info missing.

Description:

Was not able to determine the domain name of the logical host name of the cluster.

Solution:

Ensure that a valid resolv.conf(4) file exists.

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.

721115 Failed to stop derby data service using the custom stop command; trying SIGKILL now.

Description:

The derby data service did not stop correctly.

Solution:

This message is informational; no user action is needed. Automatic recovery kills the data service processes. Verify if other messages followed this one.

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:

721579 Validate callback failed. Unable to read resource properties.

Description:

An error prevented the properties of a resource from being read.

Solution:

Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.

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.

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.

722164 UNRECOVERABLE ERROR: /usr/cluster/lib/scadmin/ql/data_change file does not have execute permission

Description:

/usr/cluster/lib/scadmin/ql/data_change file does not have execute permission.

Solution:

Boot in noncluster mode and then give execute permission to /usr/cluster/lib/scadmin/ql/data_change Reboot the node in cluster mode.

722188 Method <%s> on resource <%s>, node <%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 can then choose to issue a clresourcegroup command to bring resource groups onto desired primaries, or re-try the administrative action that was interrupted by the method failure.

722270 fatal: cannot create state machine thread

Description:

The rgmd daemon 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.

722342 Could not Restart/Failover the dataservice.

Description:

The attempted recovery actions after a probe failure on the resource or resource group has failed and the resource is left in faulted status on its current master.

Solution:

Examine the /var/adm/messages to determine the cause of the failures, and after taking corrective action, attempt to restart the resource or switch over the resource group. The resource can be restarted by the sequence "clresource disable <resource>; clresource enable <resource>". Or, the whole resource group can be restarted using "clresourcegroup restart <group>". The resource group can be switched over to the next primary node by executing "clresourcegroup switch". If problem persists, contact your Sun service representative.

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.

722467 going down on signal %d

Description:

scdpmd has received a signal and is goind down.

Solution:

No action required.

722737 SCSLM <%s> popen error <%s>

Description:

Should never occur.

Solution:

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

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 recurs, 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.

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

Description:

An attempt to retrieve a resource group handle has failed.

Solution:

If the failure is cased by insufficient memory, reboot. If the problem recurs after rebooting, consider increasing swap space by configuring additional swap devices. If the failure is caused by an API call, check the syslog messages for the possible cause.

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.

724037 (%s) scan of dlmmap failed on "%s", idx =%d

Description:

Failed to scan dlmmap.

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.

724558 Error reading /etc/vfstab : %s

Description:

The /etc/vfstab file could not be read.

Solution:

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

725463 No Logical devices specified. Entire device group is to be monitored

Description:

All volumes in the disk set or disk group are to be monitored. This message is an informational message.

Solution:

No user action is required.

725949 incoming_registration: invalid dataptr size

Description:

A libsczones registration for zone state callbacks was improperly formatted. It will be ignored.

Solution:

Look for messages from clients of libsczones such as rgmd and rpc.fed to determine why they sent an improperly formatted registration. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

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.

726179 reservation warning(%s) - MHIOCGRP_INRESV error(%d) will retry in %d seconds

Description:

The device fencing program has encountered errors while trying to access a device. The failed operation will be retried

Solution:

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

726195 incoming_registration: invalid number of descriptors

Description:

A libsczones registration for zone state callbacks was improperly formatted. It will be ignored.

Solution:

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.

727160 msg of wrong version %d, expected %d

Description:

udlmctl received an illegal message.

Solution:

None. udlm will handle this error.

727738 Error stopping the SCZONE service

Description:

The SCZONE service fails to stop.

Solution:

Please reboot the node,

727805 Couldn't remove Device service %s, error = %d

Description:

scdidadm failed to remove a device service because of indicated error.

Solution:

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

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.

728881 Failed to read data: %s.

Description:

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.

729600 Probe for resource DNS successful.

Description:

This message indicated that the probe is successful.

Solution:

This is a debug message.

730584 Warning: The resource "%s" is not enabled and the UCMMD is running. Changes are not effective until the resource is enabled.

Description:

A resource property has been changed while the resource is offline and the UCMMD is running. This change is not effective until the resource is enabled.

Solution:

Re-enable the resource so that the running UCMMD is updated with the changed property.

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.

730920 - node %s vm_on_node is %s

Description:

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

Solution:

None

731009 Switch-over of RG %s to node %s successful.

Description:

The resource group that contains the metadata server resource was successfully switched over to another node. This message is an informational message.

Solution:

No user action is required.

731228 validate_options: %s 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

Description:

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.

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.

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 CMM: Halting because this node is severely short of resident physical memory; availrmem = %ld pages, tune.t_minarmem = %ld pages, freemem = %ld pages, throttlefree = %ld pages.

Description:

The local node does not have sufficient resident physical memory, due to which it may declare other nodes down. To prevent this action, the local node is going to halt.

Solution:

There may be other related messages that may indicate the cause for the node having reached the low memory state. Resolve the problem and reboot the node. If unable to resolve the problem, 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.

733110 %s: method %s terminated by signal

Description:

The process that was trying to execute the method was terminated by a signal.

Solution:

Try to rexecute the method and see if the signal is terminating the process.Try contact SUN vendor for help.

733157 %s/krb5kdc not started, exiting

Description:

krb5kdc is no longer running just after Sun Cluster tried to start it.

Solution:

This problem could be caused by a number of issues. Check the krb5.conf(4) and kdc.conf(4) files for correctness. Ensure that the master key exists: /etc/krb5/.k5.<realm name>. Check that the binary is executable and that the /var/krb5/principal database file exists.

733889 Multiple zones on the same physical host must appear consecutively in the nodelist.

Description:

NodeList contains a zone that is not consecutive with other zones on the same physical host.

Solution:

Reorder the NodeList for the resource group so that all zones on a physical host are consecutive.

734793 Failed to open /etc/vfstab.

Description:

The /etc/vfstab file could not be opened. The most probable cause of this error is that the file does not exist.

Solution:

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

734811 Restart operation failed for Resource %s

Description:

This message indicated that the RGM did not process a restart request, most likely due to the configuration settings.

Solution:

This is an informational message.

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:

Determine 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.

734946 Kerberos daemons started.

Description:

Both the krb5kdc and kadmind daemons started successfully under PMF.

Solution:

This is for informational purposes only, no action is required.

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.

Solution:

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.

735692 The dataguard settings of the Sun Cluster resource appear to be incorrect and do not match the values of the Oracle database.

Description:

The dataguard mode (primary, physical standby, logical standby) that the Sun Cluster resource has been configured with, using the DATAGUARD_ROLE and STANDBY_MODE extension properties, does not match the dataguard mode returned by the Oracle instance.

Solution:

Ensure that the DATAGUARD_ROLE and STANDBY_MODE extension property values of the Sun Cluster resource are consistent with the actual dataguard mode of the Oracle database.

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.

736694 Failed to set parameter for contract template: %s

Description:

Cannot set the various parameters for the contract

Solution:

Make sure the basic contract functionality is working fine.Contact SUN vendor for more help.

736797 %s group %s is incapable of hosting IPv4 or IPv6 addresses

Description:

The IPMP group can not host any IP address. This is an unusual situation.

Solution:

Contact your authorized Sun service provider.

736915 Failed to perform dual-partition begin tasks on the nodes of second partition

Description:

During dual-partition upgrade in a live upgrade scenario, some upgrade related tasks have failed.

Solution:

Refer to documentation about recovering from a failed dual-partition upgrade in a live upgrade scenario.

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.

737394 Failed to stop fault-monitor

Description:

An error prevented a resource's fault monitor from stopping.

Solution:

Determine why the fault monitor process could not be stopped. Contact your authorized Sun service provider for assistance in diagnosing the problem.

737444 Error: The nodelist of resource group "%s" must match the node list of resource group "%s".

Description:

The node list of the RAC framework resource group and the node list of the storage resource group are different. The storage resource group contains a resource of type SUNW.ScalDeviceGroup or SUNW.ScalMountPoint.

Solution:

Ensure that the node list of the RAC framework resource group and the node list of the storage resource group are identical.

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.

737598 Validation failed. Could not assign debug directory %s ownership to ORACLE_OWNER=%s ORACLE_OWNER_GROUP=%s

Description:

The SUNW.scalable_rac_server_proxy agent could not transfer the ownership of the Proxy resource's debug directory to the oracle user who installed the oracle home specified in the value of the ORACLE_HOME extension property of the Proxy resource being created.

Solution:

Check whether the oracle owner specified in the error message is still valid and fully operational. If so, check whether the /var/opt/SUNWscor/oracle_server/ directory is present and accessible by the root user. If the problem persists, contact your Sun support representative for further assistance.

737991 INTERNAL ERROR: are_dependee_boot_methods_pending invalid dependency type <%d>

Description:

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

Solution:

738120 Device service %s associated with path %s is in transition state.

Description:

The specified global service was in between states.

Solution:

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

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.

739877 Failed to open /etc/mnttab.

Description:

The /etc/mnttab file could not be opened. The most probable cause of this error is that the file does not exist.

Solution:

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

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.

740563 Validate - winbind is not defined in %s in the group section

Description:

Winbinbd is missing from the group section in /etc/nsswitch.conf

Solution:

Enter winbind within the group section in /etc/nsswitch.conf.

740731 Failed to retrieve property %s :%s

Description:

There was an error retrieving a resource property.

Solution:

Investigate possible RGM, DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.

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.

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.

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.

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.

744295 repl_check fatal error - dcs_get_service_parameters() error, dc_err %d

Description:

An error was encountered while checking for replicated device groups.

Solution:

Replicated device groups may not have properly started on this node. If so, you may manually configure this node as the replication master and attempt to restart the device group on this node. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

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.

744788 clexecd: Sending fd to workerd repeatedly busy. Attempted %d times. Exiting.

Description:

clexecd has tried repeatedly to set up interprocess communcation, but each time the error EAGAIN occured.

Solution:

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

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.

745452 Volume %s/%s not found.

Description:

The volume was not found in the disk set or disk group.

Solution:

Determine whether the volume was removed from the disk set or disk group.

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.

745677 SCSLM snprintf error <%s>

Description:

Should never occur.

Solution:

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.

747634 Failed to open test-file %s : %s

Description:

The test file for performing I/O operations does not exist. The absence of this file might be caused by malicious activity in your system.

Solution:

Restart the ScalMountPoint resource.

748252 init template failed

Description:

A scalable service resource attempting to execute in a non-global zone was unable to initialize a Solaris contract. This causes the currently executing method to fail. The RGM takes the usual recovery actions for a method failure. Other related syslog messages might be found near this one.

Solution:

If the cause of the failure cannot be determined from syslog messages, contact your authorized Sun service provider to determine whether a workaround or patch is available.

748569 Could not get devicegroup info for (%s)

Description:

An error occurred during the retrieval of information about the disk set or disk group.

Solution:

Check the status of the disk set or disk group. Contact your authorized Sun service provider for further assistance in diagnosing the problem.

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.

748917 Telemetry data service stop method failed for unknown reason

Description:

The telemetry data service could not stop for an unknown reason.

Solution:

This message is informational; no user action needed.

749213 Could not setup scheduling parameters: %s

Description:

The server was not able to set the scheduling mode parameters, 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.

749409 clcomm: validate_policy: high not enough. high %d low %d inc %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.

749684 SCSLM zone_list error <%s>

Description:

Should never occur.

Solution:

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

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:

Call to initialize a handle to get cluster information failed. This means that 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 patch is available.

751219 pthread_rwlock_rdlock err %d line %d

Description:

Internal error.

Solution:

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

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

Description:

An inter-node communication failed with an unknown exception while the rgmd daemon 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, save a copy of the /var/adm/messages files on all nodes and the output of clresourcetype show -v, clresourcegroup show -v +, and clresourcegroup status +. 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:

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 clresourcegroup show 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.

752872 IP address (hostname) string %s in property %s, entry %d does not resolve to an IP address that belongs to any of the resources named in resource dependency properties of this resource.

Description:

The IP address or hostname named does not belong to one of the network resources designated for use by this resource

Solution:

Either select a different IP address to use that is in one of the network resources used by this resource or create a network resource that contains the named IP address and designate that resource as one of the network resources used by this resource.

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.

754517 %s: rename of %s.db to %s FAILED

Description:

The "principal.db" database file could not be renamed to "principal".

Solution:

Check the state of the "principal" and "principal.db" files under /var/krb5.

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.

755040 Error getting handle tolibvxvm_get_version

Description:

An error occurred when the library routine was called.

Solution:

Ensure that the correct version of the library is installed. Contact your authorized Sun service provider for further assistance in diagnosing the problem.

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.

755394 Monitor for derby data service successfully stopped. PMF will restart it.

Description:

When the data service properties are updated, the data service restarts the monitor.

Solution:

This message is informational; no user action is needed.

755495 No reply from message server.

Description:

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

Solution:

No user action needed.

755760 switchover failed since the file system at %s is being unmounted.

Description:

This is an error due to a simultaneous switchover and unmount. The switchover fails and unmount succeeds.

Solution:

The switchover has to be retried.

755773 libcdb: scha_cluster_open failed with %d

Description:

Call to initialize a handle to get cluster information failed. The second part of the message gives the error code.

Solution:

The calling program should handle this error. If it is not recoverable, it will exit.

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.

756096 "%s" requeued

Description:

The tag shown has exited and was restarted by the rpc.pmfd server. An error message is output to syslog.

Solution:

This message is informational; no user action is needed.

756190 <%s> getpwuid_r uid %d error %s

Description:

Should never occur.

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.

756782 in libsecurity, unable to get client credential

Description:

While processing a call from a client program, a Sun Cluster daemon was unable to obtain the credentials of the caller. This causes the attempted operation to fail.

Solution:

Make sure that no unauthorized programs are running on the cluster. If the call appears to come from a legitimate data service method or administrative command, contact your authorized Sun service provider to determine whether a workaround or patch is available.

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.

757260 SCSLM mmap <%s> error <%s>

Description:

Should never occur.

Solution:

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.

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.

758399 SCSLM realloc error <%s>

Description:

Should never occur.

Solution:

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

758691 Current setting of Retry_interval= %d, might prevent failover on repeated probe failures. It is recommended that Retry_interval be greater than or equal to [(Thorough_probe_interval + Probe_timeout) * 2 * Retry_count]. Current values are (Thorough_probe_interval = %d,Retry_count = %d,Probe_timeout = %d).

Description:

Validation of the probe related parameters suggest that invalid values might have been specified.

Solution:

This is a warning message only. However, the current settings might prevent the resource from failing over successfully in the event of a failure. Use clresource to modify the values of these parameters so that they will hold the correct relationship as suggested in the warning message.

759011 Local mountpoint path '%s%s' has exceeded %d characters.

Description:

The full path of local zone mount point has exceeded PATH_MAX characters.

Solution:

Shorten the mount point so that the length does not exceed PATH_MAX characters.

759087 File %s is missing.

Description:

The /etc/resolv.conf file is missing.

Solution:

Create the /etc/resolv.conf file. Kerberos is dependent upon DNS to canonicalize service principal names.

759249 Telemetry data service monitor method failed to start

Description:

The monitor program of the telemetry data service could not start. This should never occur.

Solution:

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

759494 Failed to retrieve resource property %s on %s: %s

Description:

The query for a property on the specified node failed. The reason for the failure is given in the message.

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.

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.

759890 Cluster initialization encountered a problem on node ${nodename}, manual initialization by using scsetup(1M) might be necessary

Description:

The attempt to automatically reset cluster installmode or quorum votes failed on one or more nodes. The last node to join the cluster is supposed to perform these tasks. However, other nodes also perform registration tasks when they join the cluster. This message indicates that one or more of these attempts failed, which prevented the last node from initializing the cluster.

Solution:

Run clsetup or scsetup after all nodes have joined the cluster, to complete post-installation setup.

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.

760903 <%s> project <%s> user <%s> getprojidbyname() %d errno %d

Description:

Should never occur.

Solution:

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

761677 Cannot connect to message server. Return code %d.

Description:

Probe could not connect to the SAP message server.

Solution:

No user action needed.

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.

762946 PMF XDR Buffer Shortfall while encoding arguments API num = %d, will retry

Description:

A non-fatal error occurred while rpc.pmfd was marshalling arguments for a remote procedure call. The operation will be re-tried with a larger buffer.

Solution:

No user action is required. If the message recurs frequently, contact your authorized Sun service provider to determine whether a workaround or patch is available.

763088 SCSLM <%s> pool_value_set_string error <%s>

Description:

Should never occur.

Solution:

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

763191 No resource type found in the cluster.

Description:

No resource type registered in the cluster.

Solution:

Register the required resource types, create the required instances of those resource types and repeat the operation. For information about how to create resource types and their instances, see your Sun Cluster documentation.

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.

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.

764140 Method <%s> on resource <%s>, resource group <%s>, node <%s>: Timeout.

Description:

A method execution has exceeded its configured timeout and was killed by the rgmd. 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.

Solution:

Consult data service documentation to diagnose the cause of the method failure. Other syslog messages occurring just before this one might indicate the reasone for the failure. After correcting the problem that caused the method to fail, the operator can retry the operation that failed.

764502 Function: validate: The Environment script %s does not exist

Description:

The filename specified in the parameter files ENVSCRIPT variable does not exist.

Solution:

Fix the parameter file and specify a valid Environment script.

764623 zone enter failed: %m. %d

Description:

A scalable service resource attempting to execute in a non-global zone was unable to enter the zone. This might indicate that the zone has died. This causes the currently executing method to fail. The RGM takes the usual recovery actions for a method failure. Other related syslog messages might be found near this one.

Solution:

If the cause of the failure cannot be determined from syslog messages, contact your authorized Sun service provider to determine whether a workaround or patch is available.

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

766491 Waiting for ${SERVER} to be ready.

Description:

The initfed init script is waiting for the rpc.fed daemon to start. This warning informs the user that the startup of rpc.fed is abnormally long.

Solution:

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.

768219 scha_control: resource <%s> restart request is rejected because the resource type <%s> must have both START and STOP methods or both PRENET_START and POSTNET_STOP methods without START and STOP declared.

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 and represents a bug in the calling program, because the resource_restart feature can only be applied to resources that have both STOP and START methods or both PRENET_START and POSTNET_STOP methods without START and STOP declared. 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 clresourcegroup 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.

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:

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.

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 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 clnode and shutdown to take down a node, rather than directly killing the daemon.

770400 ct_ctl_abandon: %s

Description:

The rpc.pmfd was unable to abandon an empty contract. The contract will continue to exist even though it has no processes in it.

Solution:

If the message is isolated, it was probably a transient error. If there are many instances of the message, there is a problem with the contract file system. Search 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.

770767 Failed to construct command %s

Description:

There was an internal error while constructing the quotacheck or quotaon command to be run.

Solution:

Contact your Sun service representative.

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.

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.

771416 Function: validate: The Environment script %s is not a valid korn shell script

Description:

The environment script spcified in the parameter file needs to be a valid korn shell script, because the login shell of the PostgreSQL user is korn shell compliant.

Solution:

Fix the environment script until it passes ksh -n scriptname.

771693 Failed to initialize Mutex : %s

Description:

The mutex that is used to synchronize threads for the I/O probe could not be initialized.

Solution:

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

771717 fatal: could not arm failfast

Description:

The rgmd program could not enable the failfast mechanism. The failfast mechanism is designed to prevent data corruption by causing the node to be shutdown in the event that the rgmd program dies.

Solution:

To avoid data corruption, the rgmd will halt or reboot the node. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

771892 SCSLM <%s> zone <%s> corrupted project comment

Description:

Should never occur.

Solution:

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

772043 Failed to read nodes of second partition from the CCR

Description:

The upgrade process was unable to find needed information in the CCR. The CCR might be missing this information.

Solution:

Cluster upgrade has failed. Reboot all the nodes out of cluster mode and recover from upgrade. Finish the cluster upgrade by using the standard upgrade method.

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.

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.

773184 INTERNAL ERROR Failfast: ff_impl_shouldnt_happen. Rebooting zone %s with zone_id %d

Description:

An internal error has occurred in the failfast software.

Solution:

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

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:

773683 scha_resourcetype_open() failed: %s

Description:

A call to scha_resourcetype_open() failed.

Solution:

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

773690 clexecd: wait_for_ready worker_process

Description:

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.

774045 Error in the vfstab entry for mount point '%s'.

Description:

An error occurred while the vfstab entry for the specified mount point was being read.

Solution:

Verify that the vfstab entry for the mount point is correct and repeat the operation. If the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.

774178 IO to file-system %s, through mountpoint %s failed due to failure in getting UCMM state.

Description:

The UCMM process has died.

Solution:

Determine whether another problem with the cluster caused the UCMM process to die. Bring online the UCMM again and restart the ScalMountPoint resource.

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 might have failed to start on this node. If the device group was started on another node, move it to this node by using the cldevicegroup command. If the device group was not started, you can start it by using the cldevicegroup command. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group might 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.

776199 (%s) reconfigure: cm error %s

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.

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

Description:

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

Solution:

776478 Error: could not start the Derby server for an unknown reason.

Description:

The Derby server could not be started for an unknown reason.

Solution:

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

777115 Validate check for sckrb5 failed.

Description:

The validation test failed before the HA-KDC service started.

Solution:

To determine what action to take, look at the previous syslog messages for more specific error information.

777407 SCSLM <%s> error pmin zero

Description:

Should never occur.

Solution:

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

778435 Error while reading output of %s.

Description:

Need explanation of this message!

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.

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:

778655 SCSLM <%s> error pmax zero

Description:

Should never occur.

Solution:

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

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.

778818 SCSLM <%s> pool_get_status error <%s>

Description:

Should never occur.

Solution:

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

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:

Determine 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.

779295 Auto recovery of HADB database failed.

Description:

Need explanation of this message!

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.

779412 check_qmgr - <%s>

Description:

The Queue Manager check has failed.

Solution:

None required. Informational message.

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.

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.

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

781168 Error determining the resource type name

Description:

The name of the resource type could not be determined.

Solution:

Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.

781445 kill -0: %s

Description:

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:

-2 HA Storage Plus was not able to access the cluster configuration.

Solution:

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

782044 Unable to detach zone %s from door server for %s

Description:

Not able to detach this zone from the door server

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.

782271 received signal %d: continuing

Description:

The daemon indicated in the message tag has received a signal, possibly caused by an operator-initiated kill(1) command. The signal is ignored.

Solution:

The operator must use clnode and shutdown to take down a node, rather than directly killing the daemon.

782375 Unable to initialize XDR stream

Description:

An internal error has occurred in the inter-process communication between Sun Cluster processes. Related error messages might be found near this one in the syslog output.

Solution:

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

782458 Node %d is in the %s for resource %s, but the dependee resource %s cannot host an address on node/zone %s.

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.

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.

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 clresourcegroup to change the resource group dependencies.

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.

784022 system() call failed for mountpoint %s : %s

Description:

The file system that this ScalMountPoint resource represents could not be mounted on the mount point.

Solution:

Determine whether the mount-point directory exists. If the directory does not exist, create it and repeat the operation. Otherwise, contact your authorized Sun service provider to determine whether a workaround or patch is available.

784310 ERROR: scha_control() was called on resource group <%s>, resource <%s>, node <%s> before the RGM started

Description:

This message most likely indicates that a program called scha_control(1ha,3ha) before the RGM had started up. Normally, scha_control is called by a resource monitor to request failover or restart of a resource group. If the RGM had not yet started up on the cluster, no resources or resource monitors should have been running on any node. The scha_control call will fail with a SCHA_ERR_CLRECONF error.

Solution:

On the node where this message appeared, confirm that rgmd daemon was not yet running (i.e., the cluster was just booting up) when this message was produced. Find out what program called scha_control. If it was a customer-supplied program, this most likely represents an incorrect program behavior which should be corrected. If there is no such customer-supplied program, or if the cluster was not just starting up when the message appeared, contact your authorized Sun service provider for assistance in diagnosing the problem.

784499 validate_options: %s 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.

784591 Telemetry data service start method completed sucessfully

Description:

The telemetry data service started successfully.

Solution:

This message is informational; no user action needed.

784607 Couldn't fork1.

Description:

The fork(2) system call failed because a system resource is exhausted.

Solution:

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

784932 Telemetry data service start method failed for unknown reason

Description:

The telemetry data service could not start for an unknown reason.

Solution:

This message is informational; no user action needed.

785003 clexecd: priocntl to set ts returned %d. Exiting.

Description:

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.

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

Description:

The device fencing program has suffered an internal error.

Solution:

785464 Failed to write to file %s: %s.

Description:

A write operation to the specified file is failed.

Solution:

Check the man page for errors and try to resolve the the problem. Otherwise contact your authorized Sun service provider.

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:

786752 program name to connect not specified

Description:

An internal error has occurred in the inter-process communication between Sun Cluster processes. Related error messages might be found near this one in the syslog output.

Solution:

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

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.

787600 scha_resourcegroup_get() failed for RG %s: %s

Description:

A call to scha_resourcegroup_get() failed.

Solution:

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

787893 Failed to initiate the task of registering CMM version key %s, version %d in the CCR

Description:

The CMM failed to register the CMM version in the CCR. One reason could be that the CCR repository synchronization was still in progress. The result of this failure will be to continue using the old CMM version during the next reconfiguration. However, another attempt is made to register the CMM version in the next reconfiguration.

Solution:

This is an informational message. No user action is required.

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.

788651 The file %s needed by the derby data service does not exist

Description:

A program or script of the derby data service could not execute because a file does not exist. This should never occur.

Solution:

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

788773 scvxvmlg fatal error - ckmode recieved unknown mode %d

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.

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) don't exist.

Solution:

Make sure that defined basedirectory exists.

789718 Failed to stat parent directory of %s

Description:

A stat() call on the parent directory of the mount-point directory failed.

Solution:

Determine whether the directory exists. If the directory does not exist, create it and repeat the operation. Otherwise, contact your authorized Sun service provider to determine whether a workaround or patch is available.

790039 last probe for N1 Grid Service Provisioning System Tomcat failed, N1 Grid Service Provisioning System considered as unavailable

Description:

The the last probe failed, the data seves will be restarted of failed over.

Solution:

None

790080 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:

790811 Telemetry data service stop method timed out

Description:

The telemetry data service could not stop before the configured timeout elapsed.

Solution:

This message is informational; no user action needed.

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.

792065 Failfast (stop_node_panic): Zone %s (zone ID %d) rebooting

Description:

Rebooting zone with the specified zone ID, as the failfast client died.

Solution:

Check for core files of the client process after you reboot the node or zone and report these files to your authorized Sun service provider.

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.

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.

Description:

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.

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

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.

793624 cladm(CL_GET_CLUSTER_NAME) failed.

Description:

An error prevented the cluster name from being retrieved.

Solution:

Contact your authorized Sun service provider for assistance in diagnosing the problem.

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.

794413 Validation failed. Database %s is not registered with CRS

Description:

The SUNW.scalable_rac_server_proxy agent detected that the specified DB_NAME is not recognized as valid by CRS.

Solution:

Verify whether the specified DB_NAME is correct. If yes, verify whether the database is accessible via supported CRS interfaces. Use Oracle suggested steps to rectify problems with the CRS setup, if any. If the problem persists, contact your Sun support representative for further assistance.

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.

794717 reservation fatal error(%s) - did_initlibrary() failure

Description:

The device fencing program has suffered an internal error.

Solution:

794873 Shutdown of instance did not succeed. Error is (%s).

Description:

The shutdown of the Oracle instance failed.

Solution:

Check whether the Oracle instance can be successfully shut down using standard Oracle interfaces. If the problem persists, contact your Sun support representative for further assistance.

794984 validate_options - Fatal: SGE_ROOT %s not a directory

Description:

The SGE_ROOT variable configured within /opt/SUNWscsge/util/sge_config contains a value whose location does not exist or is not a directoy.

Solution:

Determine where the Sun Grid Engine software is installed (the directory containing the installation script 'inst_sge'). Initialize SGE_ROOT with this value in /opt/SUNWscsge/util/sge_config and try sge_remove and sge_register afterwards. This will stop, deregister and register the Sun Grid Engine data services.

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.

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.

795673 add_to_list: Out of memory!

Description:

A user program ran out of memory.

Solution:

Determine why the user program ran out of memory. Contact your authorized Sun service provider for assistance in diagnosing the problem.

795840 Failed to allocate memory for failfasting zone %s with zone ID %d

Description:

A data structure that is needed to failfast a zone could not be created. This might be due to lack of memory.

Solution:

Lack of memory might lead to other problems on the node. You must free up memory on the node.

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.

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:

Determine 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.

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.

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.

799228 Derby data service start method failed

Description:

The derby data service could not start.

Solution:

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

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.

799571 Could not set supplementary group list for uid '%d': %s

Description:

The program failed to set the supplementary group list of the calling process.

Solution:

Examine the setgroups(2) man page for the causes of the error displayed.