Chapter 2 Error Messages
This chapter contains a numeric listing of Sun Cluster software error messages and descriptions. The following sections are contained in this chapter.
Message IDs 100000–199999
This section contains message IDs 100000–199999.
100039 Failed to initialize pthread attribute.
Description:The pthread attribute variable could not be initialized.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
100088 fatal: Got error <%d> trying to read CCR when making resource group <%s> managed; aborting node
Description:Rgmd failed to read updated resource 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.
100098 SCSLM <%s> pool_conf_close error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
100396 clexecd: unable to arm failfast.
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.
100590 fatal: Method <%s> on resource <%s>, node <%s>: Received unexpected result <%d> from rpc.fed, aborting node
Description:A serious error has occurred in the communication between rgmd and rpc.fed. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
101010 libsecurity: program %s (%lu); clnt_authenticate failed
Description:A client of the specified server was not able to initiate an rpc connection, because it failed the authentication process. The pmfadm or scha command exits with error. 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.
101122 Validate - Couldn't retrieve MySQL version number
Description:Internal error when retrieving MySQL version.
Solution:Make sure that supported MySQL version is being used.
101231 unable to create failfast object.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
102218 couldn't initialize ORB, possibly because machine is booted in non-cluster mode
Description:could not initialize ORB.
Solution:Please make sure the nodes are booted in cluster mode.
102340 Prog <%s> step <%s>: authorization error.
Description:An attempted program execution failed, apparently due to a security violation; this error should not occur. This failure is considered a program failure.
Solution:Correct the problem identified in the error message. If necessary, examine other syslog messages occurring at about the same time to see if the problem can be diagnosed. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing the problem.
102770 Function: validate - LXrunlevel not set in %s
Description:The LXrunlevel variable is not set in the parameter file sczbt_<resource name>.
Solution:Set the LXrunlevel variable in the parameter file sczbt_<resource name>.
102967 in libsecurity for program %s (%lu); write of file %s failed: %s
Description:The specified server was not able to write to a cache file for rpcbind information. 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.
103217 Could not obtain fencing lock because we could not contact the nameserver.
Description:The local nameserver on this was not locatable.
Solution:Communication with the nameserver is required during failover situations in order to guarantee data integrity. The nameserver was not locatable on this node, so this node will be halted in order to guarantee data integrity. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
103566 %s is not an absolute path.
Description:The extension property listed is not an absolute path.
Solution:Make sure the path starts with "/".
103712 CCR: Fatal error: Node will be killed.
Description:Some fatal error occurred on this node during the synchronization of cluster repository. This node will be killed to allow the synchronization to continue.
Solution:Look for other messages on this node that indicated the fatal error occurred on this node. For example, if the root disk on the afflicted node has failed, then it needs to be replaced. Contact your authorized Sun service provider for assistance.
104035 Failed to start sap processes with command %s.
Description:Failed to start up SAP with the specified command.
Solution:SAP Application Server failed to start on this cluster node. It would be started on some other cluster node provided there is another cluster node available. If the Application Server failed to start on any other node, disable the SAP Application Server resource, then try to run the same command manually, and fix any problem found. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
104757 %s: Invalid zone cluster template.
Description:The libzccfg was unable to parse the specified zone cluster template file. The template file may be corrupt.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
104914 CCR: Failed to set epoch on node %s errno = %d.
Description:The CCR was unable to set the epoch number on the indicated node. The epoch was set by CCR to record the number of times a cluster has come up. This information is part of the CCR metadata.
Solution:There may be other related messages on the indicated node, which may help diagnose the problem, for example: 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.
104973 Method <%s> on resource <%s>, node <%s> terminated abnormally
Description:A resource method terminated without using an exit(2) call. The rgmd treats this as a method failure.
Solution:Consult resource type documentation, or contact the resource type developer for further information.
105040 'dbmcli' failed in command %s.
Description:SAP utility 'dbmcli -d <LC_NAME> -n <logical hostname> db_state' failed to complete as user <lc-name>adm.
Solution:Check the SAP liveCache installation and SAP liveCache log files for reasons that might cause this. Make sure the cluster nodes are booted up in 64-bit since liveCache only runs on 64-bit. If this error caused the SAP liveCache resource to be in any error state, use SAP liveCache utility to stop and dbclean the SAP liveCache database first, before trying to start it up again.
105222 Waiting for %s to startup
Description:Waiting for the application to startup.
Solution:This message is informational; no user action is needed.
105450 Validation failed. ASE directory %s does not exist.
Description:The Adaptive Server Environment directory does not exist. The SYBASE_ASE environment variable may be incorrectly set or the installation may be incorrect.
Solution:Check the SYBASE_ASE environment variable value and verify the Sybase installation.
105569 clexecd: Can allocate execit_msg. Exiting.
Description:Could not allocate memory. Node is too low on memory.
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.
106181 WARNING: lkcm_act: %d returned from udlm_recv_message (the error was successfully masked from upper layers).
Description:Unexpected error during a poll for dlm messages.
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.
106245 SCSLM <%s> pool_resource_create error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
107282 Package %s required for the derby data service is missing
Description:A package required for the derby data service is not installed.
Solution:Install the missing package.
107699 DB path is %s
Description:The monitor start method prints the path configured.
Solution:This message is informational; no user action is needed.
107716 Directory %s does not exist; the Cacao security keys have not been generated or copied
Description:A directory related to the Cacao security does not exist, most probably because the security have not been generated or copied over. This should never occur as the Sun Cluster Installation should take care of that.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
107958 Error parsing URI: %s
Description:The Universal Resource Identifier (URI) was unable to be parsed.
Solution:Correct the syntax of the URI.
108357 lookup: unknown binding type <%d>
Description:During a name server lookup an unknown binding type was encountered.
Solution:No user action is required. This is informational message.
108856 Failover IP resource does not exist in the resource group %s
Description:Failover IP address entered in Network_resources_used property is not part of this resource group.
Solution:Check the failover IP resource and enter the value.
108990 CMM: Cluster members: %s.
Description:This message identifies the nodes currently in the cluster.
Solution:This is an informational message, no user action is needed.
109102 %s should be larger than %s
Description:The value of Thorough_Probe_Interval specified in scrgadm command or in CCR table was smaller than Cheap_Probe_Interval.
Solution:Reissue the scrgadm command with appropriate values as indicated.
109105 (%s) setitimer failed: %d: %s (UNIX errno %d)
Description:Call to setitimer() failed. The "setitimer" man page describes possible error codes. udlmctl will exit.
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.
109666 set_rt_prio : Unable to get ff_admin_v
Description:cl_execd program could not get a reference to the CORBA failfast server object.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
109942 fatal: Resource <%s> create failed with error <%d>; aborting node
Description:Rgmd failed to read new resource 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.
110012 lkcm_dreg failed to communicate to CMM ... will probably failfast : %s
Description:Could not de-register udlm from ucmm. This node will probably failfast.
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.
110097 Major number for driver (%s) does not match the one on other nodes. Confirm that the /etc/name_to_major files are in sync on all cluster nodes.
Description:The driver identified in this message does not have the same major number across cluster nodes, and devices owned by the driver are being used in global device services.
Solution:Look in the /etc/name_to_major file on each cluster node to see if the major number for the driver matches across the cluster. If a driver is missing from the /etc/name_to_major file on some of the nodes, then most likely, the package the driver ships in was not installed successfully on all nodes. If this is the case, install that package on the nodes that don't have it. If the driver exists on all nodes but has different major numbers, see the documentation that shipped with this product for ways to correct this problem.
110491 dl_info: DL_ERROR_ACK protocol error
Description:Could not get a info_ack from 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.
110548 Validate - %s must contain exactly one SWIFTAlliance Access instance
Description:The agent does only support exactly one SWIFTAlliance Access instance.
Solution:Verify that the file /usr/swa/insts does only contain one line describing the SWIFTAlliance Access instance.
110600 dfstab file %s does not have any paths to be shared. Continuing.
Description:The specific dfstab file does not have any entries to be shared
Solution:This is a Warning. User needs to have at least one entry in the specific dfstab file.
111055 The device to mount is not specified in vfstab for mount point : %s
Description:The 'device to mount' field is missing from the vfstab entry for the specified mount point.
Solution:Add the 'device to mount' field to the vfstab entry for the specified mount point and repeat the operation.
111495 Upgrade has completed on this node
Description:Cluster upgrade has been completed on this node. A majority of nodes have joined the cluster after the upgrade. This message does not mean that the upgrade has completed on all the nodes of the cluster or that the cluster has full membership.
Solution:This is an informational message, no user action is needed.
111697 Failed to delete scalable service in group %s for IP %s Port %d%c%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.
111804 validate: Host %s is not found in /etc/hosts but it is required
Description:-2 The host specified in the parameter file is not in /etc/hosts
Solution:-2 Set the host to an existing hostname
112098 File %s is missing, exiting.
Description:The specified file does not exist.
Solution:Refer to the file's or associated service's man page on how to create this file.
112241 Needed Sun Cluster nodes are online, continuing with database start.
Description:All the Sun Cluster nodes needed to start the database are running the resource.
Solution:This is an informational message, no user action is needed.
112493 Trying to switch over the resource group '%s' of resource '%s' from this node.
Description:The zone halt handler is trying to move the resource group form this node so that MDS server(s) of shared qfs file systems configured in this resource group will not be running on this node.
Solution:This is an informational message; no user action is needed.
112826 ERROR: Option -%s not set
Description:The specified option is not set within either the Start, Stop, Probe or Validate command
Solution:The syslog tag identifies the agent script that produced this message. Fix the relevant Start, Stop, Probe or Validate command with the appropriate option. The easiest way to accomplish this is to reregister the resource.
112872 No permission for group to execute %s
Description:The specified path does not have the correct permissions as expected by a program.
Solution:Set the permissions for the file so that it is readable and executable by the group.
113346 clcomm:Cannot forkall() after ORB server initialization.
Description:A user level process attempted to forkall after ORB server initialization. This is not allowed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
113603 Error signaling <%s>: %s
Description:An error occurred while the process using libclcontract attempted to send a signal to one of the processes of the given tag. The reason for the failure is also given.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
113620 Can't create kernel thread
Description:Failed to create a crucial kernel thread for client affinity processing on the node.
Solution:If client affinity is a requirement for some of the sticky services, say due to data integrity reasons, the node should be restarted.
113792 Failed to retrieve the extension property %s: %s
Description:The data service could not retrieve the extension property.
Solution:No user action needed.
113974 Failed to restart fault-monitor : %s
Description:The fault monitor of this ScalMountPoint resource could not be restarted.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
114036 clexecd: Error %d from putmsg
Description:clexecd program has encountered a failed putmsg(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.
114153 Fault-monitor successfully started.
Description:The fault monitor of this ScalMountPoint resource was started successfully. This message is an informational message.
Solution:No user action is required.
114440 HA: exception %s (major=%d) from get_high()
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.
114485 door_create: %s
Description:door_create failed for the specified reason. The specified program will be terminated.
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.
114550 Unable to create <%s>: %s
Description:The HA-NFS stop method attempted to create the specified file but failed.
Solution:Check the error message for the reason of failure and correct the situation. If unable to correct the situation, reboot the node.
114568 Adaptive server successfully started.
Description:Sybase Adaptive server has been successfully started by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed.
114786 An error occurred while reading global zone %s file for filesystem mount point %s
Description:An error occurred while reading the vfstab entry for the specified mount point.
Solution:Verify that the vfstab entry for the mount point is correct and repeat the operation.
115057 Fencing lock already held, proceeding.
Description:The lock used to specify that device fencing is in progress is already held.
Solution:This is an informational message, no user action is needed.
115179 Failed to stat file %s
Description:A stat() call on the test file failed. The probable cause of this error is that the test file does not exist.
Solution:Determine whether the test file exists. If the file 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.
115461 in libsecurity __rpc_get_local_uid failed
Description:A server (rpc.pmfd, rpc.fed or rgmd) refused an rpc connection from a client because it failed the UNIX authentication, because it is not making the rpc call over the loopback interface. 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.
115576 INTERNAL ERROR CMM: Failure creating membership callback thread.
Description:An instance of the userland CMM encountered an internal initialization error. A thread could not be created. 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.
115617 Error in failing over the resource group:%s
Description:The number of restarts of services under the resource has reached the max. Hence Failover was attempted, but failed and the resource group remains in faulted status on its current master.
Solution:Examine the syslog to determine the cause of the failures and execute "clresourcegroup switch" to attempt to switch the resource group to a different node, or "clresourcegroup restart" to restart it.
115981 %s: Cannot create server handle
Description:The daemon cannot provide RPC service because a call to get a service handle failed.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
116312 Unable to determine password for broker %s. Sending SIGKILL now.
Description:The STOP method was unable to determine what the password was to shutdown the broker. The STOP method will send SIGKILL to shut it down.
Solution:Check that the scs1mqconfig file is accessible and correctly specifies the password.
116499 Stopping liveCache times out with command %s
Description:Stopping 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.
116520 Probe command %s finished with return code %d. See %s/ensmon%s.out.%s for output
Description:The specified probe command finished but the return code is not zero.
Solution:See the output file specified in the error message for the return code and the detail error message from SAP utility ensmon.
116614 INTERNAL ERROR: Failed to get zone cluster membership of zone cluster '%s'
Description:A error occurred while retrieving the specified zone cluster membership.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
116910 Unable to connect to Siebel database.
Description:Siebel database may be unreachable.
Solution:Please verify that the Siebel database resource is up.
117498 scha_resource_get error (%d) when reading extension property %s
Description:Error occurred in API call scha_resource_get.
Solution:Check syslog messages for errors logged from other system modules. Stop and start fault monitor. If error persists then disable fault monitor and report the problem.
117648 No entry found in /etc/vfstab, so no mount options will be used.
Description:No entry in /etc/vfstab exists for the specified NFS file system that is exported by a NAS device. This message is an informational message.
Solution:No user action is required.
117689 scvxvmlg fatal error - clconf_lib_init failed, returned %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 inaccessible 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.
117749 Livecache instance name %s is not defined via macro LC_NAME in script %s/%s/db/sap/lccluster
Description:The livecache instance name which is listed in the message is not defined in the script 'lccluster' which is also listed in the message.
Solution:Make sure livecache instance name which is defined in extension property 'Livecache_Name' is defined in script lccluster via the macro LC_NAME. See the instructions in script file lccluster for details.
117803 Veritas is not properly installed, %s not found
Description:Veritas volume manager is not properly installed on this node. Unable to locate the file at the location indicated in the message. Oracle OPS/RAC will not be able to function on this node.
Solution:If you want to run OPS/RAC on this cluster node, verify installation of Veritas volume manager and reboot the node.
118205 Script lccluster is not executable.
Description:Script 'lccluster' is not executable.
Solution:Make sure 'lccluster' is executable.
118288 Stop method completed successfully (Cacao is not running)
Description:The telemetry data service stopped successfully (in this case it was already stopped as Cacao is not running).
Solution:This message is informational; no user action needed.
119649 clcomm: Unregister of pathend state proxy failed
Description:The system failed to unregister the pathend state proxy.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
119671 Validation failed. CRS_HOME %s does not exist
Description:The SUNW.scalable_rac_server_proxy agent could not find the specified $CRS_HOME directory.
Solution:Check whether the $CRS_HOME directory is accessible, and if so, whether its permissions are set appropriately. If the problem persists, contact your Sun support representative for further assistance.
119948 CCR create table failed for zone cluster %s
Description:The CCR raised an exception while creating the clzone_config table.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
120470 (%s) t_sndudata: tli error: %s
Description:Call to t_sndudata() failed. The "t_sndudata" man page describes possible error codes. udlmctl will exit.
Solution: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.
120587 could not set timeout for program %s (%lu): %s
Description:A client was not able to make an rpc connection to the specified server because it could not set the rpc call timeout. The rpc 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.
120714 Error retrieving the resource property %s: %s.
Description:An error occurred reading the indicated property.
Solution:Check syslog messages for errors logged from other system modules. If error persists, please report the problem.
120922 Could not get the zone name. Exiting.
Description:cl_execd program encountered a failure while executing the getzonenamebyid(3C) command. The error message indicates the error number for the failure.
Solution:cl_execd program will exit and the 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.
121237 Telemetry data service monitor successfully started
Description:The monitor program of the telemetry data service started successfully.
Solution:This message is informational; no user action needed.
121286 Could not resolve 'pnm_proxy_server' in the name server. Exiting.
Description:The pnm proxy program could not resolve the pnm proxy server object from the local nameserver.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
121508 Failed to open %s of zone cluster %s: %s.
Description:Failed to open the specific file of zone cluster.
Solution:Check for specific error in the error message and rectify the problem.
121513 Successfully restarted service.
Description:This message indicates that the RGM successfully restarted the resource.
Solution:No user action is required. This is an informational message.
121763 SCSLM lseek <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
121837 Database %s found to be registered with CRS
Description:The SUNW.scalable_rac_server_proxy agent has detected that the Oracle database is valid and registered with CRS.
Solution:No user action is required. This is an informational message.
121858 tag %s: not suspended, cannot resume
Description:The user sent a resume command to the rpc.fed server for a tag that is not suspended. An error message is output to syslog.
Solution:Check the tag name.
122801 check_mysql - Couldn't retrieve defined databases for %s
Description:-2 The database in the start, stop and probe command does not exist.
Solution:-2 Fix the start, stop and probe command.
122838 Error deleting PidLog <%s> (%s) for service with config file <%s>.
Description:The resource was not able to remove the application's PidLog before starting it.
Solution:Check that PidLog is set correctly and that the PidLog file is accessible. If needed delete the PidLog file manually and start the resource group.
123315 Command %s finished with error. Refer to an earlier message with the same command for details.
Description:The command provided in the message finished with some error. The reason for the error is listed in a separate message which includes the same command.
Solution:Refer to a separate message which listed the same command for the reason the command failed.
123526 Prog <%s> step <%s>: Execution failed: no such method tag.
Description:An internal error has occurred in the rpc.fed daemon which prevents step execution. This is considered a step failure.
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 the problem. Retry the edit operation.
123851 Error reported from command: %s
Description:Printed whenever hadbm command execution fails to take off.
Solution:Make sure that java executable present in /usr/bin is linked to appropriate version of j2se needed by hadbm. Also, depending upon the subsequent messages printed, take appropriate actions. The messages following this message are printed as is from hadbm wrapper script.
123984 All specified global device services are available
Description:All global device services specified directly or indirectly via the GlobalDevicePath and FilesystemMountPoint extension properties respectively are found to be available, i.e up and running.
Solution:This is an informational message, no user action is needed.
124168 Function: check_sczbt - %s legacy runlevel [%s] not online, runlevel is %s, Try again in 5 seconds.
Description:The legacy run level is not equal to the configured SLrunlevel. The state is checked again in 5 seconds.
Solution:No user action is required.
124232 clcomm: solaris xdoor fcntl failed: %s
Description:A fcntl operation failed. The "fcntl" man page describes possible error codes.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
124601 Attempt to rebalance resource group %s failed: %s
Description:An attempt was made to bring the named resource group online on the cluster node but it failed. The reason why it failed is also provided in the message.
Solution:Wait to see if a subsequent message indicates that more attempts will be made. If no such message shows up, save a copy of the syslog on all nodes and contact your authorized Sun service provider for assistance.
124810 fe_method_full_name() failed for resource <%s>, resource group <%s>, method <%s>
Description:Due to an internal error, the rgmd daemon was unable to assemble the full method pathname. This is considered a method failure. 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: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 the problem.
124847 scf_instance_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.
124873 pxvfs:startup() Failed to create throttle monitoring thread
Description:Thread to support pxfs throttling could not be launched.
Solution:Check if the node is short on resources.
124935 Either extension property <Child_mon_level> is not defined, or an error occurred while retrieving this property; using the default value of -1
Description:Property Child_mon_level might not be defined in RTR file. The process used the default value of -1.
Solution:This is an informational message; no user action is needed.
125159 Load balancer setting distribution on %s:
Description:The load balancer is setting the distribution for the specified service group.
Solution:This is an informational message, no user action is needed.
125366 Could not create the repository handle: %s
Description:Error in creating the handle to interact with the SMF repository.
Solution:Check the SMF man page to know more about the error. Also make sure the basic SMF functionalities are working. Contact your SUN vendor for more help.
125506 Failed to kill Oracle processes.
Description:Attempt to kill Oracle processes failed. This would leave the resource in a STOP_FAILED state.
Solution:Clear the STOP_FAILED flag for the resource. Manually shutdown Oracle and restart resource.
126142 fatal: new_str strcpy: %s (UNIX error %d)
Description:The rgmd failed to allocate memory, most likely because the system has run out of swap space. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
Solution:The problem is probably cured by rebooting. If the problem recurs, you might need to increase swap space by configuring additional swap devices. See swap(1M) for more information.
126143 RSM controller %s%u unavailable
Description:This is a warning message from the RSM transport to indicate that it cannot locate or get access to an expected controller.
Solution:This is a warning message as one of the controllers for the private interconnect is unavailable. Users are encouraged to run the controller specific diagnostic tests; reboot the system if needed and if the problem persists, have the controller replaced.
126318 fatal: Unknown object type bound to %s
Description:The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.
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.
126467 HA: not implemented for userland
Description:An invocation was made on an HA server object in user land. This is not currently supported.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
126612 Fault monitor detected error %s: <%s> %s Action=%s : %s
Description:Fault monitor has detected an error. Error detected by fault monitor and action taken by fault monitor is indicated in message. This message also indicates whether the action taken is default or user-defined (custom).
Solution:No user action is required.
126887 SCSLM <%s> zone <%s> unexpected user <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
127065 About to perform file system check of %s (%s) using command %s
Description:HAStoragePlus will perform a file system check on the specified device.
Solution:This is an informational message, no user action is needed.
127182 fatal: thr_create returned error: %s (UNIX error %d)
Description:The rgmd failed in an attempt to create a thread. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
Solution:Fix the problem described by the UNIX error message. The problem may have already been corrected by the node reboot.
127561 cl_execd: dup2 of stderr returned with errno %d while exec'ing (%s). Exiting.
Description:cl_execd program has encountered a failed dup2(2) system call. The error message indicates the error number for the failure.
Solution:The cl_execd program will exit and the node will be halted to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
127607 The stop command <%s> failed to stop the application. Will now use SIGKILL to stop the Node Agent and all the server instances.
Description:This is an informational message. The stop method first tries to stop the Node Agents and the Application Server instances using the "asadmin stop-node-agent" command. The error message indicates that this command failed. The command fails if the Node Agent is already stopped. The Stop Method will send SIGKILL to all the processes using PMF to make sure all the processes are stopped.
Solution:No user action is required.
127624 must be superuser to start %s
Description:Process ucmmd did not get started by superuser. The ucmmd will exit now.
Solution:No user action is required. This is an internal error.
127800 Hosting member %s of instance %s matches with hostname %s
Description:The node specified to the SUNW.scalable_rac_server_proxy resource as hosting the RAC instance matches with the node configured as the hosting member for that RAC instance, with CRS.
Solution:No user action is required. Informational message.
127930 About to mount %s.
Description:HAStoragePlus will mount the underlying device corresponding to the specified mount point specified in /etc/vfstab.
Solution:This is an informational message, no user action is needed.
129240 SCSLM <%s> shares 0 pset %d
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
129752 Unable to stop database.
Description:The HADB agent encountered an error trying to stop the database.
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.
129832 Incorrect syntax in Environment_file.Ignoring %s
Description:Incorrect syntax in Environment_file. Correct syntax is: VARIABLE=VALUE
Solution:Please check the Environment_file and correct the syntax errors.
130346 invalid mask in hosts list: <%s> (%d)
Description:The allow_hosts or deny_hosts for the CRNP service contains an invalid mask. This error may prevent the cl_apid from starting up.
Solution:Remove the offending IP address from the allow_hosts or deny_hosts property, or fix the mask.
130768 %s has not been disabled under smf(5). Exiting.
Description:The HA-KDC service has not been disabled in SMF. It cannot remain in SMF control because of fault management conflict.
Solution:This is an internal error. No user action needed. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
130822 CMM: join_cluster: failed to register ORB callbacks with CMM
Description:The system can not continue when callback registration fails.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
131094 cl_execd: sigwait returned %d. Exiting.
Description:cl_execd program has encountered a failed sigwaitinfo(3RT) 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.
131589 Failed to retrieve property "ResourceGroup_name"
Description:The name of the resource group that contains this ScalMountPoint resource could not be retrieved.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
132032 clexecd: strdup returned %d. Exiting.
Description:clexecd program has encountered a failed strdup(3C) system call. The error message indicates the error number for the failure.
Solution:If the error number is 12 (ENOMEM), install more memory, increase swap space, or reduce peak memory consumption. If error number is something else, contact your authorized Sun service provider to determine whether a workaround or patch is available.
132294 Unable to set microstate accounting. Continue.
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
133146 Unable to execve %s: %s
Description:The libclcontract code was not able to exec the specified process, possibly due to bad arguments. The message contains the system error. The server process (which is using libclcontract) does not perform the action requested by the client, and an error message is output to syslog.
Solution:Verify that the file path to be executed exists. 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.
133612 All the sQFS file systems configured to this node through SUNW.qfs resources are available. Zone boot operation completed successfully.
Description:The zone boot handler successfully brought all the shared qfs file systems available to this node.
Solution:This is an informational message; no user action is needed.
133737 SCSLM <%s> pool_resource_to_elem error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
133818 child (pid %d) forked by pmmd could not get the signal name for signal number %d using sig2str(3C)
Description:The child that was forked by the pmmd daemon was unable to get the signal name for a signal number because the sig2str(3C) function failed.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
134167 Unable to set maximum number of rpc threads
Description:The rpc.pmfd server was not able to set the maximum number of rpc threads. This happens while the server is starting up, at boot time. The server does not come up, 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.
134411 %s can't unplumb
Description:This means that the Logical IP address could not be unplumbed from an adapter.
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.
136330 This resource depends on a HAStoragePlus resource that is not online. Unable to perform validations.
Description:The resource depends on a HAStoragePlus resource that is not online on any node. Some of the files required for validation checks are not accessible. Validations cannot be performed on any node.
Solution:Enable the HAStoragePlus resource that this resource depends on and reissue the command.
136646 SCSLM fgetprojent S9 proj <%s> zone <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
136852 in libsecurity for program %s (%lu); could not negotiate uid on any loopback transport in /etc/netconfig
Description:None of the available transport agreed to provide the uid of the clients to the specified server. This happened because either there are no available transports at all, or there are but none is a loopback. 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.
136955 Failed to retrieve main dispatcher pid
Description:Failed to retrieve the process ID for the main dispatcher process indicating the main dispatcher process is not running.
Solution:No user action is required. The fault monitor will detect this and take appropriate action.
137257 Failed to enable %s service
Description:The Solaris service management facility failed to enable the service instance that the fault management resource identifier (FMRI) in the /var/adm/messages specifies.
Solution:Run the command 'svcadm enable <fmri>' to enable the service instance. Then run the command 'svcs -x <service>' to verify that the service is online. If the problem persists, contact your Sun Support representative for further assistance.
137294 method_full_name: strdup failed
Description:The rgmd server was not able to create the full name of the method, 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.
137558 SAP xserver is running, will start SAPDB database now
Description:Informational message. The SAP xserver is running. Therefore the SAPDB database instance will be started by the Sun Cluster software.
Solution:No user action is required.
137606 clcomm: Pathend %p: disconnect_node not allowed
Description:The system maintains state information about a path. The disconnect_node operation is not allowed in this state.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
137823 Incorrect permissions detected for the executable %s: %s
Description:The specified executable is not owned by user "root" or is not executable.
Solution:Correct the rights of the filename by using the chmod/chown commands.
137964 Derby data service validate method completed successfully
Description:The derby data service could be validated.
Solution:This message is informational; no user action is needed.
138044 %s on node %d, stderr: %s
Description:A remote command failed and produced information in its standard error.
Solution:Check the message to determine what might be wrong. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
138261 File system associated with mount point %s is to be locally mounted. The AffinityOn value cannot be FALSE.
Description:HAStoragePlus detected that the specified mount point in /etc/vfstab is a local mount point, hence extension property AffinityOn must be set to True.
Solution:Set the AffinityOn extension property of the resource to True.
139161 SCSLM <%s> pool_conf_open <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
139276 Error: Unable to update scha_control timestamp file <%s> for resource <%s> on node <%s>
Description:The rgmd failed in a call to utime(2) on the local node. This may prevent the anti-"pingpong" feature from working, which may permit a resource group to fail over repeatedly between two or more nodes. The failure of the utime call might indicate a more serious problem on the 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.
139584 fatal: unable to determine if resource group %s exists.
Description:The rgmd failed to detect the existence of the specified resource group, so was unable to complete the administrative request. The node will be aborted.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified which is preventing the CCR access. 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.
139852 pmf_set_up_monitor: pmf_add_triggers: %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 syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
140045 Failed to open the resource type handle: %s
Description:HAStoragePlus failed to access the resource type information.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
140133 PMFD XDR Buffer Shortfall while encoding return arguments API num = %d. Will retry.
Description:A non-fatal error occurred while rpc.pmfd was marshalling return values for a remote procedure call. The operation will be retried 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.
140428 cl_load: error loading kernel module: %d
Description:The loading of the cl_load module failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
140749 Update on the resource failed: %s
Description:The online update operation of the HAStoragePlus resource is not successful.
Solution:Examine the syslog messages, to see if the problem can be identified. This problem is usually caused by a failure in device switchovers or failure in mounting file systems. Check the global service configuration and system configuration. If unable to resolve this problem save a copy of /var/adm/messages and contact your authorized Sun service provider for assistance.
141062 Failed to connect to host %s and port %d: %s
Description:An error occurred while fault monitor attempted to probe the health of the data service.
Solution:Wait for the fault monitor to correct this by doing restart or failover. For more error description, look at the syslog messages.
141236 Failed to format stringarray for property %s from value %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.
141242 HA: revoke not implemented for replica_handler
Description:An attempt was made to use a feature that has not been implemented.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
141504 fatal: The rgm is trying to run at a lower version than that supported by the CCR contents
Description:The cluster software has been rolled back to a version that is incompatible with the current CCR contents.
Solution:Complete an upgrade of the cluster software to the higher version at which it was previously running.
141643 Stop of HADB node %d failed with exit code %d
Description:The resource encountered an error trying to stop 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.
141970 in libsecurity caller has bad uid: get_local_uid=%d authsys=%d desired uid=%d
Description:A server (rpc.pmfd, rpc.fed or rgmd) refused an rpc connection from a client because it has the wrong uid. The actual and desired uids are 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.
142762 Failed to retrieve the resource group Nodelist property
Description:HAStoragePlus was not able to retrieve the resource group Nodelist property from the CCR.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
142889 Starting up saposcol process under PMF times out
Description:Starting up the SAP OS collector process under the control of Process Monitor facility times out. This might happen under heavy system load.
Solution:You might consider increase the start timeout value.
143694 lkcm_act: caller is allready registered
Description:Message indicating that udlm is already 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.
144303 fatal: uname: %s (UNIX error %d)
Description:A uname(2) system call failed. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
144373 pthread_create error : %s
Description:The libclcontract code was unable to create a thread as pthread_create(3C) failed. The message contains the system error. Consequently, the process that is using libclcontract was unable to receive contract events, and will exit.
Solution: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.
144509 UNRECOVERABLE ERROR: Sun Cluster boot: /usr/cluster/lib/sc/cl_execd not found
Description:/usr/cluster/lib/sc/cl_execd is missing.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
144706 File system check of %s (%s) failed: (%d) %s
Description:Fsck reported inconsistencies while checking the specified device. The return value and output of the fsck command is also embedded in the message.
Solution:Try to manually check and repair the file system which reports errors.
145286 Failed to retrieve the resource group property %s of %s: %s.
Description:An error occurred while retrieving the specified property of the resource group.
Solution:Investigate possible RGM errors. Contact your authorized Sun service provider for assistance in diagnosing the problem with copy of the /var/adm/messages files on all nodes.
145468 in libsecurity for program %s (%lu); __rpc_negotiate_uid failed for transport %s
Description:The specified server was not able to start because it could not establish a rpc connection for the network. 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.
145770 CMM: Monitoring disabled
Description:Transport path monitoring has been disabled in the cluster. It is enabled by default.
Solution:This is an informational message, no user action is needed.
145800 Validation failed. ORACLE_HOME/bin/sqlplus not found ORACLE_HOME=%s
Description:Oracle binaries (sqlplus) not found in ORACLE_HOME/bin directory. ORACLE_HOME specified for the resource is indicated in the message. HA-Oracle will not be able to manage resource if ORACLE_HOME is incorrect.
Solution:Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.
145893 CMM: Unable to read quorum information. Error = %d.
Description:The specified error was encountered while trying to read the quorum information from the CCR. This is probably because the CCR tables were modified by hand, which is an unsupported operation. The node will panic.
Solution:Reboot the node in non-cluster (-x) mode and restore the CCR tables from the other nodes in the cluster or from backup. Reboot the node back in cluster mode. The problem should not reappear.
146035 CMM: Unable to get current zone name
Description:An instance of the userland CMM encountered an internal initialization error. The name of the zone, in which the userland CMM is running, could not be obtained.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
146407 scvxvmlg error - symlink(%s, %s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
146453 UNRECOVERABLE ERROR: Mount point for alternate boot environment not found
Description:Reading mount point from ${QL_LU_CONTINUE} failed with error code ${retval}
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
146660 %s on node %d, stdout: %s
Description:A remote command failed and produced information in its standard output.
Solution:Check the message to determine what might be wrong. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
146686 Failed to add resource '%s' to the list of SUNW.qfs resource list.
Description:The zone boot handler failed to generate the list of SUNW.qfs resources.
Solution:Investigate the zone boot log messages and try to rectify the problem. If problem persists after rebooting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
146952 Hostname lookup failed for %s: %s
Description:The hostname could not be resolved into its IP address.
Solution:Check the settings in /etc/nsswitch.conf and verify that the resolver is able to resolve the hostname.
147394 scf_entry_add_value 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.
147501 Unable to make door call.
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.
147874 Out of memory
Description:The 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.
148465 Prog <%s> step <%s>: RPC connection error.
Description:An attempted program execution failed, due to an RPC connection problem. This failure is considered a program failure.
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.
148506 Cluster appears to be pingpong rebooting because of failure of method <%s> on resource <%s>. RGM is not aborting node %s.
Description:A stop method is failed and Failover_mode is set to HARD, but the RGM has detected this resource group falling into pingpong behavior and will not abort the node on which the resource's stop method failed. This is most likely due to the failure of both start and stop methods.
Solution:Save a copy of /var/adm/messages, check for both failed start and stop methods of the failing resource, and make sure to have the failure corrected. To restart the resource group, refer to the procedure for clearing the ERROR_STOP_FAILED condition on a resource group in the Sun Cluster Administration Guide.
148821 Error in trying to access the configured network resources : %s
Description:Failed to get the available network address resources for this resource.
Solution:For a failover data service, add a network address resource to the resource group. For a scalable data service, add a network resource to the resource group referenced by the RG_dependencies property. This is an internal error. Save the /var/adm/messages file and contact an authorized Sun service provider.
148902 No node was specified as part of property %s for element %s. The property must be specified as %s=Weight%cNode,Weight%cNode,...
Description:The property was specified incorrectly.
Solution:Set the property using the correct syntax.
149184 clcomm: inbound_invo::signal:_state is 0x%x
Description:The internal state describing the server side of a remote invocation is invalid when a signal arrives during processing of the remote invocation.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
149430 Unable to allocate memory in sc delegated resource mgmt
Description:Problem in creating memory space during resource management of SMF delegated restarter
Solution:Check the system memory usage
150099 Failed to obtain the absolute path of local mount point %s (%s) in zone %s
Description:HAStoragePlus failed to obtain the absolute pathname for the specified mount point of local zone.
Solution:Check the realpath(3C) man page for errors and try to resolve the problem. Otherwise contact your authorized Sun service provider.
150171 Function: validate - Zone name not set in %s
Description:The variable Zonename does not contain a value.
Solution:Review the components configuration file and make sure the variable Zonename is properly defined.
150317 The stop command <%s> failed to stop the application.
Description:The user provided stop command cannot stop the application.
Solution:No user action is required.
150535 clcomm: Could not find %s(): %s
Description:The function get_libc_func could not find the specified function for the reason specified. Refer to the man pages for "dlsym" and "dlerror" for more information.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
151010 Grant of access rights on v_$ views failed.
Description:Access rights on v_$views could not be granted to the fault monitor user that the extension property connect_string specifies.
Solution:Check that the fault monitor user has been created, and that the procedure for creating this user in the user documentation for the Oracle data service has been followed correctly. If the fault monitor user has not been created correctly, repeat the procedure for creating this user. If the fault monitor user has been created correctly, check that the database is in writable mode. If the problem persists, contact your Sun support representative for further assistance.
151213 More than one node will be offline, stopping database.
Description:When the resource is stopped on a Sun Cluster node and the resource will be offline on more then one node the entire database will be stopped.
Solution:This is an informational message, no user action is needed.
151273 CCR: Remove cluster %s failed.
Description:The CCR failed to remove the indicated cluster.
Solution:The failure can happen due to many reasons, for some of which no user action is required because the CCR client in that case will handle the failure. The cases for which user action is required depends on other messages from CCR on the node, and include: If it failed because the cluster lost quorum, reboot the cluster. 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 cluster repository is corrupted as indicated by other CCR messages, then boot the offending node(s) in -x mode to restore the cluster repository from backup. The cluster repository is located at /etc/cluster/ccr/.
151497 There are no Node Agents configured on %s in the directory %s
Description:There are no Node Agents configured on the Logical Host that is created in this Resource Group. There are no Node agents to be brought online in this resource group.
Solution:Change the configuration so that the Node Agents listen on the logical host that you have in the Resource Group or change the logical host resource to the correct logical host that the Node Agents use.
151818 SCSLM waitpid pid %u ret %d errno %d wstat 0x%x
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
152137 PNM proxy : fork1 failed, errno = %d. Exiting.
Description:The pnm proxy program has encountered failure of fork1(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.
152159 WARNING: lkcm_sync: udlm_send_reply failed, forcing reconfiguration
Description:A reconfiguration will start.
Solution:No user action is required.
152222 Fault monitor probe average response time of %d msecs exceeds 90%% of probe timeout (%d secs). The timeout for subsequent probes will be temporarily increased by 10%%.
Description:The average time taken for fault monitor probes to complete is greater than 90% of the resource's configured probe timeout. The timeout for subsequent probes will be increased by 10% until the average probe response time drops below 50% of the timeout, at which point the timeout will be reduced to it's configured value.
Solution:The database should be investigated for the cause of the slow response and the problem fixed, or the resource's probe timeout value increased accordingly.
152478 Monitor_retry_count or Monitor_retry_interval is not set
Description:The resource properties Monitor_retry_count or Monitor_retry_interval has not set. These properties control the restarts of the fault monitor.
Solution:Check whether the properties are set. If not, set these values by using clresource or scrgadm(1M).
152532 RGM isn't restarting resource group <%s> or resource <%s> on node <%s> because that node does not satisfy the strong or restart resource dependencies of the resource.
Description:A scha_control call has failed with a SCHA_ERR_CHECKS error because the specified resource has a resource dependency that is unsatisfied on the specified node. A properly-written resource monitor, upon getting the SCHA_ERR_CHECKS error code from a scha_control call, should sleep for awhile and restart its probes.
Solution:Usually no user action is required, because the dependee resource is switching or failing over and will come back online automatically. At that point, either the probes will start to succeed again, or the next scha_control attempt will succeed. If that does not appear to be happening, you can use clresource to determine the resources on which the specified resource depends that are not online, and bring them online.
152546 ucm_callback for stop_trans generated exception %d
Description:ucmm callback for stop transition 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.
153018 WARNING: missing msg, expected: dont_care, %d, %d, but received : %d %d, %d. FORCING reconfiguration.
Description:Unexpected message received by udlm. This will trigger an OPS reconfiguration.
Solution:No user action is required.
153056 Giveover attempt failed for %s: resource group is currently starting or stopping. retries exhausted.
Description:Got an error attempting to switch over the QFS meta data resource group. This error has persisted until all retries have been exhausted.
Solution:Verify that the cluster is correctly configured. If it is, contact your authorized Sun service provider to determine whether a workaround or patch is available.
153246 dl_bind: DL_BIND_ACK bad sap %u
Description:SAP in acknowledgment to bind request is different from the SAP in the request. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
153925 node %d of zone cluster %s died
Description:The RGM has detected that the indicated zone cluster node has halted or rebooted. If any resource groups were online in that zone cluster node, they might fail over to other nodes of the zone cluster.
Solution:This is an informational message; no user action is needed.
154111 Failed to reach the agents localhost:%s
Description:Could not reach the Management agent at localhost
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.
154317 launch_validate: fe_method_full_name() failed for resource <%s>, resource group <%s>, method <%s>
Description:Due to an internal error, the rgmd daemon was unable to assemble the full method pathname for the VALIDATE method. This is considered a VALIDATE method failure. This in turn will cause the failure of a creation or update operation on a resource or resource group.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Retry the creation or update operation. If the problem recurs, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
154655 Failed to issue command (%s). popen failed with error: %s
Description:There was an error issuing a command.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
155479 ERROR: VALIDATE method timeout property of resource <%s> is not an integer
Description:The indicated resource's VALIDATE method timeout, as stored in the CCR, is not an integer value. This might indicate corruption of CCR data or rgmd in-memory state; the VALIDATE method invocation will fail. This in turn will cause the failure of a creation or update operation on a resource or resource group.
Solution:Use clresource show -v to examine resource properties. If the VALIDATE method timeout or other property values appear corrupted, the CCR might have to be rebuilt. If values appear correct, this may indicate an internal error in the rgmd. Retry the creation or update operation. If the problem recurs, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
155796 About to lofs mount of %s on %s in local zone '%s'
Description:HAStoragePlus will loopback mount of file system existing on specified path name onto a specified mount point in local zone.
Solution:This is an informational message, no user action is needed.
156396 dl_bind: DLPI error %u
Description:DLPI protocol error. We cannot bind to the physical device. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
156454 Resource %s does not have the property DB_PATH defined
Description:The property DB_PATH is a mandatory property of the data service. Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
157213 CCR: The repository on the joining node %s could not be recovered, join aborted.
Description:The indicated node failed to update its repository with the ones in current membership. And it will not be able to join the current membership.
Solution:There may be other related messages on the indicated node, which help diagnose the problem, for example: If the root disk failed, it needs to be replaced. If the root disk is full, remove some unnecessary files to free up some space.
157340 invalid user name %s for method %s fmri %s
Description:Invalid username
Solution:Please check the user specified under method_credentials in the smf manifest file for this fmri.
157736 Unable to queue event %lld
Description:The cl_apid was unable to queue the incoming sysevent specified.
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.
158186 Could not retrieve the BASEDIR information of the derby package (%s)
Description:Unable to retrieve information related to a package.
Solution:Verify that the package is installed. If it is correctly installed, contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
158836 Endpoint %s initialization error - errno = %d, failing associated pathend.
Description:Communication with another node could not be established over the path.
Solution:Any interconnect failure should be resolved, and/or the failed node rebooted.
159416 fatal: unable to register door service; aborting node
Description:The rgmd daemon was unable to start up successfully because it failed to register a door service. It will produce a core file and will force the node to halt or reboot.
Solution:If rebooting the node doesn't fix the problem, examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
159501 host %s failed: %s
Description:The rgm is not able to establish an rpc connection to the rpc.fed server on the host shown, and the error message 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.
159592 clcomm: Cannot make high %d less than current total %d
Description:An attempt was made to change the flow control policy parameter specifying the high number of server threads for a resource pool. The system does not allow the high number to be reduced below current total number of server threads.
Solution:No user action required.
159607 %s:waitpid. %s
Description:The rpc.pmfd or rpc.fed server was not able to wait for a process. 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.
159763 Logical nodename '%s', unreachable
Description:Did not receive a response from the specified logical host name's interface.
Solution:Check to make sure that the interface associated with the logical host name is up and configured correctly.
159913 Membership: Unable to get cluster name for cluster ID %d.
Description:Membership subsystem was unable to get the cluster name for a cluster ID.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
160032 ping_retry %d
Description:The ping_retry value used by scdpmd.
Solution:No user action is required.
160167 Server successfully started.
Description:Informational message. Oracle server has been successfully started by HA-Oracle.
Solution:No user action is required.
160400 fatal: fcntl(F_SETFD): %s (UNIX error %d)
Description:This error should not occur. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
160472 scnetapp fatal error - Missing filer name from table %s
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
160475 "%s": missed one or more exit events
Description:The rpc.pmfd received an empty contract event before receiving exit events for one or more processes in the contract. This error will not impact the rpc.pmfd's functionality.
Solution:No user action is required.
160619 Could not enlarge buffer for DBMS log messages: %m
Description:Fault monitor could not allocate memory for reading RDBMS log file. As a result of this error, fault monitor will not scan errors from log file. However it will continue fault monitoring.
Solution:Check if system is low on memory. If problem persists, please stop and start the fault monitor.
160729 %s: exit_event: ct_pr_event_get_pid: %s
Description:The pmmd was unable to retrieve the pid from a contract event. The pmmd will continue to monitor the process, but the pmmd may have missed an event of interest.
Solution: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.
160857 scha_resource_get operation %s failed for Resource %s
Description:The Resource is left in a faulted status and is not restarted.
Solution:Examine the /var/adm/messages to determine why the resource is failing, and restart it after taking corrective action. The resource can be restarted by the sequence "clresource disable <resource>; clresource enable <resource>". You can also restart the whole resource group using "clresourcegroup restart <group>". If the problem persists, contact your Sun service representative.
161041 SCTP bind address validation failed because the size of the address list exceeds the expected value
Description:Number of addresses that are configured in the node has exceeds the maximum value.
Solution:Reduce the number of addresses that are plumbed in the system.
161104 Adaptive server stopped.
Description:The Adaptive server has been shutdown by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed.
161275 reservation fatal error(UNKNOWN) - Illegal command line option
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.
161562 ct_tmpl_activate: %s
Description:The libclcontract code was unable to configure a process template in which to launch the requested service. Consequently, the process that is using libclcontract was unable to launch the process under its control.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
161643 Function: stop_sczbt - The non-global zone %s was successfully halted and reached state %s
Description:The second zoneadm halt was able to get the non-global zone into state "installed".
Solution:No user action is required.
161683 $SYBASE/$SYBASE_ASE/install/startserver does not have execute permissions set
Description:The Sybase Adaptive Server is started by execution of the "startserver" file. The file's current permissions prevent its execution. The full path name of the "startserver" file is specified as a part of this error message. This file is located in the $SYBASE/$ASE/install directory
Solution:Verify the permissions of the "startserver" file and ensure that it can be executed. If not, use chmod to modify its execute permissions.
161903 CMM: Unable to instantiate a quorum device type object of type '%s' for qid %d with gdevname '%s'
Description:The kernel quorum module for this type of quorum device was not loaded, or an instance of the quorum device type object was not created. The node ignores this quorum device until corrective action is taken.
Solution:The most likely reason for this problem is that the system is missing the quorum module for this type of device. Determine whether the component is missing. If so, then install the missing quorum module. The quorum device can then be brought online either by rebooting the entire cluster, or by unconfiguring the quorum device and then configuring the same quorum device. If the appropriate quorum module is present, contact your authorized Sun service provider to determine if a workaround or patch is available.
161934 pid %d is stopped.
Description:HA-NFS fault monitor has detected that the specified process has been stopped with a signal.
Solution:No user action is required. HA-NFS fault monitor would kill and restart the stopped process.
161991 Load balancer for group '%s' setting weight for node %s to %d
Description:This message indicates that the user has set a new weight for a particular node from an old value.
Solution:This is an informational message, no user action is needed.
162419 ERROR: launch_method: cannot get Failover_mode for resource <%s>, assuming NONE
Description:A method execution has failed or timed out. For some reason, the rgmd is unable to obtain the Failover_mode property of the resource. The rgmd assumes a setting of NONE for this property, therefore avoiding the outcome of rebooting the node (for STOP method failure) or failing over the resource group (for START method failure). For these cases, the resource is placed into a STOP_FAILED or START_FAILED state, respectively.
Solution:Save a copy of the /var/adm/messages files on all nodes, and contact your authorized Sun service provider for assistance in diagnosing the problem.
162484 Method <%s> failed to execute on resource <%s> in resource group <%s>, SLM error: <%d>
Description:Resource group is under SC SLM control and an SLM error occurred. Some errors might be configuration errors. Check fed SLM errors for more details.
Solution:Move RG_SLM_type to manual and restart the resource group.
162502 tag %s: %s
Description:The tag specified that is being run under the rpc.fed produced the specified message.
Solution:This message is for informational purposes only. No user action is necessary.
162505 Could not start Siebel server: %s
Description:Siebel server could not start because a service it depends on is not running.
Solution:Make sure that the Siebel database and the Siebel gateway are running before attempting to restart the Siebel server resource.
162531 Failed to retrieve resource group name
Description:HAStoragePlus was not able to retrieve the resource group name to which it belongs from the CCR.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
162851 Unable to lookup nfs:nfs_server:calls from kstat
Description:See 176151
Solution:See 176151
163181 Failed to retrieve property "ResourceType_name"
Description:There was an error in retrieving the type name of the resource.
Solution:Investigate possible RGM, DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
163379 Transport heart beat quantum is changed to %s
Description:The global transport heart beat quantum is changed.
Solution:No user action is required. This is only for information.
163381 Checking for the status of SUNW.qfs resources that are configured for this zone cluster
Description:This is a notification message that the checking of the status of SUNW.qfs resources is started.
Solution:This is an informational message; no user action is needed.
164164 Starting Sybase %s: %s. Startup file: %s
Description:Sybase server is going to be started by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed.
164757 reservation fatal error(%s) - realloc() error, errno %d
Description:The device fencing program has been unable to allocate required memory.
Solution:Memory usage should be monitored on this node and steps taken to provide more available memory if problems persist. Once memory has been made available, the following steps may need to taken: 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, access to shared devices 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 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. The device group can be switched back to this node if desired by using the cldevicegroup command. If no other node was available, then the device group will not have been started. Use the cldevicegroup command 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. You can retry the desired action.
165527 Oracle UDLM package is not properly installed. %s not found.
Description:Oracle udlm package installation problem.
Solution:Make sure Oracle UDLM package is properly installed.
165638 fatal: cannot contact president
Description:The rgmd on this node was unable to make an inter-node IDL call. The rgmd will abort and the node will panic.
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.
165731 Backup server successfully started.
Description:The Sybase backup server has been successfully started by Sun Cluster HA for Sysbase.
Solution:This is an information message, no user action is needed.
165935 CCR: Cluster has lost quorum while updating table %s (cluster = %s), it is possibly in an inconsistent state - ABORTING.
Description:The cluster lost quorum while the indicated table was being changed, leading to potential inconsistent copies on the nodes.
Solution:Check if the indicated table are consistent on all the nodes in the cluster, if not, boot the cluster in -x mode to restore the indicated table from backup. The CCR tables are located at /etc/cluster/ccr/.
166068 The attempt to kill the probe failed. The probe left as-is.
Description:The failover_enabled is set to false. Therefore, an attempt was made to make the probe quit using PMF, but the attempt failed.
Solution:This is an informational message, no user action is needed.
166235 Unable to open 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.
166279 scnetapp fatal error - illegal nas type %s
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
166489 reservation error(%s) error. Node %d is not in the cluster
Description:A node which the device fencing program was communicating with has left the cluster.
Solution:This is an informational message, no user action is needed.
166560 Maximum Primaries is %d. It should be 1.
Description:Invalid value has set for Maximum Primaries. The value should be 1.
Solution:Reset this value by using clresourcegroup.
166640 Updating nsswitch.conf ...
Description:The nsswitch.conf(4) configuration file is being updated.
Solution:This is an informational message. No user action is required.
167108 Starting Oracle server.
Description:Informational message. Oracle server is being started by HA-Oracle.
Solution:No user action is required.
167253 Server stopped successfully.
Description:Informational message. Oracle server successfully stopped.
Solution:No user action is required.
167846 Could not start the events proxy server: %s
Description:The events proxy server could not be started due to some internal error. Processes in non-global zones will be unable to log systems events. System events is a mechanism to keep an audit trail of the cluster actions. Although, this will have no effect on the working of the cluster.
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.
168092 reservation warning(%s) - MHIOCGRP_REGISTER 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.
168150 INTERNAL ERROR CMM: Cannot bind quorum algorithm object to local name server.
Description:There was an error while binding the quorum subsystem object to the local name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
168318 Fault monitor probe response time of %d msecs exceeds 90%% of probe timeout (%d secs). The timeout for subsequent probes will be temporarily increased by 10%%
Description:The time taken for the last fault monitor probe to complete was greater than 90% of the resource's configured probe timeout. The timeout for subsequent probes will be increased by 10% until the probe response time drops below 50% of the timeout, at which point the timeout will be reduced to it's configured value.
Solution:The database should be investigated for the cause of the slow response and the problem fixed, or the resource's probe timeout value increased accordingly.
168444 %s is erroneously found to be unmounted.
Description:HAStoragePlus found that the specified mount point was unmounted but should not have been.
Solution:This is an informational message, no user action is needed.
168630 could not read cluster name
Description:Could not get cluster name. Perhaps the system is not booted as part of the cluster.
Solution:Make sure the node is booted as part of a cluster.
168885 Complete_Probe for resource sckrb5 successful.
Description:The complete probe of Kerberos received no error.
Solution:This is for informational purposes, no action is required.
168970 sun_udlm_read_oracle_cfg: open failed: %s ... will use default values
Description:Could not read parameter values from config file. Will use default values instead.
Solution:No user action is required.
169082 start_dependency: Exceeded %s seconds for waiting on dependent resource for resource %s to come online
Description:A resource which the resource depends on has not come online within the specified time.
Solution:check dependencies, check the resource indicated as the resource depends from.
169297 Could not create zone cluster due to lack of network addresses. Run the cluster(1CL) set-netprops command to specify the number of zone clusters and rerun the command.
Description:The clzonecluster command was not able to create the specified zone cluster due to insufficient private network addresses.
Solution:Run the cluster command to specify the number of zone clusters that you expect to create in the base cluster. Then rerun the clzonecluster command to create the zone cluster.
169308 Database might be down, HA-SAP won't take any action. Will check again in %d seconds.
Description:Database connection check failed indicating the database might be down. HA-SAP will not take any action, but will check the database connection again after the time specified.
Solution:Make sure the database and the HA software for the database are functioning properly.
169329 reservation warning(%s) - MHIOCTKOWN 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.
169358 The network resource has not been configured.
Description:The network address resource have not been configured.
Solution:Add the network resource to the associated resource group.
169409 File %s is not owned by user (UID) %d
Description:The file is not owned by the uid which is listed in the message.
Solution:Set the permissions on the file so that it is owned by the uid which is listed in the message.
169586 Monitor check for sckrb5 failed.
Description:The node to be failed over to for HA-KDC is not ready.
Solution:Use scstat to help determine the reason why the other node can not be failed over to.
169606 Unable to create thread. Exiting.
Description:clexecd program has encountered a failed thr_create(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.
169608 INTERNAL ERROR: scha_control_action: invalid action <%d>
Description:The scha_control function has encountered an internal logic error. This will cause scha_control to fail with a SCHA_ERR_INTERNAL error, thereby preventing a resource-initiated failover.
Solution:Please save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.
169765 Configuration file not found
Description:Internal error. Configuration file for online_check not found.
Solution:Please report this problem.
170417 Derby data service stop method failed for unknown reason
Description:The derby data service could not stop for an unknown reason.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
170587 INTERNAL ERROR: Failed to retrieve %s
Description:Failed to retrieve Resource STATUS.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
170704 %s is confirmed as unmounted
Description:HAStoragePlus certifies that the specified file system is not in /etc/mnttab.
Solution:This is an informational message, no user action is needed.
170910 sge_qmaster already running; start_sge_qmaster aborted.
Description:An attempt was made to start sge_qmaster by bringing the sge_qmaster-rs resource online, with an sge_qmaster process already running.
Solution:Terminate the running sge_qmaster process and retry bringing the resource online.
171031 reservation fatal error(%s) - get_control() failure
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.
171216 Malformed door call discarded
Description:A zoneup message was improperly formatted. It will be ignored.
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.
171878 in libsecurity setnetconfig failed when initializing the client: %s - %s
Description:A client was not able to make an rpc connection to a server (rpc.pmfd, rpc.fed or rgmd) because it could not establish a rpc connection for the network specified. The rpc error and the system error are 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.
171976 Execution of method <%s> on resource <%s>, node <%s> skipped to achieve user-initiated fast quiesce of the resource group <%s>.
Description:The system administrator has requested a fast quiesce of the resource group indicating that the running callback methods if any, should be killed to speed its completion. Though the method had already been scheduled to be launched when the quiesce command was given, it hadn't actually been launched. Hence RGM doesn't launch this method and instead assumes the method to have failed.
Solution:This is just an informational message generated by a quiesce operation initiated by the user.
172566 Stopping oracle server using shutdown abort
Description:Informational message. Oracle server will be stopped using 'shutdown abort' command.
Solution:Examine 'Stop_timeout' property of the resource and increase 'Stop_timeout' if you don't wish to use 'shutdown abort' for stopping Oracle server.
173100 Remove_configuration - The deletion of the MySQL replication resource group %s failed
Description:The MySQL replication resource group was not deleted
Solution:Evaluate the root cause for the failed deletion and retry the operation
173201 Removing node %s from device service %s
Description:Informational message from scdidadm.
Solution:No user action required.
173213 PNM proxy: Unable to create thread, errno = %d. Exiting\n.
Description:The pnm proxy program encountered a failure while executing thr_create(3C). The failure could be because the system may be running low on memory.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
173380 Command failed: %s -U %s db_state: %s.
Description:An SAP command failed for the reason that is stated in the message.
Solution:No user action is required.
173733 Failed to retrieve the resource type property %s for %s: %s.
Description:The query for a property 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.
173939 SIOCGLIFSUBNET: %s
Description:The ioctl command with this option failed in the cl_apid. 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.
174078 Adaptive server shutdown with nowait failed. STOP_FILE %s.
Description:The Sybase adaptive server failed to shutdown with the nowait option using the file specified in the STOP_FILE property.
Solution:No user action is needed. Other syslog messages, the log file of Sun Cluster HA for Sybase or the adaptive server log file may provide additional information on possible reasons for the failure.
174497 Invalid configuration. SUNWcvmr and SUNWcvm packages must be installed on this node when using Veritas Volume Manager for shared disk groups.
Description:Incomplete installation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters. RAC framework will not function correctly on this node due to incomplete installation.
Solution:Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.
174751 Failed to retrieve the process monitor facility tag.
Description:Failed to create the tag that has used to register with the process monitor facility.
Solution:Check the syslog messages that occurred just before this message. In case of internal error, save the /var/adm/messages file and contact authorized Sun service provider.
174909 Failed to open the resource handle: %s.
Description:An API operation has failed while retrieving the resource property. Low memory or API call failure might be the reasons.
Solution:In case of low memory, the problem will probably cured by rebooting. If the problem reoccurs, you might need to increase swap space by configuring additional swap devices. Otherwise, if it is API call failure, check the syslog messages from other components. For resource name and the property name, check the current syslog message.
174928 ERROR: process_resource: resource <%s> is offline pending boot, but no BOOT method is registered
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
175267 Error: The resource "%s" must be qualified as a local node dependency.
Description:The CRS resource dependency on a SUNW.ScalDeviceGroup or SUNW.ScalMountPoint resource was not specified as a {local_node} dependency.
Solution:When specifying a CRS resource dependency on a SUNW.ScalDeviceGroup or SUNW.ScalMountPoint resource you must qualify the dependency as a {local_node} dependency.
175461 Failed to open resource %s: %s.
Description:The PMF action script supplied by the DSDL could not retrieve information about the given resource.
Solution:Check the syslog messages around the time of the error for messages indicating the cause of the failure. If this error persists, contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
175553 clconf: Your configuration file is incorrect! The type of property %s is not found
Description:Could not find the type of property in the configuration file.
Solution:Check the configuration file.
175698 %s: cannot open %s
Description:The ucmmd was unable to open the file identified. Contact your authorized Sun service provider for assistance in diagnosing the problem.
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.
175709 Validate - nmblookup %s nonexistent executable
Description:The Samba resource tries to validate that the nmblookup program exists and is executable.
Solution:Check the correct pathname for the Samba bin directory was entered when registering the resource and that the program exists and is executable.
176065 Function: check_mysql_replication - Setting the resource status returned an error
Description:Couldn't set the resource status
Solution:No user action is required.
176151 Unable to lookup nfs:nfs_server from kstat:%s
Description:HA-NFS fault monitor failed to lookup the specified kstat parameter. The specific cause is logged with the message.
Solution:Run the following command on the cluster node where this problem is encountered. /usr/bin/kstat -m nfs -i 0 -n nfs_server -s calls Barring resource availability issues, this call should complete successfully. If it fails without generating any output, please contact your authorized Sun service provider.
176587 Start command %s returned error, %d.
Description:The command for starting the data service returned an error.
Solution:No user action needed.
176699 Service failed and the fault monitor is not running on this node. Not restarting service %s
Description:The action script for the process is trying to contact the probe, and is unable to do so. Due to the indicated resource group setting, the action script is not restarting the application.
Solution:This is an informational message, no user action is needed.
176762 %s: Could not initialize the ORB. Exiting.
Description:The pmmd program was unable to initialize ORB.
Solution:Make sure the nodes are booted in cluster mode. If so, contact your authorized Sun service provider to determine whether a workaround or patch is available.
176974 Validation failed. SYBASE environment variable is not set in Environment_file.
Description:SYBASE environment variable is not set in environment_file or is empty string.
Solution:Check the file specified in Environment_file property. Check the value of SYBASE environment variable, specified in the Environment_file. SYBASE environment variable should be set to the directory of Sybase ASE installation.
177070 Got back %d in revents of the control fd. Exiting.
Description:clexecd program has encountered an error.
Solution:The clexecd program will exit and the 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.
177121 Attempting to notify client of invalid state for zone %s
Description:The sc_zonesd has encountered an internal logic error, but it will attempt to continue.
Solution:Save a copy of the /var/adm/messages files on all nodes. If the problem persists, contact your authorized Sun service provider for assistance in diagnosing the problem.
177867 Failed to get cluster id, ret val = %d
Description:Failed to get the cluster id for a zone.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
177878 Can't access kernel timeout facility
Description:Failed to maintain timeout state for client affinity on the node.
Solution:If client affinity is a requirement for some of the sticky services, say due to data integrity reasons, the node should be restarted.
177899 t_bind (open_cmd_port) failed
Description:Call to t_bind() failed. The "t_bind" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
178616 SCSLM <%s> running is zero
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
178996 Zone cluster PNM interface invoked instead of PNM interface for exclusive-ip zones
Description:The PNM proxy subsystem interface for a zone cluster is being used for a exclusive-ip zone.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
179118 Diskgroup (%s) is NOT available
Description:The disk group is not usable.
Solution:Fix the problem that is causing the disk group to be unusable.
179364 CCR: Invalid CCR metadata.
Description:The CCR could not find valid metadata on all nodes of the cluster.
Solution:Boot the cluster in -x mode to restore the cluster repository on all the nodes in the cluster from backup. The cluster repository is located at /etc/cluster/ccr/.
179602 Warning: Failed to configure Round robin load balancing property for 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.
179728 sigprocmask(2) failed for child (pid %d) forked by pmmd: error %s
Description:The child that was forked by the pmmd daemon was unable to set its signal mask because the sigprocmask(2) function failed. The message contains the system error. The child that was forked by the pmmd daemon will not set up its signal handling settings as specified.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
179742 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 specifies the resource that is stated in the message.
180002 Failed to stop the monitor server using %s.
Description:Sun Cluster HA for Sybase failed to stop the backup server using the file specified in the STOP_FILE property. Other syslog messages and the log file will provide additional information on possible reasons for the failure. It is likely that adaptive server terminated prior to shutdown of monitor server.
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.
181193 Cannot access file <%s>, err = <%s>
Description:The rgmd has failed in an attempt to stat(2) a file used for the anti-"pingpong" feature. This may prevent the anti-pingpong feature from working, which may permit a resource group to fail over repeatedly between two or more nodes. The failure to access the file might indicate a more serious problem on the 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.
181375 Telemetry data service start method has failed. The system will restart cacao and then attempt to retry.
Description:The telemetry data service has failed to start (in this case cacao may have been started before JavaDB packages were installed).
Solution:This message is informational; no user action needed.
182069 check_smbd - Samba server <%s> not working, failed to connect to samba-resource <%s>
Description:The Samba resource's fault monitor checks that the Samba server is working by using the smbclient program. However this test failed to connect to the Samba server.
Solution:No user action is needed. The Samba server will be restarted. However, examine the other syslog messages occurring at the same time on the same node, to see if the cause of the problem can be identified.
182413 clcomm: Rejecting communication attempt from a stale incarnation of node %s; reported boot time %s, expected boot time %s or later.
Description:It is likely that system time was changed backwards on the remote node followed by a reboot after it had established contact with the local node. When two nodes establish contact in the Sun Cluster environment, they make a note of each other's boot time. In the future, only connection attempts from this same or a newer incarnation of the remote node will be accepted. If time has been adjusted on the remote note such that the current boot time there appears less than the boot time when the first contact was made between the two nodes, the local node will refuse to talk to the remote node until this discrepancy is corrected. Note that the time printed in this message is GMT time and not the local time.
Solution:If system time change on the remote node was erroneous, reset the system time there to the original value and reboot that node. Otherwise, reboot the local node. This will make the local node forget about any earlier contacts with the remote node and will allow communication between the two nodes to proceed. This step should be performed with caution keeping quorum considerations in mind. In general it is recommended that system time on a cluster node be changed only if it is feasible to reboot the entire cluster.
183071 Cannot Execute %s: %s.
Description:Failure in executing the command.
Solution:Check the syslog message for the command description. Check whether the system is low in memory or the process table is full and take appropriate action. Make sure that the executable exists.
183580 Stop command for %s failed with error %s.
Description:The data service detected an error running the stop command.
Solution:Ensure that the stop command is in the expected path (/usr/sap/<SID>/SYS/exe/run) and is executable.
183934 Waiting for %s to come up.
Description:The specific service or process is not yet up.
Solution:This is an informative message. Suitable action may be taken if the specified service or process does not come up within a configured time limit.
184448 scnetapp fatal error - Cannot lookup %s
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
185191 MAC addresses are not unique per subnet.
Description:What this means is that there are at least two adapters on a subnet which have the same MAC address. IPMP makes the assumption that all adapters have unique MAC addresses.
Solution:Look at the ifconfig man page on how to set MAC addresses manually. This is however, a temporary fix and the real fix is to upgrade the hardware so that the adapters have unique MAC addresses.
185347 Failed to deliver event %lld to remote node %d:%s
Description:The cl_eventd was unable to deliver the specified event to the specified node.
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.
185465 No action on DBMS Error %s : %ld
Description:Database server returned error. Fault monitor does not take any action on this error.
Solution:No user action is required.
185537 Unable to bind to nameserver
Description:The cl_eventd was unable to register itself with the cluster nameserver. It will exit.
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.
185720 lkdb_parm: lib initialization failed
Description:initializing a library to get the static lock manager parameters failed.
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.
186306 Conversion of hostnames failed for %s.
Description:The hostname or IP address given could not be converted to an integer.
Solution:Add the hostname to the /etc/inet/hosts file. Verify the settings in the /etc/nsswitch.conf file include "files" for host lookup.
186484 PENDING_METHODS: bad resource state <%s> (%d) for resource <%s>
Description:The rgmd state machine has discovered a resource in an unexpected state on the local node. 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.
186524 reservation error(%s) - do_scsi2_release() error for disk %s
Description:The device fencing program has encountered errors while trying to access a device. All retry attempts have failed.
Solution:The action which failed is a SCSI-2 ioctl. These can fail if there are SCSI-3 keys on the disk. To remove invalid SCSI-3 keys from a device, use 'scdidadm -R' to repair the disk (see scdidadm man page for details). If there were no SCSI-3 keys present on the device, then this error is 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, 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, you can retry the desired action.
186612 _cladm CL_GET_CLUSTER_NAME failed; perhaps system is not booted as part of cluster
Description:Could not get cluster name. Perhaps the system is not booted as part of the cluster.
Solution:Make sure the node is booted as part of a cluster.
186847 Failed to stop the application cleanly. Will try to stop using SIGKILL
Description:An attempt to stop the application did not succeed. A KILL signal will now be delivered to the application in order to stop it forcibly.
Solution:No user action is required. This is an informational message only.
187044 Waiting for the EGC failfast module to be unloaded.
Description:The svc:/system/egc/failfast:default SMF service is trying to unload the EGC farm failfast module
Solution:No user action is required. This is an informational message only.
187208 stop_DB_SAA - Command %s and/or %s do not exist or are not executable
Description:The referenced commands are either not executable or do not exist, but are required for SWIFTAlliance Access to properly function.
Solution:Verify the SWIFTAlliance Access installation and make sure the referenced commands do exist and are executable.
187307 invalid debug_level: '%s'
Description:Invalid debug_level argument passed to udlmctl. udlmctl will not startup.
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.
187835 Could not allocate memory, size = %d for %d elements
Description:Could not allocate memory. Node is too low on memory.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
187879 Failed to open /dev/null for writing; fopen failed with error: %s
Description:The cl_apid was unable to open /dev/null because of the specified error.
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.
187883 Apache service with startup script <%s> does not configure %s.
Description:The specified Apache startup script does not configure the specified variable.
Solution:Edit the startup script and set the specified variable to the correct value.
187910 repl_check fatal error - Illegal command line option
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.
188013 %s will be administrated with project 'default'.
Description:The application which is listed in the message will be started, stopped using project 'default'.
Solution:Informational message. No user action is needed.
189174 ERROR: Option %s passed to a script of the derby data service is unknown
Description:An unknown option was given to a program or script of the derby data service. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
190538 Devicegroup %s does not have any volumes.
Description:The devicegroup does not have any volumes.
Solution:Create volumes in the devicegroup.
191225 clcomm: Created %d threads, wanted %d for pool %d
Description:The system creates server threads to support requests from other nodes in the cluster. The system could not create the desired minimum number of server threads. However, the system did succeed in creating at least 1 server thread. The system will have further opportunities to create more server threads. The system cannot create server threads when there is inadequate memory. This message indicates either inadequate memory or an incorrect configuration.
Solution:There are multiple possible root causes. If the system administrator specified the value of "maxusers", try reducing the value of "maxusers". This reduces memory usage and results in the creation of fewer server threads. If the system administrator specified the value of "cl_comm:min_threads_default_pool" in "/etc/system", try reducing this value. This directly reduces the number of server threads. Alternatively, do not specify this value. The system can automatically select an appropriate number of server threads. Another alternative is to install more memory. If the system administrator did not modify either "maxusers" or "min_threads_default_pool", then the system should have selected an appropriate number of server threads. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
191492 CCR: CCR unable to read root filesystem.
Description:The CCR failed to read repository due to root file system failure on this node.
Solution:The root file system needs to be replaced on the offending node.
191598 Unknown status code %s
Description:An unexpected error occurred while the checking the status of an HAStoragePlus resource.
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.
191772 Failed to configure the networking components for scalable resource %s for method %s.
Description:The processing that is required for scalable services did not complete successfully.
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.
191957 The property %s does not have a legal value.
Description:The property named does not have a legal value.
Solution:Assign the property a legal value.
192183 freeze_adjust_timeouts: call to rpc.fed failed, tag <%s> err <%d> result <%d>
Description:The rgmd failed in its attempt to suspend timeouts on an executing method during temporary unavailability of a global device group. This could cause the resource method to time-out. 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:No user action is required if the resource method execution succeeds. If the problem recurs, rebooting this node might cure it. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing the problem.
192223 ERROR: Option -%s unknown
Description:The option provided is invalid.
Solution:Possible options are: c, u, r <arg>, x <arg>, g <arg>, R <arg>, T <arg>, and G <arg>.
192518 Cannot access start script %s: %s
Description:The start script is not accessible and executable. This may be due to the script not existing or the permissions not being set properly.
Solution:Make sure the script exists, is in the proper directory, and has read and execute permissions set appropriately.
192619 reservation error(%s) - Unable to open device %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.
192656 IPMP group %s has adapters that do not belong to the same VLAN.
Description:Sun Cluster has detected that the named IPMP group has adapters that belong to different VLANs. Since all adapters that participate in an IPMP group must host IP addresses from the same IP subnet, and an IP subnet cannot span multiple VLANs, this is not a legal configuration.
Solution:Fix the IPMP configuration by updating the appropriate /etc/hostname* file(s) so that each IPMP group spans only the adapters that host IP addresses from the same IP subnet.
193137 Service group '%s' deleted
Description:The service group by that name is no longer known by the scalable services framework.
Solution:This is an informational message, no user action is needed.
193263 Service is online.
Description:While attempting to check the health of the data service, probe detected that the resource status is fine and it is online.
Solution:This is informational message. No user action is needed.
193266 Dependency between resource %s and its MDS resource %s has not been defined !
Description:The specified ScalMountPoint resource failed to start because the resource lacks an explicit dependency on the metadata server resource that represents the mount point.
Solution:Define the required dependency between the ScalMountPoint resource and the metadata server resource.
193655 %s: fatal: reboot
Description:The rgm daemon encountered a non-recoverable error, possibly because the system ran out of swap space. The rgm daemon will force the node to halt or reboot to avoid the possibility of data corruption. A core file might be produced in some cases, but will not usually be produced in the case of low swap space.
Solution:A low swap condition might have been temporarily remedied by rebooting. If the problem recurs, you might need to increase swap space by configuring additional swap devices. See swap(1M) for more information. If it appears that exhaustion of swap space was not the cause of the problem, contact your authorized Sun service provider to determine whether a workaround or patch is available.
193783 Failed to initialize DSDL
Description:An error prevented the initialization of the DSDL library.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
193933 CMM: Votecount changed from %d to %d for node %s.
Description:The specified node's votecount has been changed as indicated.
Solution:This is an informational message, no user action is needed.
194512 Failed to stop HA-NFS system fault monitor.
Description:Process monitor facility has failed to stop the HA-NFS system fault monitor.
Solution:Use pmfadm(1M) with -s option to stop the HA-NFS system fault monitor with tag name "cluster.nfs.daemons". If the error still persists, then reboot the node.
194601 Maxdelay = %lld Mindelay = %lld Avgdelay = %lld NumEv = %d\nMaxQlen = %d CurrQlen = %d
Description:The cl_eventd is receiving and delivering messages with the specified delays, as calculated empirically during the lifetime of the daemon.
Solution:This message is informational only, and does not require user action.
194934 ping_interval %d
Description:The ping_interval value used by scdpmd.
Solution:No user action is required.
195278 Mountpoint %s does not exist.
Description:The directory for mounting the target file system does not exist.
Solution:Create the mount-point directory and mount the target file system again.
195414 in libsecurity weak UNIX authorization failed
Description:A cluster daemon refused an RPC connection from a client because it failed weak UNIX authentication.
Solution:This form of authentication is currently not used by Sun Cluster software, so this message should not occur. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
195538 Null value is passed for the handle.
Description:A null handle was passed for the function parameter. No further processing can be done without a proper handle.
Solution:It's a programming error, core is generated. Specify a non-null handle in the function call.
195547 "pmfadm -a" Action failed for <%s>
Description:The given tag has exceeded the allowed number of retry attempts (given by the 'pmfadm -n' option) and the action (given by the 'pmfadm -a' option) was initiated by rpc.pmfd. The action failed (i.e., returned non-zero), and rpc.pmfd will delete this tag from its tag list and discontinue retry attempts.
Solution:This message is informational; no user action is needed.
195565 Configuration file <%s> does not configure %s.
Description:The configuration file does not have a valid entry for the indicated configuration item.
Solution:Check that the file has a correct entry for the configuration item.
196233 INTERNAL ERROR: launch_method: method tag <%s> not found in method invocation list for resource group <%s>
Description:An internal error has occurred. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
196243 Validate - %s sbin directory %s does not exist
Description:The Samba resource could not validate that Samba sbin directory exists.
Solution:Check that the correct pathname for the Samba sbin directory was entered when registering the Samba resource and that the sbin directory really exists.
196412 sigemptyset(3C) failed for pmmd_adm while initializing ignored signal set: error %s
Description:The pmmd_adm was unable to initialize a signal set because the sigemptyset(3C) function failed. The message contains the system error. The pmmd_adm cannot do its requested action.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
196568 Running hadbm stop.
Description:The HADB database is being stopped by the hadbm command.
Solution:This is an informational message, no user action is needed.
196838 Validate - %s does not exist or is not a directory
Description:${INFORMIXDIR} does not exist or is not a directory.
Solution:Ensure that ${INFORMIXDIR} is the directory path where the Informix files are installed.
196901 Function: add_application_rgs - The resources %s do not exist any more in %s
Description:The combination, real MySQL resources, real MySQL resource groups is not valid any more
Solution:Recreate the real MySQL resources in the real MySQL resource group
196965 Failed to start fault-monitor : %s
Description:The fault monitor of this ScalMountPoint resource could not be started.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
197307 Resource contains invalid hostnames.
Description:The hostnames that has to be made available by this logical host resource are invalid.
Solution:It is advised to keep the hostnames in /etc/inet/hosts file and enable "files" for host lookup in nsswitch.conf file. Any of the following situations might have occurred. 1) If hosts are not in /etc/inet/hosts file then make sure the nameserver is reachable and has host name entries specified. 2) Invalid hostnames might have been specified while creating the logical host resource. If this is the case, use the clreslogicalhostname command to re-specify the hostnames for this logical host resource.
197640 Command [%s] failed: %s.
Description:The command could not be run successfully.
Solution:The error message specifies both - the exact command that failed, and the reason why it failed. Try the command manually and see if it works. Consider increasing the timeout if the failure is due to lack of time. For other failures, contact your authorized Sun service provider.
197997 clexecd: dup2 of stdin returned with errno %d while exec'ing (%s). Exiting.
Description:clexecd program has encountered a failed dup2(2) system call. The error message indicates the error number for the failure.
Solution:The clexecd program will exit and the 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.
198216 t_bind cannot bind to requested address
Description:Call to t_bind() failed. The "t_bind" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
198284 Failed to start fault monitor.
Description:The fault monitor for this data service was not started. There may be prior messages in syslog indicating specific problems.
Solution:The user should correct the problems specified in prior syslog messages. This problem may occur when the cluster is under load and Sun Cluster cannot start the application within the timeout period specified. Consider increasing the Monitor_Start_timeout property. Try switching the resource group to another node by using clresourcegroup or scswitch (1M).
198542 No network resources found for resource.
Description:No network resources were found for the resource.
Solution:Declare network resources used by the resource explicitly using the property Network_resources_used. For the resource name and resource group name, check the syslog tag.
198760 "at boot" field in /etc/vfstab for file-system %s must be set to "no".
Description:The value of the field 'mount at boot' in /etc/vfstab for the specified file system must be set to "no".
Solution:Set the value of the 'mount at boot' field for the specified file system to "no" and repeat the operation.
198918 resetting scsi buses shared with non-cluster nodes
Description:This is informational message.
Solution:No user action is required.
199791 failfastd: sigfillset returned %d. Exiting.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
Message IDs 200000–299999
This section contains message IDs 200000–299999.
201134 Validate - tftpd daemon has to be activated in %s when -F is being used
Description:If TFTPTESTFILE= was set within /opt/SUNWscdhc/util/dhcp_config then the tftp daemon needs to be activated witihin /etc/inet/inetd.conf.
Solution:If TFTPTESTFILE= is required, then ensure that tftp is activated within /etc/inet/inetd.conf.
202101 metastat shows volume %s/%s is in state \'%s\'.
Description:Output from metastat the command shows that the disk set or disk group is not available.
Solution:Examine the output from metastat and perform maintenance if necessary.
202528 No permission for group to read %s.
Description:The group of the file does not have read permission on it.
Solution:Set the permissions on the file so the group can read it.
203142 Update_drv successfully read did.conf file
Description:Update_drv command was successful in making did driver reread did.conf file.
Solution:This is an informational message, no user action is needed.
203202 Peer node %d attempted to contact us with an invalid version message, source IP %s. Peer node may be running pre 3.1 Sun Cluster software.
Description:Sun Cluster software at the local node received an initial handshake message from the remote node that is not running a compatible version of the Sun Cluster software.
Solution:Make sure all nodes in the cluster are running compatible versions of Sun Cluster software.
203411 A role mismatch has been discovered. Fault monitor will be stopped.
Description:The Dataguard role that the Sun Cluster resource is configured with does not match the dataguard role queried by the monitor from the Oracle instance.
Solution:Update the DATAGUARD_ROLE and STANDBY_MODE extension properties of the Sun Cluster resource to reflect the correct dataguard role shown by the instance. CSTYLED.
203680 fatal: Unable to bind to nameserver
Description:The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.
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.
204026 parameter '%s%s' must be an integer "%s". Using default value of %d.
Description:Using a default value for a parameter.
Solution:No user action is required.
204163 clcomm: error in copying for state_balancer
Description:The system failed a copy operation supporting statistics reporting.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
204584 clexecd: Going down on signal %d.
Description:clexecd program got a signal indicated in the error message.
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.
205259 Error reading properties; exiting.
Description:The cl_apid was unable to read the SUNW.Event resource properties that it needs to run.
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.
205754 All specified device services validated successfully.
Description:All device services specified directly or indirectly via the GlobalDevicePath and FilesystemMountPoint extension properties respectively are found to be correct. Other Sun Cluster components like DCS, DSDL, RGM are found to be in order. Specified file system mount point entries are found to be correct.
Solution:This is an informational message, no user action is needed.
205822 clcomm:Cannot vfork() after ORB server initialization.
Description:A user level process attempted to vfork after ORB server initialization. This is not allowed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
205863 SCSLM cannot create pset <%s%s> min=%u,max=%u
Description:Requested number of CPUs cannot be set for this resource group on this node.
Solution:Switch the resource group on a node with enough CPUs or lower RG_SLM_CPU_SHARES and or RG_SLM_PSET_MIN properties values or move RG_SLM_type to manual and restart the resource group.
205873 Permissions incorrect for %s. s bit not set.
Description:Permissions of $ORACLE_HOME/bin/oracle are expected to be '-rwsr-s--x' (set-group-ID and set-user-ID set). These permissions are set at the time or Oracle installation. Fault monitor will not function correctly without these permissions.
Solution:Check file permissions. Check Oracle installation. Re-link Oracle, if necessary.
206494 ucmm is unstable.
Description:The UCMM is stopping or aborting, or is in an unstable state.
Solution:Determine why the UCMM is aborting or stopping. This is behavior valid for a node that is shutting down. If the node is not shutting down, verify the status of the SUNW.rac_framework resource and either the SUNW.rac_svm resource or the SUNW.rac_cvm resource. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
206501 CMM: Monitoring re-enabled.
Description:Transport path monitoring has been enabled back in the cluster, after being disabled.
Solution:This is an informational message, no user action is needed.
206558 Replica is not running on this node, but is running remotely on some other node. %s cannot be started on this node.
Description:The SAP enqueue server is trying to start up on a node where the SAP replica server has not been running. The SAP enqueue server must start on the node where the replica server has been running.
Solution:No user action is needed.
206947 ON_PENDING_MON_DISABLED: bad resource state <%s> (%d) for resource <%s>
Description:The rgmd state machine has discovered a resource in an unexpected state on the local node. 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.
206969 ct_tmpl_set_critical: %s
Description:The libclcontract code was unable to configure a process template in which to launch the requested service. Consequently, the process that is using libclcontract was unable to launch the process under its control.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
207075 Issuing a resource restart request.
Description:The process monitoring facility tried to send a message to the fault monitor noting that the data service application died. It was unable to do so.
Solution:Since some part (daemon) of the application has failed, it would be restarted. If fault monitor is not yet started, wait for it to be started by Sun Cluster framework. If fault monitor has been disabled, enable it by using clresource.
207393 The %s command is missing.
Description:The command used to determine the zone name is missing.
Solution:Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Refer to the documentation of Sun Cluster support for Real Application Clusters. If the problem persists, contact your Sun service representative.
207465 No %s/quotas file exists - not starting quotas for %s
Description:The UFS mount point has quotas enabled but there is no "quotas" file under the mounted file system.
Solution:Create a "quotas" file under the mounted file system if quotas are desired. Check the man page of quotacheck(1M). If the quotas file is created you must restart the corresponding SUNW.HAStoragePlus resource.
207481 getlocalhostname() failed for resource <%s>, resource group <%s>, method <%s>
Description:The rgmd daemon was unable to obtain the name of the local host, causing a method invocation to fail. Depending on which method is 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: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 the problem.
207615 Property Confdir_list is not set.
Description:The Confdir_list property is not set. The resource creation is not possible without this property.
Solution:Set the Confdir_list extension property to the complete path to the JSAS home directory. Refer to the Configuration guide for more details.
207666 The path name %s associated with the FilesystemCheckCommand extension property is detected to be a relative path name. Only absolute path names are allowed.
Description:Self explanatory.
Solution:Specify an absolute path name to your command in the FilesystemCheckCommand extension property.
207749 Could not resolve 'rtreg_proxy_server' in the name server. Exiting.
Description:The rtreg server program could not resolve the rtreg proxy server object from the local name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
208216 ERROR: resource group <%s> has RG_dependency on nonexistent resource group <%s>
Description:A nonexistent resource group is listed in the RG_dependencies of the indicated resource group. 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.
208441 Stopping %s with command %s failed.
Description:An attempt to stop the application by the command that is listed failed. Informational message.
Solution:Other syslog messages that occur shortly before this message might indicate the reason for the failure. Check the application installation and make sure the command listed in the message can be executed successfully outside Sun Cluster. A more severe command will be used to stop the application after this. No user action is needed.
208547 Creation of resource <%s> failed because the inter-cluster strong dependencies could not be set
Description:Resource creation failed due to specification of invalid inter cluster dependencies.
Solution:Check the remote cluster name or remote resource name and retry the same command.
208596 clcomm: Path %s being initiated
Description:A communication link is being established with another node.
Solution:No user action is required.
208838 check_dhcp - The retrieved file (%s) don't exist or is zero-bytes long.
Description:The (tftp) retrieved file either does not exist or has a file size of zero bytes
Solution:No user action is required. Informational message, an immediate failover is being requested.
209090 scha_control RESOURCE_RESTART failed. error %s
Description:Fault monitor had detected problems in RDBMS server. Attempt to restart RDBMS server on the same node failed. Error returned by API call scha_control is indicated in the message.
Solution:No user action is required.
209314 No permission for group to write %s.
Description:The group of the file does not have write permission on it.
Solution:Set the permissions on the file so the group can write it.
209540 scvxvmlg warning - %s does not exist, creating it
Description:The program responsible for maintaining the VxVM device namespace has discovered inconsistencies between the VxVM device namespace on this node and the VxVM configuration information stored in the cluster device configuration system. If configuration changes were made recently, then this message should reflect one of the configuration changes. If no changes were made recently or if this message does not correctly reflect a change that has been made, the VxVM device namespace on this node may be in an inconsistent state. VxVM volumes may be inaccessible from this node.
Solution:If this message correctly reflects a configuration change to VxVM diskgroups then no action is required. If the change this message reflects is not correct, then the information stored in the device configuration system for each VxVM diskgroup should be examined for correctness. If the information in the device configuration system is accurate, then executing '/usr/cluster/lib/dcs/scvxvmlg' on this node should restore the device namespace. If the information stored in the device configuration system is not accurate, it must be updated by executing '/usr/cluster/bin/scconf -c -D name=diskgroup_name' for each VxVM diskgroup with inconsistent information.
210468 %s: returned error (%d)
Description:The command returned an error.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
210729 start_sge_qmaster failed
Description:The process sge_qmaster failed to start for reasons other than it was already running.
Solution:Check /var/adm/messages for any relevant cluster messages. Respond accordingly, then retry.
210975 Stop monitoring saposcol under PMF times out.
Description:Stopping monitoring the SAP OS collector process under the control of Process Monitor facility times out. This might happen under heavy system load.
Solution:You might consider increase the monitor stop time out value.
211018 Failed to remove events from client
Description:The cl_apid experienced an internal error that prevented proper updates to a CRNP client.
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.
211198 Completed successfully.
Description:Data service method completed successfully.
Solution:No user action is required.
211210 pxvfs:mount(): global mount is not supported for filesystem type : '%s'
Description:A global mount is not supported for the specified file system.
Solution:Check the release notes and documents about the support of the specified system.
211501 Check_replication - the check for replication failed for replication resource %s
Description:The check for the replication status failed
Solution:Fix the replication issues
211565 Validate - WebSphere MQ Broker file systems not defined
Description:The WebSphere MQ Broker file systems (/opt/mqsi and /var/mqsi) are not defined.
Solution:Ensure that the WebSphere MQ Broker file systems are defined correctly.
211588 Must have a valid %s file with dns specified.
Description:The /etc/nsswitch.conf(4) file does not have a valid "dns" source specified.
Solution:/etc/nsswitch.conf(4) must have a "dns" source under the "hosts" or "ipnodes" database entries.
211765 SCSLM <%s> zone <%s> strong while weak running
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
211869 validate: Basepath is not set but it is required
Description:The parameter Basepath is not set in the parameter file
Solution:set the variable Basepath in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.
211873 pmf_search_children: pmf_remove_triggers: %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 syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
211943 dl_info: DLPI error %u
Description:DLPI protocol error. We cannot get a info_ack from 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.
212503 reservation fatal error(%s) - get_global_fencing_status error, errno %d
Description:Failed to retrieve the global fencing status from both the global name server and the CCR.
Solution:Check whether the root file system is having access problems.
212884 Hostname %s has no usable address.
Description:The hostname does not have any IP addresses that can be hosted on the resource's IPMP group. This could happen if the hostname maps to an IPv6 address only and the IPMP group is capable of hosting IPv4 addresses only (or the other way round).
Solution:Use ifconfig -a to determine if the network adapter in the resource's IPMP group can host IPv4, IPv6 or both kinds of addresses. Make sure that the hostname specified has at least one IP address that can be hosted by the underlying IPMP group.
213583 Failed to stop Backup server.
Description:Sun Cluster HA for Sybase failed to stop backup server using KILL signal.
Solution:Please examine whether any Sybase server processes are running on the server. Please manually shutdown the server.
213599 Failed to stop backup server.
Description:Sun Cluster HA for Sybase failed to stop backup server using KILL signal.
Solution:Please examine whether any Sybase server processes are running on the server. Please manually shutdown the server.
213894 exit_event: ct_pr_event_get_pid: %s
Description:The rpc.pmfd was unable to retrieve the pid from a contract event. The rpc.pmfd will continue to monitor the process, but the rpc.pmfd may have missed an event of interest.
Solution: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.
213973 Resource depends on a SUNW.HAStoragePlus type resource that is not online anywhere.
Description:The resource depends on a SUNW.HAStoragePlus resource that is not online on any cluster node.
Solution:Bring all SUNW.HAStoragePlus resources, that this HA-NFS resource depends on, online before performing the operation that caused this error.
213991 No Network resource in resource group.
Description:This message indicates that there is no network resource configured for a "network-aware" service. A network aware service can not function without a network address.
Solution:Configure a network resource and retry the command.
214578 No resource dependencies properties of this resource contain a SharedAddress network resource.
Description:The resource dependencies property (any of strong/weak/ restart/offline-restart) must contain at least one SharedAddress network resource.
Solution:Specify a SharedAddress network resource in at least one of the resource dependencies properties of this resource.
214697 Failed to obatain the status of MDS for '%s' file system of resource '%s'. Skipping this file system ...
Description:The zone boot handler is unable to determine the status of metadata server for the specified shared qfs file system.
Solution:Investigate the zone boot log messages and try to rectify the problem. If problem persists after rebooting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
214780 Error getting handle tolibvxvm functions
Description:An error occurred when library routines in libvxvmsc.so were 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.
215191 Internal error; SAP User set to NULL.
Description:Extension property could not be retrieved and is set to NULL. Internal error.
Solution:No user action needed.
215257 About to mount on %s for zone cluster '%s'. Underlying files and directories will be inaccessible.
Description:HAStoragePlus detected that the directory of zone cluster on which mount is about to happen is not empty, hence once mounted, the underlying files will be inaccessible.
Solution:This is an informational message, no user action is needed.
215570 PNM proxy invoked for global zone public network information
Description:PNM proxy is being used to get global zone information.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
216087 rebalance: resource group <%s> is being switched updated or failed back, cannot assign new primaries
Description:The indicated resource group has lost a master due to a node death. However, the RGM is unable to switch the resource group to a new master because the resource group is currently in the process of being modified by an operator action, or is currently in the process of "failing back" onto a node that recently joined the cluster.
Solution:Use cluster status -t <resourcegroup> to determine the current mastery of the resource group. If necessary, use clresourcegroup switch to switch the resource group online on desired nodes.
216244 CCR: Table %s has invalid checksum field. Reported: %s, actual: %s.
Description:The indicated table has an invalid checksum that does not match the table contents. This causes the consistency check on the indicated table to fail.
Solution:Boot the offending node in -x mode to restore the indicated table from backup or other nodes in the cluster. The CCR tables are located at /etc/cluster/ccr/.
216379 Stopping fault monitor using pmfadm tag %s
Description:Informational message. Fault monitor will be stopped using Process Monitoring Facility (PMF), with the tag indicated in message.
Solution:No user action is required.
216623 in libsecurity for program %s ; fattach of file %dto door failed : %s
Description:A Sun Cluster daemon was unable to attach to a door descriptor for communication with its clients. A following syslog message provides the name of the daemon that failed. This might cause the node to be rebooted or halted.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
216774 WARNING: update_state:udlm_send_reply failed
Description:A warning for udlm state update and results in udlm abort.
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.
217093 Call failed: %s
Description:A client was not able to make an rpc connection to a server (rpc.pmfd, rpc.fed or rgmd) to execute the action shown. The rpc error message is shown.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
217440 The %s protocol for this node%s is not compatible with the %s protocol for the rest of the cluster%s.
Description:The cluster version manager exchanges version information between nodes running in the cluster and has detected an incompatibility. This is usually the result of performing a rolling upgrade where one or more nodes has been installed with a software version that the other cluster nodes do not support. This error may also be due to attempting to boot a cluster node in 64-bit address mode when other nodes are booted in 32-bit address mode, or vice versa.
Solution:Verify that any recent software installations completed without errors and that the installed packages or patches are compatible with the rest of the installed software. Save the /var/adm/messages file. Check the messages file for earlier messages related to the version manager which may indicate which software component is failing to find a compatible version.
217768 Verification for '%s' file system MDS node status exceeded timeout '%d' seconds.
Description:The zone boot handler found that the verification for the MDS of the specified file system has exceeded timeout.
Solution:Check for the system logs and zone boot logs to investigate on possible problem. After rectifying the problem reboot the zone cluster node. If the problem still persists contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
217797 Membership : validation of state %s failed for '%s' membership; reason '%s'.
Description:Validation of a state failed for the state machine of the specified membership. The state machine will transition to an invalid state.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
218049 Waiting for the sc_zonesd to stop
Description:The SCZONE service is being stopped.
Solution:Please wait. No user action is required. This is an informational message.
218575 low memory: unable to capture output
Description:The rpc.fed server was not able to allocate memory necessary to capture the output from methods it runs.
Solution:Determine if the host is running out of memory. If not save the /var/adm/messages file. whether a workaround or patch is available.
218655 Waiting for WebSphere MQ Queue Manager
Description:A WebSphere MQ component is waiting for the Queue Manager.
Solution:No user action is required. Informational message.
218780 Stopping the monitor server.
Description:The Monitor server is about to be brought down by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed.
218919 J2EE probe returned %s
Description:Informational message.
Solution:No user action is needed.
219058 Failed to stop the backup server using %s.
Description:Sun Cluster HA for Sybase failed to stop the backup server using the file specified in the STOP_FILE property. Other syslog messages and the log file will provide additional information on possible reasons for the failure.
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.
219205 libsecurity: create of rpc handle to program %s (%lu) failed, will keep trying
Description:A client of the specified server was not able to initiate an rpc connection. The maximum time allowed for connecting (1 hr) has not been reached yet, and the pmfadm or scha command will retry to connect. An accompanying error message shows the rpc error data. The program number is shown. To find out what program corresponds to this number, use the rpcinfo command. 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.
219277 Could not kill the monitor.
Description:The monitor for HA-KDC could not be killed with a SIGKILL.
Solution:This is an internal error. No user action needed. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
219729 Error incontract event acknowledging
Description:Not able to clear the active contract template.
Solution:Check the contract man page to know more about the error. Also make sure the basic contract functionalities are working. Contact SUN vendor for more help. Previous messages will give the reason
219787 Failed to bring resource groups containing SUNW.qfs resources online : %s.
Description:The zone boot handler failed to bring the SUNW.qfs resource groups online.
Solution:Investigate the zone boot log messages and rectify the problem. If problem persists after rebooting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
220104 Function: validate - Milestone (%s) is invalid with Zonebootopt=%s, needs single-user
Description:The Zoneboot variable is set to -s. Every milestone other than single-user is invalid.
Solution:Correct the milestone in the parameter file sczbt_<resource name>. You need to specify single user together with the boot option -s.
220173 Function: validate: Directory %s does not contain the PostgreSQL configuration files
Description:A directory is specified in the PGDATA variable which does not contain a postgresql.conf file.
Solution:Specify a directory in the PGDATA variable in the parameter file, which contains the postgresql.conf file.
220645 Failed to retrieve property : %s : %s
Description:An error occurred while a property of the resource was being retrieved.
Solution:Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
220753 %s: Arg error, invalid tag <%s> restarting service.
Description:The PMF tag supplied as argument to the PMF action script is not a tag generated by the DSDL; the PMF action script has restarted the application.
Solution:This is an internal error. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
220849 CCR: Create table %s failed.
Description:The CCR failed to create the indicated table.
Solution:The failure can happen due to many reasons, for some of which no user action is required because the CCR client in that case will handle the failure. The cases for which user action is required depends on other messages from CCR on the node, and include: If it failed because the cluster lost quorum, reboot the cluster. 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 cluster repository is corrupted as indicated by other CCR messages, then boot the offending node(s) in -x mode to restore the cluster repository backup. The cluster repository is located at /etc/cluster/ccr/.
221179 sharectl error: %s
Description:Command "sharectl get nfs" returned error.
Solution:Examine 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.
221292 Failed to stop sckrb5 using the custom stop command; trying SIGKILL now.
Description:HA-KDC's stop method was not able to gracefully terminate krb5kdc or kadmind within SMOOTH_TIMEOUT.
Solution:This is for informational purposes, no action is required. The stop method will subsequently try to forcefully kill these processes through SIGKILL.
221527 Created thread %d for node %d.
Description:The cl_eventd successfully created a necessary thread.
Solution:This message is informational only, and does not require user action.
221746 Failed to retrieve property %s: %s.
Description:HAStoragePlus was not able to retrieve the resource property from the CCR.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
222512 fatal: could not create death_ff
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.
222869 Database is already running.
Description:The database is running and does not need to be started.
Solution:This is an informational message, no user action is needed.
222921 Failed to stop sckrb5; exiting UNSUCCESSFUL.
Description:Was not able to stop the HA-KDC service through a SIGKILL.
Solution:This is an internal error. No user action needed. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
223032 %s: ct_ctl_abandon: %s
Description:The pmmd 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.
223181 Instance number <%s> contains non-numeric character.
Description:The instance number specified is not a valid SAP instance number.
Solution:Specify a valid instance number, consisting of 2 numeric character.
223458 INTERNAL ERROR CMM: quorum_algorithm_init called already.
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.
223641 Validation failed. User %s does not belong to the project %s.
Description:Resource_project_name or RG_project_name property has been set to a project whose members do not include the specified user.
Solution:Please set the Resource_project_name or the RG_project_name property to a valid project for the specified user. The project membership of a user is displayed by the command 'projects <user>'.
224682 Failed to initialize the probe history.
Description:A process has failed to allocate memory for the probe history structure, most likely because the system has run out of swap space.
Solution:To solve this problem, increase swap space by configuring additional swap devices. See swap(1M) for more information.
224718 Failed to create scalable service in group %s for IP %s Port %d%c%s: %s.
Description:A call to the underlying scalable networking code failed. This call may fail because the IP, Port, and Protocol combination listed in the message conflicts with the configuration of an existing scalable resource. A conflict can occur if the same combination exists in a scalable resource that is already configured on the cluster. A combination may also conflict if there is a resource that uses Load_balancing_policy LB_STICKY_WILD with the same IP address as a different resource that also uses LB_STICKY_WILD.
Solution:Try using a different IP, Port, and Protocol combination. Otherwise, save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
224783 clcomm: Path %s has been deleted
Description:A communication link is being removed with another node. The interconnect might have failed or the remote node might be down.
Solution:Any interconnect failure should be resolved, and/or the failed node rebooted.
224900 launching method <%s> for resource <%s>, resource group <%s>, node <%s>, timeout <%d> seconds
Description:RGM has invoked a callback method for the named resource, as a result of a cluster reconfiguration, scha_control GIVEOVER, or clresourcegroup switch.
Solution:This is an informational message; no user action is needed.
225453 Failed to stop all the services on second partition
Description:The upgrade process tries to stop all the services on the second partition before it brings down the cluster. Not all services on the partition could be stopped. Upgrade process has stopped and cannot proceed.
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.
225882 Internal: Unknown command type (%d)
Description:An internal error has occurred in the rgmd while trying to connect to the rpc.fed server.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
225883 Failed to stop derby data service with SIGTERM; retry with SIGKILL
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.
226047 The asadmin list-node-agents failed to run. Unable to communicate with the Domain Admin Server %s on port %d. Probe will just check for Node Agent <%s> PID.
Description:This error message is from the start method. After starting the Node Agents, the start method probes for the Node Agent using the asadmin list-node-agents command and makes sure it is UP before declaring the resource online. The asadmin command failed because the Domain Admin Server is unreachable. The Start method will just verify that the Node Agents PID is available.
Solution:If the Domain Admin Server is also a Sun Cluster resource then set the resource dependency between the Node Agents resource and the Domain Admin Server resource. If the Domain Admin Server is not a Sun Cluster resource then make sure it is Running.
226280 PNM daemon exiting.
Description:The PNM daemon (cl_pnmd) is shutting down.
Solution:This message is informational; no user action is needed.
226458 SCSLM <%s> pool_get_pool error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
226557 pipe returned %d. Exiting.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
226907 Failed to run the DB probe script %s
Description:This is an internal error.
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.
227107 Brining the resource groups containing SUNW.qfs resources online.
Description:This is a notification from the handler that it is bringing the SUNW.qfs resource groups online.
Solution:This is an informational message; no user action is needed.
227426 Failed to open the resource %s handle: %s.
Description:HAStoragePlus failed to access the resource information.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
227445 Unable to create directory %s: %s.
Description:A call to scds_initialize() failed because it was unable to create a directory required for fault monitoring. The reason for the failure is included in the message. This might cause an RGM-managed service to fail.
Solution:Examine other syslog messages occurring around the same time. Take corrective action based upon the contents of the error messages.
227733 Failed to complete command %s. Will continue to start up %s.
Description:The listed command failed to complete. HA-SAPDB will continue to start up SAPDB.
Solution:Informational message. No user action is needed.
227820 Attempting to stop the data service running under process monitor facility.
Description:The function is going to request the PMF to stop the data service. If the request fails, refer to the syslog messages that appear after this message.
Solution:This is an informational message, no user action is required.
227975 %s: sigfillset returned %d. Exiting.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
228038 Error in scha_res_open of res:%s, rg:%s, Err: %s,
Description:Cannot create a handle for the scha resource
Solution:Check out the man pages for help depending on the error type
228212 reservation fatal error(%s) - unable to get local node id
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.
228399 Unable to stop processes running under PMF tag %s.
Description:Sun Cluster HA for Sybase failed to stop processes using Process Monitoring Facility. Please examine if the PMF tag indicated in the message exists on the node. (command: pmfadm -l <tag>). Other syslog messages and the log file will provide additional information on possible reasons for the failure.
Solution:Please examine Sybase logs and syslog messages. If this message is seen under heavy system load, it will be necessary to increase Stop_timeout property of the resource.
228994 Validation failed. CRS_HOME/bin/crs_stop not found CRS_HOME=%s
Description:The SUNW.scalable_rac_server_proxy agent could not find the crs_stop binary in the indicated $CRS_HOME/bin/ directory.
Solution:Check whether the $CRS_HOME/bin/ directory is accessible, and if so, whether the crs_start binary exists. If the problem persists, contact your Sun support representative for further assistance.
229189 Method timeout monitoring is being resumed for Resource group <%s>.
Description:Timeout monitoring for resource methods in the resource group is being reinstated since the device group reconfigurations have completed.
Solution:This is just an informational message.
229198 Successfully started the fault monitor.
Description:The fault monitor for this data service was started successfully.
Solution:No user action is needed.
229433 The N1 Grid Service Provisioning System database is unavailable or the test user %s or the test table %s is not set up correct
Description:The PostgreSQL Database is unavailable or the test setup ios misconfigured.
Solution:Prepare the database if not done already.
229618 Failed to open contract file %s: %s
Description:Cannot open the specified contract file
Solution:Man contract(4), should help in providing the reason.
230282 scha_control GIVEOVER of resource group %s failed: %s
Description:Zone halt was unable to move the metadata server to a different node on zone shutdown. This is likely to cause operational problems with the shared QFS file systems on nodes that remain up.
Solution:Verify the operation of QFS file systems that were mounted on this zone cluster. If needed, correct by the appropriate QFS recovery procedure.
230516 Failed to retrieve resource name.
Description:HAStoragePlus was not able to retrieve the resource name from the CCR.
Solution:Check that the cluster configuration. If the problem persists, contact your authorized Sun service provider.
231168 INTERNAL ERROR: Failed to get cluster nodeid.
Description:Unable to determine the cluster node ID.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
231188 Retrying to retrieve the resource group information: %s.
Description:An update to cluster configuration occurred while resource group properties were being retrieved.
Solution:No user action is needed.
231411 An error occurred while reading VFSTAB file for filesystem mount point %s in zone cluster %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.
231426 Internal Error: Failed to initialize clconf library.
Description:Unable to initialize the libclconf library.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
231556 %s can't plumb %s: out of instance numbers on %s.
Description:This means that we have reached the maximum number of Logical IPs allowed on an adapter.
Solution:This can be increased by increasing the ndd variable ip_addrs_per_if. However the maximum limit is 8192. The default is 256.
231770 ns: Could not initialize ORB: %d
Description:could not initialize ORB.
Solution:Please make sure the nodes are booted in cluster mode.
231894 ct_pr_tmpl_set_fatal: %s
Description:The libclcontract code was unable to configure a process template in which to launch the requested service. Consequently, the process that is using libclcontract was unable to launch the process under its control.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
231991 WARNING: lkcm_dreg: udlm_send_reply failed
Description:Could not deregister udlm with ucmm.
Solution:No user action is required.
232063 Unable to open door server.
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.
232319 Extension properties %s and %s are empty.
Description:HAStoragePlus detected that no devices or file systems are to be managed.
Solution:This is an informational message, no user action is needed.
232920 -d must be followed by a hex bitmask
Description:Incorrect arguments used while setting up Sun specific startup parameters to the Oracle unix dlm.
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.
233017 Successfully stopped %s.
Description:The resource was successfully stopped by Sun Cluster.
Solution:No user action is required.
233806 %s is an invalid value for the current network address.
Description:The current network address cannot accommodate the current cluster configuration.
Solution:Either reduce the number of zone clusters to configure or change the network address so that it can accommodate the expected number of zone clusters, base cluster nodes, and private networks."
233956 Error in reading message in child process: %m
Description:Error occurred when reading message in fault monitor child process. Child process will be stopped and restarted.
Solution:If error persists, then disable the fault monitor and report the problem.
233970 Failed to read the status_fd
Description:Cannot read the contract status file descriptor.
Solution:Depending on the error, check the SMF man page. Contact SUN vendor for help.
234146 Function: add_application_rgs - The application resource group %s contains the real MySQL resource %s
Description:The application resource group contains the real MySQL resource group
Solution:Specify an application resource group that does not contain the real MySQL resource
234249 scha_resource_get() failed for %s: %s
Description:A call to scha_resource_get() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
234330 Failed to start NFS daemon %s.
Description:HA-NFS implementation failed to start the specified NFS daemon.
Solution:HA-NFS would attempt to remedy this situation by attempting to restart the daemon again, or by failing over if necessary. If the system is under heavy load, increase Start_timeout for the HA-NFS resource.
234438 INTERNAL ERROR: Invalid resource property type <%d> on resource <%s>; aborting node
Description:An attempted creation or update of a resource has failed because of invalid resource type data. This may indicate CCR data corruption or an internal logic error in the rgmd. The rgmd will produce a core file and will force the node to halt or reboot.
Solution:Use clresource show -v and clresourcetype show -v to examine resource properties. If the resource or resource type properties appear to be corrupted, the CCR might have to be rebuilt. If values appear correct, this may indicate an internal error in the rgmd. Retry the creation or update operation. If the problem recurs, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
234547 No entry for file-system %s found in /etc/mnttab.
Description:No entry exits in /etc/mnttab for the specified file system.
Solution:Manually unmount the file system.
234655 Function: validate - SLrunlevel (%s) is invalid with Zonebootopt=%s, needs single-user
Description:The Zoneboot variable is set to -s. Every SLrunlevel other than "S" is invalid.
Solution:Correct the SLrunlevel variable in the parameter file sczbt_<resource name>. You need to specify "S" together with the boot option -s.
234970 %s - The user %s does not belong to project %s
Description:The userid does not belong to the specified project.
Solution:Ensure the userid exists within the project. Check that you have the correct userid and project name.
235032 Function: validate - LXrunlevel (%s) is invalid with Zonebootopt=%s, needs single-user
Description:The Zoneboot variable is set to -s. Every LXrunlevel other than "unknown" is invalid.
Solution:Correct the LXrunlevel variable in the parameter file sczbt_<resource name>. You need to specify "unknown" together with the boot option -s.
235131 Could not enumerate multi-node devices
Description:An error occurred while the list of multinode devices was being retrieved.
Solution:Investigate possible DCS errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
235455 inet_ntop: %s
Description:The cl_apid received the specified error from inet_ntop(3SOCKET). The attempted connection was ignored.
Solution:No user action is required. If the problem persists, 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.
235481 Membership: Unable to change number of threads in membership threadpool.
Description:Threads could not be added to the membership threadpool. 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.
235707 pmf_monitor_suspend: pmf_remove_triggers: %s
Description:The rpc.pmfd server was not able to suspend the monitoring of a process and the monitoring of the process has been aborted. The message contains the system error.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
236604 Mount options for file system mount point %s is incorrect: %s.
Description:The information for the specified mount point is incorrect.
Solution:Check the entries and edit them with valid values.
236733 lookup of oracle dba gid failed.
Description:Could not find group id for dba. udlm will not startup.
Solution:Make sure /etc/nswitch.conf and /etc/group files are valid and have correct information to get the group id of dba.
236737 libsecurity: NULL RPC to program %s (%lu) failed; will not retry %s
Description:A client of the specified server was not able to initiate an rpc connection, because it could not execute a test rpc call. The program will not retry because the time limit of 1 hr was exceeded. The message shows the specific rpc error. The program number is shown. To find out what program corresponds to this number, use the rpcinfo command. 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.
236789 Failed to open the resource group <%s> handle: <%s>.
Description:An API operation on the resource group has failed. Low memory might be the reason for the problem.
Solution:Check the syslog messages from other components for details. If the problem persists, rebooting the node will help. If the problem recurs after rebooting, additional swap space may need to be configured.
237149 clcomm: Path %s being constructed
Description:A communication link is being established with another node.
Solution:No user action is required.
237532 Service %s is not defined.
Description:The SAP service listed in the message is not defined on the system.
Solution:Define the SAP service.
237547 Adaptive server stopped (nowait).
Description:The Sybase adaptive server has been stopped by Sun Cluster HA for Sybase using the nowait option.
Solution:This is an informational message, no user action is needed.
237744 SAP was brought up outside of HA-SAP, HA-SAP will not shut it down.
Description:SAP was started up outside of the control of Sun cluster. It will not be shutdown automatically.
Solution:Need to shut down SAP, before trying to start up SAP under the control of Sun Cluster.
237781 WARNING: lkcm_sync: %d returned from udlm_recv_message
Description:The UDLM has received a message of unknown type. This message is ignored.
Solution:No user action is required.
237999 CMM: Erstwhile inaccessible quorum device %s (qid %d) is online now.
Description:An erstwhile inaccessible quorum device has become accessible now. This node has registered its key on the quorum device. One of the cluster nodes has taken up ownership of the device. The quorum device is considered online now.
Solution:This is an informational message, no user action is needed.
238422 Error while binding 'ifconfig_proxy_server' in the name server. Exiting.
Description:The ifconfig proxy program couldn't bind the corba object from the local nameserver.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
238988 Validate - qping file does not exist or is not executable at %s/qping
Description:The binary file qping can not be found, or is nor executable.
Solution:Confirm the binary file '${SGE_ROOT}/bin/<arch>/qping' exists at that location, and is executable. qping was introduced with Sun Grid Engine 6.0.
239041 clcomm: solaris xdoor: Failed to get credentials returned, errno = %d
Description:Failed to get the credential information associated with the client of the current door invocation.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
239177 The SUNW.qfs resource '%s' that is configured for zone cluster '%s' has a dependency on SUNW.wait_zc_boot resource '%s' that is configured for zone cluster '%s'.
Description:The zone boot handler detected an invalid configuration.
Solution:Correct the configuration by removing the specified dependency.
239415 Failed to retrieve the cluster handle: %s.
Description:Access to the object named failed or an API operation failed while retrieving the cluster information. The reason for the failure is given in the message.
Solution:This might be solved by rebooting the node. For more details about API failure, check the messages from other components. You can also save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
239631 The status of device: %s is set to UNMONITORED
Description:A device is not monitored.
Solution:No user action is required.
239844 sigemptyset(3C) failed while initializing ignored signal set: error %s
Description:The rgmd_starter was unable to initialize a signal set because the sigemptyset(3C) function failed. The message contains the system error. The rgmd_starter cannot launch an rgmd daemon.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
240051 clq_scsi3: One of the key was found to be zero value on quorum device %s.
Description:One of the registration keys is found to be zero value on specified quorum device. This error occurs because of unexpected behavior from device driver or multipathing driver or device's firmware.
Solution:Unconfigure the quorum device and scrub it and then configure it back as a quorum device. Please also look for updates to the device driver, multipathing driver or device firmware. If no updates are available, please contact Sun device driver support team.
240376 No protocol was given as part of property %s for element %s. The property must be specified as %s=PortNumber%cProtocol,PortNumber%cProtocol,...
Description:The IPMP group named is in a transition state. The status will be checked again.
Solution:This is an informational message, no user action is needed.
240388 Prog <%s> step <%s>: timed out.
Description:A step has exceeded its configured timeout and was killed by ucmmd. This in turn will cause a reconfiguration of OPS.
Solution:Other syslog messages occurring just before this one might indicate the reason for the failure. After correcting the problem that caused the step to fail, the operator can retry reconfiguration of OPS.
240529 Listener status probe failed with exit code %s.
Description:An attempt to query the status of the Oracle listener using command 'lsnrctl status <listener_name>' failed with the error code indicated. HA-Oracle will attempt to kill the listener and then restart it.
Solution:No user action is required. HA-Oracle will attempt to restart the listener. However, the cause of the failure should be investigated further. Examine the log file and syslog messages for additional information.
240625 perform_takeover - the promotion to primary failed for %s
Description:The promotion to primary for the replicated object failed on the secondary side.
Solution:Evaluate the root cause for the failed promotion and retry the operation.
241147 Invalid value %s for property %s.
Description:An invalid value was supplied for the property.
Solution:Supply "conf" or "boot" as the value for DNS_mode property.
241215 AS_DEF_DOMAINS_PATH not found in the JSAS config file %s
Description:The variable AS_DEF_DOMAINS_PATH is not set in the asenv.conf configuration file. The path to the default domain directory is by default set in this variable in the asenv.conf file. If this is not available, the agent cannot know the default domain directory.
Solution:Set the extension property domaindir while creating the resource.
241369 clq_netapp: Error %d from quorum_read_reservations --- failed to read reservations from quorum device %s.
Description:An error was encountered while trying to read reservations on the specified quorum device.
Solution:There may be other related messages on this and other nodes connected to this quorum device that may indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.
241441 clexecd: ioctl(I_RECVFD) returned %d. Returning %d to clexecd.
Description:clexecd program has encountered a failed ioctl(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.
241630 File %s should be readable only by the owner %s.
Description:The specified file is expected to be readable only by the specified user, who is the owner of the file.
Solution:Make sure that the specified file has correct permissions by running "chmod 600 <file>" for nonexecutable files, or "chmod 700 <file>" for executable files.
241761 Unknown error on door server: %s
Description:The zone state change registration with sc_zonesd failed for an unknown reason.
Solution:Search for messages from sc_zonesd to determine the source of the error. Save a copy of the /var/adm/messages files on all nodes. If the problem persists, contact your authorized Sun service provider for assistance in diagnosing the problem.
241828 Method <%s> on resource <%s>, resource group <%s>, node <%s>: Timed out.
Description:A VALIDATE method execution has exceeded its configured timeout and was killed by the rgmd. This in turn will cause the failure of a creation or property update operation on a resource or resource group.
Solution:Consult data service documentation to diagnose the cause of the method failure. Other syslog messages occurring just before this one might indicate the reason for the failure. After correcting the problem that caused the method to fail, the operator can retry the operation that failed.
241914 Waiting for volume (%s) of disk group (%s) till it is in good state ...
Description:The ScalDeviceGroup is waiting for the specified volume to be in healthy state.
Solution:No user action is required.
241948 Failed to retrieve resource <%s> extension property <%s>
Description:Can not get extension property.
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.
242209 Error: ${LOGGER} is already running.
Description:The cl_eventlog init script found the cl_eventlogd already running. It will not start it again.
Solution:No user action is required.
242214 clexecd: fork1 returned %d. Returning %d to clexecd.
Description:clexecd program has encountered a failed fork1(2) system call. The error message indicates the error number for the failure.
Solution:If the error number is 12 (ENOMEM), install more memory, increase swap space, or reduce peak memory consumption. If error number is something else, contact your authorized Sun service provider to determine whether a workaround or patch is available.
242261 Incorrect permissions detected for the executable %s associated with the FilesystemCheckCommand extension property: %s.
Description:The specified executable associated with the FilesystemCheckCommand extension property is not owned by user "root" or is not executable.
Solution:Correct the rights of the filename by using the chmod/chown commands.
242385 Failed to stop liveCache with command %s. Return code from SAP command is %d.
Description:Failed to shutdown liveCache immediately with listed command. The return code from the SAP command is listed.
Solution:Check the return code for dbmcli command for reasons of failure. Also, check the SAP log files for more details.
243322 Unable to launch dispatch thread on remote node %d
Description:An attempt to deliver an event to the specified node failed.
Solution:Examine other syslog messages occurring at about the same time on both this node and the remote node 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.
243585 cl_execd: Got an unexpected signal %d (pid=%d, ppid=%d)
Description:The cl_execd program got an unexpected signal and is exiting.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
243639 Scalable service instance [%s,%s,%d] deregistered on node %s.
Description:The specified scalable service had been deregistered on the specified node. Now, the gif node cannot redirect packets for the specified service to this node.
Solution:This is an informational message, no user action is needed.
243648 %s: Could not create %s table
Description:The libscdpm could not create either 1. cluster-wide consistent table that the Disk Path Monitoring Daemon uses to maintain persistent information about disks and their monitoring status. OR 2. cluster-wide consistent table that the Disk Path Monitoring Daemon uses to maintain persistent information about the autoreboot feature status of all nodes.
Solution:This is a fatal error for the Disk Path Monitoring daemon and will mean that the daemon cannot run on this node. Check to see if there is enough space available on the root file system. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
243781 cl_event_open_channel(): %s
Description:The cl_eventd 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.
243947 Failed to retrieve resource group mode.
Description:HAStoragePlus was not able to retrieve the resource group mode to which it belongs from the CCR.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
243965 udlm_ack_msg: udp is null!
Description:Can not acknowledge a message received from udlmctl because the address to acknowledge to is null.
Solution:No user action is required.
244116 clcomm: socreate on routing socket failed with error = %d
Description:The system prepares IP communications across the private interconnect. A socket create operation on the routing socket failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
244571 Initialization failed. Invalid command line %s %s.
Description:Unable to process parameters passed to the call back method. The parameters are indicated in the message. This is a Sun Cluster HA for Sybase internal error.
Solution:Report this problem to your authorized Sun service provider
244794 Failed to issue vxdg list command.
Description:An error occurred when the command 'vxdg list' was run.
Solution:Ensure that the correct version of VxVM is installed. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
245128 Extension property %s must be set.
Description:The indicated property must be set by the user.
Solution:Use scrgadm to set the property.
246751 Failed to stop derby data service; unsuccessful exit
Description:Could not stop the derby data service.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
246769 kill -TERM: %s
Description:The rpc.fed server is not able to kill a tag that timed out, and the error message is shown. An error message is output to syslog.
Solution:Save the /var/adm/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.
247336 Going down on signal %d.
Description:The cl_eventlogd daemon has received a SIGTERM signal, which indicates that it must exit.
Solution:This message is informational only, and does not require user action.
247392 scnetapp fatal error - Cannot get element from %s
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
247405 Failed to take the resource out of PMF control. Will shutdown WLS using sigkill
Description:The resource could not be taken out of pmf control. The WLS will however be shutdown by killing the process using sigkill.
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.
247682 recv_message: cm_reconfigure: %s
Description:udlm received a message to reconfigure.
Solution:No user action is required. OPS is going to reconfigure.
247720 %s: t_alloc() failed: %s.
Description:The cluster was unable to allocate space for network protocol information during a cluster installation or configuration change.
Solution:Check memory utilization on each cluster node and install more memory or increase swap space, as necessary. If memory utilization appears to be otherwise normal, contact your authorized Sun service provider to determine whether a workaround or patch is available. Once the issue is addressed, retry the affected administrative operation.
247752 Failed to start the service %s.
Description:Specified data service failed to start.
Solution:Look in /var/adm/messages for the cause of failure. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
247805 The current resource-type version (%d) of ScalDeviceGroup does not support zone cluster. Create the resource with the latest available resource-type version.
Description:Self explanatory.
Solution:Register the latest available ScalDeviceGroup resource type, and create the resource with that version. If the problem persists contact your authorized Sun service provider.
247973 pthread_mutex_trylock error %d line %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
248287 Telemetry data service failed to get cacao port
Description:The port number to connect to Cacao could not be retrieved. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
248355 Invalid Parameter for check_properties
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
248838 SAPDB parent kernel process file does not exist.
Description:The SAPDB parent kernel process file cannot be found on the system.
Solution:During normal operation, this error should not occurred, unless the file was deleted manually. No user action is required.
248975 Failfast: Destroying failfast unit %s while armed in zone "%s" (zone ID %d)
Description:The specified failfast unit was destroyed while it was still armed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
249196 The ZFS pool '%s' is already configured in the resource %s.
Description:HAStoragePlus detected that the specified ZFS pool is already configured in another resource. HAStoragePlus does not allow the same ZFS pool to be configured in multiple resources to avoid data corruption and availability problems.
Solution:Do not use the specified ZFS pool in this resource.
249804 INTERNAL ERROR CMM: Failure creating sender thread.
Description:An instance of the userland CMM encountered an internal initialization error. 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.
249904 Error while binding 'pnm_proxy_server' in the name server. Exiting.
Description:The pnm proxy program could not bind the corba object in the global name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
250133 Failed to open the device %s: %s.
Description:This is an internal error. System failed to perform the specified operation.
Solution:For specific error information check the syslog message. Provide the following information to your authorized Sun service provider to diagnose the problem. 1) Saved copy of /var/adm/messages file 2) Output of "ls -l /dev/sad" command 3) Output of "modinfo | grep sad" command.
250151 write: %s
Description:The cl_apid experienced the specified error when attempting to write to a file descripter. If this error occurs during termination of the daemon, it may cause the cl_apid to fail to shutdown properly (or at all). If it occurs at any other time, it is probably a CRNP client error.
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.
250364 SCSLM <%s> pool_value_get_uint64 error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
250387 Stop fault monitor using pmfadm failed. tag %s error=%s.
Description:The Process Monitoring Facility could not stop the Sun Cluster HA for Sybase fault monitor. The fault monitor tag is provided in the message. The error returned by the PMF is indicated in the message.
Solution:Stop the fault monitor processes. Contact your authorized Sun Service provider to report this problem.
250885 CMM: Quorum device %s: owner set to node %d.
Description:The specified node has taken ownership of the specified quorum device.
Solution:This is an informational message, no user action is needed.
251472 Validation failed. SYBASE directory %s does not exist.
Description:The indicated directory does not exist. The SYBASE environment variable may be incorrectly set or the installation may be incorrect.
Solution:Check the SYBASE environment variable value and verify the Sybase installation.
251482 Error: Can't start ${SERVER} : $rgmd_exec_cmd_output
Description:An attempt to start the rgmd server failed. This error will prevent this node from participating as a full member of the cluster.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save a copy of these 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
251552 Failed to validate configuration.
Description:The data service is not properly configured.
Solution:Look at the prior syslog messages for specific problems and take corrective action.
251565 Validation failed. Neither default PARAMETER_FILE: %s
Description:Neither the parameter file init<sid>.ora nor the server parameter file spfile<sid>.ora is present in the default location $ORACLE_HOME/dbs/ folder.
Solution:Create a valid parameter file or server parameter file for that Oracle instance in the default location, or provide a valid parameter file in the PARAMETER_FILE extension property of the HA-Oracle resource.
251591 This node has a lower preference to node %d for global service %s associated with path %s.Device switchover can still be done to this node.
Description:HAStoragePlus determined that the node is less preferred to another node from the DCS global service view, but as the Failback setting is Off, this is not a problem.
Solution:This is an informational message, no user action is needed.
251702 Error initializing an internal component of the version manager (error %d).
Description:This message can occur when the system is booting if incompatible versions of cluster software are installed.
Solution:Verify that any recent software installations completed without errors and that the installed packages or patches are compatible with the rest of the installed software. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.
251825 Access error to %s : %s.
Description:The zone handler failed to access the specified configuration file.
Solution:Check for the error message and rectify the problem.
251867 SCSLM <%s> zone <%s> unexpected group <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
252457 The %s command does not have execute permissions: <%s>
Description:This command input to the agent builder does not have the expected default execute permissions.
Solution:Reset the permissions to allow execute permissions using the chmod command.
252941 Giveover attempt failed for %s: resource group is currently starting or stopping. Will retry.
Description:Got an error attempting to switch over the QFS meta data resource group. This is probably a transient error because the resource group is being modified.
Solution:If this problem persists, verify that the resource group is configured correctly.
253279 The asadmin list-node-agents command failed to run. Unable to communicate with the Domain Admin Server %s on port %d. Probe Cannot determine the status of the Node Agent %s.
Description:This error is from the Node Agents Probe. Before checking for the status of the Node Agents, the probe makes sure the Domain Admin Server is accessible. This error message indicates that the Domain Admin Server is not UP and the probe cannot get the status of the Node Agents.
Solution:If the Domain Admin Server is also a Sun Cluster resource then set the resource dependency between the Node Agents resource and the Domain Admin Server resource. If the Domain Admin Server is not a Sun cluster resource then make sure it is Running.
253709 The %s protocol for this node%s is not compatible with the %s protocol for node %u%s.
Description:This is an informational message from the cluster version manager and may help diagnose what software component is failing to find a compatible version during a rolling upgrade. This error may also be due to attempting to boot a cluster node in 64-bit address mode when other nodes are booted in 32-bit address mode, or vice versa.
Solution:This message is informational; no user action is needed. However, if this message is for a core component, one or more nodes may shut down in order to preserve system integrity. Verify that any recent software installations completed without errors and that the installed packages or patches are compatible with the rest of the installed software.
253810 Resource dependency on %s is not set.
Description:The resource dependency on the resource listed in the error message is not set.
Solution:Set the resource dependency on the appropriate resource.
254053 Initialization error. Fault Monitor password is NULL
Description:Internal error. Environment variable SYBASE_MONITOR_PASSWORD not set before invoking fault monitor.
Solution:Report this problem to your authorized Sun service provider.
254131 resource group %s removed.
Description:This is a notification from the rgmd that the operator has deleted a resource group. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
254388 Failed to retrieve Message server pid.
Description:Failed to retrieve the process ID for the message server indicating the message server process is not running.
Solution:No user action is required. The fault monitor will detect this and take appropriate action.
254477 Error stopping the PMF
Description:The PMF service fails to stop.
Solution:Please reboot the node,
254534 (%s) not a member of the diskgroup (%s)
Description:This node is not in the node list of the disk set or disk group.
Solution:Determine whether the node is in the node list of the disk set or disk group. To retrieve the node list of the disk set or disk group, run scstat -D or cldevicegroup show.
254692 scswitch: internal error: bad state <%s> (<%d>) for resource group <%s>
Description:While attempting to execute an operator-requested switch of the primaries of a resource group, the rgmd has discovered the indicated resource group to be in an invalid state. The switch action will fail.
Solution:This may indicate an internal error or bug in the rgmd. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
255071 Low memory: unable to process client registration
Description:The cl_apid experienced a memory error that prevented it from processing a client registration request.
Solution:Increase swap space, install more memory, or reduce peak memory consumption.
255115 Retrying to retrieve the resource type information.
Description:An update to cluster configuration occurred while resource type properties were being retrieved
Solution:Ignore the message.
255135 create_and_arm_failfast : Unable to get ff_admin_ptr
Description:Unable to get the reference for the failfast_admin object from the name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
255314 Could not stop monitor for resource %s.
Description:The monitor for HA-KDC is running and could not be stopped.
Solution:Check to see if the monitor is still running and try to manually stop the monitor. Observe the behavior and take the appropriate action.
255771 Failed to add the MDS node '%s' to the list of MDS nodes.
Description:The zone boot handler failed to generate the list of MDS server nodes.
Solution:Investigate the zone boot log messages and try to rectify the problem. If problem persists after rebooting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
255870 Complete_Probe for resource sckrb5 failed.
Description:Sun Cluster could not complete the thorough probing of HA-KDC.
Solution:Check for other error messages logged before this one to determine the specific cause of failure.
256023 pmf_monitor_suspend: 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. This error occurred for a process whose monitoring had been suspended. The monitoring of this process has been aborted and can not be resumed.
Solution:Determine if the machine is running out of memory. If this is not the case, save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
256245 ORB initialization failure
Description:An attempt to start the scdpmd failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
256574 Device group type is cvm
Description:The disk group type is Veritas Volume Manager with the cluster feature. This message is an informational message.
Solution:No user action is required.
256703 Notice: not OK to join. Error: %s Retrying.
Description:An unknown error has prevented the node from rejoining the cluster. The RAC framework will automatically retry this operation.
Solution:No user action is required.
256915 Method <%s> on resource <%s>, node <%s>: authorization error: %d.
Description:An attempted method execution failed, apparently due to a security violation; this error should not occur. This failure is considered a method failure. 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:Examine other syslog messages occurring at about the same time to see if the problem can be diagnosed. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing the problem.
256960 scvxvmlg error - opendir(%s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
257641 CMM: Unable to register for membership change callbacks.
Description:An instance of the userland CMM encountered an internal initialization error. The userland CMM could not register for membership change callbacks.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
257965 File %s should be readable by %s.
Description:A program required the specified file to be readable by the specified user.
Solution:Set correct permissions for the specified file to allow the specified user to read it.
258289 The resource groups containing SUNW.qfs resources brought online successfully.
Description:This is a notification from the handler that it brought the SUNW.qfs resource groups online.
Solution:This is an informational message; no user action is needed.
258308 UNRECOVERABLE ERROR: Sun Cluster boot: failfastd not started
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
258909 clexecd: sigfillset returned %d. Exiting.
Description:clexecd program has encountered a failed sigfillset(3C) 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.
259034 Failfast : Real Time class not configured in this system
Description:Real time class is not configured in this system, but a task needs to run with real time priority.
Solution:Configure real time priority class for the system.
259455 in fe_set_env_vars malloc failed
Description:The rgmd server was not able to allocate memory for the environment name, 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.
259548 File-system %s is not mounted on mountpoint directory %s
Description:The file system that this ScalMountPoint resource represents is not 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.
259588 Function: validate - Milestone not set in %s
Description:The Milestone variable is not set in the parameter file sczbt_<resource name>.
Solution:Set the Milestone variable in the parameter file sczbt_<resource name>.
259775 Validate - nmbd %s non-existent executable
Description:The Samba executable nmbd either doesn't exist or is not executable.
Solution:Check the correct pathname for the Samba (s)bin directory was entered when registering the resource and that the program exists and is executable.
259810 reservation error(%s) - do_scsi3_reserve() 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.
259985 SCSLM <%s> ret %d, outputs <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
260883 In J2EE probe, failed to find http header in %s.
Description:The data service could not find an http header in reply from J2EE engine.
Solution:Informational message. No user action is needed.
260951 Validate_sbp - The short ping timeout %s is not numeric
Description:The short ping timeout is not numeric
Solution:Make sure that the specified short ping timeout is numeric
261109 Method <%s> failed to execute on resource <%s> in resource group <%s>, on node <%s>, error: <%d>
Description:A resource method failed to execute, due to a system error number identified in the message. The indicated error number appears not to match any of the known errno values described in intro(2). This is considered a method failure. Depending on which method is 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, or it might cause an attempted edit of a resource group or its resources to fail.
Solution:Other syslog messages occurring at about the same time might provide evidence of the source of the problem. If not, save a copy of the /var/adm/messages files on all nodes, and (if the rgmd did crash) a copy of the rgmd core file, and contact your authorized Sun service provider for assistance.
261123 resource group %s state change to managed.
Description:This is a notification from the rgmd that a resource group's state has changed. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
261236 Validate - my.cnf %s does not exist
Description:The my.cnf configuration does not exist in the defined database directory.
Solution:Make sure that my.cnf is placed in the defined database directory.
261537 Failed to issue samcmd command: %s
Description:An error occurred when the command 'samcmd' was run.
Solution:Correct the entries in the master configuration file /etc/opt/SUNWsamfs/mcf and repeat the operation.
261662 Not attempting to start Resource Group <%s> on node <%s>, because the Resource Groups <%s> for which it has strong negative affinities are online.
Description:The rgmd is enforcing the strong negative affinities of the resource groups. This behavior is normal and expected.
Solution:No user action is required. If desired, use clresourcegroup to change the resource group affinities.
262047 Switchover of RG %s to node %s failed. Trying node %s.
Description:An attempt to switch over the resource group that contains the metadata server resource to another node failed. The RGM is trying to switch the resource group to another node in the resource group's node list. This message is an informational message.
Solution:No user action is required.
262567 Failed to initialize DSDL : %s.
Description:An error prevented the initialization of the DSDL library.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
262898 Name service not available.
Description:The monitor_check method detected that name service is not responsive.
Solution:Check if name service is configured correctly. Try some commands to query name serves, such as ping and nslookup, and correct the problem. If the error still persists, then reboot the node.
262901 Validation failed. CRS_HOME/bin/crs_stat not found CRS_HOME=%s
Description:The SUNW.scalable_rac_server_proxy agent could not find the crs_stat binary in the indicated $CRS_HOME/bin/ directory.
Solution:Check whether the $CRS_HOME/bin/ directory is accessible, and if so, whether the crs_stat binary exists. If the problem persists, contact your Sun support representative for further assistance.
263258 CCR: More than one copy of table %s has the same version but different checksums. Using the table from node %s.
Description:The CCR detects that two valid copies of the indicated table have the same version but different contents. The copy on the indicated node will be used by the CCR.
Solution:This is an informational message, no user action is needed.
263440 Only a single path to the JSAS install directory has to be set in Confdir_list
Description:Each JSAS resource can handle only a single installation of JSAS. You cannot create a resource to handle multiple installations.
Solution:Create a separate resource for making each installation of JSAS Highly Available.
263495 INTERNAL ERROR : program name is NULL
Description:The program name being processed was incorrect.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
263582 Node Agent %s failed to stay up.
Description:This is an informational message. The Probe detected that the Node Agent is down. The Probe will either restart the Node Agents and all the Application Server instances or Failover to another node.
Solution:No User action needed.
263652 Error in binding the handle:%s
Description:Error in creating the handle to bind with the SMF repository.
Solution:Check the SMF man page to know more about the error. Also make sure the basic SMF functionalities are working. Contact your SUN vendor for more help.
264326 Error (%s) when reading extension property <%s>.
Description:Error occurred in API call scha_resource_get or the program failed to read an extension property of the resource.
Solution:Save the contents of /var/adm/messages or check syslog messages for errors logged from other system modules. If the error persists, contact your Sun service representative.
264801 Check_takeover - the check for takeover failed because the replication is still working for resource %s
Description:The check for the replication status is successful on a takeover
Solution:Try a switchover instead
264895 Validate - smbd %s nonexistent executable
Description:The Samba executable smbd either doesn't exist or is not executable.
Solution:Check the correct pathname for the Samba (s)bin directory was entered when registering the resource and that the program exists and is executable.
265013 Update on the resource is completed successfully.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
265109 Successfully stopped the database.
Description:The resource was able to successfully shutdown the HADB database.
Solution:This is an informational message, no user action is needed.
265139 stop_pgs: Stop PostgreSQL with the option %s
Description:The PostgreSQL database server is shut down with the specified option.
Solution:No user action is required.
265504 scf_property_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.
265832 in libsecurity for program %s (%lu); svc_tli_create failed for transport %s
Description:A server (rpc.pmfd, rpc.fed or rgmd) was not able to start on the specified transport. The server might stay up and running as long as the server can start on other transports. 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.
265925 CMM: Cluster lost operational quorum; aborting.
Description:Not enough nodes are operational to maintain a majority quorum, causing the cluster to fail to avoid a potential split brain.
Solution:The nodes should rebooted.
266055 "pmfctl -R": Error resuming pid %d for tag <%s>: %d
Description:An error occurred while rpc.pmfd attempted to resume the monitoring of the indicated pid, possibly because the indicated pid has exited while attempting to resume its monitoring.
Solution:Check if the indicated pid has exited, if this is not the case, Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
266059 security_svc_reg failed.
Description:The rpc.pmfd server was not able to initialize authentication and rpc initialization. This happens while the server is starting up, at boot time. The server does not come up, 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.
266097 Function: validate: WAIT %s is not numeric
Description:The value specified in the WAIT variable is not numeric
Solution:Fix the WAIT variable in the Configuration file.
266099 PNM proxy server killed(sigterm) Exiting.
Description:The pnm program received a SIGTERM signal and is exiting.
Solution:This is an informational message. No user action is required.
266116 get_node_list failed for malloc of size %d
Description:Unable to allocate memory when reading nodelist.
Solution:Increase swap space, install more memory, or reduce peak memory consumption.
266274 %s: No memory, restarting service.
Description:The PMF action script supplied by the DSDL could not complete its function because it could not allocate the required amount of memory; the PMF action script has restarted the application.
Solution:If this error persists, contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
266357 Membership: Could not initialize membership subsystem.
Description:Could not initialize membership subsystem.
Solution:No user action needed.
266519 invalid value for parameter '%sfailfast': "%s". Using default value of 'panic'
Description:/opt/SUNWudlm/etc/udlm.conf did not have a valid entry for failfast mode. Default mode of 'panic' will be used.
Solution:No user action is required.
266582 Failed to initialize Condition Variable : %s
Description:The condition variable 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.
266640 Specified global device path %s is invalid : %s.
Description:HAStoragePlus found that the specified path is not a global device.
Solution:Usually, this means that a typo has been made when filling the GlobalDevicePaths property. Check and specify valid global device path.
266834 CMM: Our partition has been preempted.
Description:The cluster partition to which this node belongs has been preempted by another partition during a reconfiguration. The preempted partition 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 quorum was lost. Determine why quorum was lost on this node partition, resolve the problem and reboot the nodes in this partition.
266873 Started obtaining the list of SUNW.qfs resources that are configured for this zone cluster.
Description:This is a notification about retrieval of the configured SUNW.qfs resources for this zone cluster.
Solution:This is an informational message; no user action is needed.
267096 SCSLM thread pools facility error %d
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
267361 check_cmg - Database connect to %s failed
Description:While probing the Oracle E-Business Suite concurrent manager, a test to connect to the database failed.
Solution:No user action is required. If two successive failures occur, the concurrent manager resource will be restarted.
267589 launch_fed_prog: call to rpc.fed failed for program <%s>, step <%s>
Description:Launching of fed program failed due to a failure of ucmmd to communicate with the rpc.fed daemon. If the rpc.fed process died, this might lead to a subsequent reboot of the node.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
267673 Validation failed. ORACLE binaries not found ORACLE_HOME=%s
Description:Oracle binaries not found under ORACLE_HOME. ORACLE_HOME specified for the resource is indicated in the message. HA-Oracle will not be able to manage Oracle if ORACLE_HOME is incorrect.
Solution:Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.
267839 The entry in mnttab for mount point '%s' exceeds %d characters.
Description:The internal buffer size of the mnttab entry for the specified mount point has exceeded MNT_LINE_MAX characters.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
268346 Cannot connect to message server on port <%d>. Return code %d.
Description:Probe could not connect to the SAP message server.
Solution:No user action needed.
268460 check_for_ccrdata failed malloc of size %d
Description:Call to malloc failed. The "malloc" man page describes possible reasons.
Solution:Install more memory, increase swap space or reduce peak memory consumption.
268467 Function: start_sczbt - logical interface %s:%s placed into %s
Description:The interface of the logical host resource is placed by the start command into the referenced zone.
Solution:No user action is required.
268593 Failed to take the resource out of PMF control. Sending SIGKILL now.
Description:An error was encountered taking the resource out of PMF's control while stopping the resource. The resource will be stopped by sending it SIGKILL.
Solution:This message is informational; no user action is required.
268646 Extension property <network_aware> has a value of <%d>
Description:Resource property Network_aware is set to the given value.
Solution:This is an informational message, no user action is needed.
269027 sigfillset: %s
Description:The daemon was unable to configure its signal handling functionality, so it is unable to run.
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.
269195 zc_member(%d): Could not initialize clconf. Exiting.
Description:This process failed to initialize clconf. Support for the current zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
269240 clconf: Write_ccr routine shouldn't be called from kernel
Description:Routine write_ccr that writes a clconf tree out to CCR should not be called from kernel.
Solution:No user action is required. This is informational message.
269251 Failing over all NFS resources from this node.
Description:HA-NFS is failing over all NFS resources.
Solution:This is an informational message, no action is needed. Look for previous error messages from HA-NFS for the reason for failing over.
269454 Validate - Userid %s is not a member of group mqm
Description:The specified userid is not a member of group mqm.
Solution:The specified user must be a member of group mqm.
269641 Error in failing over the res group:%s
Description:The number of restarts of services under the resource has reached the max. So the resource will be failing over
Solution:No user action is required. This is an informational message.
270179 SCSLM pools facility, no static config file
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
270351 The derby data service failed to retrieve private local nodename
Description:The data service tried to find the local nodename associated with the private interconnects.
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.
270904 Test-file %s is not expected to be symlink.
Description:The test file for performing I/O operations is a symbolic link. The replacement of the test file by a symbolic link might be caused by malicious activity in your system.
Solution:Delete the symbolic link and restart the ScalMountPoint resource.
271274 Failed to get RT parameters
Description:Could not query Real Time parameters for the system. The process will be aborted and this zone will not be available 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.
272086 CMM: Quorum device %s does not appear to be configured on quorum server. This quorum device will be unavailable.
Description:The quorum device is unknown to the quorum server. This quorum device may have been unconfigured on the quorum server.
Solution:Remove the device using scconf, and try adding it again.
272139 Message Server Process is not running. pid was %d.
Description:Message server process is not present on the process list indicating message server process is not running on this node.
Solution:No user action is required. Fault monitor will detect that message server process is not running, and take appropriate action.
272434 Validation failed. SYBASE text server startup file RUN_%s not found SYBASE=%s.
Description:Text server was specified in the extension property Text_Server_Name. However, text server startup file was not found. Text server startup file is expected to be: $SYBASE/$SYBASE_ASE/install/RUN_<Text_Server_Name>
Solution:Check the text server name specified in the Text_Server_Name property. Verify that SYBASE and SYBASE_ASE environment variables are set property in the Environment_file. Verify that RUN_<Text_Server_Name> file exists.
273018 INTERNAL ERROR CMM: Failure starting CMM.
Description:An instance of the userland CMM encountered an internal initialization error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
273046 impossible to read the resource name
Description:An internal error prevented the application from recovering its resource name
Solution:This is an informational message, no user action is needed
273354 CMM: Node %s (nodeid = %d) is dead.
Description:The specified node has died. It is guaranteed to be no longer running and it is safe to take over services from the dead node.
Solution:The cause of the node failure should be resolved and the node should be rebooted if node failure is unexpected.
273861 Validate - Infrastructure directory %s does not exist
Description:The value of the Oracle Application Server Infrastructure directory within the xxx_config file is wrong, where xxx_config is either 9ias_config for Oracle 9iAS or 10gas_config for Oracle 10gAS.
Solution:Specify the correct OIAS_INFRA in the appropriate xxx_config file.
273892 fatal: CCR callback registration error: %s
Description:An error occurred in a CCR related operation while registering the callbacks for updating nodename cache. Hence RGM will abort.
Solution:Contact your authorized Sun service representative for resolution.
274020 Using mount options "%s" from /etc/vfstab
Description:Mount options from the entry in /etc/vfstab for the specified NFS file system will be used for mounting the file system. This message is an informational message.
Solution:No user action is required.
274138 Could not get device group info for (%s)
Description:An error occurred while status information for the VxVM volume was being retrieved.
Solution:Ensure that the correct version of the library is installed. Contact your authorized Sun service provider for assistance in diagnosing the problem.
274229 validate_options: %s Option -N not set
Description:The option -N 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.
274386 reservation error(%s) - Could not determine controller number for device %s
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.
274506 Wrong data format from kstat: Expecting %d, Got %d.
Description:See 176151
Solution:See 176151
274562 Fault monitor for resource %s failed to stay up.
Description:Resource fault monitor failed. The resource will not be monitored.
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.
274603 No interfaces found
Description:The allow_hosts or deny_hosts for the CRNP service specifies LOCAL and the cl_apid is unable to find any network interfaces on the local host. 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.
274605 Server is online.
Description:Informational message. Oracle server is online.
Solution:No user action is required.
274887 clcomm: solaris xdoor: rejected invo: door_return returned, errno = %d
Description:An unusual but harmless event occurred. System operations continue unaffected.
Solution:No user action is required.
274901 Invalid protocol %s given as part of property %s.
Description:The property named does not have a legal value.
Solution:Assign the property a legal value.
275313 SCSLM zone <%s> bind to pool.sys_id %llu, should be <%s%s> (pool.sys_id %llu)
Description:A non-global zone used to run resource groups under SLM control is not dynamically bind to the expected SCSLM pool (poolbind).
Solution:Set zone pool binding to the displayed SCSLM pool (with poolbind command) before launching a resource group under SLM control in this zone.
275415 Broker_user extension property must be set
Description:A Sun ONE Message Queue resource with the Smooth_Shutdown property set to true must also set the Broker_User extension property.
Solution:Set the Broker_User extension property on the resource.
275532 "pmfadm -k": Error signaling <%s>: %s
Description:An error occurred while rpc.pmfd attempted to send a signal to one of the processes of the given tag. The reason for the failure is also given. The signal was sent as a result of a 'pmfadm -k' command.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
275564 SCSLM zone_getattr errno <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
275628 SCSLM <%s> pool_conf_alloc error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
276672 reservation error(%s) - did_get_did_path() error
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.
277044 Error occurred while waiting for first partition nodes
Description:During a dual-partition upgrade in a live upgrade scenario, processing must wait for the first partition nodes to come online. Some error occurred while waiting for the nodes to come online. Upgrade process has stopped and cannot proceed.
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.
277745 Monitor check for derby data service not successful.
Description:The data service check of the node was unsuccessful.
Solution:This message is informational; no user action is needed.
277995 (%s) msg of wrong version %d, expected %d
Description:Expected to receiver a message of a different version. udlmctl will fail.
Solution: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.
278199 reset_rg_state: unable to change state of resource group <%s> on node <%s>; assuming that node died
Description:The rgmd daemon was unable to reset the state of the specified resource group to offline on the specified node or zone, presumably because the node or zone died.
Solution:Examine syslog output on the specified node to determine the cause of node death. The syslog output might indicate further remedial actions.
278240 Stopping fault monitor using pmf tag %s.
Description:The fault monitor will be stopped using the Process Monitoring Facility (PMF), with the tag indicated in the message.
Solution:This is an information message, no user action is needed.
278292 Function: validate - Zone %s is configured with ip-type=exclusive, and the sczbt resource is dependand on a SUNW.LogicalHostname resource. This combination does not work.
Description:The configured non-global zone has set ip-type=exclusive within its zone config, and the resource was configured to depend on a SUNW.LogicalHostname resource. It is not possible to assign the IP address from this SUNW.LogicalHostname resource for the non-global zone if ip-type=exclusive is set.
Solution:Either set ip-type=shared for the non-global zone config, or remove the dependency to the SUNW.LogicalHostname resource.
278526 in libsecurity for program %s (%lu); creation of file %s failed: %s
Description:The specified server was not able to create a cache file for rpcbind information. 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.
278654 Unable to determine password for broker %s.
Description:Cannot retrieve the password for the broker.
Solution:Check that the scs1mqconfig file is accessible and correctly specifies the password.
278952 Issuing a failover request because of probe failures.
Description:This message indicates that the fault monitor is about to make a failover request because of probe failures. If the request fails, refer to the syslog messages that appear after this message.
Solution:This is an informational message; no user action is required.
279035 Unparsed sysevent received
Description:The cl_apid was unable to process an incoming sysevent. The message will be dropped.
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.
279061 The file %s needed by the telemetry data service does not exist
Description:A program or script of the telemetry 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.
279084 CMM: node reconfiguration
Description:The cluster membership monitor has processed a change in node or quorum status.
Solution:This is an informational message, no user action is needed.
279152 listener %s probe successful.
Description:Informational message. Listener monitor successfully completed first probe.
Solution:No user action is required.
279195 Error determining the resource group name
Description:The name of the resource group that contains this resource could not be determined.
Solution:Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
279309 Failfast: Invalid failfast mode %s specified. Returning default mode PANIC.
Description:An invalid value was supplied for the failfast mode. The software will use the default PANIC mode instead.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
279565 Function: validate - exclude: lofs found in /etc/system
Description:The kernel module for the lofs filesystem is still excluded in /etc/system.
Solution:Place a * in front of the exlude: lofs line and reboot the node.
280001 Invalid special device path %s detected for mount point %s %s zone cluster %s.
Description:The specified special device path is not valid.
Solution:Check the path and correct the entry with a valid global device path.
280265 ucmmd got invalid upgrade callback from version manager: unrecognized ucc_name %s
Description:Version manager delivered upgrade callback to ucmmd passing an upgrade callback object name that was not registered by ucmmd.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
280280 statvfs failed on the mount point %s for local zone %s : %s
Description:The file system specified on the mount point is not available for local zone.
Solution:Check the statvfs(2) man page for errors and try to resolve the problem. Otherwise contact your authorized Sun service provider.
280492 time for %s: %s
Description:The time(2) function failed with the specified error. This error will cause the rpc.pmfd to stop monitoring the specified nametag.
Solution: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.
280505 Validate - Application user <%s> does not exist
Description:The Oracle E-Business Suite applications userid was not found in /etc/passwd.
Solution:Ensure that a local applications userid is defined on all nodes within the cluster.
280559 IPMP group %s is not homogenous
Description:Not all adapters in the IPMP group can host the same types of IP addresses. For example, some adapters are IPv4 only, others are capable of hosting IPv4 and IPv6 both and so on.
Solution:Configure the IPMP group such that each adapter is capable of hosting IP addresses that the rest of the adapters in the group can.
280685 Failfast : Zone %s (zone ID %d) rebooting
Description:Rebooting zone with the specified zone ID, as the specified failfast unit was destroyed while it was still armed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
280981 validate: The N1 Grid Service Provisioning System start command does not exist, its not a valid masterserver installation
Description:The cr_server command is not found in the expected subdirectory
Solution:Correct the Basepath specified in the parameter file.
281043 parse_path() failed for Resource %s : %s
Description:The specified filer is not configured in the cluster.
Solution:Please configure the filer in the cluster OR Contact your authorized Sun service provider to determine whether a workaround or patch is available.
281428 Failed to retrieve the resource group handle: %s.
Description:An API operation on the resource group has failed.
Solution:For the resource group name, check the syslog tag. For more details, check the syslog messages from other components. If the error persists, reboot the node.
281601 CMM: Could not find device information in CCR. Quorum device %s will be unavailable.
Description:In order to configure a quorum server as a quorum device, the module must be able to read certain information from the CCR. Because the necessary information in unavailable, the device will be in a failed state.
Solution:Remove the device using scconf, and try adding it again.
281680 fatal: couldn't initialize ORB, possibly because machine is booted in non-cluster mode
Description:The rgmd daemon was unable to initialize its interface to the low-level cluster machinery. This might occur because the operator has attempted to start the rgmd on a node that is booted in non-cluster mode. The rgmd will produce a core file, and in some cases it might cause the node to halt or reboot to avoid data corruption.
Solution:If the node is in non-cluster mode, boot it into cluster mode before attempting to start the rgmd. If the node is already in cluster mode, 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.
281732 The directory %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 directory does not exist. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
281775 Telemetry data service stop method returned with error %s
Description:The telemetry data service could not stop for an unknown reason.
Solution:This message is informational; no user action needed.
281819 %s exited with error %s in step %s
Description:A ucmm step execution failed in the indicated step.
Solution:See /var/adm/messages for previous errors and report this problem if it occurs again during the next reconfiguration.
281954 Incorrect resource group properties for RAC framework resource group %s. Value of Maximum_primaries(%s) is not equal to number of nodes in nodelist(%s).
Description:The RAC framework resource group is a scalable resource group. The value of the Maximum_primaries and Desired_primaries properties should be set to the number of nodes specified in the Nodelist property. RAC framework will not function correctly without these values.
Solution:Specify correct values of the properties and reissue command. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.
282009 scf_service_add_pg 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.
282011 sigaddset(3C) failed while adding signal SIG%s to ignored signal set: error %s
Description:The rgmd_starter was unable to add a signal number to a signal set, because the sigaddset(3C) function failed. The messages contains the system error. The rgmd_starter cannot launch an rgmd daemon.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
282194 %s: sigdelset returned %d. Exiting.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available
282406 fork1 returned %d. Exiting.
Description:clexecd program has encountered a failed fork1(2) system call. The error message indicates the error number for the failure.
Solution:If the error number is 12 (ENOMEM), install more memory, increase swap space, or reduce peak memory consumption. If error number is something else, contact your authorized Sun service provider to determine whether a workaround or patch is available.
282508 INTERNAL ERROR: r_state_at_least: state <%s> (%d)
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
282527 Function: lofsmount - Non-global zones mount from %s to %s with options %s successful
Description:The mount of the directory into the root path of the non-global zone was successful.
Solution:No user action is required.
282827 Executable %s is not a regular file.
Description:HAStoragePlus found that the specified file was not a plain file but of different type (directory, symbolic link, etc.).
Solution:Usually, this means that an incorrect filename was given in one of the extension properties.
282980 liveCache %s was brought down outside of Sun Cluster. Sun Cluster will suspend monitoring for it until it is started up successfully again by the user.
Description:LiveCache fault monitor detects that liveCache was brought down by user intendedly outside of Sun Cluster. Sun Cluster will not take any action upon it until liveCache is started up successfully again by the user.
Solution:No user action is needed if the shutdown is intended. If not, start up liveCache again using LC10 or lcinit, so it can be under the monitoring of Sun Cluster.
283262 HA: rm_state_machine::service_suicide() not yet implemented
Description:Unimplemented feature was activated.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
283767 network is very slow.
Description:This means that the PNM daemon was not able to read data from the network - either the network is very slow or the resources on the node are dangerously low.
Solution:It is best to restart the PNM daemon. Send KILL (9) signal to cl_pnmd. PMF will restart it automatically. If the problem persists, restart the node with clnode evacuate and shutdown.
284150 Nodelist must contain two or more nodes.
Description:The nodelist resource group property must contain two or more Sun Cluster nodes.
Solution:Recreate the resource group with a nodelist that contains two or more Sun Cluster nodes.
284228 Prog <%s> failed to execute step <%s> - SLM error
Description:Resource group is under SC SLM control and an SLM error occurred. Some errors might be configuration errors. Check fed SLM errors for more details.
Solution:Move RG_SLM_type to manual and restart the resource group.
284702 Error parsing URI: %s (%s)
Description:There was an error parsing the URI for the reason given.
Solution:Fix the syntax of the URI.
284962 Validate - %s configuration directory %s does not exist
Description:The Samba resource could not validate that the Samba configuration directory exists.
Solution:Check that the correct pathname for the Samba configuration directory was entered when registering the Samba resource and that the configuration directory really exists.
285040 The application process tree has died and the action to be taken as determined by scds_fm_history is to failover. However the application is not being failed over because the failover_enabled extension property is set to false. The application is left as-is. Probe quitting ...
Description:The application is not being restarted because failover_enabled is set to false and the number of restarts has exceeded the retry_count. The probe is quitting because it does not have any application to monitor.
Solution:This is an informational message, no user action is needed.
285668 reservation warning(%s) - MHIOCSTATUS 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.
285836 No SUNW.qfs resources configured for this zone cluster.
Description:There are no SUNW.qfs resources configured for this zone cluster.
Solution:This is an informational message; no user action is needed.
286259 Incorrect resource group properties for RAC framework resource group %s. Value of Maximum_primaries(%s) is not equal to Desired_primaries(%s).
Description:The RAC framework resource group is a scalable resource group. It must be created with identical values for the Maximum_primaries and Desired_primaries properties. RAC framework will not function correctly without these values.
Solution:Specify correct values of the properties and reissue command. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.
286286 reservation fatal error(UNKNOWN) - get_control() failure
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.
286518 The mountpoint %s is not authorized for use in zone cluster
Description:The MountPointDir is not authorized for use in the zone cluster.
Solution:Use clzonecluster to add the mountpoint to zone cluster.
286807 clnt_tp_create_timed of program %s failed %s.
Description:HA-NFS fault monitor was not able to make an rpc connection to an nfs server.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
287111 Validate - RUN_NMBD=%s is invalid - specify YES or NO
Description:The Samba resource can run without nmbd, however you must specify the service when configuring the Samba resource
Solution:Specify either YES or NO for RUN_NMBD within /opt/SUNWscsmb/samba/util/samba_config
287174 Could not find complete_probe for sckrb5.
Description:The complete_probe file could not be found or is not executable.
Solution:Ensure that the file exists and is executable. By default the file can be found at /opt/SUNWsckrb5/bin/complete_probe.
287202 DB port is %s
Description:The monitor start method prints the port number configured.
Solution:This message is informational; no user action is needed.
287363 Failed to register CZMM callbacks: Unknown Error
Description:The cznetd daemon was unable to register for configuration callbacks.
Solution:These callbacks are used for enabling or disabling the private IP communication for zone cluster zones. So, this feature // will be unavailable. To recover, it may be necessary to reboot this node or the entire cluster. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
287579 Creation of the %s directory has failed: %s
Description:The cp(1) command has returned an error.
Solution:Investigate the cause of the failure and correct the condition prior to attempting this operation again.
287834 Stopping fault monitor: %s:<%s>:%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:No user action is required.
288058 Monitor for derby data service successfully started
Description:The data service monitor successfully started.
Solution:This message is informational; no user action is needed.
288423 Failed to retrieve the cluster information. Retrying...
Description:HAStoragePlus was not able to the cluster configuration, but it will retry automatically.
Solution:This is an informational message, no user action is needed.
288452 Error retrieving zone name; assuming global zone
Description:On a Solaris 10 system, a zone or the entire node is being shut down or rebooted. Before stopping the RGM service, a script is executed to evacuate resource groups from the zone. This script cannot determine which zone is being stopped, and assumes the entire node is being rebooted.
Solution:This message might indicate an internal error or misconfiguration of Sun Cluster software. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
288677 scf_transaction_start 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.
288687 fe_set_env_vars() failed for zoneadm for zone %s
Description:The rgmd daemon was unable to set up environment variables for executing zoneadm. The zone will stay up, but the rgmd will not attempt to start services on it.
Solution:Reboot the zone. 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.
288839 mount_client_impl::add_notify() failed to start filesystem replica for %s at mount point %s nodeid %s
Description:Filesystem availability may be lessened due to reduced component redundancy.
Solution:Check the device.
288900 internal error: invalid reply code
Description:The cl_apid encountered an invalid reply code in an sc_reply message.
Solution:This particular error should not cause problems with the CRNP service, but it might be indicative of other errors. 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.
289229 zc_member(%d): Failure in notifying membership subsystem that zone %s came up, exception <%s> thrown. Exiting.
Description:Failed to notify the cluster membership infrastructure that this zone (that is part of a zone cluster) came up. Support for this zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
289503 Unable to re-compute NFS resource list.
Description:The list of HA-NFS resources online on the node has gotten corrupted.
Solution:Make sure there is space available in /tmp. If the error is showing up despite that, reboot the node.
289910 Check_takeover - the check for remote MySQL connectivity is successful, it should be unsuccessful for the replicated object %s
Description:The check for the remote mysql connectivity successful, takeover not advisable.
Solution:Ensure that the remote MySQL databse is down for a takeover.
290718 Error: Can't start ${SERVER}.
Description:An attempt to start the rpc.fed server failed. This error will prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.
Solution: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.
290926 Successful validation.
Description:The validation of the configuration for the data service was successful.
Solution:No user action is required. This is an informational message.
291077 Invalid variable name in the Environment file %s. Ignoring %s
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 Lines starting with " VARIABLE is expected to be a valid Korn shell variable that starts with alphabet or "_" and contains alphanumerics and "_".
Solution:Please check the environment file and correct the syntax errors. Do not use export statement in environment file.
291245 Invalid type %d passed.
Description:An invalid value was passed for the program_type argument in the pmf routines.
Solution:This is a programming error. Verify the value specified for program_type argument and correct it. The valid types are: SCDS_PMF_TYPE_SVC: data service application SCDS_PMF_TYPE_MON: fault monitor SCDS_PMF_TYPE_OTHER: other
291342 validate_options: HA N1 Grid Service Provisioning System Remote Agent %s Option %s is not set
Description:A required option is not set in the start, stop, validate and probe command.
Solution:Set the specific option in the command.
291378 No Database probe script specified. Will Assume the Database is Running
Description:This is a informational messages. probing of the URL's set in the Server_url or the Monitor_uri_list failed. Before taking any action the WLS probe would make sure the DB is up (if a db_probe_script extension property is set). But, the Database probe script is not specified. The probe will assume that the DB is UP and will go ahead and take action on the WLS.
Solution:Make sure the DB is UP.
291625 CMM: Votecount changed from %d to %d for quorum device %d (%s).
Description:The votecount for the specified quorum device has been changed as indicated.
Solution:This is an informational message, no user action is needed.
291716 Error while executing siebenv.sh.
Description:There was an error while attempting to execute (source) the specified file. This may be due to improper permissions, or improper settings in this file.
Solution:Please verify that the file has correct permissions. If permissions are correct, verify all the settings in this file. Try to manually source this file in korn shell (". siebenv.sh"), and correct any errors.
292013 clcomm: UioBuf: uio was too fragmented - %d
Description:The system attempted to use a uio that had more than DEF_IOV_MAX fragments.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
292193 NFS daemon %s did not start. Will retry in 100 milliseconds.
Description:While attempting to start the specified NFS daemon, the daemon did not start.
Solution:This is an informational message. No user action is required. HA-NFS would attempt to correct the problem by restarting the daemon again. HA-NFS imposes a delay of 100 milliseconds between restart attempts.
293867 Failed to get handle for zone cluster membership of '%s'.
Description:A error occurred while retrieving the specified zone cluster membership.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
294380 problem waiting the deamon, read errno %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
294409 check_dhcp - Dhcpclient test exited with %s
Description:The dhcpclient test exited with a non-zero return code.
Solution:No user action is required. This is an informational message; an immediate failover is being requested.
294962 fatal: Error registering for zone state change notifications
Description:The rgmd or rpc.fed failed to register with sc_zonesd for zone state change notification. The node will be aborted.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified which is preventing this registration. Look for door-related or sc_zonesd-related errors. 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.
295075 Configuration file %s synchronization not required
Description:This is informational message. Configuration file specified in the message is synchronized with resource properties.
Solution:No user action is required.
295428 QUORUM_GENERIC: quorum_reserve error: reading registration keys on quorum device %s failed with error code %d.
Description:An error was encountered when reserving the specified quorum device. The registration keys could not be read from the quorum device, before attempting to reserve it. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
295456 Error: /var/run is not mounted; cannot start cl_eventlogd.
Description:The cl_eventlog init script found that /var/run is not mounted. Because cl_eventlogd requires /var/run for sysevent reception, cl_eventlogd will not be started.
Solution:Examine other syslog messages occurring at about the same time to see if the problem with /var/run 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.
295576 SCSLM ftruncate <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
295666 clcomm: setrlimit(RLIMIT_NOFILE): %s
Description:During cluster initialization within this user process, the setrlimit call failed with the specified error.
Solution:Read the man page for setrlimit for a more detailed description of the error.
295755 Derby data service start method returned with error %s
Description:The derby data service could not start for an unknown reason.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
295838 Listener %s started.
Description:Informational message. HA-Oracle successfully started Oracle listener.
Solution:No user action is required.
296046 INTERNAL ERROR: resource group <%s> is PENDING_BOOT or ERROR_STOP_FAILED or ON_PENDING_R_RESTART, but contains no resources
Description:The operator is attempting to delete the indicated resource group. Although the group is empty of resources, it was found to be in an unexpected state. This will cause the resource group deletion to fail.
Solution:Use clresourcegroup offline to switch the resource group offline on all nodes, then retry the deletion operation. 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 report the problem to your authorized Sun service provider.
296099 Function: validate - Zonebrand for zone %s is configured as lx, but the zone is configured as brand type %s.
Description:Zonebrand is set to "lx". But the Zone is not configured as brand type lx according to zonecfg info.
Solution:Review the components configuration file and make sure the variable Zonebrand defines "lx" only for a Zone that got really setup with brand type "lx".
296514 Internal Error: ORACLE_OWNER not set even after successful validation.
Description:An internal error occurred while attempting to save the name of the owner of the Oracle installation in a local file for use during shutdown of Oracle listener.
Solution:This message is informational. If the problem persists, report it to your Sun support representative.
297061 clcomm: can't get new reference
Description:An attempt was made to obtain a new reference on a revoked handler.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
297139 CCR: More than one data server has override flag set for the table %s. Using the table from node %s.
Description:The override flag for a table indicates that the CCR should use this copy as the final version when the cluster is coming up. In this case, the CCR detected multiple nodes having the override flag set for the indicated table. It chose the copy on the indicated node as the final version.
Solution:This is an informational message, no user action is needed.
297178 Error opening procfs control file <%s> for tag <%s>: %s
Description:The rpc.pmfd server was not able to open a procfs control file, and the system error is shown. The procfs control 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.
297286 The FilesystemCheckCommand extension property is set to %s. File system checks will however be skipped because the resource group %s is scalable.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
297325 The node portion of %s at position %d in property %s is not a valid node identifier or node name.
Description:An invalid node was specified for the named property. The position index, which starts at 0 for the first element in the list, indicates which element in the property list was invalid.
Solution:Specify a valid node instead.
297328 Successfully restarted resource group.
Description:This message indicates that the rgm restarted a resource group, as expected.
Solution:This is an informational message.
297493 Validate - Applications directory %s does not exist
Description:The Oracle E-Business Suite applications directory does not exist.
Solution:Check that the correct pathname was entered for the applications directory when registering the resource and that the directory exists.
297536 Could not host device service %s because this node is being shut down
Description:An attempt was made to start a device group on this node while the node was being shutdown.
Solution:If the node was not being shutdown during this time, or if the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
297717 Local HADB Management Agent is Waiting for other MAs to Join
Description:The management agent at host localhost is not ready to execute the operation, since it is about to do repository recovery.
Solution:Make sure that a majority of the management agents in the domain are running.
297867 (%s) t_bind: tli error: %s
Description:Call to t_bind() failed. The "t_bind" man page describes possible error codes. udlmctl will exit.
Solution: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.
297942 Oracle commands inaccessible. Forcing shutdown of Oracle listener by killing the listener process.
Description:The resource shutdown will attempt to kill the Oracle listener process. A graceful shutdown could not be attempted as Oracle commands are inaccessible, possibly due to the commands residing on a failover, global, or NAS file system on which the listener resource's dependency has not been set.
Solution:This message is informational. You must ensure that the resource comes online correctly on an alternate cluster node or on the same node after the Oracle commands become accessible again. If possible and supported, set the dependency of the listener resource on the file system resource.
298060 Invalid project name: %s
Description:Either the given project name doesn't exist, or root is not a valid user of the given project.
Solution:Check if the project name is valid and root is a valid user of that project.
298312 check_stdby: The database in %s is not running as a standby database, reload the primary and restart the standby database.
Description:The database is running as a primary database, but is configured to be a standby.
Solution:If you want to start the old primary database, reload the primary and restart the standby database.
298320 Command %s is too long.
Description:The command string passed to the function is too long.
Solution:Use a shorter command name or shorter path to the command.
298360 HA: exception %s (major=%d) from initialize_seq().
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.
298532 Script lccluster does not exist.
Description:Script 'lccluster' is not found under /sapdb/<livecache_Name>/db/sap/.
Solution:Follow the HA-liveCache installation guide to create 'lccluster'.
298562 Tcp_transport could not create tcp_rio_client reaper
Description:The replyio subsystem was unable to create this thread. 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.
298588 Invalid upgrade callback from version manager: version %d.%d higher than highest version
Description:Version manager delivered upgrade callback to rgmd about a new version that is higher than the highest version supported by rgmd.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
298679 Either extension property <Child_mon_level> is not defined, or an error occurred while retrieving this property. The default value of -1 is being used.
Description:Property Child_mon_level may not be defined in RTR file. Use the default value of -1.
Solution:No user action is needed.
298719 getrlimit: %s
Description:The rpc.pmfd or rpc.fed server was not able to get the limit of files open. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, 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.
298744 validate: %s is not set in the parameterfile %s but it is required
Description:The variable $Variable is not set in the parameter file $Filename.
Solution:set the variable in the file $Filename to a valid contents.
298776 scnetapp fatal error - Cannot read CCR table %s
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
298833 Validate - Group informix does not exist
Description:The group informix does not exist.
Solution:You must create the group informix.
298911 setrlimit: %s
Description:The rpc.pmfd server was not able to set the limit of files open. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, 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.
298997 Unexpected eventmask while performing: '%s' result %d revents %x
Description:clexecd program has encountered an error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
299114 Probe failed in the prenet start method.
Description:The disk set or disk group failed its availability check.
Solution:Verify the status of the disk set or disk group and perform maintenance if required. After confirming that the disk set or disk group is available, try to restart the resource.
299452 Validate - De-activating %s, by removing it
Description:The DHCP resource validates that /etc/rc3.d/S34dhcp is not active and achieves this by deleting/etc/rc3.d/S34dhcp.
Solution:No user action is needed. /etc/rc3.d/S34dhcp will be deleted.
299639 Failed to retrieve the property %s: %s. Will shutdown the WLS using sigkill
Description:This is an internal error. The property could not be retrieved. The WLS stop method however will go ahead and kill the WLS process.
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.
Message IDs 300000–399999
This section contains message IDs 300000–399999.
300397 resource %s property changed.
Description:This is a notification from the rgmd that a resource's property has been edited by the cluster administrator. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
300512 Failed to stop DNS; exiting UNSUCCESFUL
Description:The STOP method was unable to stop the application by sending it a SIGKILL.
Solution:Examine the /var/adm/messages to determine why the resource failed to stop. If problem persists, contact your Sun service representative.
300537 scvxvmlg error - lstat(%s) failed with errno %d
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
300705 Failed to look up the service group.
Description:Failed to look up the internal data structure during connection establishment.
Solution:The connection involved might be disconnected. If it happens repeatedly contact your authorized Sun service provider to determine whether a workaround or patch is available.
300777 reservation warning(%s) - Unable to open device %s, errno %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.
301092 file specified in ENVIRONMENT_FILE parameter %s does not exist.
Description:The 'Environment_File' property was set when configuring the resource. The file specified by the 'Environment_File' property may not exist. The file should be readable and specified with a fully qualified path.
Solution:Specify an existing file with a fully qualified file name when creating a resource.
301114 Command failed: /bin/rm -f %s/ppid/%s
Description:An attempt to remove the directory and all the files in the directory failed. This command is being executed as the user that is specified by the extension property DB_User.
Solution:No user action is required.
301149 %s: unable to create failfast object.
Description:The pmmd program was not able to register with failfast.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
301162 zc_rgm_halt for zone %s: Exception <%s> thrown while querying membership. Exiting.
Description:An exception was thrown when zc_rgm_halt queried for the membership of the zone cluster, and thus zc_rgm_halt failed to check whether the zone is part of the zone cluster membership or not. Hence zc_rgm_halt will not be able to evacuate resource groups for this zone which belongs to a zone cluster. Support for this zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
301573 clcomm: error in copying for cl_change_flow_settings
Description:The system failed a copy operation supporting a flow control state change.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
301603 fatal: cannot create any threads to handle switchback
Description:The rgmd daemon was unable to create a sufficient number of threads 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.
301635 clexecd: close returned %d. Exiting.
Description:clexecd program has encountered a failed thr_create(3THR) 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.
302286 Incorrect specification of tunable at line %d in file %s.
Description:The zone handler detected that key=value pair is not specified in appropriate manner.
Solution:Check the line number and ensure that tunables are kept in the format 'key'='value'.
302670 udlm_setup_port: fcntl: %d
Description:A server was not able to execute fnctl(). udlm exits and the node aborts and panics.
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.
303009 validate: EnvScript %s does not exist but it is required
Description:The environment script $Filename is set in the parameter file but does not exist.
Solution:set the variable EnvScript in the parameter file mentioned in option -N of the start, stop and probe command to a valid contents.
303231 mount_client_impl::remove_client() failed attempted RM change_repl_prov_status() to remove client, spec %s, name %s
Description:The system was unable to remove a PXFS replica on the node that this message was seen.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
303502 Logical changepw principal does not exist in %s.
Description:The logical host name associated with the "changepw" service principal does not exist in the /etc/krb5/kadm5.keytab file.
Solution:Create and/or add the "changepw/<logical host name>" service principal's keys in the /etc/krb5/kadm5.keytab file. Note: that the logical host name must be fully qualified.
303630 Cannot execute %s: %d.
Description:Failure in executing the command.
Solution:Check the syslog message for the command description. Check whether the system is low in memory or the process table is full and take appropriate action. Make sure that the executable exists.
303756 CMM: Unable to get reference to membership API object.
Description:An instance of the userland CMM encountered an internal initialization error. The userland CMM could not obtain a reference to the membership API object.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
303805 Cannot change the IPMP group on the local host.
Description:A different IPMP group for property NetIfList is specified in clreslogicalhostname command. The IPMP group on local node is set at resource creation time. Users may only update the value of property NetIfList for adding a IPMP group on a new node.
Solution:Rerun the clreslogicalhostname command with proper value for the NetIfList property.
304365 clcomm: Could not create any threads for pool %d
Description:The system creates server threads to support requests from other nodes in the cluster. The system could not create any server threads during system startup. This is caused by a lack of memory.
Solution:There are two solutions. Install more memory. Alternatively, take steps to reduce memory usage. Since the creation of server threads takes place during system startup, application memory usage is normally not a factor.
304749 Probe for resource sckrb5 successful.
Description:The complete or simple probe for the HA-KDC service has completed successfully.
Solution:This is for informational purposes only, no action is required.
304836 check_ids - Database Instance %s is down
Description:The Informix Server database is down.
Solution:No user action is required. Solaris Cluster will restart the Informix Server.
305163 Start of HADB database completed successfully.
Description:The resource was able to successfully start the HADB database.
Solution:This is an informational message, no user action is needed.
305298 cm_callback_impl abort_trans: exiting
Description:ucmm callback for abort transition 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.
305331 Sun Cluster is waiting for lock on device %s. Lock is currently held by %s for fsck/mount.
Description:Sun Cluster boot is waiting for the mentioned node to complete fsck/mount of a global filesystem and release the lock on a device.
Solution:Check the console of the specified cluster node to see if any of the nodes are waiting for a manual fsck to be done. If this is so, exiting the shell after performing the fsck will allow the boot of the other nodes to continue.
305895 ucmmd got invalid upgrade callback from version manager: version %d.%d higher than highest version
Description:Version manager delivered upgrade callback to ucmmd about a new version that is higher than the highest version supported by ucmmd.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
306407 Failed to stop Adaptive server.
Description:Sun Cluster HA for Sybase failed to stop using KILL signal.
Solution:Please examine whether any Sybase server processes are running on the server. Please manually shutdown the server.
306483 scf_transaction_property_change failed error %d: %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.
307195 clcomm: error in copying for cl_read_flow_settings
Description:The system failed a copy operation supporting flow control state reporting.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
307322 Unable to create thread. Exiting.
Description:clexecd program has encountered a failed thr_create(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.
307531 open: %s
Description:open failed for the specified reason. The specified 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.
307657 Oracle UDLM package is not installed. %s not found.
Description:Oracle UNIX Distributed Lock Manager (UDLM) is not properly installed on this node. The UDLM reconfiguration program could not locate the lock manager binary at the location indicated in the message. Oracle OPS/RAC will not be able to function on this node.
Solution:If you want to run OPS/RAC on this cluster node, verify installaton of ORCLudlm package. Refer to Oracle's documentation for installaton of Oracle UDLM.
307834 CCR: Invalid CCR table : %s cluster %s.
Description:CCR could not find a valid version of the indicated table on the nodes in the cluster.
Solution:There may be other related messages on the nodes where the failure occurred. They may help diagnose the problem. If the indicated table is unreadable due to disk failure, the root disk on that node needs to be replaced. If the table file is corrupted or missing, boot the cluster in -x mode to restore the indicated table from backup. The CCR tables are located at /etc/cluster/ccr/.
308100 Validate - Couldn't retrieve Samba version number
Description:The Samba resource tries to validate that an acceptable version of Samba is being deployed, however it was unable to retrieve the Samba version number.
Solution:Check that Samba has been installed correctly
308297 Directory %s, exported from filer %s, is not configured within Sun Cluster.
Description:The specified directory, which is exported from the specified NAS device, has not yet been configured with Sun Cluster.
Solution:Run the 'scnasdir' command to configure the directory with Sun Cluster and repeat the operation.
308378 Derby data service stop method returned with error %s
Description:The derby data service could not stop for an unknown reason.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
308814 CCR: Updating table %s failed to startup on node %s for cluster %s.
Description:The operation to update the indicated table failed to start on the indicated node.
Solution:There may be other related messages on the nodes where the failure occurred, which may help diagnose the problem. If the root disk failed, it needs to be replaced. If the indicated table was deleted by accident, boot the offending node(s) in -x mode to restore the indicated table from other nodes in the cluster. The CCR tables are located at /etc/cluster/ccr/. If the root disk is full, remove some unnecessary files to free up some space.
308975 Resource type "%s" does not exist.
Description:The SUNW.qfs resource type is not registered in the cluster.
Solution:Register the SUNW.qfs resource type, create the required instances of this resource type, and repeat the operation. 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.
309609 Failed to validate the accessibility of the adapters in the zone cluster.
Description:There is no adapter found on this system that is authorized to be used for this zone cluster.
Solution:Use the clzonecluster(1M) command to configure the adapters to be used for this zone cluster and run the command to create the resource.
309961 Error during reading the property from repository %s
Description:There was an error in reading the property of the SMF service instance from the repository
Solution:Check the SMF man page to know more about the error. Also make sure the basic SMF functionalities are working. Contact SUN vendor for more help.
310084 scal_initialize() call failed.
Description:There was an error in initializing.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
310098 The SUNW.wait_zc_boot resource can be configured in scalable resource group only.
Description:SUNW.wait_zc_boot resource is not configured in a scalable resource group.
Solution:Add this resource to a scalable resource group.
310555 CMM: Quorum device %d (%s) added; votecount = %d, bitmask of nodes with configured paths = 0x%llx.
Description:The specified quorum device with the specified votecount and configured paths bitmask has been added to the cluster. The quorum subsystem treats a quorum device in maintenance state as being removed from the cluster, so this message will be logged when a quorum device is taken out of maintenance state as well as when it is actually added to the cluster.
Solution:This is an informational message, no user action is needed.
310953 clnt_control of program %s failed %s.
Description:HA-NFS fault monitor failed to reset the retry timeout for retransmitting the rpc request.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
311129 Failed to retrieve IP address for %s
Description:Cluster cannot generate a callback for the RDS module. Operation of RDS sockets might be affected.
Solution:If Reliable Datagram Sockets (RDS) is used by applications running on this cluster, contact your Sun Microsystems service representative to determine if a workaround or patch is available.
311291 sema_post badchild: %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: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.
311505 The resource group %s containing the resource %s is suspended. This has blocked a resource %s attempt on %s
Description:The operation requested by scha_control is prevented because the resource group is suspended.
Solution:No user action is required. To enable automatic recovery actions, use 'clresourcegroup resume'
311644 fork_event depth: ct_pr_event_get_pid: %s
Description:The rpc.pmfd was unable to retrieve the pid from a contract event. The rpc.pmfd will continue to monitor the process, but the rpc.pmfd may have missed an event of interest.
Solution: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.
312053 Cannot execute %s: %s.
Description:Failure in executing the command.
Solution:Check the syslog message for the command description. Check whether the system is low in memory or the process table is full and take appropriate action. Make sure that the executable exists.
312124 Failed to establish socket's default destination: %s
Description:Default destination for a raw icmp socket could not be established.
Solution:If the error message string that is logged in this message does not offer any hint as to what the problem could be, contact your authorized Sun service provider.
312406 setproject call failed : %s
Description:The setproject call failed. Should never occur.
Solution:Verify project database. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
312826 The Skgxn Service which provides Oracle RAC support in the ucmmd daemon encountered a nonrecoverable error and must abort
Description:The Oracle RAC clustered database relies on the Skgxn Service provided by the ucmmd daemon for group membership services and will not function without it. The Skgxn Service has encountered a nonrecoverable error and could not provide service.
Solution:Save copies of /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log files from all of the nodes in the cluster. Check for and save any core files of the ucmmd daemon or operating system. Contact your authorized Sun service provider for assistance in diagnosing the problem. Please provide to them the saved files which are mentioned above.
313017 Membership : Failure in notifying membership subsystem that zone %s went down, exception <%s> thrown.
Description:Failed to notify the cluster membership infrastructure that a zone cluster node went down. Support for the zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
313500 Probe - Fatal: Can't determine Schedd pid file - %s/schedd/schedd.pid does not exist.
Description:The file ${qmaster_spool_dir}/schedd.pid was not found. ${qmaster_spool_dir}/schedd.pid is the second argument to the 'Shutdown' function. 'Shutdown' is called within the stop script of the sge_schedd resource.
Solution:Confirm the file 'schedd.pid' exists. Said file should be found in the respective spool directory of the daemon in question.
313506 stop_chi - WebSphere MQ Channel Initiator %s stopped
Description:The specified WebSphere MQ Channel Initiator has been stopped.
Solution:No user action is required. Informational message.
313510 SAP xserver is not available.
Description:SAP xserver is not running currently.
Solution:Informative message, no action is required.
313784 Admin Disable is been called. The stop method of the service will be called and outcome is unknown. For proper functioning of the res, continue by disabling the resource first.
Description:This message comes when user does "svcadm disable". Since manual "disabling" of a service is not encouraged once the service
Solution:Check for the validity and the states of resource and services. Contact SUN vendor for more help. T should not be a problem in normal operation of the delegated restarter.
313801 check_pgs: The host %s is not accessible, a failover will occur
Description:The address specified in the PGHOST variable is unavailable.
Solution:No user action is required. A failover will occur.
313867 Unknown step: %s
Description:Request to run an unknown udlm step.
Solution:No user action is required.
314033 Server still running. Sleeping for 5 sec.
Description:We are allowing pmon some time to finish its work and exit cleanly.
Solution:No user action is required.
314185 Switchover error (%s): cannot find clexecd
Description:The file system specified in the message could not be hosted on the node the message came from. Check to see if the user program "clexecd" is running on that node.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
314314 prog <%s> step <%s> terminated due to receipt of signal <%d>
Description:ucmmd step terminated due to receipt of a signal.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
314334 Falied to do lstat() on test-file %s : %s
Description:The lstat() operation on the test file for I/O operations failed. One possible cause of this error is that the test file has been deleted. The deletion of this file might be caused by malicious activity in your system.
Solution:Restart the ScalMountPoint resource.
314356 resource %s enabled.
Description:This is a notification from the rgmd that the operator has enabled a resource. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
314358 Command %s failed to complete. Return code is %d.
Description:The listed command failed to complete with the listed return code. The return code is from the script db_clear.
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.
314460 stop_pgs: Allow pmf to stop the remaining ssh-agent for the user %s
Description:It can not be determined which ssh agent is working for the user/database, it is now killed by PMF using the configured stop signal.
Solution:No user action is required.
314502 Resources of type ScalDeviceGroup and ScalMountPoint must only be configured for nodes in the global zone, or nodes in a zone cluster
Description:Resources of type ScalDeviceGroup and ScalMountPoint are supported only in the global zone or in zones that are members of a zone cluster.
Solution:This is an unsupported configuration. Reconfigure the cluster so that resources of type ScalDeviceGroup and ScalMountPoint are not in non-global zones unless the non-global zone is a member of a zone cluster.
315207 Failed to execute %s on %s. optval = %d
Description:Attempt to execute a command on a remote cluster node failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
315333 Function: stop_mysql - clrs disable for (%s) was unsuccessful
Description:The clrs disable of the MySQL replication resource was unsuccessful.
Solution:Examine the /var/adm/messages for the additional error messages and fix the root cause
315446 node id <%d> is out of range
Description:The low-level cluster machinery has encountered an error.
Solution:Look for other syslog messages occurring just before or after this one on the same node; they may provide a description of the error.
315699 mc_multi_openconn failed to open connection.
Description:Failed to allocate memory during connection establishment for an SCTP non-sticky service.
Solution:Install more memory, increase swap space, or reduce peak memory consumption.
315729 WARNING: Unable to get privatelink IP address for nodeid %d
Description:Call to get privatelink IP address for node failed.
Solution:Make sure entries in /etc/nsswitch.conf are correct to get information about this node.
316215 Process sapsocol is already running outside of Sun Cluster. Will terminate it now, and restart it under Sun Cluster.
Description:The SAP OS collector process is running outside of the control of Sun Cluster. HA-SAP will terminate it and restart it under the control of Sun Cluster.
Solution:Informational message. No user action is required.
316625 Timeout monitoring on method tag <%s> has been %s.
Description:The timeout monitoring on the running method is being suspended or resumed because a device group switchover has started or finished respectively.
Solution:This is just an informational message.
316649 pthread_rwlock_unlock err %d line %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
317213 in libsecurity for program %s (%lu); setnetconfig failed: %s
Description:The specified server was not able to initiate an rpc connection, because it could not get the network database handle. The server does not start. The rpc error message 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.
317928 dbmcli option (%s) is not 'db_warm' nor 'db_online'.
Description:The extension property in the message is set to an invalid value.
Solution:Change the value of the extension property to a valid value.
318011 in libsecurity for program %s (%lu); file registration failed for transport %s
Description:A server (rpc.pmfd, rpc.fed or rgmd) was not able to create the "cache" file to duplicate the rpcbind information. The server should still be able to receive requests from clients (using rpcbind). 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.
318313 monitor_check: set_env_vars() failed for resource <%s>, resource group <%s>, node <%s>
Description:During execution of a scha_control(1HA,3HA) function, the rgmd daemon was unable to set up environment variables for method execution, causing a MONITOR_CHECK method invocation to fail. This in turn will prevent the attempted failover of the resource group from its current master to a new master.
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.
319261 liveCache %s failed to start.
Description:liveCache started up with error.
Solution:Sun Cluster will fail over the liveCache resource to another available node. No user action is needed.
319374 Incoming argument size is zero.
Description:An internal error has occurred in the inter-process communication between rgmd and another clustering process. Other related error messages might precede or follow this one in the syslog output.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
319375 clexecd: wait_for_signals got NULL.
Description:clexecd problem encountered an error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
319413 Siebel server can be started only after Siebel database and Siebel gateway are running, and the scsblconfig file is correctly configured.
Description:This is a warning message indicating a problem in determining the status of Siebel database and/or the Siebel gateway.
Solution:Please verify that the scsblconfig file is correctly configured, and that the Siebel database and Siebel gateway are up before attempting to start the Siebel server.
319602 daemon started.
Description:The scdpmd is started.
Solution:No user action is required.
319737 The raw device to fsck is not specified in vfstab for mount point : %s.
Description:The 'device to fsck' field is missing from the vfstab entry for the specified mount point.
Solution:Add the 'device to fsck' field to the vfstab entry for the specified mount point and repeat the operation.
320970 Failed to retrieve the node id from the node name for node %s: %s.
Description:Self explanatory.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
321245 resource <%s> is disabled but not offline
Description:While attempting to execute an operator-requested enable or disable of a resource, the rgmd has found the indicated resource to have its Onoff_switch property set to DISABLED, yet the resource is not offline. This suggests corruption of the RGM's internal data and will cause the enable or disable action to fail.
Solution:This may indicate an internal error or bug in the rgmd. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
321832 Could not set the contract id to 0 in the repository
Description:Not able to set the desired values in the SMF repository.
Solution:Check the SMF man page to know more about the error. Also make sure the basic SMF functionalities are working. Contact your SUN vendor for more help.
321962 Command %s failed to complete. HA-SAP will continue to start SAP.
Description:The command to cleanipc failed to complete.
Solution:This is an internal error. No user action needed. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
321972 The resource groups containing SUNW.qfs resources brought offline successfully.
Description:This is a notification message that zone halt brought the SUNW.qfs resource groups offline successfully.
Solution:This is an informational message; no user action is needed.
322159 Error setting states inrepository: %s: %d
Description:Have problems in starting a communication with the SMF repository
Solution:Depending on the error, check the SMF man page. Contact your SUN vendor for help.
322252 %s failed to stop the application and returned with %d
Description:A command was run to stop the application but it failed with an error. Both the command and the error code are specified in the message.
Solution:Save the syslog and contact your authorized Sun service provider.
322323 INTERNAL ERROR in J2EE probe calling scds_fm_tcp_disconnect(): %s.
Description:The data service detected an internal error from scds.
Solution:Informational message. No user action is needed.
322797 Error registering provider '%s' with the framework.
Description:The device configuration system on this node has suffered an internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
322853 The device special file (%s) is not either character or block device.
Description:Self explanatory.
Solution:Specify either a character or a block device path.
322862 clcomm: error in copying for cl_read_threads_min
Description:The system failed a copy operation supporting flow control state reporting.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
322879 clcomm: Invalid copyargs: node %d pid %d
Description:The system does not support copy operations between the kernel and a user process when the specified node is not the local node.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
322895 exception %s raised while attempting to get running version of CMM.
Description:An exception occurred when retrieving the running version of CMM.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
322908 CMM: Failed to join the cluster: error = %d.
Description:The local node was unsuccessful in joining the cluster.
Solution:There may be other related messages on this node that may indicate the cause of this failure. Resolve the problem and reboot the node.
322920 Error unloading the EGC failfast module.
Description:The svc:/system/egc/failfast:default SMF service has failed to unload the EGC farm failfast module
Solution:Reboot the node.
323405 Error in informing the res group about the svc restart:%s
Description:When a service is restarted, the sc delegate restarter informs RGM about the restart of the resource using SCHA_RESOURCE_IS_RESTARTED scha control API. This message is displayed when this call cannot be made.
Solution:Check for the validity and the states of resource and services. Contact your SUN vendor for more help. This should not be a problem in normal operation of the delegated restarter.
323592 Validation failed. CRS is not up. Please start it up before attempting to create proxy resource.
Description:Creation of a resource of type SUNW.scalable_rac_server_proxy failed because CRS is not up.
Solution:Bring up CRS before attempting to create a resource of the SUNW.scalable_rac_server_proxy resource type. If the problem persists, contact your Sun support representative for further assistance.
323640 open64 while setting up process template: %s
Description:The libclcontract code was unable to open a file in the /system/contract/process/ directory. Consequently, the process that is using libclcontract was unable to launch the requested process under its control.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
323873 Resource "%s" disabled.
Description:This ScalMountPoint resource was successfully disabled. This message is an informational message.
Solution:No user action is required.
324478 (%s): Error %d from read
Description:An error was encountered in the clexecd program while reading the data from the worker process.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
324924 in libsecurity contacting program %s (%lu): could not copy host name
Description:A client was not able to make an rpc connection to the specified server because the host name could not be saved. This problem can occur if the machine has low memory. An error message is output to syslog.
Solution:Determine if the host is low on memory. If not, save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
325032 qdmd: Quorum device type variable for type %s not found
Description:The quorum device monitoring daemon encountered an error while fetching device type information for the indicated quorum device type.
Solution:Contact service support.
325322 clcomm: error in copying for state_resource_pool
Description:The system failed a copy operation supporting statistics reporting.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
325482 File %s is not owned by group (GID) %d
Description:The file is not owned by the gid which is listed in the message.
Solution:Set the permissions on the file so that it is owned by the gid which is listed in the message.
325530 Creation of the shutdown file %s has failed: %s
Description:The cp(1) command has returned an error.
Solution:Investigate the cause of the failure and correct the condition prior to attempting this operation again.
326023 reservation warning(%s) - MHIOCGRP_PREEMPTANDABORT error in MHIOCGRP_INKEYS, error %d
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.
326030 Local mountpoint %s must begin with / in local zone '%s'.
Description:The specified mount point in local zone is not an absolute path. An absolute path must start with slash(/).
Solution:Correct the mount point path value so that it is absolute path and repeat the operation.
326363 Function: stop_sczbt - Logical interface %s:%s placed into the global zone
Description:The interface of the associated logical host is placed back into the global zone by the stop command of the sczbt component.
Solution:No user action is required.
326528 Nonexistent Broker_name (%s).
Description:The broker name provided in the extension property Broker_Name does not exist.
Solution:Check that a broker instance exists for the supplied broker name. It should match the broker name portion of the path in Confdir_list.
326636 The profile for SAP %s instance %s does not exist
Description:The check for SAP profile failed. The start up of sap instance requires the profile to be present.
Solution:Make sure the sap profile is present under /usr/sap/SAPSID/SYS/profile/ directory.
327057 SharedAddress stopped.
Description:The stop method is completed and the resource is stopped.
Solution:This is informational message. No user action required.
327132 Validate - Couldn't retrieve faultmonitor-user <%s> from the nameservice
Description:The Samba resource could not validate that the fault monitor userid exists.
Solution:Check that the correct fault monitor userid was used when registering the Samba resource and that the userid really exists.
327302 reservation fatal error(%s) - lock not specified
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.
327339 unable to create file %s errno %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
327353 Global device path %s is not recognized as a device group or a device special file.
Description:Self explanatory.
Solution:Check that the specified global device path is valid.
327549 Stop of HADB node %d did not complete.
Description:The resource was unable to successfully run the hadbm startnode command because it was unable to execute the program or the hadbm command received a signal.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.
328113 %s logical interface configuration operation failed with <%d>.
Description:An attempt to bring a network interface up or down has failed with the indicated error, while attempting to bring an IP address resource (of type LogicalHostname or SharedAddress) online or offline. Additional related failure messages are likely to be found following this one in the syslog output.
Solution:Check the configuration of network resources using the "clresourcegroup show -v +" command, and make any necessary corrections to the network configuration.
328580 rgmd died on node %s
Description:An internode communication failed because the rgmd died on another node. To avoid data corruption, the failfast mechanism will cause that node to halt or reboot.
Solution:No user action is required. The cluster will reconfigure automatically. Examine syslog output on the rebooted node to determine the cause of node death. The syslog output might indicate further remedial actions.
328675 The mount point property of file system '%s' in pool '%s' is set to 'legacy', which is not supported by HAStoragePlus.
Description:Self explanatory. HAStoragePlus does not support Zettabyte File Systems (ZFS) as Failover File Systems (FFS) that have the mountpoint property set to 'legacy'.
Solution:Set the mountpoint property for the specified file system to 'default'.
328779 Probe for J2EE engine timed out in scds_fm_tcp_connect().
Description:The data service timed out while connecting to the J2EE engine port.
Solution:Informational message. No user action is needed.
329039 Cannot access file %s/config.xml or %s/config/config.xml: %s
Description:The config.xml file does not exist either in the <domain> or <domain>/config directory.
Solution:Make sure if config.xml file is present in the <domain> or <domain>/config directory and also make sure if proper permissions are set for the file.
329286 (%s) instead of UDLM_ACK got a %d
Description:Did not receive an acknowledgement from udlm as was expected.
Solution:No user action is required.
329429 reservation fatal error(%s) - host_name not specified
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.
329616 svc_probe used entire timeout of %d seconds during connect operation and exceeded the timeout by %d seconds. Attempting disconnect with timeout %d
Description:The probe timed out connecting to the application.
Solution:If the problem persists investigate why the application is responding slowly or if the Probe_timeout property needs to be increased.
330182 Internal error: default value missing for resource property
Description:A non-fatal internal error has occurred in the RGM.
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.
330505 start_ssh_agent: The start of the ssh-agent was unsuccessful
Description:The ssh-agent is not startable for the given user
Solution:Determine and fix the root cause by running the ssh-agent manually as the target user
330526 CMM: Number of steps specified in registering callback = %d; should be <= %d.
Description:The number of steps specified during registering a CMM callback exceeds the allowable maximum. This is an internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
330530 Failed to retrieve the resource property %s of resource %s: %s.
Description:There was a failure while retrieving a property of a resource. The names of the resource and the property are both provided in the error message. The reason that the error occurred is also provided in the message.
Solution:The operation will be retried after some time. But there might be a delay in failing over some HA-NFS resources. If this message is logged repeatedly, save a copy of the syslog and contact your authorized Sun service provider.
330565 clcomm: solaris xdoor: Got zoneid %d instead of %d
Description:Zone information that has been passed does not match the client credentials.
Solution:Someone has tampered with Sun cluster code. This is a security violation. Shut down the identified zone.
330686 Function: validate - Non-global zones mountpoint %s does not exist
Description:The directory used as a mountpoint in the non-global zone is missing.
Solution:Create the mountpoint in the non-global zone.
330700 Cannot read template file (%s).
Description:Template file name was passed to the function for synchronizing the configuration file. Unable to locate the file indicated in he message. Unable to store property value of resource to configuration file.
Solution:Verify installation of Sun Cluster support packages for Oracle RAC. If the problem persists, save the contents of /var/adm/messages and contact your Sun service representative.
330722 The derby data service is not already running
Description:Trying to stop the derby data service when it is not running.
Solution:This message is informational; no user action is needed.
330772 DB_password_file must be set when Auto_recovery is set to true.
Description:When auto_recovery is set to true the db_password_file extension property must be set to a file that can be passed as the value to the hadbm command's --dbpasswordfile argument.
Solution:Retry the resource creation and provide a value for the db_password_file extension property.
331074 mc_multi_openconn failed to open bindtab connection.
Description:Failed to allocate memory during connection establishment for an SCTP sticky service.
Solution:Install more memory, increase swap space, or reduce peak memory consumption.
331221 CMM: Max detection delay specified is %ld which is larger than the max allowed %ld.
Description:The maximum of the node down detection delays is larger than the allowable maximum. The maximum allowed will be used as the actual maximum in this case.
Solution:This is an informational message, no user action is needed.
331301 Stop - can't determine Qmaster Spool dir
Description:The qmaster spool directory could not be determined, using the 'QmasterSpoolDir' function.
Solution:Use the command 'qconf -sconf' to determine the value of 'qmaster_spool_dir'. Update/correct the value if necessary using 'qconf -mconf'.
331325 sigprocmask: %s
Description:The rpc.pmfd server was not able to set its signal mask. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
331879 Function: validate - ServiceProbeCommand (%s) not a fully qualified path.
Description:The command specified for variable ServiceProbeCommand 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 ServiceProbeCommand, 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.
332256 Validate - winbind is not defined in %s in the passwd section
Description:Winbinbd is missing from the passwd section in /etc/nsswitch.conf
Solution:Enter winbind within the passwd section in /etc/nsswitch.conf.
333069 Failed to retrieve nodeid for %s.
Description:The nodeid for the given name could not be determined.
Solution:Make sure that the name given is a valid node identifier or node name.
333163 Malformed %s group specification %s.
Description:Failed to retrieve the ipmp information. The given IPMP group specification is invalid.
Solution:Check whether the IPMP group specification is in the form of ipmpgroup@nodename. If not, recreate the resource with the properly formatted group information.
333387 INTERNAL ERROR: starting_iter_deps_list: meth type <%d>
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
333428 Error getting handle tolibvxvm_get_dginfo
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.
333622 Property %s can be changed only while ucmmd is not running on the node.
Description:This property can be changed only while ucmmd is not running on the node. The volume manager processes on all the nodes must use identical value of this property for proper functioning on the cluster.
Solution:Change the RAC framework resource group to unmanaged state. Reboot all the nodes that can run RAC framework and modify the property.
333752 scha_control() returned error %d for %s in %s.
Description:The data service detected an internal error from scds.
Solution:Informational message. No user action is needed.
333874 failfastd: sigdelset returned %d. Exiting.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available
333878 fatal: Unable to get the cluster configuration (%s).
Description:A call to an internal library to get the cluster configuration unexpectedly failed. RGMD will exit causing the node to reboot.
Solution:Report the problem to your authorized Sun service provider.
334268 CCR: Can't read CCR metadata for cluster %s.
Description:Reading the CCR metadata failed on this node during the CCR data server initialization.
Solution:There may be other related messages on this node, which may help diagnose the problem. For example: If the root disk on the afflicted node has failed, then it needs to be replaced. If the cluster repository is corrupted, then boot this node in -x mode to restore the cluster repository from backup or other nodes in the cluster. The cluster repository is located at /etc/cluster/ccr/. Contact your authorized Sun service provider for assistance.
334412 Telemetry data service monitor check method failed
Description:The monitor program of the telemetry data service detected an error. The cause of the error is given in some error messages displayed before this one.
Solution:Check if there are other error messages before this one, and contact your authorized Sun service provider to determine whether a workaround or patch is available.
334697 Failed to retrieve the cluster property %s: %s.
Description:The query for a property 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.
334724 There should be one Network Resource in this resource group.
Description:There must be only one Failover IP address resource in this resource group. The Failover host for which the Node agents are configured must be created in this resource group.
Solution:Create the Failover host resource, on which the Node Agent and the Application Server instances are configured, in this resource group.
334965 Error writing configuration file %s.
Description:An error occurred when attempting to write the configuration file.
Solution:Investigate the cause of the failure and correct the condition prior to attempting this operation again.
334992 clutil: Adding deferred task after threadpool shutdown id %s
Description:During shutdown this operation is not allowed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
335206 Failed to get host names from the resource.
Description:Retrieving the IP addresses from the network resources from this resource group has failed.
Solution:Internal error or API call failure might be the reasons. Check the error messages that occurred just before this message. If there is internal error, contact your authorized Sun service provider. For API call failure, check the syslog messages from other components. For the resource name and resource group name, check the syslog tag.
335363 cl_execd: Error %d from open(/dev/zero). Exiting.
Description:cl_execd 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.
335468 Time allocated to stop development system is too small (less than 5 seconds).
Description:Time allocated to stop the development system is too small.
Solution:The time for stopping the development system is a percentage of the total Start_timeout. Increase the value for property Start_timeout or the value for property Dev_stop_pct.
335569 The quorum configuration task encountered a problem on node ${nodename}, manual configuration by using scsetup(1M) might be necessary
Description:The attempt to automatically configure quorum disks failed on one or more nodes. The last node to join the cluster is supposed to configure quorum. 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 configuring quorum.
Solution:Manually configure quorum disks and initialize the cluster by using clsetup or scsetup after all nodes have joined the cluster.
335587 The nonexistent mount point %s was created successfully with permissions %s and owned by the superuser.
Description:HAStoragePlus detected the mount point was missing, and created the mount point with the specified information.
Solution:This is an informational message, no user action is needed.
335591 Failed to retrieve the resource group property %s: %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.
335836 Failed to mount file-system %s on mountpoint %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.
336760 Could not restart or failover the derby data service
Description:Could not restart or failover the derby data service.
Solution:For more detailed error message, check the syslog messages. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
336860 read %d for %snum_ports
Description:Could not get information about the number of ports udlm uses from config file udlm.conf.
Solution:Check to make sure udlm.conf file exist and has entry for udlm.num_ports. If everything looks normal and the problem persists, contact your Sun service representative.
336868 Monitor for sckrb5 successfully started.
Description:The probe for HA-KDC has been started.
Solution:This message is for informational purposes only, no action is required.
337008 rgm_comm_impl::_unreferenced() called unexpectedly
Description:The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.
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.
337212 resource type %s removed.
Description:This is a notification from the rgmd that a resource type has been deleted. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
337736 %s: svc_run returned
Description:The RPC server exited unexpectedly.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
337957 Validation failed. The RAC framework resource %s that is specified in the RESOURCE_DEPENDENCIES property is not in the resource group that is specified by the resource group property RG_AFFINITIES.
Description:The resource being created or modified should be dependent upon the RAC framework resource in the RAC framework resource group.
Solution:If not already created, create the scalable resource group containing RAC framework resource and its associated resources. Specify this resource's dependency on the RAC framework by updating the RESOURCE_DEPENDENCIES property.
338067 This resource does not depend on any SUNW.HAStoragePlus resources. Proceeding with normal checks.
Description:The resource does not depend on any HAStoragePlus file systems. The validation will continue with it's other checks.
Solution:This message is informational; no user action is required.
338321 SCSLM <%s> zone <%s> corrupted project.cpu-shares
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
338839 clexecd: Could not create thread. Error: %d. Sleeping for %d seconds and retrying.
Description:clexecd program has encountered a failed thr_create() system call. The error message indicates the error number for the failure. It will retry the system call after specified time.
Solution:If the message is seen repeatedly, contact your authorized Sun service provider to determine whether a workaround or patch is available.
339119 scvxvmlg warning - chmod(%s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
339206 validate: An invalid option entered or
Description:-2 A wrong variable is set in the parameter file or a line does not start with
Solution:-2 Fix the parameter file.
339217 Function: validate - Zonebrand for zone %s is configured as %s. Valid values are native, lx, solaris8 and solaris9.
Description:Currently Zonebrand can only be set to "native", "lx" or "solaris8".
Solution:Review the components configuration file and make sure the variable Zonebrand defines either "native", "lx" or "solaris8".
339424 Could not host device service %s because this node is being removed from the list of eligible nodes for this service.
Description:A switchover/failover was attempted to a node that was being removed from the list of nodes that could host this device service.
Solution:This is an informational message, no user action is needed.
339444 Failed to stop fault-monitor : %s
Description:The fault monitor of this ScalMountPoint resource could not be stopped.
Solution:Manually kill the fault monitor process.
339590 Error (%s) when reading property %s.
Description:Unable to read property value using API. Property name is indicated in message. Syslog messages may give more information on errors in other modules.
Solution:Check syslog messages. Please report this problem.
339657 Issuing a restart request.
Description:This is informational message. We are above to call API function to request for restart. In case of failure, follow the syslog messages after this message.
Solution:No user action is needed.
339908 strtol: %s
Description:strtol failed. Should never occur. This might have failed if the return value could not be represented.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
339954 fatal: cannot create any threads to launch callback methods
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.
340157 huge address size %d
Description:Size of MAC address in acknowledgment of the bind request exceeds the maximum size allotted. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
340180 Prog <%s> step <%s>: quiesced.
Description:An internal error has occurred. The quiesce command, which is applicable only to resource groups, appears to have been applied to a ucmmd reconfiguration step.
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 authorized Sun service provider.
340211 monitor_check: getlocalhostname() failed for resource <%s>, resource group <%s>, node <%s>
Description:While attempting to process a scha_control(1HA,3HA) call, the rgmd failed in an attempt to obtain the hostname of the local node. This is considered a MONITOR_CHECK method failure. This in turn will prevent the attempted failover of the resource group from its current master to a new master.
Solution: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.
340287 idl_set_timestamp(): IDL Exception
Description:The rgmd has encountered an error that prevents the scha_control function from successfully setting a ping-pong time stamp, probably because of a node death or network failure.
Solution:Usually, no action is required. If another node is available, services will be restarted automatically.
340464 SCSLM fork1 error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
341205 Failed to replace bootcluster on the nodes of second partition
Description:During dual-partition upgrade, bootcluster component was not replaced on the nodes of the second partition. The dual-partition upgrade will continue to completion.
Solution:Do not boot any nodes in second partition into cluster mode until the dual-partition upgrade completes.
341259 Property %s can't start with a "/"
Description:The value of the property TargetFileSystem starts with a slash (/). However, the value of this property must not start with a slash.
Solution:Correct the value of the property and repeat the operation.
341539 fatal: Aborting node %s because method <%s> failed on resource <%s> and Failover_mode is set to HARD
Description:A STOP method has failed or timed out on a resource, and the Failover_mode property of that resource is set to HARD.
Solution:No user action is required. This is normal behavior of the RGM. With Failover_mode set to HARD, the rgmd reboots the indicated node or zone to force the resource group offline so that it can be switched onto another node. Other syslog messages that occurred just before this one might indicate the cause of the STOP method failure.
341719 Restarting daemon %s.
Description:HA-NFS is restarting the specified daemon.
Solution:No user action is required.
341801 No Port_list extension property configured in resource.
Description:The port_list extension property is not configured for a "network-aware" resource.
Solution:Configure the port_list extension property.
341804 Failed to retrieve information for user %s.
Description:Failed to retrieve information for the specified HADB MA user
Solution:Check if the proper HADB MA User ID is set or check if this user exists on all the nodes of the cluster.
342113 Invalid script name %s. It cannot contain any '/'.
Description:The script name should be just the script name, no path is needed.
Solution:Specify just the script name without any path.
342193 Attempt to mount %s failed on this node.
Description:In a scalable resource group, each node that is configured in the resource group attempts to mount the file system. Only one node can succeed in mounting the file system. The remaining nodes which fail to mount the file system issue this message.
Solution:This is an informational message. However, if no node succeeds in mounting the file system, check the failure message of each node. If you are unable to resolve the problem contact your authorized Sun service provider with copies of /var/adm/messages files on all nodes.
342336 clcomm: Pathend %p: path_down not allowed in state %d
Description:The system maintains state information about a path. A path_down operation is not allowed in this state.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
342472 Error while posting sysevent from %s: %s
Description:An internal error has occurred while posting a system event. System events are used for keeping an audit trail of cluster behavior. 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.
342597 sigaddset: %s
Description:-2 The rpc.fed server encountered an error with the sigemptyset function, and was not able to start. The message contains the system error.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
342922 User %s does not belong to the project %s: %s.
Description:The specified user does not belong to the project that is specified in the error message.
Solution:Use the projadd(1M) command to add the specified user to the specified project.
342950 start_ids - Informix Server (%s) started rc(%s)
Description:The specified Informix Server was started successfully.
Solution:No user action is required. Informational message.
343233 Failed to disable %s.
Description:The Solaris SMF service indicated above could not be disabled as required by Sun Cluster to make the service capable of restart/failover.
Solution:Try to manually disable the SMF service specified by the error message using the 'svcadm disable' command and retry the operation.
343271 getzonenamebyid: %s
Description:getzonenamebyid failed for the specified reason. The specified program will be terminated. 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.
343307 Could not open file %s: %s.
Description:System has failed to open the specified file.
Solution:Check whether the permissions are valid. This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action. For specific error information, check the syslog message.
343667 Function: validate: The LD_LIBRARY_PATH %s is not valid for this PostgreSQL installation
Description:The LD_LIBRARY_PATH is not valid to call the postgres binary.
Solution:Qualify the LD_LIBRARY_PATH in the parameter file until it is sufficient for the psql binary.
344059 RAC server %s probe successful.
Description:This message indicates that fault monitor has successfully probed the RAC server
Solution:No user action is required. This is informational message.
344291 clq_scsi3: Duplicate keys 0x%llx, found in registration key list of quorum device %s.
Description:Duplicate keys found on specified quorum device. This error occurs because of unexpected behavior from device driver or multipathing driver or device's firmware.
Solution:Please look for updates in device driver, multipathing driver or device firmware. If no updates are available please contact Sun device driver support team.
344368 scvxvmlg warning - chown(%s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
344512 Failed to create a temporary file during determining MDS node of '%s' file system : %s.
Description:The zone boot handler failed to create a temporary file.
Solution:Check the log messages to rectify the problem. If the problem persists, contact your authorized Sun service provider.
344614 Started SAP processes under PMF successfully.
Description:Informational message. SAP is being started under the control of Process Monitoring Facility (PMF).
Solution:No user action is required.
344672 Unable to open door descriptor %s
Description:A process running in a non-global zone was unable to communicate with the cluster framework in the global zone.
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.
345736 Unable to allocate memory
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.
346015 Function: check_sczbt - %s Milestone [%s] not online, try again in 5 seconds
Description:The milestone is not online or degraded. The state is checked again in 5 seconds.
Solution:No user action is required.
346395 UNRECOVERABLE ERROR: Creation of %s failed with error code %s
Description:Creation of ${QL_TRANSFORM_CCR_FILE} failed with error code ${retval}.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
346439 Could not verify value of property %s for %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.
346831 Notice: not OK to join
Description:This is informational message. This message can be seen when ucmm reconfiguration is in progress on other cluster nodes. The operation will be retried.
Solution:This message is informational; no user action is needed.
346858 UPDATE operation successfully completed.
Description:An UPDATE operation has completed successfully.
Solution:No user action is required. Informational message.
347023 Could not run %s. User program did not execute cleanly.
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.
347091 resource type %s added.
Description:This is a notification from the rgmd that the operator has created a new resource type. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
348065 CCR: Lost quorum while starting to update table %s, cluster %s.
Description:The cluster lost quorum when CCR started to update the indicated table.
Solution:Reboot the cluster.
348240 clexecd: putmsg returned %d.
Description:clexecd program has encountered a failed putmsg(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.
348504 Error: Startup of ${SERVER} failed.
Description:An attempt to start the rpc.fed server failed. This error will prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.
Solution: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.
349041 RGM unblocked, returned from blocked invocation.
Description:The RGM has been unblocked. cluster file systems are available.
Solution:This is an informational message, no user action is needed.
349049 CCR reported invalid table %s; halting node
Description:The CCR reported to the rgmd that the CCR table specified is invalid or corrupted. The node will be halted to prevent further errors.
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.
349741 Command %s is not a regular file.
Description:The specified pathname, which was passed to a libdsdev routine such as scds_timerun or scds_pmf_start, does not refer to a regular file. This could be the result of 1) misconfiguring the name of a START or MONITOR_START method or other property, 2) a programming error made by the resource type developer, or 3) a problem with the specified pathname in the file system itself.
Solution:Ensure that the pathname refers to a regular, executable file.
349932 validate_options: %s Option %s not set
Description:The referenced script needs a mandatory option which got not set.
Solution:Verify the options upon registration for the referenced script and make sure all mandatory options got provided.
350574 Start of HADB database did not complete: %s.
Description:The resource was unable to successfully run the hadbm start command because it was unable to execute the program, or the hadbm command received a signal.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.
350783 set_ts_prio : Unable to get ff_admin_v
Description:The cl_execd program could not get a reference to the CORBA failfast server object.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
351887 Bulk registration failed
Description:The cl_apid was unable to perform the requested registration for the CRNP service.
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.
351983 Validate - can't determine path to Grid Engine utility binaries
Description:The Sun Grid Engine binary 'gethostname' was not found in ${SGE_ROOT}/utilbin/<arch>. 'gethostname' is used only representatively. If it is not found the other Sun Grid Engine utilities are presumed misplaced also.
Solution:Find 'gethostname' in the Sun Grid Engine installation. Make certain it is in a location conforming to ${SGE_ROOT}/utilbin/<arch>, where <arch> is the result of running ${SGE_ROOT}/util/arch.
352149 monitor_check: method <%s> failed on resource <%s> in resource group <%s> on node <%s>, exit code <%d>, time used: %d%% of timeout <%d seconds>
Description:In scha_control, monitor_check method of the resource failed on specific node.
Solution:No user action is required, this is normal phenomenon of scha_control, which launches the corresponding monitor_check method of the resource on all candidate nodes and looks for a healthy node which passes the test. If a healthy node is found, scha_control will let the node take over the resource group. Otherwise, scha_control will just exit early.
352218 WebSphere MQ Channel Initiator %s started
Description:The specified WebSphere MQ Channel Initiator has been started.
Solution:No user action is required. Informational message.
352271 %s: Unable to determine hostname. Error: %s
Description:The hostname of the cluster node could not be determined.
Solution:Check if the command was run prior to setting the hostname. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
352954 Resource (%s) not configured.
Description:This is an internal error. Resource name indicated in the message was passed to the function for synchronizing the configuration files. Unable to locate the resource.
Solution:If the problem persists, save the contents of /var/adm/messages and contact your Sun service representative.
353368 Unable to run %s: %s.
Description:The specified command was unable to run because of the specified reason.
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.
353467 %s: CCR exception for %s table
Description:The libscdpm could not perform an operation on the CCR table specified in the message.
Solution:Check if the table specified in the message is present in the Cluster Configuration Repository (CCR). The CCR is located in /etc/cluster/ccr. This error could happen because the table is corrupted, or because there is no space left on the root file system to make any updates to the table. This message will mean that the Disk Path Monitoring daemon cannot access the persistent information it maintains about disks and their monitoring status. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
353557 Filesystem (%s) is locked and cannot be frozen
Description:The file system has been locked with the _FIOLFS ioctl. It is necessary to perform an unlock _FIOLFS ioctl. The growfs(1M) or lockfs(1M) command may be responsible for this lock.
Solution:An _FIOLFS LOCKFS_ULOCK ioctl is required to unlock the file system.
353566 Error %d from start_failfast_server
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
353753 invalid mask in hosts list: %s
Description:The allow_hosts or deny_hosts for the CRNP service contained an invalid mask. This error may prevent the cl_apid from starting up.
Solution:Remove the offending IP address from the allow_hosts or deny_hosts property, or fix the mask.
353894 SCSLM write <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
354821 Attempting to start the fault monitor under process monitor facility.
Description:The function is going to request the PMF to start the fault monitor. If the request fails, refer to the syslog messages that appear after this message.
Solution:This is an informational message, no user action is required.
355663 Failed to post event %lld: %s
Description:The cl_eventd was unable to post an event to the sysevent queue locally, and will not retry.
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.
355950 HA: unknown invocation result status %d
Description:An invocation completed with an invalid result status.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
356795 CMM: Reconfiguration step %d was forced to return.
Description:One of the CMM reconfiguration step transitions failed, probably due to a problem on a remote node. A reconfiguration is forced assuming that the CMM will resolve the problem.
Solution:This is an informational message, no user action is needed.
356930 Property %s is empty. This property must be specified for scalable resources.
Description:The value of the specified property must not be empty for scalable resources.
Solution:Use clresource to specify a non-empty value for the property.
357117 reservation notice(%s) - MHIOCSTATUS success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action required.
357260 Could not stop derby data service monitor (resource: %s)
Description:The monitor program of the derby data service could not stop. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
357263 munmap: %s
Description:The rpc.pmfd server was not able to delete shared memory for a semaphore, possibly due to low memory, and the system error is shown. This is part of the cleanup after a client call, so the operation might have gone through. An error message is output to syslog.
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.
357511 reservation warning(%s) - MHIOCGRP_INKEYS 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.
357766 ping_retry out of bound. The number of retry must be between %d and %d: using the default value
Description:The scdpmd config file (/etc/cluster/scdpm/scdpmd.conf) has a bad ping_retry value. The default ping_retry value is used.
Solution:Fix the value of ping_retry in the config file.
357959 Found another active instance of ifconfig proxy server. Exiting ifconfig_serverd.
Description:The ifconfig server program found another active ifconfig program already in execution.
Solution:This is an information message. No user action is required.
358206 clcomm: solaris xdoor: Got zone cluster id %d instead of %d for zone %s
Description:Zone cluster id information that has been passed does not match the client credentials.
Solution:Someone has tampered with Sun cluster code. This is a security violation. Shut down the identified zone.
358404 Validation failed. PASSWORD missing in CONNECT_STRING
Description:PASSWORD is missing in the specified CONNECT_STRING. The format could be either 'username/password' or '/' (if operating system authentication is used).
Solution:Specify CONNECT_STRING in the specified format.
358533 Invalid protocol is specified in %s property.
Description:The specified system property does not have a valid protocol.
Solution:Using clnode, change the value of the property to use a valid protocol. For example: TCP, UDP.
358621 Misconfiguration of the RAC framework resource group. The UDLM resource is missing, while the Oracle UDLM package is installed.
Description:The Oracle UDLM resource is missing from the RAC framework resource group while the Oracle UDLM package (ORCLudlm) is installed.
Solution:Configure the RAC framework resource group to have only one SKGXN interface, either the Oracle UDLM or the Sun Cluster native and then start the resource group.
358861 validate: The Tomcat port is not set but it is required
Description:The Tomcat port is not set in the parameter file
Solution:Set the Tomcat Port in the parameter file.
359013 cl_execd: Unable to create thread in the worker process. Exiting.
Description:cl_execd program has encountered a failed thr_create(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.
359970 zc_rgm_halt for zone %s: Could not get hostname of this zone. Exiting.
Description:The zc_rgm_halt could not get the hostname of the zone going down. Hence zc_rgm_halt will not be able to evacuate resource groups for this zone which belongs to a zone cluster. Support for this zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
360300 Unable to determine Sun Cluster node for HADB node %d.
Description:The HADB database must be created using the hostnames of the Sun Cluster private interconnect, the hostname for the specified HADB node is not a private cluster hostname.
Solution:Recreate the HADB and specify cluster private interconnect hostnames.
360349 %s: sigemptyset(3C): %s
Description:The pmmd daemon was unable to initialize a signal set because the sigemptyset(3C) function failed. The message contains the system error. The pmmd daemon will not do the requested action.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
360363 Validation failed. Resource group property RG_AFFINITIES should specify a STRONG POSITIVE affinity (++) with the SCALABLE resource group containing the RAC framework resource.
Description:The resource being created or modified must belong to a resource group that has a strong positive affinity with the scalable resource group containing the RAC framework resource.
Solution:If not already created, create the scalable resource group containing the RAC framework resource and its associated resources. Specify a strong positive (++) affinity with the scalable resource group containing the RAC framework resource by using RG_AFFINITIES property of the resource group.
360600 Oracle UDLM package wrong instruction set architecture.
Description:Proper Oracle UNIX Distributed Lock Manager (UDLM) is not installed on this node. A 64 bit UDLM package should not be installed in 32 bit operating environment. Oracle OPS/RAC will not be able to function on this node.
Solution:Install ORCLudlm package that is appropriate in this operating environment. Refer to Oracle's documentation for installaton of Oracle UDLM.
360923 contract_open: %s
Description:The libclcontract code was unable to retrieve the status of the newly created process template. The libclcontract code will kill the newly forked process because the process using the libclcontract code is unable to monitor the forked process.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
360990 Service is already running. Cannot use PMF.
Description:The data service detected a running SAP instance. Webas_Use_Pmf is specified, thus the data service cannot start probing the instance.
Solution:Either set Webas_Use_Pmf to False, or stop the service.
361048 ERROR: rgm_run_state() returned non-zero while running boot methods
Description:The rgmd state machine has encountered an error on this node.
Solution:Look for preceding syslog messages on the same node, which may provide a description of the error.
361447 Failed to get the list of adapters for the zone cluster %s, error = %d
Description:There was a failure to get the list of adapters configured to be used for the zone cluster.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
361471 Stopping Oracle CRS using: "%s".
Description:This is to show the command that the CRS Framework used to stop Oracle CRS in the event that Oracle CRS does not stop.
Solution:No user action is required.
361880 None of the hostnames/IP addresses specified can be managed by 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.
362117 Config file: %s unknown variable name line %d
Description:Error in scdpmd config file (/etc/cluster/scdpm/scdpmd.conf).
Solution:Fix the config file.
362242 The asadmin list-node-agents command failed to run. Unable to communicate with the Domain Admin Server %s on port %d. The Probe method will wait for the Domain Admin Server to be UP before starting the Node Agents.
Description:Before Starting the Node Agents, the start method checks for the status of the Domain Admin Server. The Node Agents are started only if the Domain Admin Server is UP. This error indicates that the Domain Admin Server is not running. The resource will be brought online but the start method will not start the Node Agents. The probe will monitor the status of the Domain Admin Server and will start the Node Agents once the Domain Admin Server is accessible.
Solution:If the Domain Admin Server is also a Sun Cluster resource then set the resource dependency between the Node Agents resource and the Domain Admin Server resource. If the Domain Admin Server is not a Sun Cluster resource, ensure it is running.
362630 Failed to open the file %s : %s
Description:The zone boot handler failed to open the specified file.
Solution:Check for the possible reasons for open failure and reboot the node after rectify the problem.
362657 Error when sending response from child process: %m
Description:Error occurred when sending message from fault monitor child process. Child process will be stopped and restarted.
Solution:If error persists, then disable the fault monitor and report the problem.
363357 Failed to unregister callback for IPMP group %s with tag %s (request failed with %d).
Description:An unexpected error occurred while trying to communicate with the network monitoring daemon (cl_pnmd).
Solution:Make sure the network monitoring daemon (cl_pnmd) is running.
363696 Error: unable to bring Resource Group <%s> ONLINE, because the Resource Groups <%s> for which it has a strong positive affinity are not online.
Description:The rgmd is enforcing the strong positive affinities of the resource groups. This behavior is normal and expected.
Solution:No user action is required. If desired, use clresourcegroup to change the resource group affinities.
364188 Validation failed. Listener_name not set
Description:'Listener_name' property of the resource is not set. HA-Oracle will not be able to manage Oracle listener if Listener name is not set.
Solution:Specify correct 'Listener_name' when creating resource. If resource is already created, please update resource property.
364203 check_ids - Database Instance %s is restarting
Description:The Informix Server database is starting up.
Solution:No user action is required. Solaris Cluster will restart the Informix Server so that it is managed by Solaris Cluster.
364387 dl_attach: bad ACK header %u
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.
364510 The specified Oracle dba group id (%s) does not exist
Description:Group id of oracle dba does not exist.
Solution:Make sure /etc/nswitch.conf and /etc/group files are valid and have correct information to get the group id of dba.
364618 getzoneid() failed. Unable to verify privilege.
Description:The validate method for the SUNW.Event service was unable to query the zoneid of the zone where it was launched into.
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.
364735 No PMF tag registered for the telemetry data service monitor
Description:The monitor program of the telemetry data service does not seem to be registered with the PMF. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
364774 The entry in vfstab for mount point '%s' exceeds %d characters.
Description:The internal buffer size of the vfstab entry for the specified mount point has exceeded VFS_LINE_MAX characters.
Solution:Shorten the vfstab entry for that mount point so that the length of the entry does not exceed VFS_LINE_MAX characters. You can shorten the vfstab entry by reducing the length of, for example, the block device, character device, or mount point.
365287 Error detected while parsing -> %s
Description:This message shows the line that was being parsed when an error was detected.
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.
365747 Derby data service stop method completed successfully
Description:The derby data service stopped successfully.
Solution:This message is informational; no user action needed.
365980 Wrong number of parameters for check_properties
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
366225 Listener %s stopped successfully
Description:Informational message. HA-Oracle successfully stopped Oracle listener.
Solution:No user action is required.
366483 SAPDB parent kernel process was terminated.
Description:The SAPDB parent kernel process was not running on the system.
Solution:During normal operation, this error should not occurred, unless the process was terminated manually, or the SAPDB kernel process was terminated due to SAPDB kernel problem. Consult the SAPDB log file for additional information to determine whether the process was terminated abnormally.
366803 %s: Unable to set automatic MT mode.
Description:This program could not set automatic MT mode.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
367077 Failfast: timeout - unit "%s"%s"%s.
Description:A failfast client has encountered a timeout and is going to panic the node or zone.
Solution:There might be other related messages on this node that can help diagnose the problem. Resolve the problem and reboot the node or zone if the node or zone panic is unexpected.
367270 INTERNAL ERROR: Failed to create the path to the %s file.
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.
367417 Could not put the prop %s of svc %s, in the repository: %s
Description:Problem in creating memory space during resource management of SMF delegated restarter
Solution:Check the system memory usage
367864 svc_init failed.
Description:The rpc.pmfd server was not able to initialize server operation. This happens while the server is starting up, at boot time. The server does not come up, 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.
367880 Probe command '%s' timed out: %s.
Description:Probing with the specified command timed out.
Solution:Other syslog messages occurring just before this one might indicate the reason for the failure. You might consider increasing the timeout value for the method that generated the error.
368373 %s is locally mounted. Unmounting it.
Description:HAStoragePlus found the specified mount point mounted as a local file system. It will unmount it, as asked for.
Solution:This is an informational message, no user action is needed.
368456 Invalid global device path %s detected for mount point %s.
Description:The specified global device path is not valid.
Solution:Check the path and correct the entry with a valid global device path.
368529 Dual-partition upgrade state prevents booting into cluster mode.
Description:Dual-partition cluster upgrade is in progress. Until the upgrade is completed, you can boot the node only into noncluster mode.
Solution:Boot the node into noncluster mode (boot -x). Then continue with the upgrade.
368571 Validate - Faultmonitor-resource <%s> does not exist
Description:The Samba resource could not validate that the fault monitor resource exists.
Solution:Check that the Samba instance's smb.conf file has the fault monitor resource scmondir defined. Please refer to the data service documentation to determine how to do this.
368596 libsecurity: program %s (%lu); unexpected getnetconfigent error
Description:A client of the specified server was not able to initiate an rpc connection, because it could not get the network information. The pmfadm or scha command exits with error. 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.
368819 t_rcvudata in recv_request: %s
Description:Call to t_rcvudata() failed. The "t_rcvudata" man page describes possible error codes. udlm will exit and the node will abort.
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.
369460 udlm_send_reply %s: udp is null!
Description:Can not communicate with udlmctl because the address to send to is null.
Solution:No user action is required. The udlm will handle this error.
369570 Multiple ports specified in property %s.
Description:The validate method for the SUNW.Event service found the specified problem. Thus, the service could not be started.
Solution:Modify the specified property to fix the problem specified.
369728 Taking action specified in Custom_action_file.
Description:Fault monitor detected an error specified by the user in a custom action filer. This message indicates that the fault monitor is taking action as specified by the user for such an error.
Solution:This is an informational message.
370604 This resource depends on a HAStoragePlus resouce that is in a different Resource Group. This configuration is not supported.
Description:The resource depends on a HAStoragePlus resource that is configured in a different resource group. This configuration is not supported.
Solution:Please add this resource and the HAStoragePlus resource in the same resource group.
370750 The Failover_mode setting of %s for resource %s in resource group %s has blocked a resource %s attempt on %s
Description:The rgmd is enforcing the RESTART_ONLY or LOG_ONLY value for the Failover_mode system property. Those settings may prevent some operations initiated by scha_control.
Solution:No user action is required. If desired, use clresourcegroup to change the Failover_mode setting.
370949 created %d threads to launch resource callback methods; desired number = %d
Description:The rgmd daemon was unable to create the desired number of threads upon starting up. This is not a fatal error, but it might cause RGM reconfigurations to take longer because it will limit the number of tasks that the rgmd can perform concurrently.
Solution:Make sure that the hardware configuration meets documented minimum requirements. Examine other syslog messages on the same node to see if the cause of the problem can be determined.
371250 Failed to set this node as primary for service '%s'.
Description:There were problems while trying make this node primary for this service.
Solution:Retry the last service switchover operation.
371489 Validate - Informix Server (%s) validation was successful
Description:The Informix Server validation was successful.
Solution:No user action is required. Informational message.
371615 In J2EE probe, failed to find Content-Length: in %s.
Description:The reply from the J2EE engine did not contain a Content-Length: entry in the http header.
Solution:Informational message. No user action is needed.
371681 Derby data service monitor successfully stopped (resource: %s)
Description:The monitor program of the derby data service stopped successfully.
Solution:This message is informational; no user action needed.
372134 Volume (%s) of disk group (%s) has gone bad
Description:The volume is not accessible.
Solution:Determine whether the volume is in an error state. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
372460 Failed to take DNS out of PMF control; trying to send SIGKILL now
Description:Sun Cluster failed to stop restarting the application.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
372492 scvxvmlg error - found non device-node or non link %s, directory not removed
Description:The program responsible for maintaining the VxVM namespace had detected suspicious entries in the global device namespace.
Solution:The global device namespace should only contain diskgroup directories and volume device nodes for registered diskgroups. The specified path was not recognized as either of these and should be removed from the global device namespace.
372618 Unable to extract the primary source IP address from the SCTP Cookie chunk.
Description:Either the SCTP COOKIE-ACK packet does not contain a cookie in the right position or the cookie does not contain a primary client IP address.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
372887 HA: repl_mgr: exception occurred while invoking RMA
Description:An unrecoverable failure occurred in the HA framework.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
372920 Validate_sbp - MySQL replication resource is not specified in option %s
Description:The required mysql replication resource is not specified.
Solution:Make sure that the required resource is specified.
373148 The port portion of %s at position %d in property %s is not a valid port.
Description:The property named does not have a legal value. The position index, which starts at 0 for the first element in the list, indicates which element in the property list was invalid.
Solution:Assign the property a legal value.
373816 clcomm: copyinstr: max string length %d too long
Description:The system attempted to copy a string from user space to the kernel. The maximum string length exceeds length limit.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
374006 prog <%s> failed on step <%s> retcode <%d>
Description:ucmmd step failed on a step.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
374748 Membership : Could not create state machine thread for membership (%s).
Description:A thread required for membership 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.
374839 Failfast : Fair share class not configured in this system
Description:Fair share scheduling class is not configured in this system, but a task needs to run in fair share scheduling class.
Solution:Configure fair share priority class for the system.
375331 dl_bind: DL_BIND_ACK protocol error
Description:Could not bind to the physical device. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
375416 metaset -o returned (%d). %s not owner
Description:The node is not the owner of the metaset.
Solution:Determine why the node is not the owner of the metaset. Examine the output from metaset. Determine whether the SUNW.rac_framework resource and either the SUNW.rac_svm resource or the SUNW.rac_cvm resource are online.
375575 Devicegroup (%s) not healthy!
Description:The volume is not available.
Solution:Determine the status of the disk set or disk group and the volume. For Solaris Volume Manager for Sun Cluster volumes, run 'metastat -s'. For Veritas Volume Manager volumes, run 'vxprint'.
375584 Unexpected signal %d.
Description:The cl_eventlogd daemon has received a signal, possibly caused by an operator-initiated kill(1) command. The signal is ignored.
Solution:This message is informational only, and does not require user action.
375650 Function: val_parfile - %s not specified in %s, which is required
Description:The referenced necessary parameter is not mentioned in the parameter file.
Solution:Specify the parameter as a key value pair in the parameter file.
376111 Unable to compose %s path. Sending SIGKILL now.
Description:The STOP method was not able to construct the applications stop command. The STOP method will send SIGKILL to stop the application.
Solution:Other messages will indicate what the underlying problem was such as no memory or a bad configuration.
376118 Interface name %s too long
Description:Cluster cannot generate a callback for the RDS module. Operation of RDS sockets might be affected.
Solution:If Reliable Datagram Sockets (RDS) is used by applications running on this cluster, contact your Sun Microsystems service representative to determine if a workaround or patch is available.
376369 Invalid configuration. SUNWudlmr and SUNWudlm packages must be installed on this node when using the Oracle UDLM.
Description:The required SUNWudlm and SUNWudlmr packages must be installed when using the Oracle UDLM.
Solution:Install the SUNWudlm and SUNWudlmr packages from the distribution. If the problem persists, contact your Sun service representative for assistance in diagnosing and correcting the problem.
376596 Property "%s" should be of the form <filer name>:<absolute path to exported directory>
Description:The form of the TargetFileSystem property is incorrect. For an NFS file system that is exported from a NAS device, the value of the property TargetFileSystem must begin with the NAS device name, followed by a colon (:) and the full path to the directory that the device is exporting.
Solution:Correct the value of the property and repeat the operation.
376905 Failed to retrieve WLS extension properties. Will shutdown the WLS using sigkill
Description:Failed to retrieve the WLS extension properties that are needed to do a smooth shutdown. The WLS stop method however will go ahead and kill the WLS process.
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.
376974 Error in initialization; exiting.
Description:The cl_apid was unable to start up. There should be other error message with more detailed explanations of the specific problems.
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.
377035 The path name %s associated with the FilesystemCheckCommand extension property is not a regular file.
Description:HAStoragePlus found that the specified file was not a plain file, but of different type (directory, symbolic link, etc.).
Solution:Correct the value of the FilesystemCheckCommand extension property by specifying a regular executable.
377347 CMM: Node %s (nodeid = %ld) is up; new incarnation number = %ld.
Description:The specified node has come up and joined the cluster. A node is assigned a unique incarnation number each time it boots up.
Solution:This is an informational message, no user action is needed.
377483 Creation of resource <%s> failed because the inter-cluster offline-restart dependencies could not be set
Description:Resource creation failed due to specification of invalid inter cluster dependencies.
Solution:Check the remote cluster name or remote resource name and retry the same command.
377531 Stop saposcol under PMF times out.
Description:Stopping the SAP OS collector process under the control of Process Monitor facility times out. This might happen under heavy system load.
Solution:You might consider increase the stop time out value.
377807 ucmmd unable to register for upgrade callbacks with version manager: %s
Description:An exception was raised when ucmmd tried to register for upgrade callbacks with the Version Manager.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
377897 Successfully started the service.
Description:Informational message. SAP started up successfully.
Solution:No user action is required.
378220 Siebel gateway already running.
Description:Siebel gateway was not expected to be running. This may be due to the gateway having started outside Sun Cluster control.
Solution:Please shutdown the gateway instance manually, and retry the previous operation.
378360 Validate - DHCP directory %s does not exist
Description:The DHCP resource could not validate that the DHCP directory defined in the /etc/inet/dhcpsvc.conf file for the PATH variable exists.
Solution:Ensure that /etc/inet/dhcpsvc.conf has the correct entry for the PATH variable by configuring DHCP appropriately, i.e. as defined within the Sun Cluster Data Service for DHCP.
378427 prog <%s> step <%s> terminated due to receipt of signal
Description:The ucmmd step terminated due to receipt of a signal.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
378807 clexecd: %s: sigfillset returned %d. Exiting.
Description:clexecd program has encountered a failed sigfillset(3C) 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.
378872 %s operation failed : %s.
Description:Specified system operation could not complete successfully.
Solution:This is as an internal error. Contact your authorized Sun service provider with the following information. 1) Saved copy of /var/adm/messages file. 2) Output of "ifconfig -a" command.
379098 Request to mount QFS file systems returned successfully.
Description:This is a notification from the handler that the request to RGM to mount the shared qfs file systems returned without failure.
Solution:This is an informational message; no user action is needed.
379450 reservation fatal error(%s) - fenced_node not specified
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.
379568 Failed to resolve CCR directory from the Nameserver
Description:The pnm proxy daemon could not get a reference to the CCR.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
379627 ct_pr_event_get_ppid: %s
Description:The rpc.pmfd was unable to retrieve the parent pid from a contract event. The rpc.pmfd will continue to monitor the process, but the rpc.pmfd may have missed an event of interest.
Solution: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.
379820 INTERNAL ERROR in J2EE probe calling scds_fm_tcp_write(): %s.
Description:The data service could not write to the J2EE engine port.
Solution:Informational message. No user action is needed.
380088 clq_sq_disk: Preempted from quorum device %s.
Description:Unable to locate this node's registration key on the quorum device. This node might have been preempted by another node. Because this node was expelled from the cluster, the node now halts.
Solution:Correct the problem that caused the node to be expelled from the cluster. The most common cause is a network communication failure between this node and other members of the cluster. After completing repairs, reboot the node back into the cluster.
380317 Failed to verify that all IPMP groups are in a stable state. Assuming this node cannot respond to client requests.
Description:The state of the IPMP groups on the node could not be determined.
Solution:Make sure all adapters and cables are working. Look in the /var/adm/messages file for message from the network monitoring daemon (cl_pnmd).
380365 (%s) t_rcvudata, res %d, flag %d: tli error: %s
Description:Call to t_rcvudata() failed. The "t_sndudata" man page describes possible error codes. udlmctl will exit.
Solution: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.
380445 scds_pmf_stop() failed with error %s.
Description:Shutdown through PMF returned an error.
Solution:No user action needed.
380939 SCSLM scslm_init pthread_create error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
381244 in libsecurity mkdir of %s failed: %s
Description:The rpc.pmfd, rpc.fed or rgmd server was not able to create a directory to contain "cache" files for rpcbind information. The affected component should still be able to function by directly calling rpcbind.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
381386 Prog <%s> step <%s>: unkillable.
Description:The specified callback method for the specified resource became stuck in the kernel, and could not be killed with a SIGKILL. The UCMM reboots the node to prevent the stuck node from causing unavailability of the services provided by UCMM.
Solution:No user action is required. This is normal behavior of the UCMM. Other syslog messages that occurred just before this one might indicate the cause of the method failure.
381577 getzonenamebyid failed in security_svc_reg.
Description:The getzonenamebyid(3C) operation failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
382169 Share path name %s not absolute.
Description:A path specified in the dfstab file does not begin with "/"
Solution:Only absolute path names can be shared with HA-NFS.
382252 Share path %s: file system %s is not mounted.
Description:The specified file system, which contains the share path specified, is not currently mounted.
Solution:Correct the situation with the file system so that it gets mounted.
382343 %s: Not root.
Description:A user other than root attempted to run this program.
Solution:If this error occurred during normal operation, save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
382460 Failed to obtain SAM-FS constituent volumes from mount point %s: %s.
Description:HAStoragePlus was not able to determine the volumes that are part of this SAM-FS file system.
Solution:Check the SAM-FS file system configuration. If the problem persists, contact your authorized Sun service provider.
382554 Membership : Received a 'down' notification for local member component of membership (%s), that was already down.
Description:The membership subsystem received a notification saying that a local member component went down. But the membership subsystem already knew that the local member component is down. Normally, a notification about the local member component coming up should arrive before a notification that says that the local member component went down. (1) Either the local member component went down before it could tell membership subsystem that it has come up, or (2) the membership code has a bug.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
382666 cl_execd: Error %d from pipe
Description:cl_execd program has encountered a failed pipe(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.
382995 ioctl in negotiate_uid failed
Description:Call to ioctl() failed. The "ioctl" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
383040 Failed to map adapter %s to an IPMP group, error = %d
Description:There was an error while attempting to map an adapter to an IPMP group.
Solution:This is an informational message. No user action is required.
383045 dl_bind: bad ACK header %u
Description:An unexpected error occurred. The acknowledgment header for the bind request (to bind to the physical device) is bad. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
383264 Function: validate - %s configured with address %s, please remove the address using zonecfg
Description:There is an IP address conflict between the SUNW.LogicalHostname resource and the configured zone.
Solution:Remove the IP address from the zones configuration with the zonecfg command.
383583 Instance number <%s> does not consist of 2 numeric characters.
Description:The instance number specified is not a valid SAP instance number.
Solution:Specify a valid instance number.
383706 NULL value returned for the resource property %s.
Description:NULL value was specified for the extension property of the resource.
Solution:For the property name check the syslog message. Any of the following situations might have occurred. Different user action is needed for these different scenarios. 1) If a new resource is created or updated, check whether the value of the extension property is empty. If it is, provide a valid value by using clresource. 2) For all other cases, treat it as an Internal error. Contact your authorized Sun service provider.
383767 scha_cluster_close failed with %d
Description:Call to close the cluster information handle failed. The second part of the message gives the error code.
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.
384373 Failed to save old zpools.
Description:The online update of the HAStoragePlus resource is not successful because of failure in saving the old zpools that were present before updating the resource.
Solution:Check the syslog messages and try to resolve the problem. Try again to update the resource. If the problem persists, contact your authorized Sun service provider.
384549 CCR: Could not backup the CCR table %s errno = %d.
Description:The indicated error occurred while backing up indicated CCR table on this node. 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 file system on the indicated node is full. Other values of errno can be returned when the root disk has failed(EIO) or some of the CCR tables have been deleted outside the control of the cluster software(ENOENT).
Solution:There may be other related messages on this node, which may help diagnose the problem, for example: 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 CCR table was accidently deleted, then boot this node in -x mode to restore the indicated CCR table from other nodes in the cluster or backup. The CCR tables are located at /etc/cluster/ccr/. Contact your authorized Sun service provider for assistance.
384621 RDBMS probe successful
Description:This message indicates that Fault monitor has successfully probed the RDBMS server
Solution:No user action is required. This is informational message.
384629 Function: validate: Directory %s does not contain the PostgreSQL binaries
Description:The directory mentioned in the PGROOT variable does not contain the PostgreSQL binaries in its bin directory.
Solution:Provide the directory which does contain at least the PostgreSQL binaries in the path ./bin.
384651 Proxy monitor not running (%d)
Description:The Monitor of a resource of type SUNW.scalable_rac_server_proxy is not running.
Solution:No user action is required. Informational message.
385176 Ifconfig proxy : Unexpected signal, Exiting.
Description:The ifconfig proxy program got an unexpected signal and is exiting.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
385407 t_alloc (open_cmd_port) failed with errno%d
Description:Call to t_alloc() failed. The "t_alloc" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
385550 Can't setup binding entries from node %d for GIF node %d
Description:Failed to maintain client affinity for some sticky services running on the named server node due to a problem on the named GIF node. Connections from existing clients for those services might go to a different server node as a result.
Solution:If client affinity is a requirement for some of the sticky services, say due to data integrity reasons, switchover all global interfaces (GIFs) from the named GIF node to some other node.
385655 reservation fatal error(%s) - Unable to retrieve DID device information
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.
385803 Nodelist must contain an even number of nodes.
Description:The HADB resource must be configured to run on an even number of Sun Cluster nodes.
Solution:Recreate the resource group and specify an even number of Sun Cluster nodes in the nodelist.
385902 pmf_search_children: Error signaling <%s>: %s
Description:An error occurred while rpc.pmfd attempted to send a signal to one of the processes of the given tag. The reason for the failure is also given. The signal was sent to the process as a result of some event external to rpc.pmfd. rpc.pmfd "intercepted" the signal, and is trying to pass the signal on to the monitored process.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
385991 monitor_check: fe_method_full_name() failed for resource <%s>, resource group <%s>, node <%s>
Description:During execution of a scha_control(1HA,3HA) function, the rgmd daemon was unable to assemble the full method pathname for the MONITOR_CHECK method. This is considered a MONITOR_CHECK method failure. This in turn will prevent the attempted failover of the resource group from its current master to a new master.
Solution: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.
386072 chdir: %s
Description:The rpc.pmfd server was not able to change directory. 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.
386282 ccr_initialize failure
Description:An attempt to start the scdpmd failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
386327 Stop Startup script using pmfadm failed. tag %s error=%s
Description:The agent's attempt to stop a previous instance startup instruction that was issued to it failed.
Solution:Contact your Sun support representative for further assistance.
386333 SCSLM <%s> meth 0x%x with running 0x%x
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
387003 CCR: CCR metadata not found.
Description:The CCR is unable to locate its metadata.
Solution:Boot the offending node in -x mode to restore the indicated table from backup or other nodes in the cluster. The CCR tables are located at /etc/cluster/ccr/. Contact your authorized Sun service provider for assistance.
387232 resource %s monitor enabled.
Description:This is a notification from the rgmd that the operator has enabled monitoring on a resource. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
387288 clcomm: Path %s online
Description:A communication link has been established with another node.
Solution:N user action is required.
387572 File %s should be readable and writable by %s.
Description:A program required the specified file to be readable and writable by the specified user.
Solution:Set correct permissions for the specified file to allow the specified user to read it and write to it.
388195 scf_handle_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.
388330 Text server stopped.
Description:The Text server has been stopped by Sun Cluster HA for Sybase.
Solution:This is an informational message, no user action is needed.
388501 Error while unbinding 'ifconfig_proxy_server' in the name server. Exiting.
Description:The ifconfig proxy program could not register the corba object in the nameserver.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
388555 Usage: %s [-c|-u] -R <resource-name> -T <type-name> -G <group-name> [-r <sys_def_prop>=<value> ...] [-x <ext_prop>=<value> ...] [-Z <zone-name>]
Description:Incorrect arguments are passed to the callback method of a cluster data service agent.
Solution:This error might occur while developing and testing a new agent, if a method is manually invoked with incorrect command line arguments. If seen on a production cluster, this message indicates an internal error. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
388645 Failed to open the configuration file %s : %s.
Description:The zone handler failed to open the specified configuration file.
Solution:Check for the error message and rectify the problem.
389071 Validate - Group mqbrkrs does not exist
Description:The WebSphere MQ Broker resource failed to validate that the group mqbrkrs exists.
Solution:Ensure that the group mqbrkrs exists.
389221 could not open configuration file: %s
Description:The specified configuration file could not be opened.
Solution:Check if the configuration file exists and has correct permissions. If the problem persists, contact your Sun Service representative.
389231 clcomm: inbound_invo::cancel:_state is 0x%x
Description:The internal state describing the server side of a remote invocation is invalid when a cancel message arrives during processing of the remote invocation.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
389369 Validation failed. SYBASE ASE STOP_FILE %s is not executable.
Description:File specified in the STOP_FILE extension property is not an executable file.
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.
389516 NULL value returned for the extension property %s.
Description:NULL value was specified for the extension property of the resource.
Solution:For the property name check the syslog message. Any of the following situations might have occurred. Different user action is needed for these different scenarios. 1) If a new resource is created or updated, check whether the value of the extension property is empty. If it is, provide a valid value by using clresource. 2) For all other cases, treat it as an Internal error. Contact your authorized Sun service provider.
390130 Failed to allocate space for %s.
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.
390212 Core files in ${SCCOREDIR}: ${CORES_FILES}
Description:One of the daemon launched by /etc/init.d/bootcluster script has core dumped.
Solution:Provide core dumps to your authorized Sun service provider. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
390515 Function: validate - %s (%s) already in use on %s:%s for %s, please resolve this conflict
Description:The logical host is used in another zone already. A logical host can not be used in two zones at the same time.
Solution:Resolve the conflicting IP address configuration for your zones.
390782 lkcm_cfg: Unable to get new nodelist
Description:Error when reading nodelist.
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.
391177 Failed to open %s: %s.
Description:HA Storage Plus failed to open the specified file.
Solution:Check the system configuration. If the problem persists, contact your authorized Sun service provider.
391240 RAC server %s is not running. Manual intervention is required.
Description:The fault monitor for the RAC server instance has identified that the instance is no longer running. The fault monitor does NOT attempt to restart or failover the resource or resource group.
Solution:The cause of the instance failure should be investigated, and once rectified, the RAC server instance should be restarted.
391502 Database is still running after %d seconds. Selecting new Sun Cluster node to run the stop command.
Description:The database is still running but the resource on the Sun Cluster node that was selected to run the hadbm stop command is now offline, possibly because of an error while running the hadbm command. A different Sun Cluster node will be selected to run the hadbm stop command again.
Solution:This is an informational message, no user action is needed.
391738 (%s) bad poll revent: %x (hex)
Description:Call to poll() failed. The "poll" man page describes possible error codes. udlmctl will exit.
Solution: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.
392288 Unmounting the file systems is completed successfully.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
392732 No suitable adapter is authorized to be used with resource %s on zone cluster %s.
Description:There is no adapter found on this system that is authorized to be used for this zone cluster.
Solution:Use the clzonecluster(1M) command to configure the adapters to be used for this zone cluster and run the command to create the resource.
392782 Failed to retrieve the property %s for %s: %s.
Description:API operation has failed in retrieving the cluster property.
Solution:For property name, check the syslog message. For more details about API call failure, check the syslog messages from other components.
392998 Fault monitor probe response time exceeded timeout (%d secs). The timeout for subsequent probes will be temporarily increased by 10%%
Description:The time taken for the last fault monitor probe to complete was greater than the resource's configured probe timeout, so a timeout error occurred. The timeout for subsequent probes will be increased by 10% until the probe response time drops below 50% of the timeout, at which point the timeout will be reduced to it's configured value.
Solution:The database should be investigated for the cause of the slow response and the problem fixed, or the resource's probe timeout value increased accordingly.
393382 DNS successfully stopped
Description:The STOP method for DNS for was successful.
Solution:No user action is required.
393934 Stopping the adaptive server with wait option.
Description:The Sun Cluster HA for Sybase will attempt to shutdown the Sybase adaptive server using the wait option.
Solution:This is an informational message, no user action is needed.
393957 Failed to read mount point on local node
Description:During dual-partition upgrade in a live upgrade scenario, the mount point information is not present.
Solution:Refer to documentation about recovering from a failed dual-partition upgrade in a live upgrade scenario.
393960 sigaction failed in set_signal_handler
Description:The ucmmd has failed to initialize signal handlers by a call to sigaction(2). The error message indicates the reason for the failure. The ucmmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
Solution:Save a copy of the /var/adm/messages files on all nodes and of the ucmmd core. Contact your authorized Sun service provider for assistance in diagnosing the problem.
394325 Received notice that IPMP group %s has failed.
Description:The status of the named IPMP group has become degraded. If possible, the scalable resources currently running on this node with monitoring enabled will be relocated off of this node, if the IPMP group stays in a degraded state.
Solution:Check the status of the IPMP group on the node. Try to fix the adapters in the IPMP group.
394661 Failed to stop the Node Agent %s and the server instances with SIGKILL.
Description:The Stop method failed to stop the Node Agent and the Application Server instances even with SIGKILL.
Solution:Manually stop or kill the Node Agent and Application Server instances.
395008 Error reading stopstate file.
Description:The stopstate file could not be opened and read.
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.
395353 Failed to check whether the resource is a network address resource.
Description:While retrieving the IP addresses from the network resources, the attempt to check whether the resource is a network resource or not has failed.
Solution:Internal error or API call failure might be the reasons. Check the error messages that occurred just before this message. If there is internal error, contact your authorized Sun service provider. For API call failure, check the syslog messages from other components.
395359 Function: validate: The Environment script %s is not a valid c shell script
Description:The environment script specified in the parameter file needs to be a valid c shell script, because the login shell of the PostgreSQL user is c shell compliant.
Solution:Fix the environment script until it passes csh -n scriptname.
395492 qdmd: ORB initialization failed. Exiting.
Description:The quorum device monitoring daemon received an error during ORB initialization.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
396490 Misconfiguration of the RAC framework resource group. The UDLM resource is present, while the Oracle UDLM package is not installed.
Description:The Oracle UDLM resource is configured in the RAC framework resource group while the Oracle UDLM package (ORCLudlm) is not installed.
Solution:Configure the RAC framework resource group to have only one SKGXN interface, either the Oracle UDLM or the Sun Cluster native and then start the resource group.
396509 Function: validate - The host %s is not configured UP on the hosts adapters
Description:The host specified in the PGHOST variable is not configured up on the hosts adapters.
Solution:Fix either the network configuration or the PGHOST variable
396727 Attempting to check for existence of %s pid %d resulted in error: %s.
Description:HA-NFS fault monitor attempted to check the status of the specified process but failed. The specific cause of the error is logged.
Solution:No user action is required. HA-NFS fault monitor would ignore this error and would attempt this operation at a later time. If this error persists, check to see if the system is lacking the required resources (memory and swap) and add or free resources if required. Reboot the node if the error persists.
396901 clq_netapp: quorum open error: No %s data for quorum device was found in CCR --- quorum device %s will be unavailable.
Description:The configuration information obtained from the CCR for the NetApp NAS device was missing one or more items of required data. The device will not be available.
Solution:Remove the device using scconf, and try adding it again.
396947 clq_scsi3: One of the key 0x%llx was found to be invalid value on quorum device %s.
Description:One of the registration keys is found to be invalid value on specified quorum device. This error occurs because of unexpected behavior from device driver or multipathing driver or device's firmware.
Solution:Unconfigure the quorum device and scrub it and then configure it back as a quorum device. Please also look for updates to the device driver, multipathing driver or device firmware. If no updates are available, please contact Sun device driver support team.
397020 Unix DLM abort failed
Description:Failed to abort UNIX dlm. This is an error that can be ignored.
Solution:No user action is required.
397340 Monitor initialization error. Unable to open resource: %s Group: %s: error %d
Description:Error occurred in monitor initialization. Monitor is unable to get resource information using API calls.
Solution:Check syslog messages for errors logged from other system modules. Stop and start fault monitor. If error persists then disable fault monitor and report the problem.
397371 'dbmcli -d <LC_NAME> -n <logical host name> db_state' timed out.
Description:The SAP utility listed timed out.
Solution:Make sure the logical host name resource is online.
397421 fork error: %s
Description:The libclcontract code was not able to fork the specified process. The message contains the system error. The server process (which is using libclcontract) 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 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.
397940 INTERNAL ERROR in J2EE probe calling scds_fm_tcp_read(): %s.
Description:The data service could not read the J2EE probe reply.
Solution:Informational message. No user action is needed.
399037 mc_closeconn failed to close connection
Description:The system has run out of resources that is required to process connection terminations for a scalable service.
Solution:If cluster networking is required, add more resources (most probably, memory) and reboot.
399172 first probe for N1 Grid Service Provisioning System Tomcat was unsuccessful, try again in 5 seconds
Description:The first probe for the Tomcat will be rescheduled in 5 seconds
Solution:No user action is required.
399216 clexecd: Got an unexpected signal %d in process %s (pid=%d, ppid=%d)
Description:clexecd program got a signal indicated in the error message.
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.
399477 Function: validate_probe - Directory for the parameter file %s does not exist any more, a failover will occur
Description:The file specified in the PARFILE variable does not exist any more.
Solution:Create the directory and restore the parameter file. None if it was a lost mount.
399548 %s failed with exit code %d.
Description:The specified command returned the specified exit code.
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.
399552 "pmfctl -S": Error suspending pid %d for tag <%s>: %d
Description:An error occurred while rpc.pmfd attempted to suspend the monitoring of the indicated pid, possibly because the indicated pid has exited while attempting to suspend its monitoring.
Solution:Check if the indicated pid has exited, if this is not the case, Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
399753 CCR: CCR data server failed to register with CCR transaction manager.
Description:The CCR data server on this node failed to join the cluster, and can only serve readonly requests.
Solution:There may be other related CCR messages on this and other nodes in the cluster, which may help diagnose the problem. It may be necessary to reboot this node or the entire cluster.
Message IDs 400000–499999
This section contains message IDs 400000–499999.
400164 SCSLM <%s> pool_put_property <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
400225 Function: validate: Return code for failed connections %s is not numeric
Description:The value for the NOCONRET variable contains a non numeric character.
Solution:Fix the NOCONRET variable in the parameter file.
400579 in libsecurity for program %s (%lu); could not register on any transport in /etc/netconfig
Description:A server (rpc.pmfd, rpc.fed or rgmd) was not able to register with rpcbind and not able to create the "cache" files for any transport. 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.
400592 Unix DLM is asking for a reconfiguration to recover from a communication error. This message is acceptable during a reconfiguration already in progress.
Description:The cluster will reconfigure.
Solution:No user action is required.
400904 fatal: getzoneid() failed. Unable to verify privilege.
Description:The cl_apid was unable to query the zoneid and hence exited prematurely.
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.
401115 t_rcvudata (recv_request) failed
Description:Call to t_rcvudata() failed. The "t_rcvudata" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
401190 Monitor check for derby data service successful.
Description:The data service successfully checked that node.
Solution:This message is informational; no user action is needed.
401400 Successfully stopped the application
Description:The STOP method successfully stopped the resource.
Solution:This message is informational; no user action is needed.
402190 Validate - %s bin directory %s does not exist
Description:The Samba bin directory does not exist.
Solution:Check the correct pathname for the Samba bin directory was entered when registering the Samba resource and that the directory exists.
402289 t_bind: %s
Description:Call to t_bind() failed. The "t_bind" man page describes possible error codes. udlm will exit and the node will abort.
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.
402359 dl_attach: DL_ERROR_ACK access error
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
402484 NULL command string passed.
Description:A NULL value was specified for the command argument.
Solution:Specify a non-NULL value for the command string.
402596 cl_execd: fork1 returned %d. Returning %d to cl_execd.
Description:The cl_execd program has encountered a failed fork1(2) system call. The error message indicates the error number of failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
402992 Failfast: Destroying failfast unit %s while armed.
Description:The specified failfast unit was destroyed while it was still armed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
403257 Failed to start Backup server.
Description:Sun Cluster HA for Sybase failed to start the backup server. 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, backup server log files and setup.
403317 pxvfs:mount(): global mounts are not enabled (need to run "clconfig -g" first)
Description:A global mount command is attempted before the node has initialized the global file system name space. Typically this caused by trying to perform a global mount while the system is booted in single user mode.
Solution:If the system is not at run level 2 or 3, change to run level 2 or 3 using the init(1M) command. Otherwise, check message logs for errors during boot.
403618 Stale upgrade callback from version manager: upgrade version is %d.%d while current version is %d.%d
Description:Version manager delivered upgrade callback to rgmd about a new version that is not higher than the current version of rgmd.
Solution:No user action is required. This message is for informational purpose only.
403701 Shutdown request successfully issued to RAC instance.
Description:The agent successfully issued a shutdown request to the Oracle RAC instance.
Solution:No user action is required. Informational message.
403891 Error in scha_res_get of extn prop,res:%s, Err: %s
Description:Cannot read the extension property.
Solution:Take action depending on the error. Contact your SUN vendor for updates or patches if any are available.
404130 Failed to bring resource groups containing SUNW.qfs resources offline : %s.
Description:The zone halt handler failed to bring SUNW.qfs resource groups offline successfully.
Solution:Check for the system and zone halt logs to analyze the possible problem. After rectifying the problem try halting the zone cluster node. If the problem still persists contact your authorized Sun service provider with a copy of /var/adm/messages files on all nodes.
404309 in libsecurity cred flavor is not AUTH_SYS
Description:A server (rpc.pmfd, rpc.fed or rgmd) refused an rpc connection from a client because the authorization is not of UNIX type. 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.
404500 Probe failed in the prenet start method. ucmm is aborting
Description:The disk set or disk group failed its availability check because the UCMM is aborting.
Solution:This is behavior valid for a node that is aborting. If the node is not aborting, determine whether the SUNW.rac_framework resource and either the SUNW.rac_svm resource or the SUNW.rac_cvm resource are online. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
404866 method_full_name: malloc failed
Description:The rgmd server was not able to create the full name of the method, while trying to connect to the rpc.fed server. This problem can occur if the machine has 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.
404924 validate: there are syntactical errors in the parameterfile %s
Description:The parameter file did not pass ksh -n filename.
Solution:fix the parameter file until it passe ksh -n.
405019 ERROR: Option %s unknown
Description:Unable to process parameters passed to the call back method. This is an internal error.
Solution:Please report this problem.
405201 Validation failed. Resource group property NODELIST must contain only 1 node
Description:The resource being created or modified must belong to a group that can have only one node name in its NODELIST property.
Solution:Specify just one node in the NODELIST property.
405588 ERROR: Option %s passed to a script of the telemetry data service is unknown
Description:An unknown option was given to a program or script of the telemetry data service. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
405649 validate: User %s does not exist but it is required
Description:The user with the name $Username does not exist or was not returned by the nameservice.
Solution:set the variable User in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.
405790 gethostname() call failed : %s
Description:A call to gethostname() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
405989 %s can't plumb %s.
Description:This means that the Logical IP address could not be plumbed on an adapter belonging to the named IPMP group.
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.
406042 Communication module initialization error
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
406321 INTERNAL ERROR CMM: Cannot resolve type registry object in 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.
406429 Waiting for %s service to be moved into disabled/maintenance state.
Description:The specified SMF service is being moved to disabled/maintenance state.
Solution:This is an informational message. No user action is required.
406610 st_ff_arm failed: %s
Description:The rpc.pmfd server was not able to initialize the failfast mechanism. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog. 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.
406635 fatal: joiners_run_boot_methods: exiting early because of unexpected exception
Description:The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.
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.
407357 in libsecurity strong UNIX authorization failed
Description:A cluster daemon refused an RPC connection from a client because it failed UNIX authentication. This might happen if a caller program is required to run as superuser or as a specific user ID, and fails to do so; or if the caller is attempting to access a Sun Cluster daemon from a remote host, in a case where only local node access is permitted.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Check that the clustering software is properly installed, and that no unauthorized user processes are running on the cluster. If these checks cannot explain the error, contact your authorized Sun service provider to determine whether a workaround or patch is available.
407415 qdmd: Quorum device %s is healthy now.
Description:The quorum device monitoring daemon reports that the indicated quorum device is now healthy after a previous failure.
Solution:No user action is required.
407784 socket: %s
Description:The cl_apid experienced an error while constructing a socket. This error may prohibit event delivery to CRNP clients.
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.
407851 Probe for J2EE engine timed out in scds_fm_tcp_read().
Description:The data service timed out while reading J2EE probe reply.
Solution:Informational message. No user action is needed.
407913 Error getting handle tolibvxvm_get_volinfo
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.
408164 Invalid value for property %s.
Description:The cl_apid encountered an invalid property value. If it is trying to start, it will terminate. If it is trying to reload the properties, it will use the old properties instead.
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.
408214 Failed to create 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.
408254 check_dhcp - tftp transfer test generated an error code of (%s)
Description:The tftp transfer exited with a non-zero return code.
Solution:No user action is required. Informational message, an immediate failover is being requested.
408282 clcomm: RT or TS classes not configured
Description:The system requires either real time or time sharing thread scheduling classes for use in user processes. Neither class is available.
Solution:Configure Solaris to support either real time or time sharing or both thread scheduling classes for user processes.
408621 INTERNAL ERROR: stopping_iter_deps_list: invalid dependency type <%d>
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
408742 svc_setschedprio: Could not save current scheduling parameters: %s
Description:The server was not able to save the original scheduling mode. The system error message 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.
408757 %s: fsync_core_files: could not get any core file paths: pcorefile error %s, gcorefile error %s, zcorefile error %s
Description:The pmmd was unable to retrieve any core file paths from a contract event. The pmmd will continue to monitor the process, but the pmmd has missed information of interest.
Solution: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.
409230 ct_event_read: %s
Description:The libclcontract code was unable to read the next contract event. It will retry.
Solution: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.
409267 Error opening procfs control file (for parent process) <%s> for tag <%s>: %s
Description:The rpc.pmfd server was not able to open the procfs control file for the parent process, and the system error is shown. The procfs control 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.
409693 Aborting startup: failover of NFS resource groups may be in progress.
Description:Startup of an NFS resource was aborted because a failure was detected by another resource group, which would be in the process of failover.
Solution:Attempt to start the NFS resource after the failover is completed. It may be necessary to start the resource on another node if current node is not healthy.
409751 Validate callback skipped.
Description:This resource will not perform validation checks (during UPDATE of Nodelist) on this node, because the resource that it depends on is not configured on this node.
Solution:No user action is required.
409938 Failed to get state of SMF service %s
Description:There was a failure in attempting to determine the state of the SMF service.
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.
410176 Failed to register callback for IPMP group %s with tag %s and callback command %s (request failed with %d).
Description:An unexpected error occurred while trying to communicate with the network monitoring daemon (cl_pnmd).
Solution:Make sure the network monitoring daemon (cl_pnmd) is running.
410272 Validate - ORACLE_HOME directory %s does not exist
Description:The Oracle E-Business Suite ORACLE_HOME directory does not exist.
Solution:Check that the correct pathname was entered for the Oracle Home directory when registering the resource and that the directory exists.
410860 lkcm_act: cm_reconfigure failed: %s
Description:ucmm reconfiguration failed. This could also point to a problem with the interconnect components.
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.
411227 Failed to stop the process with: %s. Retry with SIGKILL.
Description:Process monitor facility is failed to stop the data service. It is reattempting to stop the data service.
Solution:This is informational message. Check the Stop_timeout and adjust it, if it is not appropriate value.
411369 Not found clexecd on node %d for %d seconds. Giving up!
Description:Could not find clexecd to execute the program on a node. Indicated giving up after retries.
Solution:This is an informational message, no user action is needed.
411471 Error while initializing 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.
412106 Internal Error. Unable to get fault monitor name
Description:This is an internal error. Could not determine fault monitor program name.
Solution:Please report this problem.
412366 setsid failed: %s
Description:Failed to run the "setsid" command. The "setsid" man page describes possible error codes.
Solution:No user action is required. The ucmmd will exit.
412530 Error: could not start the Derby server because the directory path specified in the resource property DB_path is not valid.
Description:The Derby server could not be started because the path specified in DB_path is not valid.
Solution:Use a valid directory path as the value of the DB_path property.
412533 clcomm: validate_policy: invalid relationship moderate %d low %d pool %d
Description:The system checks the proposed flow control policy parameters at system startup and when processing a change request. The moderate server thread level cannot be less than the low server thread level.
Solution:No user action required.
412717 scvxvmlg error - getminor called with a bad filename: %s
Description:The program responsible for maintaining the VxVM namespace has suffered an internal error. If configuration changes were recently made to VxVM diskgroups or volumes, this node may be unaware of those changes. Recently created volumes may be unaccessible from this node.
Solution:If no configuration changes have been recently made to VxVM diskgroups or volumes and all volumes continue to be accessible from this node, then no action is required. If changes have been made, the device namespace on this node can be updated to reflect those changes by executing '/usr/cluster/lib/dcs/scvxvmlg'. If the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
413513 INTERNAL ERROR Failfast: ff_impl_shouldnt_happen.
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.
413569 CCR: Invalid CCR table : %s.
Description:The rgmd daemon was unable to open the cluster configuration repository (CCR). The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
413925 in libsecurity ; unable to create door : %s
Description:A Sun Cluster daemon was unable to create a door for communication with its clients. A following syslog message provides the name of the daemon that failed. This might cause the node to be rebooted or halted.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
414007 CMM: Placing reservation on quorum device %s failed.
Description:An error was encountered while trying to place a reservation on the specified quorum device, hence this node can not take ownership of this quorum device.
Solution:There may be other related messages on this and other nodes connected to this quorum device that may indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.
414208 QUORUM_GENERIC: quorum preempt error in CMM: Error %d --- QUORUM_GENERIC Tkown ioctl failed on quorum device %s.
Description:This node encountered an error when issuing a QUORUM_GENERIC Take Ownership operation on a quorum device. This error indicates that the node was unsuccessful in preempting keys from the quorum device, and the partition to which it belongs was preempted. If a cluster is divided into two or more disjoint subclusters, one of these must survive as the operational cluster. The surviving cluster forces the other subclusters to abort by gathering enough votes to grant it majority quorum. This action is called "preemption of the losing subclusters".
Solution:Other related messages identify the quorum device where the error occurred. If an EACCES error occurs, the QUORUM_GENERIC command might have failed because of the SCSI3 keys on the quorum device. Scrub the SCSI3 keys off the quorum device and reboot the preempted nodes.
414281 %s affinity property for %s resource group is set. Retry_count cannot be greater than 0.
Description:The specified affinity has been set for the specified resource group. That means the SAP enqueue server is running with the replica server. Hence the retry_count for SAP enqueue server resource must not restart locally. Therefore, the Retry_count must be set to zero.
Solution:Set the value for Retry_count to zero for the SAP enqueue server resource.
414431 Unable to create server thread for immediate failfast of zone %s with zone ID %d
Description:A server thread that is needed for failfasting 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.
414680 fatal: register_president: Don't have reference to myself
Description:The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.
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.
414705 RGM unblocked, encountered an exception
Description:The RGM returned from the blocking invocation with an exception. The process that hosts the server object might have terminated. As a result of this, RGM might try to bring the resources online that need global file systems data. The data might not be available yet, which might result in failure to start the resource groups.
Solution:Save a copy of /var/adm/messages, /var/cluster/logs/ql_server_debug.log and /var/cluster/logs/install/ql_upgrade_debug.log on all the nodes. Report the problem to your authorized Sun service provider.
415110 Error: pmfadm could not start fault monitor, tag "%s" error="%s"
Description:The PMF could not start the CRS framework monitor.
Solution:Check for other errors on the system and correct them before restarting the CRS framework resource. If you cannot resolve this problem, contact your Sun service representative for assistance.
415591 SCSLM fstat <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
415619 srm_function - The user %s does not belongs to project %s
Description:The specified user does not belong to the project defined by Resource_project_name or Rg_project_name.
Solution:Add the user to the defined project in /etc/project.
415736 Failed to retrieve failback value.
Description:Unable to retrieve the failback property value.
Solution:Check the resource group configuration in which this resource is configured. If the problem persists, contact your authorized Sun service provider with copies of /var/adm/messages files on all nodes.
415842 fatal: scswitch_onoff: invalid opcode <%d>
Description:While attempting to execute an operator-requested enable or disable of a resource, the rgmd has encountered an internal error. This error should not occur. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
416483 Failed to retrieve the resource information.
Description:A Sun Cluster data service is unable to retrieve the resource information. 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.
416930 fatal: %s: internal error: bad state <%d> for resource group <%s>
Description:An internal error has occurred. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
Solution:Save a copy of the /var/adm/messages files on all nodes, and of the rgmd core file(s). Contact your authorized Sun service provider for assistance in diagnosing the problem.
417144 Must be root to start %s
Description:The program or daemon has been started by someone not in superuser mode.
Solution:Login as root and run the program. If it is a daemon, it may be incorrectly installed. Reinstall cluster packages or contact your service provider.
417232 scvxvmlg warning - %s does not link to %s, changing it
Description:The program responsible for maintaining the VxVM device namespace has discovered inconsistencies between the VxVM device namespace on this node and the VxVM configuration information stored in the cluster device configuration system. If configuration changes were made recently, then this message should reflect one of the configuration changes. If no changes were made recently or if this message does not correctly reflect a change that has been made, the VxVM device namespace on this node may be in an inconsistent state. VxVM volumes may be inaccessible from this node.
Solution:If this message correctly reflects a configuration change to VxVM diskgroups then no action is required. If the change this message reflects is not correct, then the information stored in the device configuration system for each VxVM diskgroup should be examined for correctness. If the information in the device configuration system is accurate, then executing '/usr/cluster/lib/dcs/scvxvmlg' on this node should restore the device namespace. If the information stored in the device configuration system is not accurate, it must be updated by executing '/usr/cluster/bin/scconf -c -D name=diskgroup_name' for each VxVM diskgroup with inconsistent information.
417629 Database or gateway down.
Description:This indicates that the Siebel database or Siebel gateway is unavailable for the Siebel server.
Solution:Please determine the reason for Siebel database or Siebel gateway failure, and ensure that they are both running. If the Siebel server resource is not offline, it should get started by the fault monitor.
417740 Unregistered syscall. %s(%d)
Description:An event which was not registered for, has been received. This can happen if the monitored process is simultaneously being controlled by another process, most notably, by a proc tool.
Solution:This is informational. No user action is required.
417835 Failed to read the cz info
Description:The private IP address assigned to a zone was not configured correctly.
Solution:The private IP address assigned to the zone is used for private IP communication for the zone. So, this feature may not work as expected as a result of this error. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
417903 clexecd: waitpid returned %d.
Description:clexecd program has encountered a failed waitpid(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.
418511 XDR Error while decoding return arguments.
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.
418772 Unable to post event %lld: %s: Retrying..
Description:The cl_eventd was unable to post an event to the sysevent queue locally, but will retry.
Solution:No user action is required.
418787 Dependency on %s or %s not defined
Description:A ScalDeviceGroup resource is defined without the required dependency on a resource of type SUNW.rac_svm or of type SUNW.rac_svm.
Solution:Modify the ScalDeviceGroup resource to depend on a resource either of type SUNW.rac_svm or of type SUNW.rac_cvm.
418869 clq_scsi3: Error %d from MHIOCGRP_INRESV --- failed to read reservations from quorum device %s.
Description:An error was encountered while trying to read reservations on the specified quorum device.
Solution:There may be other related messages on this and other nodes connected to this quorum device that may indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.
419061 getlocalhostname() failed; unable to execute zoneadm reboot for zone %s
Description:The rgmd daemon was unable to obtain the name of the local host, causing a zoneadm reboot invocation to fail. The zone will stay up, but the rgmd will not attempt to start services on it.
Solution:Reboot the zone. 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 the problem.
419291 Unable to connect to Siebel gateway.
Description:Siebel gateway may be unreachable.
Solution:Please verify that the Siebel gateway resource is up.
419301 The probe command <%s> timed out
Description:Probe of the data service timed out. Timeout occurred when executing the probe command provided by user under the hatimerun(1M) utility.
Solution:This problem might occur when the cluster is under load. Consider increasing the Probe_timeout property.
419529 INTERNAL ERROR CMM: Failure registering callbacks.
Description:An instance of the userland CMM encountered an internal initialization error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
419733 Database is already stopped.
Description:The database does not need to be stopped.
Solution:This is an informational message, no user action is needed.
419972 clcomm: Adapter %s is faulted
Description:A network adapter has encountered a fault.
Solution:Any interconnect failure should be resolved, and/or a failed node rebooted.
420196 Failed to retrieve private IP address for node %d
Description:Cluster cannot generate a callback for the RDS module. Operation of RDS sockets might be affected.
Solution:If Reliable Datagram Sockets (RDS) is used by applications running on this cluster, contact your Sun Microsystems service representative to determine if a workaround or patch is available.
420338 Validate - RUN_MODE has to be server
Description:The DHCP resource requires that the /etc/inet/dhcpsvc.conf file has RUN_MODE=SERVER.
Solution:Ensure that /etc/inet/dhcpsvc.conf has RUN_MODE=SERVER by configuring DHCP appropriately, i.e. as defined within the Sun Cluster Data Service for DHCP.
420573 Error sending signal to contract <%d>: %s
Description:The rpc.pmfd was not able to send the requested signal to the specified contract id.
Solution:If the message is isolated, it was probably a transient error. If you were running pmfadm(1M) directly, retry the requested action. 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.
420763 Switchover (%s) error (%d) after failure to become secondary
Description:The file system specified in the message could not be hosted on the node the message came from.
Solution:Check /var/adm/messages to make sure there were no device errors. If not, contact your authorized Sun service provider to determine whether a workaround or patch is available.
420823 XDR Error while encoding return arguments.
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.
421576 Validation failed. PARAMETER_FILE: %s does not exist.
Description:The file that the extension property parameter_file specifies does not exist.
Solution:Check that the extension property parameter_file specifies the correct file name. If the file name is correct, check that the file system where the file resides is accessible. If the file system is accessible, check that the file exists on all nodes where the resource can be brought online. If the file exists on all nodes, check that the access permissions of the file are correct. If the problem persists, contact your Sun support representative for further assistance.
421944 Could not load transport %s, paths configured with this transport will not come up.
Description:Topology Manager could not load the specified transport module. Paths configured with this transport will not come up.
Solution:Check if the transport modules exist with right permissions in the right directories.
421967 Cannot stat() home directory: %s
Description:Home directory of the SAP admin user could not be checked.
Solution:Ensure that the directory is accessible from all relevant cluster nodes.
422033 HA: exception %s (major=%d) from stop_receiving_ckpt().
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.
422190 Failed to reboot node: %s.
Description:HA-NFS fault monitor was attempting to reboot the node, because rpcbind daemon was unresponsive. However, the attempt to reboot the node itself did not succeed.
Solution:Fault monitor would exit once it encounters this error. However, process monitoring facility would restart it (if enough resources are available on the system). If rpcbind remains unresponsive, the fault monitor (restarted by PMF) would again attempt to reboot the node. If this problem persists, reboot the node. Also see message id 804791.
422302 scnetapp fatal error - Unexpected filer type(%s) in table %s
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
422541 Failed to register with PDTserver
Description:This means that we have lost communication with PDT server. Scalable services will not work any more. Probably, the nodes which are configured to be the primaries and secondaries for the PDT server are down.
Solution:Need to restart any of the nodes which are configured be the primary or secondary for the PDT server.
422561 SCSLM zone <%s> rg_name <%s> not found
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
422570 Probing thread failed to wait on Condition variable : %s
Description:The thread that was created to perform a probe failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
422594 Error: The resource property RESOURCE_DEPENDENCIES must contain the "%s" resource.
Description:An attempt was made to create or update a CRS framework resource without specifying a dependency on the RAC framework resource.
Solution:Repeat the attempt to create or update the CRS framework resource, specifying the required dependency on the RAC framework resource.
423137 A resource restart attempt on resource %s in resource group %s has been blocked because the number of restarts within the past Retry_interval (%d seconds) would exceed Retry_count (%d)
Description:A request to restart a resource is denied because the resource has already been restarted Retry_count times within the past Retry_interval seconds
Solution:No user action is required. If desired, use clresourcegroup to change the Failover_mode setting.
423291 RGM isn't failing resource group <%s> off of node <%s>, because there are no other current or potential masters
Description:A scha_control(1HA,3HA) GIVEOVER attempt failed because no candidate node was healthy enough to host the resource group, and the resource group was not currently mastered by any other node.
Solution:Examine other syslog messages on all cluster members that occurred about the same time as this message, to see why other candidate nodes were not healthy enough to master the resource group. Note: A properly-implemented resource monitor, upon encountering the failure of a scha_control GIVEOVER call, will sleep for awhile and restart its probes. If the original error condition is temporary, later probes will succeed and the resource can continue providing service on its current master. If probe failures continue to occur on this node, the scha_control GIVEOVER will be reattempted and might then succeed in relocating the resource group to a new master. In these cases, no user action is required.
423538 WARNING: UDLM_PROCEED was picked up by a lkcm_act, returning LKCM_NOOP
Description:An internal warning during udlm state update.
Solution:No user action is required.
423704 Validate - DHCP config file %s does not exist
Description:The DHCP resource could not validate that /etc/inet/dhcpsvc.conf exists.
Solution:Ensure that /etc/inet/dhcpsvc.conf exists.
423928 Error reading line %d from stopstate file: %s.
Description:There was an error reading from the stopstate file at the specified line.
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. Check to see if their is a problem with the stopstate file.
423958 resource group %s state change to unmanaged.
Description:This is a notification from the rgmd that a resource group's state has changed. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
424061 Validation failed. ORACLE_HOME %s does not exist
Description:Directory specified as ORACLE_HOME does not exist. ORACLE_HOME property is specified when creating Oracle_server and Oracle_listener resources.
Solution:Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.
424083 Validation failed. Specified DB_NAME %s not registered with CRS
Description:Creation of a resource of type SUNW.scalable_rac_server_proxy failed because the specified DB_NAME %s is not recognized by CRS as a valid RAC database.
Solution:Verify using CRS interfaces whether the specified DB_NAME is valid or not. If the problem persists, contact your Sun support representative for further assistance.
424683 SCSLM file <%s> is empty
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
424774 Resource group <%s> requires operator attention due to STOP failure
Description:This is a notification from the rgmd that a resource group has had a STOP method failure or timeout on one of its resources. The resource group is in ERROR_STOP_FAILED state. This may cause another operation such as clresource or scha_control(1HA,3HA) to fail with a SCHA_ERR_STOPFAILED error.
Solution:Refer to the procedure for clearing the ERROR_STOP_FAILED condition on a resource group in the Sun Cluster Administration Guide.
424783 pmf_monitor_suspend: PCRUN: %s
Description:The rpc.pmfd server was not able to suspend the monitoring of a process and the monitoring of the process has been aborted. The message contains the system error.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
424816 Unable to set automatic MT mode.
Description:The rpc.pmfd server was not able to set the multi-threaded operation mode. This happens while the server is starting up, at boot time. The server does not come up, 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.
425256 Started SAP processes successfully w/o PMF.
Description:The data service started the processes without PMF.
Solution:Informational message. No user action is needed.
425328 validate: Return String is not set but it is required
Description:The Return string is not set in the parameter file.
Solution:Specify the ReturnString in the parameter file.
425366 check_cmg - FUNDRUN = %s, FNDMAX = %s
Description:While probing the Oracle E-Business Suite concurrent manager, the actual percentage of processes running is below the user defined acceptable limit set by CON_LIMIT when the resource was registered.
Solution:Determine why the number of actual processes for the concurrent manager is below the limit set by CON_LIMIT. The concurrent manager resource will be restarted.
425551 getnetconfigent (open_cmd_port) failed
Description:Call to getnetconfigent failed and ucmmd could not get network information. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
425618 Failed to send ICMP packet: %s
Description:There was a problem in sending an ICMP packet over a raw socket.
Solution:If the error message string that is logged in this message does not offer any hint as to what the problem could be, contact your authorized Sun service provider.
426221 CMM: Reservation key changed from %s to %s for node %s (id = %d).
Description:The reservation key for the specified node was changed. This can only happen due to the CCR infrastructure being changed by hand, which is not a supported operation. The system can not continue, and the node will panic.
Solution:Boot the node in non-cluster (-x) mode, recover a good copy of the file /etc/cluster/ccr/infrastructure from one of the cluster nodes or from backup, and then boot this node back in cluster mode. If all nodes in the cluster exhibit this problem, then boot them all in non-cluster mode, make sure that the infrastructure files are the same on all of them, and boot them back in cluster mode. The problem should not happen again.
426570 Property %s can be changed only while UNIX Distributed Lock Manager is not running on the node.
Description:This property can be changed only while UNIX Distributed Lock Manager (UDLM) is not running on the node. The UDLM on all the nodes must use identical value of this property for proper functioning of the UDLM.
Solution:Change the RAC framework resource group to unmanaged state. Reboot all the nodes that can run RAC framework and modify the property.
426613 Error: unable to bring Resource Group <%s> ONLINE, because one or more Resource Groups with a strong negative affinity for it are in an error state.
Description:The rgmd is unable to bring the specified resource group online on the local node, because one or more resource groups related to it by strong negative RG affinities are in STOP_FAILED error state.
Solution:Find the errored resource groups and resources by using "clresourcegroup status" and "clresource status". Clear the STOP_FAILED error states by using "clresource clear". Use ps(1) or application-specific commands to make sure that the resource has stopped completely; kill resource-related processes if necessary.
426721 Diskgroup (%s) could not be found!
Description:The disk set or disk group that is being validated was not found.
Solution:Determine whether the disk set or disk group was removed. Contact your authorized Sun service provider for assistance in diagnosing the problem.
426827 reservation error(%s) - Unable to gain access to device '%s', errno %d
Description:The device fencing program has encountered errors while trying to access a device.
Solution:Another cluster node has fenced this node from the specified device, preventing this node from accessing that device. Access should have been reacquired when this node joined the cluster, but this must have experienced problems. If the message specifies the 'node_join' transition, this node will be unable to access the specified device. If the failure occurred during the 'make_primary' transition, then this will be unable to access the specified device and a device group that contains the specified device might have failed to start on this node. An attempt can be made to acquire access to the device by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on this node. If a device group failed to start on this node, the cldevicegroup command can be used to start the device group on this node if access can be reacquired. If the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
427250 Membership: Unable to create membership threadpool.
Description:The membership threadpool 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.
427346 check_mysql_slave - MySQL slave instance %s is not connected to master %s with MySql error (%s)
Description:The fault monitor has detected that the MySQL slave instance is not connected to the specified master.
Solution:Check MySQL log files to determine why the slave has been disconnected to the master.
427984 Completed verification of SUNW.qfs resources metadata server status.
Description:This is a notification from the handler that it has completed verification of metadata servers status of SUNW.qfs resources.
Solution:This is an informational message; no user action is needed.
428036 Function: validate - %s state is %
Description:The SMF service state is not installed or ready.
Solution:If the SMF service is required to be managed by the Sun Cluster the SMF satte must be either installed or ready.
428115 Failed to open SAM-FS volume file %s: %s.
Description:HAStoragePlus was not able to open the specified volume that is part of the SAM-FS file system.
Solution:Check the SAM-FS file system configuration. If the problem persists, contact your authorized Sun service provider.
428367 QUORUM_GENERIC: quorum_reserve error: writing reservation key on quorum device %s failed with error code %d.
Description:An error was encountered when reserving the specified quorum device. The reservation key could not be written on the quorum device. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
429203 Exceeded Monitor_retry_count: Fault monitor for resource %s failed to stay up.
Description:Resource fault monitor failed to start after Monitor_retry_count number of attempts. The resource will not be monitored.
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.
429368 CMM: sector read for validation failed after write, error code %d
Description:After writing to a sector, an attempt to read the sector for validation of the Persistent Group Reservation Emulation (PGRE) ID string failed. The error could be either in the driver or the hardware.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available for this driver/hardware error.
429403 Function: validate: The STDBY_PING value of %s is not numeric
Description:In the parameter file, there is a non numeric character in the value for the STDBY_PING variable.
Solution:Fix the STDBY_PING variable in the parameter file.
429549 reservation warning(%s) - MHIOCGRP_REGISTERANDIGNOREKEY 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.
429663 Node %s not in list of configured nodes
Description:The specified scalable service could not be started on this node because the node is not in the list of configured nodes for this particluar service.
Solution:If the specified service needs to be started on this node, use clresourcegroup to add the node to the list of configured nodes for this service and then restart the service.
429962 Successfully unmounted %s.
Description:HAStoragePlus successfully mounted the specified file system.
Solution:This is an informational message, no user action is needed.
430034 Monitor for resource %s successfully stopped.
Description:The monitor for HA-KDC has been stopped.
Solution:This is for informational purposes, no action is required.
430055 CCR: Can't access cluster %s 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/.
430296 Starting Proxy monitor. pmf tag %s
Description:The agent is attempting to startup the Monitor of a resource of type SUNW.scalable_rac_server_proxy.
Solution:No user action is required. Informational message.
430445 Monitor initialization error. Incorrect arguments
Description:Error occurred in monitor initialization. Arguments passed to the monitor by callback methods were incorrect.
Solution:This is an internal error. Disable the monitor and report the problem.
431018 fork1 returned %d while creating daemon. Exiting.
Description:The cl_execd program has encountered a failed fork1(2) system call. The error message indicates the error number of failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
431650 User %s does not exist
Description:The User list operation failed for broker_user.
Solution:Check the syslog and /var/adm/messages for more details.
432222 %s is not a valid IPMP group name on this node.
Description:Validation of the adapter information has failed. The specified IPMP group does not exist on this node.
Solution:Create appropriate IPMP group on this node or recreate the logical host with correct IPMP group.
432473 reservation fatal error(%s) - joining_node not specified
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.
432951 %s is not a directory.
Description:The path listed in the message is not a directory.
Solution:Specify a directory path for the extension property.
432987 Failed to retrieve nodeid.
Description:Data service is failed to retrieve the host information.
Solution:If the logical host and shared address entries are specified in the /etc/inet/hosts file, check these entries are correct. If this is not the reason then check the health of the name server. For more error information, check the syslog messages.
433041 The Diskgroup (%s) is not imported on this node.
Description:The VxVM disk group has not been imported.
Solution:Ensure that the SUNW.rac_framework resource and the SUNW.rac_cvm resource are online.
433438 Setup error. SUPPORT_FILE %s does not exist
Description:This is an internal error. Support file is used by HA-Oracle to determine the fault monitor information.
Solution:Please report this problem.
433501 fatal: priocntl: %s (UNIX error %d)
Description:The daemon indicated in the message tag (rgmd or ucmmd) has encountered a failed system call to priocntl(2). The error message indicates the reason for the failure. The daemon will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
Solution:If the error message is not self-explanatory, 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.
433689 CVM version is not compatible
Description:The version of the library libvxvmsc.so is incompatible with this version of Sun Cluster.
Solution:Install a compatible version of the library libvxvmsc.so.
433895 INTERNAL ERROR: Invalid resource property tunable flag <%d> for property <%s>; aborting node
Description:An internal error occurred in the rgmd while checking whether a resource property could be modified. The rgmd will produce a core file and will force the node to halt or reboot.
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.
434318 %s: thr_sigsetmask returned %d. Exiting.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
434480 CCR: CCR data server not found.
Description:The CCR data server could not be found in the local name server.
Solution:Reboot the node. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.
434733 All WebSphere MQ non-attached IPC shared memory segments removed
Description:All the WebSphere MQ shared memory segments that were not being used have been removed.
Solution:No user action is required. Informational message.
435295 Unable to create thread, errno = %d. Exiting.
Description:The rtreg server program encountered a failure while executing thr_create(3C).
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
435895 Found another active instance of cl_execd. Exiting cl_execd.
Description:The cl_execd program found another active cl_execd program already in execution.
Solution:This is an information message. No user action is required.
435929 Validation failed. Resource group property RG_AFFINITIES should specify affinities only on SCALABLE resource groups.
Description:The resource group should have affinities only on resource groups that are of type SCALABLE.
Solution:Specify only SCALABLE resource groups in the RG_AFFINITIES property of the resource group that is to contain the proxy resource.
435944 Error: could not start the Derby server, check whether the port specified in the resource property DB_port is already used.
Description:The Derby server could not be started probably because the port specified in DB_port is already used.
Solution:Check the resource property DB_port of the Derby data service and try to use another port number.
436058 There might be still metadata server of configured SUNW.qfs resources running on this node which can prevent the sQFS file systems to be unmounted by Solaris during zone halt. Zone halt operation is not successful.
Description:The zone halt handler failed to complete its action successfully.
Solution:Check for the system and zone halt logs to analyze the problem. After rectifying the problem try halting the node. If the problem still persists contact your authorized Sun service provider with a copy of /var/adm/messages files on all nodes.
436659 Failed to start the adaptive server.
Description:Sun Cluster HA for Sybase failed to start Sybase server. 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.
436871 liveCache is already online.
Description:liveCache was started up outside of Sun Cluster when Sun Cluster tries to start it up. In this case, Sun Cluster will just put the already started up liveCache under Sun Cluster's control.
Solution:Informative message, no action is needed.
437100 Validation failed. Invalid command line parameter %s %s
Description:Unable to process parameters passed to the call back method. This is an internal error.
Solution:Please report this problem.
437350 File system associated with mount point %s is to be locally mounted. Local file systems cannot be specified with scalable service resources.
Description:HAStoragePlus detected an inconsistency in its configuration: the resource group has been specified as scalable, hence local file systems cannot be specified in the FilesystemMountPoints extension property.
Solution:Correct either the resource group type or remove the local file system from the FilesystemMountPoints extension property.
437834 stat of share path %s failed: %s.
Description:HA-NFS fault monitor reports a probe failure on a specified file system.
Solution:Make sure the specified path exists.
437850 in libsecurity for program %s (%lu); svc_reg failed for transport %s. Remote clients won't be able to connect
Description:A server (rpc.pmfd, rpc.fed or rgmd) was not able to register with rpcbind. The server should still be able to receive requests from clients using the "cache" files under /var/run/scrpc/ but remote clients won't be able to connect. 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.
437950 Global service %s associated with path %s is found to be unavailable: %s.
Description:The DCS reported that the specified global service was unavailable.
Solution:Check the device links (SCSI, Fiberchannel, etc.) cables.
438175 HA: exception %s (major=%d) from start_receiving_ckpt().
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.
438420 Interface %s is plumbed but is not suitable for global networking.
Description:The specified adapter may be either point to point adapter or loopback adapter which is not suitable for global networking.
Solution:Reconfigure the appropriate IPMP group to exclude this adapter.
438639 Zone cluster %s is not configured to run on node %s
Description:The PNM proxy subsystem is called on a physical node for a zone cluster that is not configured to run on that node.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
438700 Some ip addresses might still be on loopback.
Description:Some of the ip addresses managed by the specified SharedAddress resource were not removed from the loopback interface.
Solution:Use the ifconfig command to make sure that the ip addresses being managed by the SharedAddress implementation are present either on the loopback interface or on a physical adapter. If they are present on both, use ifconfig to delete them from the loopback interface. Then use clresourcegroup to move the resource group that contains the SharedAddresses to another node to make sure that the resource group can be switched over successfully.
438866 sysinfo in getlocalhostname failed
Description:The sysinfo call did not succeed. The "sysinfo" man page describes possible error codes.
Solution:This is an internal error. Please report this problem.
439933 monitor_check: call to rpc.fed failed for resource <%s>, resource group <%s>, node <%s>, method <%s>
Description:A scha_control(1HA,3HA) GIVEOVER attempt failed, due to a failure of the rgmd to communicate with the rpc.fed daemon. If the rpc.fed process died, this might lead to a subsequent reboot of the node. Otherwise, this will prevent a resource group on the local node from failing over to an alternate primary node
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
440289 validate: The N1 Grid Service Provisioning System local distributor agent start command does not exist, its not a valid local distributor installation
Description:The Basepath is set to a false value.
Solution:Set the Basepath to the right directory
440309 Creation of the %s directory failed.
Description:The mkdir(1) command has returned an error.
Solution:Investigate the cause of the failure and correct the condition prior to attempting this operation again.
440406 Cannot check online status. Server processes are running.
Description:HA-Oracle could not check online status of Oracle server. Oracle server processes are running but Oracle server may or may not be online yet.
Solution:Examine 'Connect_string' property of the resource. Make sure that user id and password specified in connect string are correct and permissions are granted to user for connecting to the server.
440477 Validate - This version of samba <%s> is not supported with this dataservice
Description:The Samba resource check to see that an appropriate version of Samba is being deployed. Versions below v2.2.2 will generate this message.
Solution:Ensure that the Samba version is equal to or above v2.2.2.
440530 Started the fault monitor.
Description:The fault monitor for this data service was started successfully.
Solution:No user action is required.
441874 Ignoring %s set in environment file %s
Description:HA-Oracle methods read the file specified by the USER_ENV property and set the environment variables declared in this file. If an entry in the file specified by the USER_ENV property tries to set a critical environment variable, that entry is ignored.
Solution:Check USER_ENV and remove any entries which attempt to set the environment variable specified in the error message.
442053 clcomm: Invalid path_manager client_type (%d)
Description:The system attempted to add a client of unknown type to the set of path manager clients.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
442581 request addr > max "%s"
Description:Error from udlm on an address request. Udlm exits and the nodes aborts and panics.
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.
442767 Failed to stop SAP processes under PMF with SIGKILL.
Description:Failed to stop SAP processes with Process Monitor Facility(PMF) with signal.
Solution:This is an internal error. No user action needed. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
442846 in libsecurity for program %s ; creation of file %s failed: %s
Description:A Sun Cluster daemon was unable to create a door descriptor for communication with its clients. A following syslog message provides the name of the daemon that failed. This might cause the node to be rebooted or halted.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
442862 scha_cluster_open() failed: %s
Description:A call to scha_cluster_open() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
443010 WARNING !!! Current node is hosting the MDS Resource %s, file-system %s has been left in mounted-state...
Description:An attempt to unmount a shared QFS file system failed because the current node is hosting the metadata server resource for the file system. The attempt to unmount the file system occurred because the ScalMountPoint resource was going offline on the current node.
Solution:Manually switch over the metadata resource to another suitable node and unmount the shared QFS file system.
443271 clcomm: Pathend: Aborting node because %s for %u ms
Description:The pathend aborted the node for the specified reason.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
443542 repl_check fatal error - could not load DID repl list
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.
443746 resource %s state on node %s change to %s
Description:This is a notification from the rgmd that a resource's state has changed. This may be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
444001 %s: Call failed, return code=%d
Description:A client was not able to make an RPC or door connection to a server (rpc.pmfd, rpc.fed or rgmd) to execute the action shown. The error number is shown.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
444078 Cleaning up IPC facilities.
Description:Sun Cluster is cleaning up the IPC facilities used by the application.
Solution:This is an informational message, no user action is needed.
444144 clcomm: Cannot change increment
Description:An attempt was made to change the flow control policy parameter that specifies the thread increment level. The flow control system uses this parameter to set the number of threads that are acted upon at one time. This value currently cannot be changed.
Solution:No user action required.
444161 dl_attach: DLPI error %u
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.
444335 Could not allocate memory, size = %d
Description:Could not allocate memory, PNM proxy program will exit.
Solution:The system is running low on memory. Free up resources so that sufficient memory is available.
444479 Unable to allocate memory in sc delegated service_mgmt
Description:Problem in creating memory space during service management of SMF delegated restarter
Solution:Check the system memory usage
445216 stop_trm - WebSphere MQ Trigger Monitor %s stopped
Description:The specified WebSphere MQ Trigger Monitor has been stopped.
Solution:No user action is required. Informational message.
445855 Switchover error (%s): failed to fsck disk
Description:The file system specified in the message could not be hosted on the node the message came from because an fsck on the file system revealed errors.
Solution:Unmount the PXFS file system (if mounted), fsck the device, and then mount the PXFS file system again.
446068 CMM: Node %s (nodeid = %ld) is down.
Description:The specified node has gone down in that communication with it has been lost.
Solution:The cause of the failure should be resolved and the node should be rebooted if node failure is unexpected.
446650 SCSLM cannot modify pset <%s%s> to min=%u,max=%u
Description:Requested number of CPUS cannot be set for this resource group on this node.
Solution:Switch the resource group on a node with enough CPUs or lower RG_SLM_CPU_SHARES or RG_SLM_PSET_MIN properties values or move RG_SLM_type to manual and restart the resource group.
446764 SCSLM lseek <%s> off is 0
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
446827 fatal: cannot create thread to notify President of status changes
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.
446967 Stopping Proxy monitor using pmfadm tag %s
Description:The agent is attempting to stop the Monitor of a resource of type SUNW.scalable_rac_server_proxy.
Solution:No user action is required. Informational message.
447268 Proxy Daemon failed to start.
Description:The Monitor of the SUNW.scalable_rac_server_proxy resource failed to startup.
Solution:Try disabling the resource on the failed node. This will lead to a STOP_FAILED condition for that RAC instance resource. Try enabling the resource again. If the problem persists, contact your Sun support representative for further assistance.
447417 call get_dpm_global with an invalid argument
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
447451 Not attempting to start resource group <%s> on node <%s> because this resource group has already failed to start on this node %d or more times in the past %d seconds
Description:The rgmd is preventing "ping-pong" failover of the resource group, i.e., repeated failover of the resource group between two or more nodes.
Solution:The time interval in seconds that is mentioned in the message can be adjusted by using clresourcegroup to set the Pingpong_interval property of the resource group.
447465 call set_dpm_global with an invalid argument
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
447578 Duplicated installed nodename when Resource Type <%s> is added.
Description:User has defined duplicated installed node name when creating resource type.
Solution:Recheck the installed nodename list and make sure there is no nodename duplication.
447846 Invalid registration operation
Description:The cl_apid experienced an internal error that prevented proper registration of a CRNP client.
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.
447872 fatal: Unable to reserve %d MBytes of swap space; exiting
Description:The rgmd daemon was unable to allocate a sufficient amount of memory 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.
448079 Dataguard_role is IN_TRANSITION. Switchover may be in progress. Instance will not be started.
Description:The administrator has set the 'dataguard_role' resource property to indicate that role switchover operation is in progress outside Sun Cluster control. This resource will not be started.
Solution:If this property is incorrectly set, please set the correct value of 'dataguard_role' and restart the resource.
448703 clcomm: validate_policy: high too small. high %d low %d nodes %d pool %d
Description:The system checks the proposed flow control policy parameters at system startup and when processing a change request. The high server thread level must be large enough to grant the low number of threads to all of the nodes identified in the message for a fixed size resource pool.
Solution:No user action required.
448844 clcomm: inbound_invo::done: state is 0x%x
Description:The internal state describing the server side of a remote invocation is invalid when the invocation completes server side processing.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
448898 %s.nodes entry in the configuration file must be between 1 and %d.
Description:Illegal value for a node number. Perhaps the system is not booted as part of the cluster.
Solution:Make sure the node is booted as part of a cluster.
449159 clconf: No valid quorum_vote field for node %u
Description:Found the quorum vote field being incorrect while converting the quorum configuration information into quorum table.
Solution:Check the quorum configuration information.
449288 setgid: %s
Description:The rpc.pmfd server was not able to set the group id of a process. 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.
449336 setsid: %s
Description:The rpc.pmfd or rpc.fed server was not able to set the session id, 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.
449344 setuid: %s
Description:The rpc.pmfd server was not able to set the user id of a process. 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.
449661 No permission for owner to write %s.
Description:The owner of the file does not have write permission on it.
Solution:Set the permissions on the file so the owner can write it.
449819 scvxvmlg fatal error - %s does not exist
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
450032 SCSLM <%s> pool_resource_destroy error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
450412 Unable to determine resource group status.
Description:A critical method was unable to determine the status of the specified resource group.
Solution:Please examine other messages in the /var/adm/messages file to determine the cause of this problem. Also verify if the resource group is available or not. If not available, start the service or resource and retry the operation which failed.
450579 door_call: %s; will retry
Description:The door_call failed with the specified reason.
Solution:No user action is required.
451010 INTERNAL ERROR: stopping_iter_deps_list: meth type <%d>
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
451115 ucmmd is already running.
Description:This is informational message.
Solution:No user action is required.
451315 Error retrieving the extension property %s: %s.
Description:An error occurred reading the indicated extension property.
Solution:Check syslog messages for errors logged from other system modules. If error persists, please report the problem.
451699 No reference to remote node %d, not forwarding event %lld
Description:The cl_eventd cannot forward the specified event to the specified node because it has no reference to the remote node.
Solution:This message is informational only, and does not require user action.
451793 Class<%s> SubClass<%s> Pid<%d> Pub<%s> Seq<%lld> Len<%d>
Description:The cl_eventd received the specified event.
Solution:This message is informational only, and does not require user action.
452202 clcomm: sdoor_sendstream::send
Description:This operation should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
452205 Failed to form the %s command.
Description:The method searches the commands input to the Agent Builder for the occurrence of specific Builder defined variables, e.g. $hostnames, and replaces them with appropriate value. This action failed.
Solution:Check syslog messages and correct the problems specified in prior syslog messages. If the error still persists, report this problem.
452302 Validation failed. Resource property RESOURCE_DEPENDENCIES should contain at least the RAC framework resource of type SUNW.rac_framework or SUNW.rac_framework:*
Description:The resource being created or modified must be dependent upon the RAC framework resource.
Solution:Update the RESOURCE_DEPENDENCIES property to include the RAC framework resource.
452366 The resource '%s' is at resourcetype version '%d' that does not support zones.
Description:The specific resource is at resourcetype version where there is no zones support.
Solution:Upgrade the resource to latest resourcetype version which has zones support.
452552 Extension property <%s> has a value of <%s>
Description:The property is set to the indicated value.
Solution:This message is informational; no user action is needed.
452747 Reaping tcp_rio_client %p [%x]
Description:The replyio subsystem starts deferred processing of a tcp_rio_client object.
Solution:This message is for diagnostic purposes only; no action required.
452923 About to mount %s. Underlying files and directories will be inaccessible.
Description:HAStoragePlus detected that the directory that will become the specified mount point is not empty, hence once mounted, the underlying files will be inaccessible.
Solution:This is an informational message. No user action is required.
453064 Error: ${PROCESS} is not started.
Description:The rgmd depends on a server which is not started. The specified server probably failed to start. This error will prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.
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.
453087 Killed(sigterm) Exiting.
Description:The rtreg server program received a SIGTERM signal and is exiting.
Solution:This is an informational message. No user action is required.
453193 Failure in sending signal to cl_apid.
Description:The update method for the SUNW.Event service was unable to notify the cl_apid following changes to property values.
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.
453919 Pathprefix is not set for resource group %s.
Description:Resource Group property Pathprefix is not set.
Solution:Use scrgadm to set the Pathprefix property on the resource group.
454032 CMM: Quorum device %d (old name %s) configuration has changed.
Description:The configuration (name/access_mode/type) of the specified quorum device was changed as indicated. This change might occur if the previous quorum device was removed from the cluster while this node was down, and a new device was added to the cluster and assigned the same ID as the old device. This configuration change might also occur if the configuration (access_mode or type) of the old quorum device was changed.
Solution:This message is informational; no user action is required.
454214 Resource %s is associated with scalable resource group %s. AffinityOn set to TRUE will be ignored.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
454247 Error: Unable to create directory <%s> for scha_control timestamp file
Description:The rgmd is unable to access the directory used for the anti-"pingpong" feature, and cannot create the directory (which should already exist). This may prevent the anti-pingpong feature from working, which may permit a resource group to fail over repeatedly between two or more nodes. The failure to access or create the directory might indicate a more serious problem on the 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.
454584 Error: more than one rpc.pmfd is running; will retry
Description:The rpc.pmfd is probably in the process of forking a process to monitor. The script will retry.
Solution:This is an informational message only: No user action is necessary.
454607 INTERNAL ERROR: Invalid resource extension property type <%d> on resource <%s>; aborting node
Description:An attempted creation or update of a resource has failed because of invalid resource type data. This may indicate CCR data corruption or an internal logic error in the rgmd. The rgmd will produce a core file and will force the node to halt or reboot.
Solution:Use clresource show -v and clresourcetype show -v to examine resource properties. If the resource or resource type properties appear to be corrupted, the CCR might have to be rebuilt. If values appear correct, this may indicate an internal error in the rgmd. Retry the creation or update operation. If the problem recurs, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
454930 Scheduling class %s not configured
Description:An attempt to change the thread scheduling class failed, because the scheduling class was not configured.
Solution:Configure the system to support the desired thread scheduling class.
456015 Validate - mysqladmin %s nonexistent or nonexecutable
Description:The mysqladmin command does not exist or is not executable.
Solution:Make sure that MySQL is installed correctly or right base directory is defined.
456036 File system checking is disabled for global 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. 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.
456053 Could not commit zone cluster %s configuration.
Description:The process_cmd_log was unable to commit the zone cluster configuration.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
456566 Validate_sbp - The application resource group %s is not created
Description:The specified application resource group is not configured.
Solution:Make sure that the application resource group is created.
456853 %s can't DOWN.
Description:This means that the Logical IP address could not be set to DOWN.
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.
457114 fatal: death_ff->arm failed
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.
457121 Failed to retrieve the host information for %s: %s.
Description:The data service failed to retrieve the host information.
Solution:If the logical hostname and shared address entries are specified in the /etc/inet/hosts file, check that the entries are correct. Verify the settings in the /etc/nsswitch.conf file include "files" for host lookup. If these are correct, check the health of the name server. For more error information, check the syslog messages.
457308 No SUNW.qfs resource required to run INIT method.
Description:There are no SUNW.qfs resources required to invoke INIT method.
Solution:This is an informational message; no user action is needed.
457918 Validate - Userid %s is not a member of group informix
Description:The user is not a member of the group informix.
Solution:Ensure the user is a member of the group informix.
458373 fatal: cannot create thread to notify President of state changes
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.
458880 event lacking correct names
Description:The cl_apid event cache was unable to store an event because of the specified reason.
Solution:No user action is required.
459216 Error determining the resource name
Description:The program could not determine the resource name.
Solution:Investigate possible RGM, DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
459485 Error: could not start the Derby server because of an internal error.
Description:The Derby command server could not be started because of an internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
460452 %s access error: %s Continuing with the scdpmd defaults values
Description:No scdpmd config file (/etc/cluster/scdpm/scdpmd.conf) has been found. The scdpmd daemon uses default values.
Solution:No user action is required.
461673 Function: validate: Directory %s does not exist, an existing directory is required
Description:The directory mentioned in the parameter file for the PGROOT or PGDATA variable does not exist.
Solution:Fix the parameter file and provide an existing directory for the variable PGROOT or PGDATA.
461872 check_cmg - Actual (%s) FND processes running is below limit (%s)
Description:While probing the Oracle E-Business Suite concurrent manager, the actual percentage of processes running is below the user defined acceptable limit set by CON_LIMIT when the resource was registered.
Solution:Determine why the number of actual processes for the concurrent manager is below the limit set by CON_LIMIT. The concurrent manager resource will be restarted.
461944 ORACLE_SID is set to a default value. Assign a
Description:The value of the ORACLE_SID extension property should be valid and not the default value of " ".
Solution:The default value is used to facilitate the creation of certain resource and resource group configurations. If the instance needs to be brought online, change the ORACLE_SID extension property value to the valid value for that instance using the appropriate Sun Cluster commands and retry bringing the resource online.
462032 ct_tmpl_set_informative: %s
Description:The libclcontract code was unable to configure a process template in which to launch the requested service. Consequently, the process that is using libclcontract was unable to launch the process under its control.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
462048 Telemetry data service start method timed out
Description:The telemetry data service could not start before the configured timeout elapsed.
Solution:This message is informational; no user action needed.
462083 fatal: Resource <%s> update failed with error <%d>; aborting node
Description:Rgmd failed to read updated resource 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.
462253 fattach: %s
Description:The fattach failed for the specified reason. The specified program will be terminated.
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.
462632 HA: repl_mgr: exception invalid_repl_prov_state %d
Description:The system did not perform this operation on the primary object.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
463171 Probe for derby data service successful
Description:Derby data service probe method completed successfully.
Solution:This message is informational; no user action needed.
463828 Failed to start Kerberos daemons.
Description:The krb5kdc and kadmind daemons had failed to come up.
Solution:Check the syslog messages for further information on specific configuration issues of Kerberos.
463953 %s failed to complete
Description:The command failed.
Solution:Check the syslog and /var/adm/messages for more details.
464111 validate: Directory %s does not exist
Description:The specified directory does not exist
Solution:Set the directory name to the right directory.
464484 Function: validate: Port %s is not numeric
Description:In the parameter file, there is a non numeric character in the value for the PGPORT variable.
Solution:Fix the PGPORT variable in the parameter file.
464869 Command %s failed with exit status <%d>.
Description:Failure in executing the command.
Solution:Check the syslog message for the command description. Check whether the system is low in memory or the process table is full and take appropriate action. Make sure that the executable exists.
465295 Command %s failed to complete - unable to catch signal: %d, HA-SAP will continue to start SAP.
Description:Command exited abnormally as process was not able to catch a particular signal.
Solution:Contact your authorized Sun service provider.
465358 fatal: cannot create thread to cleanup_rg_aff
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.
466153 getipnodebyname() timed out.
Description:A call to getipnodebyname(3SOCKET) timed out.
Solution:Check the settings in /etc/nsswitch.conf and make sure that the name resolver is not having problems on the system.
466876 The setnum device path '/dev/%s' is not configured for zone %s. A volume is accessible to a zone cluster when both the set name path and set number path is configured to zone cluster.
Description:The specified set number device path is not configured for the zone.
Solution:Check whether the disk group or specified volumes set for the resource is configured to the specified zone in terms of set number path. If the problem persists even though the devices are properly configured and available in specified zone, contact your authorized Sun service provide with /var/adm/messages of cluster nodes and zone configuration information.
468009 Could not process %s command for zone cluster %s. Error %d.
Description:The process_cmd_log was unable to replay the specified zone cluster command log entry.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
468199 The %s file of the Oracle UNIX Distributed Lock Manager not found or is not executable.
Description:Unable to locale the lock manager binary. This file is installed as a part of Oracle UNIX Distributed Lock Manager (UDLM). The Oracle OPS/RAC will not be able to run on this node if the UDLM is not available.
Solution:Make sure Oracle UDLM package is properly installed on this node.
468477 Failed to retrieve the property %s: %s.
Description:API operation has failed in retrieving the cluster property.
Solution:For property name, check the syslog message. For more details about API call failure, check the syslog messages from other components.
468587 Unable to register for version upgrade callbacks with version manager: %s
Description:An exception was raised when RGM tried to register for version upgrade callbacks with the Version Manager.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
468732 Too many modules configured for autopush.
Description:The system attempted to configure a clustering STREAMS module for autopush but too many modules were already configured.
Solution:Check in your /etc/iu.ap file if too many modules have been configured to be autopushed on a network adapter. Reduce the number of modules. Use autopush(1m) command to remove some modules from the autopush configuration.
469752 fatal: could not start rgm reconfig thread
Description:Could not start RGM reconfiguration thread. This may be due to 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.
470086 sigaction(2) failed while querying disposition for signal SIG%s: error %s
Description:The rgmd_starter was unable to query the signal disposition for a signal number because the sigaction(2) function failed. The message contains the system error. rgmd_starter cannot launch an rgmd daemon.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
470528 Could not resolve 'ifconfig_proxy_server' in the name server. Exiting.
Description:The ifconfig proxy program could not resolve the ifconfig proxy server object from the local nameserver.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
471182 cl_execd: unable to create failfast object.
Description:The cl_execd program was not able to register with failfast.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
471241 Probing SAP Message Server times out with command %s.
Description:Checking SAP message server with utility lgtst times out. This may happen under heavy system load.
Solution:You might consider increasing the Probe_timeout property. Try switching the resource group to another node using scswitch (1M).
471587 Resource <%s> is restarting too often on <%s>. Sleeping for <%d> seconds.
Description:A misconfiguration in the application and/or its monitor probe, or an administrative action is causing continuous restart requests to be sent to the RGM. Hence RGM is blocking the requests for some time, so that too many restarts are prevented.
Solution:Check accompanying syslog messages being issued from the application or the fault monitor of the data service to diagnose any misconfiguration issues.
471757 %s : %s
Description:Self explanatory.
Solution:Check the syslog messages and try to resolve the problem. If the problem persists, contact your authorized Sun service provider.
471788 Unable to resolve hostname %s
Description:The cl_apid could not resolve the specified hostname. If this error occurs at startup of the daemon, it may prevent the daemon from starting. Otherwise, it will prevent the daemon from delivering an event to a CRNP client.
Solution:If the error occurred at startup, verify the integrity of the resource properties specifying the IP address on which the CRNP server should listen. Otherwise, no action is required.
472060 CMM: Halting because realtime callout processing is not working on this node. current_time %lld last_update_time %lld
Description:This node is being aborted from the cluster as the CMM's real-time callout monitor thread did not run for more than the maximum allowed period. This is caused by heavy interrupt processing load or a blocked interrupt.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
472185 Failed to retrieve the resource group property %s for %s: %s.
Description:The query for a property 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.
472312 Stop - can't determine Qmaster pid file - %s/qmaster.pid does not exist.
Description:The file '${qmaster_spool_dir}/qmaster.pid' was not found. '${qmaster_spool_dir}/qmaster.pid' is the second argument to the 'Shutdown' function. 'Shutdown' is called within the stop script of the sge_qmaster-rs resource.
Solution:Confirm the file 'qmaster.pid' exists. Said file should be found in the respective spool directory of the daemon in question.
472444 Stop - can't determine sge_schedd pid file - %s/schedd/schedd.pid does not exist.
Description:The file '${qmaster_spool_dir}/schedd.pid' was not found. '${qmaster_spool_dir}/schedd.pid' is the second argument to the 'Shutdown' function. 'Shutdown' is called within the stop script of the sge_schedd-rs resource.
Solution:Confirm the file 'schedd.pid' exists. Said file should be found in the respective spool directory of the daemon in question.
472501 Failed to disable resource: %s.
Description:An attempt to disable the specified resource on this node failed.
Solution:Contact your authorized Sun service provider for further assistance in diagnosing the problem.
472748 Error: /usr/ucb/ps is not installed!
Description:HA-Oracle attempted to determine if tnslsnr was running with the command /usr/ucb/ps. The /usr/ucb/ps command does not exist or is not executable.
Solution:Please check that /usr/ucb/ps exists and has correct permissions. If /usr/ucb/ps does not exist, install the package SUNWscpu. Alternatively, shorten the listener name or path to tnslnsr so that the length of the tnslsnr command is less than 80 characters.
473021 in libsecurity uname sys call failed: %s
Description:A client was not able to make an rpc connection to a server (rpc.pmfd, rpc.fed or rgmd) because the host name could not be obtained. The system error message 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.
473141 Resource is disabled, stopping database.
Description:The HADB database will be stopped because the resource is being disabled.
Solution:This is an informational message, no user action is needed.
473257 scf_transaction_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.
473361 Removing Device service %s
Description:Informational message from scdidadm.
Solution:No user action required.
473571 Mismatch between the resource group %s node list preference and the global device %s node list preference detected.
Description:HAStoragePlus detected that the RGM node list preference and the DCS device service node list preference do not match. This is not allowed because AffinityOn is set to True.
Solution:Correct either the RGM node list preference or the DCS node list preference.
473653 Failed to retrieve the resource type handle for %s while querying for property %s: %s.
Description:Access to the object named 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.
474256 Validations of all specified global device services complete.
Description:All device services specified directly or indirectly via the GlobalDevicePath and FilesystemMountPoint extension properties respectively are found to be correct. Other Sun Cluster components like DCS, DSDL, RGM are found to be in order. Specified file system mount point entries are found to be correct.
Solution:This is an informational message, no user action is needed.
474413 Validate - sge_schedd file does not exist or is not executable at %s/sge_schedd
Description:The file sge_schedd can not be found, or is not executable.
Solution:Confirm the file '${SGE_ROOT}/bin/<arch>/sge_schedd' both exists at that location, and is executable.
474468 Function: validate: The trigger file %s not set in %s
Description:The trigger file specified in the configuration file is not mentioned in the recovery.conf.
Solution:Fix the configuration file or the recovery.conf.
474690 clexecd: Error %d from send_fd
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.
475251 Error: Sun Cluster software does not support transitioning from run level 3 to levels S (single-user), 1, or 2; halting
Description:A transition which is not allowed by Sun Cluster software has been requested. Sun Cluster software does not permit transition from run level 3 to run level 1, 2 or S. The node is halted.
Solution:Reboot the node.
475259 Membership : State machine for '%s' encountered an invalid event, currently in '%s'.
Description:The membership state machine for this membership encountered an invalid event.
Solution:In this scenario, more syslog messages will appear. Search for these subsequent syslog messages and follow the suggested recovery steps. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.
475398 Out of memory (memory allocation failed):%s.%s
Description:There is not enough swap space on the system.
Solution:Add more swap space. See swap(1M) for more details.
475562 Successfully stopped the Node Agent %s and the server instances.
Description:This is an informational message indicating that the Node Agent and all its Application Server instances are stopped.
Solution:No user action is required.
475611 Fault monitor probe response time exceeded extended timeout (%d secs). The database should be checked for hangs or locking problems, or the probe timeout should be increased accordingly
Description:The time taken for the last fault monitor probe to complete was greater than the probe timeout, which had been increased by 10% because of previous slow response.
Solution:The database should be investigated for the cause of the slow response and the problem fixed, or the resource's probe timeout value increased accordingly.
476157 Failed to get the pmf_status. Error: %s.
Description:A method could not obtain the status of the service from PMF. The specific cause for the failure may be logged with the message.
Solution:Look in /var/adm/messages for the cause of failure. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
476399 Cannot initialize the ORB. Error %d
Description:The process_cmd_log was unable to initialize the ORB.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
476649 Could not lookup %s scheduling class info: %s
Description:The server was not able to determine the scheduling mode info, 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.
476979 scds_pmf_stop() timed out.
Description:Shutdown through PMF timed out.
Solution:No user action is required.
477116 IP Address %s is already plumbed.
Description:An IP address corresponding to a hostname in this resource is already plumbed on the system. You can not create a LogicalHostname or a SharedAddress resource with hostnames that map to that IP address.
Solution:Unplumb the IP address or remove the hostname corresponding to that IP address from the list of hostnames in the SUNW.LogicalHostname or SUNW.SharedAddress resource.
477291 scnetapp fatal error - Unable to open CCR
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
477296 Validation failed. SYBASE ASE STOP_FILE %s not found.
Description:File specified in the STOP_FILE extension property was not found. Or the file specified is not an ordinary file.
Solution:Please check that file specified in the STOP_FILE extension property exists on all the nodes.
477378 Failed to restart the service.
Description:Restart attempt of the data service is failed.
Solution:Check the syslog messages that are occurred just before this message to check whether there is any internal error. In case of internal error, contact your Sun service provider. Otherwise, any of the following situations may have happened. 1) Check the Start_timeout and Stop_timeout values and adjust them if they are not appropriate. 2) This might be the result of lack of the system resources. Check whether the system is low in memory or the process table is full and take appropriate action.
477816 clexecd: priocntl returned %d. Exiting.
Description:The 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.
478328 Failed to retrieve property %s of storage %s : %s
Description:An error occurred while a property of the resource was being retrieved.
Solution:Ensure that the property is defined for the resource. If the property is defined, investigate possible RGM or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
478523 Could not mount '%s' because there was an error (%d) in opening the directory.
Description:While mounting a Cluster file system, the directory on which the mount is to take place could not be opened.
Solution:Fix the reported error and retry. The most likely problem is that the directory does not exist - in that case, create it with the appropriate permissions and retry.
478877 scvxvmlg error - mkdirp(%s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
479184 Error determining the zonename.
Description:The cl_boot_check service could not determine the zonename.
Solution:This message might indicate an internal error. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
479213 Monitor server terminated.
Description:Graceful shutdown did not succeed. Monitor server processes were killed in STOP method. It is likely that adaptive server terminated prior to shutdown of monitor server.
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.
479308 There should be at least one Network Resource in this resource group
Description:Since DAS resource is a Failover Resource, the Failover IP address that DAS uses must be created in this Resource Group.
Solution:Create the Failover IP address resource in this Resource Group.
479331 Error in res %s execution Stop
Description:Not able to process the resource to stop all the services. Previous messages to this should give the reason.
Solution:If it fails after couple of retries, contact your SUN vendor for assistance.
479442 in libsecurity could not allocate memory
Description:A server (rpc.pmfd, rpc.fed or rgmd) was not able to start, or a client was not able to make an rpc connection to the server. This problem can occur of the machine has low memory. An error message is output to syslog.
Solution:Determine if the host is low on memory. If not, save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
479591 File %s is not configured, exiting.
Description:The specified file has not been configured.
Solution:Look at the file's man page to determine how to properly configure the file.
480068 Function: validate - Directory for the socket file %s does not exist
Description:The directory specified in the PGHOST variable does not exist.
Solution:Create the directory. None if it was a lost mount.
480354 Error on line %ld: %s
Description:Indicates the line number on which the error was detected. The error message follows the line number.
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.
481187 Validate - smbconf %s does not exist
Description:The smb.conf file does not exist.
Solution:Check the correct pathname for the Samba smb.conf file was entered when registering the Samba resource and that the smb.conf file exists.
481570 qdmd: An error occurred while reading keys on quorum device %s
Description:The quorum device monitoring daemon encountered an error while performing the quorum_read_keys operation on the indicated device.
Solution:Unconfigure the quorum device and reconfigure it. If that fails, replace the quorum device.
481848 %s: received callback from CZMM for cluster %s, seqnum = %llu
Description:Informational message from the cznetd daemon.
Solution:No user action is required.
481983 Misconfiguration of the RAC framework resource group. The Oracle UDLM and the Sun Cluster native SKGXN are configured, reverting to the Oracle UDLM based SKGXN.
Description:The Sun Cluster native SKGXN interface appears to be installed while both the Oracle UDLM package (ORCLudlm) and the RAC framework UDLM resource are installed.
Solution:Configure the RAC framework resource group to have only one SKGXN interface, either the Oracle UDLM or the Sun Cluster native and then start the resource group.
482034 scvxvmlg fatal error - dcs_get_service_names_of_class(%s) failed, returned %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.
482231 Failed to stop fault monitor, %s.
Description:Error in stopping the fault monitor.
Solution:No user action needed.
482531 IPMP group %s has unknown status %d. Skipping this IPMP group.
Description:The status of the IPMP group is not among the set of statuses that is known.
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.
482901 Can't allocate binding element
Description:Client affinity state on the node has become incomplete due to unexpected memory shortage. New connections from some clients that have existing connections with this node might go to a different node as a result.
Solution:If client affinity is a requirement for some of the sticky services, say due to data integrity reasons, these services must be brought offline on the node, or the node itself should be restarted.
483409 Validate - User mqm does not exist
Description:The userid mqm does not exist.
Solution:The userid mqm must exist within /etc/passwd.
483446 Fault-monitor successfully stopped.
Description:The fault monitor of this ScalMountPoint resource was stopped successfully. This message is an informational message.
Solution:No user action is required.
483858 Must set at least one of Port_List or Monitor_Uri_List.
Description:When creating the resource a Port_List or Monitor_Uri_List must be specified.
Solution:Run the resource creation again specifying either a Port_List or Monitor_Uri_List.
484189 Failed to disable %s service
Description:The Solaris service management facility failed to disable the service instance that the fault management resource identifier (FMRI) in the /var/adm/messages specifies.
Solution:Run the command 'svcadm disable <fmri>' to disable the service instance. Then run the command 'svccfg -s <fmri>' to enable you to modify the configuration of the service instance interactively. Use the subcommand 'addpg startd framework' to add the started and framework property group and the subcommand 'setprop startd/duration = astring: transient' to set the duration to transient. After modifying the configuration of the service instance, run the command 'svcadm enable <fmri>' to enable the service instance. Then run the command 'svcs -x <service>' command to verify that the service is online. If the problem persists, contact your Sun Support representative for further assistance.
484248 SCSLM pools facility is disabled
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
484330 Function: check_sczbt - who -r did not run successfully (return code %s) in the non-global zone %s, try again in 5 seconds
Description:The who -r command did not run successfully in the configured non-global zone. The state is checked again in 5 seconds.
Solution:No user action is required.
484513 Failed to retrieve the probe command with error <%d>. Will continue to do the simple probe.
Description:The fault monitor failed to retrieve the probe command from the cluster configuration. It will continue using the simple probe to monitor the application.
Solution:No user action is required.
484726 Resource %s named in one of the resource dependencies properties is not a SharedAddress resource.
Description:The dependee resource is not a SharedAddress resource.
Solution:Specify at least one SharedAddresses resource as a dependee.
485462 Error: duplicate method <%s> launched on resource <%s> in resource group <%s> on node <%s>
Description:Due to an internal error, the rgmd state machine has attempted to launch two different methods on the same resource on the same node, simultaneously. The rgmd will reject the second attempt and treat it as a method failure.
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.
485464 clcomm: Failed to allocate simple xdoor server %d
Description:The system could not allocate a simple xdoor server. This can happen when the xdoor number is already in use. This message is only possible on debug systems.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
485680 reservation warning(%s) - Unable to lookup local_only flag for device %s.
Description:The device fencing program was unable to determine if the specified device is marked as local_only. This device will be treated as a non-local_only device and nodes not within the cluster will be fenced from it.
Solution:If the device in question is marked as local_only and is being used as the boot device or the mirror of a boot device for a node, then that node may be unable to access this device and hence, unable to boot. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
485759 transition '%s' failed for cluster '%s'
Description:The mentioned state transition failed for the cluster. 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.
485941 Function: check_sczsh - %s does not exist or is not executable in zone %s - early End
Description:The command specified for variable ServiceProbeCommand 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 ServiceProbeCommand 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 reregister the resource, make sure the variable ServiceProbeCommand is properly set within the ${PARAMETERDIR}/sczsh_${RS} parameter file.
485942 (%s) sigprocmask failed: %s (UNIX errno %d)
Description:Call to sigprocmask() failed. The "sigprocmask" man page describes possible error codes. udlmctl will exit.
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.
486037 cl_execd: Attempt to set scheduling class to Fixed returned %d. Exiting.
Description:cl_execd program failed to set the priority and the scheduling class to Fixed for the task in execution.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
486057 J2EE probe didn't return expected message: %s
Description:The data service received an unexpected reply from the J2EE engine.
Solution:Informational message. No user action is needed.
486201 Disabling of %s under smf(5), failed. Admin intervention may be required.
Description:The initialization script was not able to disable krb5kdc or kadmind under SMF.
Solution:Check the state of krb5kdc or kadmind using "svcs -x".
486301 Confdir_list %s is not defined via macro CONFDIR_LIST in script %s/%s/db/sap/lccluster.
Description:Confdir_list path which is listed in the message is not defined in the script 'lccluster' which is listed in the message.
Solution:Make sure the path for Confdir_list is defined in the script lccluster using parameter 'CONFDIR_LIST'. The value should be defined inside the double quotes, and it is the same as what is defined for extension property 'Confdir_list'.
486484 Error: The Oracle CRS shutdown script "%s" is missing.
Description:The Oracle CRS shutdown script could not be located.
Solution:Ensure that Oracle CRS is correctly installed.
486841 SIOCGLIFCONF: %s
Description:The ioctl command with this option failed in the cl_apid. 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.
487022 The networking components for scalable resource %s have been configured successfully for method %s.
Description:The calls to the underlying scalable networking code succeeded.
Solution:This is an informational message, no user action is needed.
487148 Could not find a mapping for %s in %s or %s. It is recommended that a mapping for %s be added to %s.
Description:No mapping was found in the local hosts or ipnodes file for the specified ip address.
Solution:Applications might use hostnames instead of ip addresses. It is recommended to have a mapping in the hosts and/or ipnodes file. Add an entry in the hosts and/or ipnodes file for the specified ip address.
487270 Sun Java Systems Application Server <%s> is already running on this node outside of Sun Cluster. The start of <%s> from Sun Cluster will be aborted.
Description:It is detected that DAS is already running on this node outside of Sun Cluster. The start of DAS from Sun Cluster will be aborted.
Solution:No user action is needed.
487418 libsecurity: create of rpc handle to program %s (%lu) failed, will not retry
Description:A client of the specified server was not able to initiate an rpc connection, after multiple retries. The maximum time allowed for connecting has been exceeded, or the types of rpc errors encountered indicate that there is no point in retrying. An accompanying error message shows the rpc error data. The pmfadm or scha command exits with error. The program number is shown. To find out what program corresponds to this number, use the rpcinfo command. 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.
487484 lkcm_reg: lib initialization failed
Description:The udlm could not register with cmm because lib initialization failed.
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.
487516 Failed to obtain SAM-FS constituent volumes for %s.
Description:HAStoragePlus was not able to determine the volumes that are part of this SAM-FS special device.
Solution:Check the SAM-FS file system configuration. If the problem persists, contact your authorized Sun service provider.
487574 Failed to alloc memory
Description:A scha_control call failed because the system has run out of swap space. The system is likely to halt or reboot if swap space continues to be depleted.
Solution:Investigate the cause of swap space depletion and correct the problem, if possible.
487827 CCR: Waiting for repository synchronization to finish.
Description:This node is waiting to finish the synchronization of its repository with other nodes in the cluster before it can join the cluster membership.
Solution:This is an informational message, generally no user action is needed. If all the nodes in the cluster are hanging at this message for a long time, look for other messages. The possible cause is the cluster hasn't obtained quorum, or there is CCR metadata missing or invalid. If the cluster is hanging due to missing or invalid metadata, the ccr metadata needs to be recovered from backup. Contact your authorized Sun service provider for assistance.
487835 CCR lookup failed for zone cluster %s
Description:The CCR raised an exception while looking up the clzone_config table.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
488313 Could not start Proxy Daemon.
Description:The agent failed to startup the Monitor of a resource of type SUNW.scalable_rac_server_proxy.
Solution:Contact your Sun support representative for further assistance.
488595 Cluster Configuration Repository transformation completed successfully
Description:Cluster Configuration Repository transformation completed successfully.
Solution:This is an informational message, no user action is needed.
488980 HTTP GET Response Code for probe of %s is %d. Failover will be in progress
Description:The status code of the response to a HTTP GET probe that indicates the HTTP server has failed. It will be restarted or failed over.
Solution:This message is informational; no user action is needed.
488988 Unable to open libxml2.so.
Description:The SUNW.Event validate method was unable to find the libxml2.so library on the system. The Event service will not be started.
Solution:Install the libxml2.so library.
489438 clcomm: Path %s being drained
Description:A communication link is being removed with another node. The interconnect might have failed or the remote node might be down.
Solution:Any interconnect failure should be resolved, and/or the failed node rebooted.
489465 Severe XDR Error, Cannot recover.
Description:An internal error has occurred in the inter-process communication between rgmd and another clustering process. Other related error messages might precede or follow this one in the syslog output.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
489615 The dependent SUNW.wait_zc_boot resource '%s' of SUNW.qfs resource '%s' is not online. Skipping this resource ...
Description:The dependent SUNW.wait_zc_boot resource of specified SUNW.qfs resource is not online. It means the shared qfs file systems are not mounted by INIT method of SUNW.qfs as they are blocked by INIT method of SUNW.wait_zc_boot resource. Hence skipping the resource to avoid invoking INIT method explicitly.
Solution:This is an informational message; no user action is needed.
489903 setproject: %s; attempting to continue the process with the system default project.
Description:Either the given project name was invalid, or the caller of setproject() was not a valid user of the given project. The process was launched with project "default" instead of the specified project.
Solution:Use the projects(1) command to check if the project name is valid and the caller is a valid user of the given project.
489913 The state of the path to device: %s has changed to OK
Description:A device is seen as OK.
Solution:No user action is required.
490049 Giveover attempt failed for %s after exhausting retries: resource group is currently stuck in reconfiguration.
Description:Repeated reconfiguration errors while attempting to switch over the QFS metadata resource group is likely an error in the cluster software.
Solution:It is likely that the shared QFS file system metadata server has been forcibly unmounted. This can cause problems with proper operation of shared QFS on other nodes. Verify that shared QFS filesystem in use are working properly. If they are not, follow the QFS file system recovery procedures. If this problem persists contact your authorized Sun service provider to determine whether a workaround or patch is available.
490249 Stopping SAP Central Service.
Description:This message indicates that the data service is stopping the SCS.
Solution:No user action needed.
490268 Failfast : Failed to reboot zone %s (zone ID %d) as door upcall to 'zoneadmd' door failed with error code %d. Failfast will halt the zone now.
Description:Failfast failed to reboot zone, because door upcall to zoneadmd daemon failed. Failfast will halt the zone as a result.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
490977 dl_bind ack bad len %d
Description:Sanity check. The message length in the acknowledgment to the bind request is different from what was expected. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
491081 resource %s removed.
Description:This is a notification from the rgmd that the operator has deleted a resource. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
491533 DB_password_file should be a regular file: %s
Description:The DB_password_file extension property needs to be a regular file.
Solution:Give appropriate file name to the extension property. Make sure that the path name does not point to a directory or any other file type. Moreover, the DB_password_file could be a link to a file also.
491579 clcomm: validate_policy: fixed size pool low %d must match moderate %d
Description:The system checks the proposed flow control policy parameters at system startup and when processing a change request. The low and moderate server thread levels must be the same for fixed size resource pools.
Solution:No user action required.
492603 launch_fed_prog: fe_method_full_name() failed for program <%s>
Description:The ucmmd was unable to assemble the full method pathname for the fed program to be launched. This is considered a launch_fed_prog failure.
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.
492781 Retrying to retrieve the resource information: %s.
Description:An update to cluster configuration occurred while resource properties were being retrieved
Solution:This is only an informational message.
492922 Validate callback failed.
Description:The validate callback failed.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
492953 ORACLE_HOME/bin/lsnrctl not found ORACLE_HOME=%s
Description:Oracle listener binaries not found under ORACLE_HOME. ORACLE_HOME specified for the resource is indicated in the message. HA-Oracle will not be able to manage Oracle listener if ORACLE_HOME is incorrect.
Solution:Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.
493130 Could not copy %s to %s
Description:HA-Oracle copies the Oracle shared library used by the fault monitor to a local file system. Without this local copy of the Oracle shared library, the HA-Oracle installation is vulnerable because failures may not be detected when the shared library under <ORACLE_HOME>/lib or <ORACLE_HOME>/lib32 (32-bit installation) is unavailable.
Solution:Verify that the specified Oracle shared library under <ORACLE_HOME>/lib or <ORACLE_HOME>/lib32 (32-bit installation) is readable and that the local directory/file as specified in the error message is writable. There should be sufficient disk space in the local file system to copy the shared library. You may manually copy the shared library by using 'cp -p <source> <destination>' as 'root' (replace the source and destination by the appropriate pathnames as indicated in the error message).
493261 Could not remove node %s from device service %s, error = %d
Description:Failed to remove the indicated node from a device service because of the indicated error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
493641 Failed to open file %s.
Description:The master configuration file under /etc/opt/SUNWsamfs for the specified shared QFS file system could not be opened.
Solution:Determine whether the file exists. If the file exists, ensure that the file-access permissions are correct. If the file does not exist, ensure that the specified file system is correctly configured with Sun Cluster.
493657 Unable to get status for IPMP group %s.
Description:The specified IPMP group is not in functional state. Logical host resource can't be started without a functional IPMP group.
Solution:LogicalHostname resource will not be brought online on this node. Check the messages (cl_pnmd errors) that encountered just before this message for any IPMP or adapter problem. Correct the problem and rerun the clresourcegroup command.
494475 Function: val_in_global - Not in the global zone
Description:A start, stop or probe command was used from the local zone.
Solution:Use the start, stop and probe commands from the global zone only.
494478 resource %s in resource group %s has requested %s on %s.
Description:The RGM has received a request for the specified scha_control(1HA) or scha_control(3HA) operation.
Solution:No user action required.
494534 clcomm: per node IP config %s%d:%d (%d): %d.%d.%d.%d failed with %d
Description:The system failed to configure IP communications across the private interconnect of this device and IP address, resulting in the error identified in the message. This happened during initialization. Someone has used the "lo0:1" device before the system could configure it.
Solution:If you used "lo0:1", use another device. Otherwise, Contact your authorized Sun service provider to determine whether a workaround or patch is available.
494913 pmfd: unknown action (0x%x)
Description:An internal error has occurred in the rpc.pmfd server. This should not happen.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
495386 INTERNAL ERROR: %s.
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.
495529 Prog <%s> failed to execute step <%s> - <%s>
Description:The ucmmd failed to execute a step.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
495587 CCR commit transaction failed for zone cluster %s
Description:The CCR raised an exception while committing a transaction on the zone cluster configuration table.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
495710 Stopping oracle server using shutdown immediate
Description:Informational message. Oracle server will be stopped using 'shutdown immediate' command.
Solution:No user action is required.
496555 couldn't query zonename
Description:A scalable service resource attempting to execute in a non-global zone was unable to find the zone name in Solaris. 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.
496746 reservation error(%s) - USCSI_RESET failed for device %s, returned%d
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.
496749 Membership : Consecutive 'coming-up' notifications received by membership (%s).
Description:The membership subsystem received consecutive notifications saying that a local member component came up. Normally, a notification about the local member component going down should arrive between two notifications that say that the local member component came up.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
496814 restart_dependency - Dependent resource to resource %s has been restarted, restart this resource %s
Description:-4 a restart of the dependant resource has been noticed, it might be necessary to restart the resource depending on
Solution:-4 check the validity of the service. there might be a dependency problem, a sub resource has been restarted, and functionality might have been impaired
496884 Despite the warnings, the validation of the hostname list succeeded.
Description:While validating the hostname list, non fatal errors have been found.
Solution:This is informational message. It is suggested to correct the errors if applicable. For the error information, check the syslog messages that have been encountered before this message.
497704 Creation of resource <%s> failed because the inter-cluster weak dependencies could not be set
Description:Resource creation failed due to specification of invalid inter cluster dependencies.
Solution:Check the remote cluster name or remote resource name and retry the same command.
497867 open64 pbundle: %s
Description:The libclcontract code was unable to open a file in the /system/contract/process/ directory. Consequently, the process that is using libclcontract was unable to receive contract events. That process will exit.
Solution: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.
498266 Could not delete inter-cluster resource group affinity information on the targetcluster; source RG = <%s>, target RG_affinity = <%s>
Description:The indicated source resource group on the local cluster is being deleted. This resource group had the indicated inter-cluster target RG affinity. Sun Cluster was unable to remove the affinity information on the target cluster. Possible cause could be that the remote zone cluster is down, or the target affinity rg is switching, or the remote target affinity rg itself is invalid
Solution:No user action is required.
498582 Attempt to load %s failed: %s.
Description:A shared address resource was in the process of being created. In order to prepare this node to handle scalable services, the specified kernel module was attempted to be loaded into the system, but failed.
Solution:This might be the result from the lack of system resources. Check whether the system is low in memory and take appropriate action (e.g., by killing hung processes). For specific information check the syslog message. After more resources are available on the system , attempt to create shared address resource. If problem persists, reboot.
498711 Could not initialize the ORB. Exiting.
Description:clexecd program was unable to initialize its interface to the low-level clustering software.
Solution:This might occur because the operator has attempted to start clexecd program on a node that is booted in non-cluster mode. If the node is in non-cluster mode, boot it into cluster mode. If the node is already in cluster mode, contact your authorized Sun service provider to determine whether a workaround or patch is available.
498909 accept: %s
Description:The cl_apid received the specified error from accept(3SOCKET). The attempted connection was ignored.
Solution:No user action is required. If the problem persists, 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.
498946 Validate_sbp - MySQL resource %s is configured for something else
Description:The specified mysql replication resource is configured for something else.
Solution:Make sure that the defined resource is either unconfigured, or is the desired MySQL replication resource.
499382 Request to mount QFS file systems is failed : %s.
Description:The zone boot handler received failure status for the request to RGM to mount the shared qfs file systems.
Solution:Investigate the zone boot log messages and rectify the problem. If the problem persists after rebooting the zone, contact your authorized Sun service provider with a copy of /var/adm/messages files on all nodes.
499486 Unable to set socket flags: %s.
Description:Failed to set the non-blocking flag for the socket used in communicating with the application.
Solution:This is an internal error, no user action is required. Also contact your authorized Sun service provider.
499715 Error in scha_resourcegroup_get
Description:Error in reading the resource group
Solution:Verify that the RGM functionalities are working and if the resource group is present. Contact your SUN vendor for more help.
499756 CMM: Node %s: joined cluster.
Description:The specified node has joined the cluster.
Solution:This is an informational message, no user action is needed.
499775 resource group %s added.
Description:This is a notification from the rgmd that a new resource group has been added. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
499796 reservation notice(%s) - MHIOCENABLEFAILFAST success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action required.
499903 Error %d running quotacheck for %s
Description:The /usr/sbin/quotacheck command failed for $mountp.
Solution:The system administrator should run the /usr/sbin/quotacheck command manually. If that succeeds, also run /usr/sbin/quotaon. If the quotacheck attempt fails, stop any applications that are using the file system and attempt the quotacheck command again.
499940 Attempted client registration would exceed the maximum clients allowed: %d
Description:The cl_apid refused a CRNP client registration request because it would have exceeded the maximum number of clients allowed to register.
Solution:If you wish to provide access to the CRNP service for more clients, modify the max_clients parameter on the SUNW.Event resource.
Message IDs 500000–599999
This section contains message IDs 500000–599999.
500054 Check_switchover - the check for remote MySQL connectivity failed for the replicated component %s
Description:The check for the remote mysql connectivity failed
Solution:Ensure that the remote MySQL database is working
500095 The "%s" command returned error %s, unable to start the UCMMD under the PMMD.
Description:The command used to launch the UCMMD has failed.
Solution:Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Refer to the documentation of Sun Cluster support for Real Application Clusters. If the problem persists, contact your Sun service representative.
500193 Validate_replication_rs - MySQL resource %s does not exist
Description:The defined real MySQL resource (-r option) does not exist.
Solution:Make sure that defined resource exists.
500540 QUORUM_GENERIC: quorum_register error: writing registration key on quorum device %s failed with error code %d.
Description:An error was encountered when placing the node's registration key on a specified quorum device. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
501495 Validation failed. The RAC framework resource %s that is specified in the RESOURCE_DEPENDENCIES property is not in any of the resource groups specified by the resource group property RG_AFFINITIES.
Description:The resource being created or modified should be dependent upon the rac_framework resource in the RAC framework resource group.
Solution:If not already created, create the scalable resource group containing RAC framework resource and its associated resources. Specify this resource's dependency on the RAC framework by updating the RESOURCE_DEPENDENCIES property, and ensure that the RAC framework resource group is a part of the strong positive affinity (++) list specified in the RG_AFFINITIES property value for the resource group containing the proxy resource.
501628 Function: check_sczbt - runlevel did not run successfully (return code %s) in the non-global zone %s, try again in 5 seconds
Description:The run-level command did not run successfully in the configured non-global zone. The state is checked again in 5 seconds.
Solution:No user action is required.
501632 Incorrect syntax in the environment file %s. Ignoring %s
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 Lines starting with " VARIABLE is expected to be a valid Korn shell variable that starts with alphabet or "_" and contains alphanumerics and "_".
Solution:Please check the environment file and correct the syntax errors. Do not use export statement in environment file.
501723 Insufficient memory. Exiting.
Description:process_cmd_log was unable to allocate memory.
Solution:Ensure that the cluster node has sufficient memory.
501733 scvxvmlg fatal error - _cladm() failed
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.
501763 recv_request: t_alloc: %s
Description:Call to t_alloc() failed. The "t_alloc" man page describes possible error codes. udlm will exit and the node will abort.
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.
501981 Valid connection attempted from %s: %s
Description:The cl_apid received a valid client connection attempt from the specified IP address.
Solution:No user action is required. If you do not wish to allow access to the client with this IP address, modify the allow_hosts or deny_hosts as required.
502022 fatal: joiners_read_ccr: exiting early because of unexpected exception
Description:The low-level cluster machinery has encountered a fatal error. The rgmd 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 rgmd core file. Contact your authorized Sun service provider for assistance in diagnosing the problem.
502258 fatal: Resource group <%s> create failed with error <%s>; aborting node
Description:Rgmd failed to read new 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.
502326 UNRECOVERABLE ERROR: Reading mount point from %s failed with error code %s
Description:Reading mount point from ${QL_LU_CONTINUE} failed with error code ${retval}
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
502438 IPMP group %s has status %s.
Description:The specified IPMP group is not in functional state. Logical host resource can't be started without a functional IPMP group.
Solution:LogicalHostname resource will not be brought online on this node. Check for messages (cl_pnmd errors) encountered just before this message for any IPMP or adapter problem. Correct the problem and rerun the clresourcegroup command.
502659 ucmmd to retrieve version from version manager: %s
Description:ucmmd got a nil reference to the version manager and hence failed to retrieve the version.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
502943 SCSLM <%s> is not a regular file
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
503686 CMM: Node %d has version %d higher than the local version %d
Description:The configuration information shows that the node supports a higher version than the currently running software can support. This happens when old software is loaded onto a machine.
Solution:Upgrade the software on this node to support the version shown in the configuration information.
503803 scha_resource_get() failed for MDS Resource %s : %s
Description:A call to scha_resource_get() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
503817 No PDT Dispatcher thread.
Description:The system has run out of resources that is required to create a thread. The system could not create the connection processing thread for scalable services.
Solution:If cluster networking is required, add more resources (most probably, memory) and reboot.
503911 The action to be taken as determined by scds_fm_action is failover. However the application is not being failed over because %s. The application is left as-is. Probe quitting ...
Description:Based on the restart history, the fault monitor decided for application failover. However the application is not being failed over because of the specified reason. The probe is quitting because it does not have any application to monitor.
Solution:The application or the monitor is not working properly. Correct the problem and restart the application and/or its monitor.
504050 The current resource-type version (%d) of ScalMountPoint does not support zone cluster. Create the resource with the latest available resource-type version.
Description:Self explanatory.
Solution:Register the latest available ScalMountPoint resource type, and create the resource with that version. If the problem persists contact your authorized Sun service provider.
504363 ERROR: process_resource: resource <%s> is pending_update but no UPDATE method is registered
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
504559 FED XDR Buffer Shortfall while encoding return arguments API num = %d, will retry.
Description:A non-fatal error occurred while rpc.fed was marshalling arguments for a remote procedure call. The operation will be retried 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.
505040 Failed to allocate memory.
Description:HAStoragePlus ran out of resources.
Solution:Usually, this means that the system has exhausted its resources. Check if the swap file is big enough to run Sun Cluster software.
505101 Found another active instance of clexecd. Exiting daemon_process.
Description:An active instance of clexecd program is already running on the node.
Solution:This would usually happen if the operator tries to start the clexecd program by hand on a node which is booted in cluster mode. If that is not the case, contact your authorized Sun service provider to determine whether a workaround or patch is available.
505506 clq_sq_disk: callback_failfast error: quorum error code %d obtained while trying to read keys on quorum device %s.
Description:The quorum subsystem was not able to read the keys from the quorum device. Therefore, the quorum subsystem could not determine if this node is part of the operational cluster. This read operation was expected to succeed. Errors similar to these might occur because of unexpected behavior from the device driver or disk.
Solution:Check for disk failure or contact the device manufacturer for firmware updates.
505840 SCSLM <%s> zone <%s> missing project.cpu-shares
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
505922 Failed to open global zone %s: %s.
Description:Failed to open the specific file.
Solution:Check for specific error in the error messages and rectify the problem.
506381 Custom action file %s contains errors.
Description:The custom action file that is specified contains errors which need to be corrected before it can be processed completely.
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.
506673 Error in scha_res_get of retry cnt prop,res:%s, Err: %s
Description:Cannot read the resource retry count in sc delegated restarter
Solution:Take action depending on the error and contact Sun vendor for more help.
507193 Queued event %lld
Description:The cl_apid successfully queued the incoming sysevent.
Solution:This message is informational only. No user action is required.
507263 Telemetry data service stop method completed sucessfully
Description:The telemetry data service stopped successfully.
Solution:This message is informational; no user action needed.
507882 J2EE engine probe returned http code 503. Temp. not available.
Description:The data service received http code 503, which indicates that the service is temporarily not available.
Solution:Informational message. No user action is needed.
508003 check_pgs: The test database %s is not in the database catalog
Description:The database to monitor does not exist in the database catalog.
Solution:Fix the parameter file to contain the right database name in the SCDB variable, or prepare the database.
508391 Error: failed to load catalog %s
Description:The cl_apid was unable to load the xml catalog for the dtds. No validation will be performed on CRNP xml messages.
Solution:No user action is required. If you want to diagnose the problem, 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.
508671 mmap: %s
Description:The rpc.pmfd server was not able to allocate shared memory for a semaphore, possibly due to low memory, and the system error is shown. The server does not perform the action requested by the client, and pmfadm returns error. An error message is also output to syslog.
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.
509069 CMM: Halting because this node has no configuration info about node %ld which is currently configured in the cluster and running.
Description:The local node has no configuration information about the specified node. This indicates a misconfiguration problem in the cluster. The /etc/cluster/ccr/global/infrastructure table on this node may be out of date with respect to the other nodes in the cluster.
Solution:Correct the misconfiguration problem or update the infrastructure table if out of date, and reboot the nodes. To update the table, boot the node in non-cluster (-x) mode, restore the table from the other nodes in the cluster or backup, and boot the node back in cluster mode.
509136 Probe failed.
Description:Fault monitor was unable to perform complete health check of the service.
Solution:1) Fault monitor would take appropriate action (by restarting or failing over the service). 2) Data service could be under load, try increasing the values for Probe_timeout and Thororugh_probe_interval properties. 3) If this problem continues to occur, look at other messages in syslog to determine the root cause of the problem. If all else fails reboot node.
510343 zc_rgm_halt for zone %s: Could not get reference to membership API object. Exiting.
Description:The zc_rgm_halt failed to get a reference to the membership API object, and thus failed to check whether the zone is part of the zone cluster membership or not. Therefore, zc_rgm_halt will not be able to evacuate resource groups for this zone which belongs to a zone cluster. Support for this zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
510369 sema_wait parent: %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.
510372 Error: /var/run is not mounted; cannot start cl_eventd.
Description:The cl_event init script found that /var/run is not mounted. Because cl_eventd requires /var/run for sysevent reception, cl_eventd will not be started. This error may prevent the event subsystem from working correctly.
Solution:Examine other syslog messages occurring at about the same time to see if the problem with /var/run 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.
510585 Found (%d) did devices and (%d) ctd devices in dg (%s)
Description:The method queried for and found DID and ctd devices.
Solution:No user action is required.
510646 SCSLM <%s> pool_create error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
510675 Successfully updated nsswitch.conf file.
Description:The nsswitch.conf file is successfully updated on the zone cluster.
Solution:No user action is required.
510857 Using the tunable values %s=%d, %s=%d, %s=%d.
Description:This is a notification message about the tunables used by zone handler.
Solution:This is an informational message; no user action is needed.
511177 clcomm: solaris xdoor door_info failed
Description:A door_info operation failed. Refer to the "door_info" man page for more information.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
511749 rgm_launch_method: failed to get method <%s> timeout value from resource <%s>
Description:Due to an internal error, the rgmd daemon was unable to obtain the method timeout for the indicated resource. This is considered a method failure. 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: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 the problem.
512422 WARNING: unknown msg (type %d) was picked up by a lkcm_act, returning LKCM_NOOP
Description:Warning for unknown message picked up during udlm state update.
Solution:No user action is required.
512691 <%s> using fake user name for setproject
Description:Should never occur.
Solution:Verify project database. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
512896 Filer "%s" and directory "%s" not found in CCR
Description:The NAS device is not configured with Sun Cluster. Before the ScalMountPoint resource can be brought online, the NAS device must be configured by using the scnas command.
Solution:Use the scnas command to configure the NAS device with Sun Cluster.
512980 Internal Error: ORACLE_OWNER not set even after successful validation. Shutdown may not be successful in cleaning up all resources.
Description:An internal error occurred while attempting to save the name of the owner of the Oracle installation in a local file for use during shutdown of Oracle.
Solution:After next shutdown of the resource, check to verify if the shutdown completed successfully by cleaning up all the resources. If the problem persists, report it to your Sun support representative.
513986 Waiting for the first partition nodes to come online
Description:During a dual-partition upgrade in a live upgrade scenario, the node is waiting for all the nodes of the first partition to come online in the new boot environment.
Solution:This is a informational message. If the user sees that any of the nodes of the first partition has panicked or hung, then he should abort the upgrade and do a normal upgrade after doing the recovery steps.
514047 select: %s
Description:The cl_apid received the specified error from select(3C). No action was taken by the daemon.
Solution:No user action is required. If the problem persists, 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.
514078 Validate - The keyword INTERFACES have to be set in %s when -T is being used
Description:If USE_CGTP=TRUE was set within /opt/SUNWscdhc/util/dhcp_config then the INTERFACES within /etc/inet/dhcpsvc.conf needs to be set.
Solution:If USE_CGTP=TRUE is required, then ensure that the INTERFACES variable is set within /etc/inet/dhcpsvc.conf. If USE_CGTP=TRUE is required, then ensure that the INTERFACES variable is set within /etc/inet/dhcpsvc.conf. Refer to dhcpsvc.conf(4) man page for further information on INTERFACES.
514234 Error probing devicegroup (%s)
Description:An error occurred during a probe of the disk set or disk group.
Solution:Verify the status of the disk set or disk group. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
514383 ping_timeout %d
Description:The ping_timeout value used by scdpmd.
Solution:No user action is required.
514440 Check__mysql_replication_rs - the check for the MySQL replication resource failed because of replication issues on replication resource %s
Description:The check for the replication status failed
Solution:Fix the replication issues
514574 Upgrade has completed on all the nodes that have joined the cluster
Description:Cluster upgrade has completed on all the nodes that have joined the cluster. Software upgrade might not be complete on any nodes that have not rejoined the cluster.
Solution:This is an informational message, no user action is needed.
514630 The entry in vfstab for mount point '%s' has too few fields.
Description:The entry in vfstab for the specified mount point has fewer fields than are defined for a single vfstab entry.
Solution:Add the missing fields from the entry in vfstab for the mount point and repeat the operation.
514688 Invalid port number %s in the %s property.
Description:The specified system property does not have a valid port number.
Solution:Using clresource, specify the positive, valid port number.
514731 Failed to kill listener process for %s
Description:Failed to kill listener processes.
Solution:No user action is required.
515159 method <%s> completed successfully for resource <%s>, resource group <%s>, node <%s>, time used: %d%% of timeout <%d seconds>
Description:RGM invoked a callback method for the named resource, as a result of a cluster reconfiguration, scha_control GIVEOVER, or clresourcegroup switch. The method completed successfully.
Solution:This is an informational message; no user action is needed.
515225 Validate_sbp - MySQL replication object is not specified in option %s
Description:The required replicated component is not specified.
Solution:Make sure that the replicated component is specified.
515411 CMM: Registered key on and acquired quorum device %d (gdevname %s).
Description:When this node was booting up, it had found only non-cluster member keys on the specified device. After joining the cluster and having its CCR recovered, this node has been able to register its keys on this device and is its owner.
Solution:This is an informational message, no user action is needed.
516089 Oracle commands inaccessible. Forcing shutdown of Oracle by killing Oracle processes and removing any shared memory.
Description:The resource shutdown will attempt to clean up any Oracle processes or shared memory segments. A graceful shutdown could not be attempted as Oracle commands are inaccessible, possibly due to the commands residing on a failover, global, or NAS file system on which the database resource's dependency has not been set.
Solution:This message is informational. You must ensure that the resource comes online correctly on an alternate cluster node or on the same node after the Oracle commands become accessible again. If possible and supported, set the dependency of the database resource on the file system resource.
516515 Function: validate_options: %s Option %s not set
Description:The start, stop or probe command requires an option which is not set.
Solution:Fix the start, stop or probe command in the SUNW.gds resource.
516650 "pmfadm -s": Error signaling <%s>: %s
Description:An error occurred while rpc.pmfd attempted to send a signal to one of the processes of the given tag. The reason for the failure is also given. The signal was sent as a result of a 'pmfadm -s' command.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
516722 WARNING !!! Devicegroup %s does not have any volumes.
Description:The devicegroup does not have any volumes.
Solution:Make sure to create volumes in the devicegroup, before starting the resource.
517009 lkcm_act: invalid handle was passed %s %d
Description:Handle for communication with udlmctl is invalid.
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.
517036 connection from outside the cluster - rejected.
Description:There was a connection from an IP address which does not belong to the cluster. This is not allowed so the PNM daemon rejected the connection.
Solution:This message is informational; no user action is needed. However, it would be a good idea to see who is trying to talk to the PNM daemon and why?
517343 clexecd: Error %d from pipe
Description:clexecd program has encountered a failed pipe(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.
517363 clconf: Unrecognized property type
Description:Found the unrecognized property type in the configuration file.
Solution:Check the configuration file.
518018 CMM: Node being aborted from the cluster.
Description:This node is being excluded from the cluster.
Solution:Node should be rebooted if required. Resolve the problem according to other messages preceding this message.
518158 Probe for resource sctelemetry successful
Description:Telemetry data service probe method completed successfully.
Solution:This message is informational; no user action needed.
518378 The file system type is not specified in vfstab for mount point : %s.
Description:The 'file system type' field in the vfstab entry for the specified mount point does not specify the type of file system.
Solution:Add the type of file system to the 'file system type' field in the vfstab entry for the specified mount point and repeat the operation.
518383 Received notice that IPMP group %s has repaired.
Description:The named IPMP group is now functional.
Solution:No user action is required. This is an informational message.
518710 Validate - WebSphere MQ file systems not defined
Description:The required WebSphere MQ file systems, /opt/mqm and /var/mqm are not defined.
Solution:Ensure that /opt/mqm and /var/mqm are defined.
518710 Unknown command '%s' in the command log of zone cluster %s
Description:There was an unrecognized entry in the zone cluster command log. The command log table may be corrupt.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
518966 SCSLM getzoneidbyname error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
518999 ${PROG}: WARNING: ${file} has ${numlines} ${db} entries.
Description:The nsswitch.conf file on the zone cluster has more than one entry for this.
Solution:Remove the duplicate entries from the nsswitch.conf file of the zone cluster nodes.
519262 Validation failed. SYBASE monitor server startup file RUN_%s not found SYBASE=%s.
Description:Monitor server was specified in the extension property Monitor_Server_Name. However, monitor server startup file was not found. Monitor server startup file is expected to be: $SYBASE/$SYBASE_ASE/install/RUN_<Monitor_Server_Name>
Solution:Check the monitor server name specified in the Monitor_Server_Name property. Verify that SYBASE and SYBASE_ASE environment variables are set property in the Environment_file. Verify that RUN_<Monitor_Server_Name> file exists.
519406 %s: Couldn't fork to execute method %s
Description:Have problems in starting a communication with the SMF repository
Solution:Depending on the error, check the SMF man page. Contact your SUN vendor for help.
519419 Warning: Failed to update the nsswith.conf file.
Description:This service has failed to update the nsswitch.conf file on zone cluster.
Solution:Examine other syslog messages occurring at about the same time to see if the source of 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. Also, the user can manually edit the nsswitch.conf file on zone cluster nodes to have the following syntax needed by cluster: 1) Ensure that the lookup order for "hosts" and "netmasks" starts with "cluster files". 2) Ensure that the lookup order for all other entries starts with "files".
519641 sckrb5 not running.
Description:HA-KDC's stop method was called but the service was not running.
Solution:This is for informational purposes only, no action is required.
520047 Zone cluster %s is not authorized to access adapter %s
Description:An attempt was made to retrieve information about an adapter that is not configured to be used for the zone cluster.
Solution:This is an informational message. No user action is required.
520231 Unable to set the number of threads for the FED RPC threadpool.
Description:The rpc.fed server was unable to set the number of threads for the RPC threadpool. This happens while the server is starting up.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
520373 Internal error: %s.
Description:Self explanatory.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
520437 SCSLM <%s> pool_value_get_int64 error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
520810 Requesting RGM to mount QFS file systems.
Description:This is a notification from the handler about requesting the RGM to mount the shared qfs file systems by invoking INIT method of SUNW.qfs resources.
Solution:This is an informational message; no user action is needed.
521185 pthread_cond_wait: %s
Description:The sc_zonesd daemon received an unexpected error from pthread_cond_wait. This error should not impact the sc_zonesd's operations.
Solution:If the problem persists, 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.
521319 Waiting for the FED to stop
Description:The FED service is being stopped.
Solution:Please wait. No user action is required. This is an informational message.
521393 Backup server stopped.
Description:The backup server was stopped by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed. may
521560 Resource %s named in one of the resource dependencies properties does not exist.
Description:The resource dependencies property (one of strong/weak/restart/offline-restart) contains an invalid resource. This is an internal error and should not occur.
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.
521671 uri <%s> probe failed
Description:The probing of the url set in the monitor_uri_list extension property failed. The agent probe will take action.
Solution:No user action is required. 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.
521918 Validation failed. Connect string is NULL.
Description:The 'Connect_String' extension property used for fault monitoring is null. This has the format "username/password".
Solution:Check for syslog messages from other system modules. Check the resource configuration and the value of the 'Connect_string' property.
522480 RGM state machine returned error %d
Description:An error has occurred on this node while attempting to execute the rgmd state machine.
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 the problem.
522710 Failed to parse xml: invalid reg_type [%s]
Description:The cl_apid was unable to parse an xml message because of an invalid registration type.
Solution:No user action is required.
523346 Failed to retrieve extension properties.
Description:An internal error occurred in the rgmd while checking a cluster property.
Solution:Serious error. The RTR file may be corrupted. Reload the package for HA-HADB MA. If problem persists save a copy of the /var/adm/messages files on all nodes and contact the Sun Cluster HA developer.
523531 Listener probe timed out two times consecutively.
Description:Listener monitor has timed out in two successive attempts to probe the listener.
Solution:No user action is required.
523643 INTERNAL ERROR: %s
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.
524232 %s: Unable to register.
Description:This program could not register the RPC service.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
524368 Kerberos database %s is missing, exiting.
Description:The /var/krb5/principal database is missing or of zero length.
Solution:Verify that the principal database has been properly configured and that the /etc/krb5/krb5.conf and /etc/krb5/kdc.conf files have been specified correctly.
525152 Sigsend failed to send sig to contract %d: %s
Description:Could not send the signal to the specified contract
Solution:Man pages for sigsend will give more info about it. Contact your SUN vendor for more help.
525197 No network address resources in resource group.
Description:The cl_apid encountered an invalid property value. If it is trying to start, it will terminate. If it is trying to reload the properties, it will use the old properties instead.
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.
525628 CMM: Cluster has reached quorum.
Description:Enough nodes are operational to obtain a majority quorum; the cluster is now moving into operational state.
Solution:This is an informational message, no user action is needed.
526056 Resource <%s> of Resource Group <%s> failed pingpong check on node <%s>. The resource group will not be mastered by that node.
Description:A scha_control(1HA,3HA) call has rejected the indicated node as a new master for the resource group, because the indicated resource has recently initiated a failover off of that node by a previous scha_control call. In this context, "recently" means within the past Pingpong_interval seconds, where Pingpong_interval is a user-configurable property of the resource group. The default value of Pingpong_interval is 3600 seconds. For more information, see 'Pingpong_interval' in the rg_properties(5) man page. This check is performed to avoid the situation where a resource group repeatedly "ping-pongs" or moves back and forth between two or more nodes, which might occur if some external problem prevents the resource group from running successfully on *any* node.
Solution:No user action is required. Sun Cluster will continue to check other eligible nodes to see if they are healthy enough to master the resource group. If the system administrator wishes to permit failovers to be attempted even at the risk of ping-pong behavior, the Pingpong_interval property of the resource group can be set to a smaller value.
526324 scnetapp fatal error - clconf_lib_init() error
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
526340 Resource %s does not have the property DB_PROBE_PORT defined
Description:The property DB_PROBE_PORT is a mandatory property of the data service. Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
526492 Service object [%s, %s, %d] removed from group '%s'
Description:A specific service known by its unique name SAP (service access point), the three-tuple, has been deleted in the designated group.
Solution:This is an informational message, no user action is needed.
526671 Failed to initialize the DSDL.
Description:HA Storage Plus was not able to connect to the DSDL.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
526876 check_pgs: The test database manipulation failed for database %s, user %s and table %s
Description:The monitoring action on the specified table failed.
Solution:No user action is required.
526963 Checking UFS quota for %s
Description:The UFS mount point specified by %s, which has quotas enabled, is being checked using /usr/sbin/quotacheck.
Solution:This is an informational message. No user action is required.
527073 Could not set uid to '%d': %s
Description:The program failed to change the user ID to the specified value. The reason for the failure is also specified in the above message.
Solution:Please verify that the specified user ID is valid. For Oracle, the specified user ID is obtained from the owner of the file $ORACLE_HOME/bin/oracle.
527153 find_our_mds_rs() call failed.
Description:The resource that represents the metadata server of the specified file system could not be found.
Solution:Examine more specific error messages about not finding this resource to determine why the resource was not found.
527795 clexecd: setrlimit returned %d
Description:The clexecd program has encountered a failed setrlimit() 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.
528020 CCR: Remove table %s failed.
Description:The CCR failed to remove the indicated table.
Solution:The failure can happen due to many reasons, for some of which no user action is required because the CCR client in that case will handle the failure. The cases for which user action is required depends on other messages from CCR on the node, and include: If it failed because the cluster lost quorum, reboot the cluster. 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 cluster repository is corrupted as indicated by other CCR messages, then boot the offending node(s) in -x mode to restore the cluster repository from backup. The cluster repository is located at /etc/cluster/ccr/.
528051 Failed to obtain the absolute path of mount point %s (%s) in zone cluster %s.
Description:HAStoragePlus failed to obtain the absolute pathname for the specified mount point of local zone.
Solution:Check the realpath(3C) man page for errors and try to resolve the problem. Otherwise contact your authorized Sun service provider.
528499 scsblconfig not configured correctly.
Description:The specified file has not been configured correctly, or it does not have all the required settings.
Solution:Please verify that required variables (according to the installation instructions for this data service) are correctly configured in this file. Try to manually source this file in korn shell (". scsblconfig"), and verify if the required variables are getting set correctly.
528701 Failed to create repository object %s
Description:Error in creating various handles to interact with the SMF repository.
Solution:Check the SMF man page to know more about the error. Also verify that the basic SMF functionalities are working. Contact your SUN vendor for more help.
529096 Function: validate - %s is not executable
Description:The Zone SMF Probe Script is not executable.
Solution:Review the /opt/SUNWsczone/sczsmf/util/sczsmf_config configuration file and make sure you have specified the correct SERVICE_PROBE.
529191 clexecd: Sending fd to workerd returned %d. Exiting.
Description:There was some error in setting up interprocess communication in the clexecd program.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
529407 resource group %s state on node %s change to %s
Description:This is a notification from the rgmd that a resource group's state has changed. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
529502 UNRECOVERABLE ERROR: /etc/cluster/ccr/infrastructure file is corrupted
Description:/etc/cluster/ccr/infrastructure file is corrupted.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
529952 Failfast : Failed to reboot zone %s (zone ID %d) as opening of 'zoneadmd' door failed with error code %d. Failfast will halt the zone now.
Description:Failfast failed to reboot zone, because the door to the zoneadmd daemon could not be opened. Failfast will halt the zone as a result.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
530064 reservation error(%s) - do_enfailfast() 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.
530289 CCR begin transaction failed for zone cluster %s
Description:The CCR raised an exception while starting a transaction on the zone cluster configuration table.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
530492 fatal: ucmm_initialize() failed
Description:The daemon indicated in the message tag (rgmd or ucmmd) was unable to initialize its interface to the low-level cluster membership monitor. This is a fatal error, and causes the node to be halted or rebooted to avoid data corruption. The daemon produces a core file before exiting.
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.
530574 CCR: Updating invalid table %s in cluster %s.
Description:This joining node carries a valid copy of the indicated table with override flag set while the current cluster membership does not have a valid copy of this table. This node will update its copy of the indicated table to other nodes in the cluster.
Solution:This is an informational message, no user action is needed.
530628 Could not allocate memory in get_method
Description:Could not allocate memory
Solution:Check the availability of the memory. Contact your SUN vendor for more help.
530828 Failed to disconnect from host %s and port %d.
Description:The data service fault monitor probe was trying to disconnect from the specified host/port and failed. The problem may be due to an overloaded system or other problems. If such failure is repeated, Sun Cluster will attempt to correct the situation by either doing a restart or a failover of the data service.
Solution:If this problem is due to an overloaded system, you may consider increasing the Probe_timeout property.
530938 Starting NFS daemon %s.
Description:The specified NFS daemon is being started by the HA-NFS implementation.
Solution:This is an informational message. No user action is required.
530977 Error in scha_rg_get of rg:%s, Err: %s
Description:Cannot get the requesting rg.
Solution:Depending on the error take action and the details are provided in the man page scha_rg_get(3HA)
531148 fatal: thr_create stack allocation failure: %s (UNIX error %d)
Description:The rgmd daemon was unable to create a thread stack, most likely because the system has run out of swap space. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
Solution:Rebooting the node has probably cured the problem. If the problem recurs, you might need to increase swap space by configuring additional swap devices. See swap(1M) for more information.
531989 Prog <%s> step <%s>: authorization error: %s.
Description:An attempted program execution failed, apparently due to a security violation; this error should not occur. The last portion of the message describes the error. This failure is considered a program failure.
Solution:Correct the problem identified in the error message. If necessary, examine other syslog messages occurring at about the same time to see if the problem can be diagnosed. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing the problem.
532118 All the SUNW.HAStoragePlus resources that this resource depends on are not online on the local node. Skipping the checks for the existence and permissions of the start/stop/probe commands.
Description:The HAStoragePlus resources that this resource depends on are online on another node. Validation checks will be done on that other node.
Solution:This message is informational; no user action is needed.
532454 file specified in USER_ENV parameter %s does not exist
Description:'User_env' property was set when configuring the resource. File specified in 'User_env' property does not exist or is not readable. File should be specified with fully qualified path.
Solution:Specify existing file with fully qualified file name when creating resource. If resource is already created, please update resource property 'User_env'.
532654 The -c or -u flag must be specified for the %s method.
Description:The arguments passed to the function unexpected omitted the given flags.
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.
532740 Failed to parse the Nodelist property
Description:A LogicalHostname resource could not be initialized because of failure to parse the resource group's Nodelist property.
Solution:This is an internal error. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
532774 Function: validate - %s state is %s
Description:The referenced zone is not in the state installed, ready or running.
Solution:Make sure that the referenced zone name is configured properly. Check if you have done a zlogin -C. Make sure that the name in the appropriate config file is correct.
532854 Probe for J2EE engine timed out in scds_fm_tcp_disconnect().
Description:The data service timed out while disconnecting the socket.
Solution:Informational message. No user action is needed.
532973 clcomm: User Error: Loading duplicate TypeId: %s.
Description:The system records type identifiers for multiple kinds of type data. The system checks for type identifiers when loading type information. This message identifies that a type is being reloaded most likely as a consequence of reloading an existing module.
Solution:Reboot the node and do not load any Sun Cluster modules manually.
532980 clcomm: Pathend %p: deferred task not allowed in state %d
Description:The system maintains state information about a path. 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.
533294 sig_handler sigwait: %s
Description:The daemon was unable to configure its signal handling functionality, so it is unable to run.
Solution:Save the syslog messages file. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
533359 pmf_monitor_suspend: Error opening procfs control file <%s> for tag <%s>: %s
Description:The rpc.pmfd server was not able to resume the monitoring of a process because the rpc.pmfd server was not able to open a procfs control file. If the system error is 'Device busy', the procfs control file is being used by another command (like truss, pstack, dbx...) and the monitoring of this process remains suspended. If this is not the case, the monitoring of this process has been aborted and can not be resumed.
Solution:If the system error is 'Device busy', stop the command which is using the procfs control file and issue the monitoring resume command again. Otherwise investigate if the machine is running out of memory. If this is not the case, save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
533824 Function: validate - %s invalid boot option [%s]
Description:The specified boot option is not allowed.
Solution:Consult the man page of zoneadm which boot options are allowed and specify one of them.
533854 reservation notice(%s) - MHIOCGRP_PREEMPTANDABORT success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action required.
533895 Error getting ucmm state.
Description:The state of the UCMM could not be determined.
Solution:Verify the status of the SUNW.rac_framework resource and either the SUNW.rac_svm resource or the SUNW.rac_cvm resource. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
533912 Warning! Sun Cluster resource cannot be brought online on this node because the corresponding Solaris SMF services may be online. Please disable the Solaris SMF services using the following command: 'svcadm disable %s'
Description:The Solaris SMF service indicated above could not be disabled as required by Sun Cluster to make the service capable of restart/failover.
Solution:Try to manually disable the SMF service specified by the error message using the 'svcadm disable' command and retry the operation.
534112 File system associated with mount point %s is to be locally mounted in zone cluster %s. The AffinityOn value cannot be FALSE.
Description:HAStoragePlus detected that the specified mount point in /etc/vfstab is a local mount point, hence extension property AffinityOn must be set to True.
Solution:Set the AffinityOn extension property of the resource to True.
534408 "%s" restarting too often ... sleeping %d seconds.
Description:The tag shown, run by rpc.pmfd server, is restarting and exiting too often. This means more than once a minute. This can happen if the application is restarting, then immediately exiting for some reason, then the action is executed and returns OK (0), which causes the server to restart the application. When this happens, the rpc.pmfd server waits for up to 1 minute before it restarts the application. An error message is output to syslog.
Solution:Examine the state of the application, try to figure out why the application doesn't stay up, and yet the action returns OK.
534415 stop_pgs: Stop PostgreSQL process %s with kill -9
Description:The previous stop attempts for PostgreSQL failed. The server is now killed with kill -9.
Solution:No user action is required.
534499 Failed to take the resource out of PMF control.
Description:Sun Cluster was unable to remove the resource out of PMF control. This may cause the service to keep restarting on an unhealthy node.
Solution:Look in /var/adm/messages for the cause of failure. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
534592 %s is not a local or a global mount point in /etc/mnttab.
Description:Self explanatory.
Solution:This is a warning message. If the file system that is associated with the specified mount point is not available, copy the /var/adm/messages and contact an authorized Sun service provider.
534644 Failed to start SAP processes with %s.
Description:The data service failed to start the SAP processes.
Solution:Check the script and execute manually.
534755 Shutdown - can't access pidfile %s of process %s
Description:The file ${pidfile} was not found. ${pidfile} is the second argument to the 'Shutdown' function. 'Shutdown' is called within the stop scripts of sge_qmaster-rs and sge_schedd-rs resources.
Solution:Confirm the file schedd.pid or qmaster.pid exists. Said file should be found in the respective spool directory of the daemon in question.
535044 Creation of resource <%s> failed because none of the nodes on which VALIDATE would have run are currently up
Description:In order to create a resource whose type has a registered VALIDATE method, the rgmd must be able to run VALIDATE on at least one node. However, all of the candidate nodes are down. "Candidate nodes" are either members of the resource group's Nodelist or members of the resource type's Installed_nodes list, depending on the setting of the resource's Init_nodes property.
Solution:Boot one of the resource group's potential masters and retry the resource creation operation.
535181 Host %s is not valid.
Description:Validation method has failed to validate the ip addresses.
Solution:Invalid hostnames/ip addresses have been specified while creating resource. Recreate the resource with valid hostnames. Check the syslog message for the specific information.
535684 clconf: Memory allocation failure.
Description:When quorum configuration information was converted into the quorum table, memory was not allocated correctly to store a field in the quorum device information.
Solution:Insufficient memory might lead to other problems; free up memory if possible.
535809 malloc failed for ipaddr string
Description:Call to malloc failed. The "malloc" man page describes possible reasons.
Solution:Install more memory, increase swap space or reduce peak memory consumption.
535886 Could not find a mapping for %s in %s. It is recommended that a mapping for %s be added to %s.
Description:No mapping was found in the local hosts file for the specified ip address.
Solution:Applications might use hostnames instead of ip addresses. It is recommended to have a mapping in the hosts file. Add an entry in the hosts file for the specified ip address.
535964 INTERNAL ERROR: resource group <%s> state <%s> node <%s> has invalid rgl_switching flag <%d>
Description:The rgmd has discovered that the indicated resource group's state information appears to be incorrect. This may prevent any administrative actions from being performed on the resource group.
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.
536048 libsecurity, door_call: %s
Description:A door_call failed with the specified reason, causing a Sun Cluster daemon to be terminated, and the node to be rebooted or halted.
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.
536091 Failed to retrieve the cluster handle while querying for property %s: %s.
Description:Access to the object named 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.
536458 Failed to register CMM version key %s, version %d in the CCR infrastructure table
Description:The CMM failed to register the CMM version in the CCR. The result of this failure will be to continue using the old CMM version during the next reconfiguration.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
536550 check_dhcp - Dhcpclient didn't retrieve any IP-number
Description:The dhcpclient could not retrieve any IP number.
Solution:No user action is required. Informational message, an immediate failover is being requested.
536867 scvxvmlg error - dcs_get_service_parameters() failed, returned %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.
537175 CMM: Node %s (nodeid: %ld, incarnation
Description:The cluster can communicate with the specified node. A node becomes reachable before it is declared up and having joined the cluster.
Solution:This is an informational message, no user action is needed.
537352 reservation error(%s) - do_scsi3_preemptandabort() 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.
537367 Failed build path to status message file.
Description:The path to the status message file could not be built. This is an internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
537380 Invalid option -%c for the validate method.
Description:Invalid option is passed to validate call back method.
Solution:This is an internal error. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
537498 Invalid value was returned for resource property %s for %s.
Description:The value returned for the named property was not valid.
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.
537607 Not found clexecd on node %d for %d seconds. Retrying...
Description:Could not find clexecd to execute the program on a node. Indicated retry times.
Solution:This is an informational message, no user action is needed.
538150 sigprocmask(2) failed for pmmd_adm while querying current signal mask: error %s
Description:The pmmd_adm was unable to query its current signal mask because the sigprocmask(2) function failed. The message contains the system error. The pmmd_adm cannot do its requested action.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
538177 in libsecurity contacting program %s (%lu); uname sys call failed: %s
Description:A client was not able to make an rpc connection to the specified server because the host name could not be obtained. The system error message 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.
538570 sema_post parent: %s
Description:The libclcontract code was not able to act on a semaphore. The message contains the system error. The server process (which is using libclcontract) 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 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.
539085 Could not destroy zone cluster %s configuration. Error %d.
Description:The process_cmd_log was unable to destroy the zone cluster configuration.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
539351 init_signal_handlers pthread_sigmask: %s
Description:Internal error.
Solution:Save the syslog messages file. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
539459 cl_execd: priocntl returned %d. Exiting.
Description:cl_execd program has encountered a failed priocntl(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.
539760 Error parsing URL: %s. Will shutdown the WLS using sigkill
Description:There is an error in parsing the URL needed to do a smooth shutdown. The WLS stop method however will go ahead and kill the WLS process.
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.
540024 INTERNAL ERROR: %s: %s.
Description:The PMF action script supplied by the DSDL could not complete its function because an snprintf(3c) call failed. The PMF action script has restarted the application.
Solution:If this error persists, contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
540274 got unexpected exception %s
Description:An inter-node communication failed with an unknown exception.
Solution:Examine syslog output for related error messages. Save a copy of the /var/adm/messages files on all nodes, and of the rgmd core file (if any). Contact your authorized Sun service provider for assistance in diagnosing the problem.
540279 scha_cluster_get failed for (%s) with %d
Description:Call 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.
540705 The DB probe script %s Timed out while executing
Description:probing of the URL's set in the Server_url or the Monitor_uri_list failed. Before taking any action the WLS probe would make sure the DB is up. The Database probe script set in the extension property db_probe_script timed out while executing. The probe will not take any action till the DB is UP and the DB probe succeeds.
Solution:Make sure the DB probe (set in db_probe_script) succeeds. Once the DB is started the WLS probe will take action on the failed WLS instance.
541100 Failed to determine the resource type version of this resource
Description:An error occurred while determining the resource type of the resource.
Solution:Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem with a copy of the /var/adm/messages files on all nodes.
541145 No active replicas where detected for the global service %s.
Description:The DCS did not find any information on the specified global service.
Solution:Check the global service configuration.
541180 Sun udlmlib library called with unknown option: '%c'
Description:Unknown option used while starting up Oracle UNIX dlm.
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.
541206 Couldn't read deleted directory: error (%d)
Description:The file system is unable to create temporary copies of deleted files.
Solution:Mount the affected file system as a local file system, and ensure that there is no file system entry with name "._" at the root level of that file system. Alternatively, run fsck on the device to ensure that the file system is not corrupt.
541277 PMF did not restart tag <%s>, cmd_path="%s"
Description:The process with the given tag failed to stay up and exceeded the allowed number of retry attempts (given by the 'pmfadm -n' option) and the action (given by the 'pmfadm -a' option) was initiated by rpc.pmfd. The action failed (i.e., returned non-zero), and rpc.pmfd will delete this tag from its tag list and discontinue retry attempts. For more information, see pmfadm(1M).
Solution:This message is informational; no user action is needed.
541415 SCSLM malloc error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
541445 Unable to compose %s path.
Description:Unable to construct the path to the indicated file.
Solution:Check system log messages to determine the underlying problem.
541818 Service group '%s' created
Description:The service group by that name is now known by the scalable services framework.
Solution:This is an informational message, no user action is needed.
543543 Unauthorized to check the status of zone cluster '%s'.
Description:The resource is unauthorized to check the status of the specified zone cluster. The zone cluster process is prevented from accessing the information of the specified zone cluster.
Solution:Create the resource with zone cluster name which the resource has authorized access.
543720 Desired Primaries is %d. It should be 1.
Description:Invalid value for Desired Primaries property.
Solution:Invalid value is set for Desired Primaries property. The value should be 1. Reset the property value by using clresourcegroup.
544030 The entry in mnttab for mount point '%s' has too many fields.
Description:The entry in mnttab for the specified mount point has more fields than are defined for a single mnttab entry.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
544097 Unable to allocate memory in sc delegated resource mgmt
Description:Problem in creating memory space during resource management of SMF delegated restarter
Solution:Check the system memory usage
544178 Error: could not start the Derby server, check whether the port specified in the resource property DB_probe_port is already used.
Description:The Derby server could not be started probably because the port specified in DB_probe_port is already used.
Solution:Check the resource property DB_probe_port of the Derby data service and try to use another port number.
544185 A resource restart attempt on resource %s in resource group %s on node %s with Failover_mode=RESTART_ONLY has been blocked because the number of restarts within the past Retry_interval (%d seconds) would exceed Retry_count (%d)
Description:The rgmd is enforcing the RESTART_ONLY value for the Failover_mode system property. A request to restart a resource is denied because the resource has already been restarted Retry_count times within the past Retry_interval seconds.
Solution:No user action is required. If desired, use clresourcegroup to change the Failover_mode setting.
544380 Failed to retrieve the resource type handle: %s.
Description:An API operation on the resource type has failed.
Solution:For the resource type name, check the syslog tag. For more details, check the syslog messages from other components. If the error persists, reboot the node.
544497 Auto_recovery_command is not set.
Description:Auto recovery was performed and the database was reinitialized by running the hadbm clear command. However the extension property auto_recovery_command was not set so no further recovery was attempted.
Solution:HADB is up with a fresh database. Session stores will need to be recreated. In the future the auto_recovery_command extension property can be set to a command that can do this whenever autorecovery is performed.
544592 PCSENTRY: %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.
544600 Reading from server timed out: server %s port %d
Description:While reading the response from a request sent to the server the probe timeout ran out.
Solution:Check that the server is functioning correctly and if the resources probe timeout is set too low.
544775 libpnm system error: %s
Description:A system error has occurred in libpnm. This could be because of the resources on the system being very low (for example, low memory).
Solution:The user of libpnm should handle these errors. However, if the message is out of memory - increase the swap space, install more memory or reduce peak memory consumption. Otherwise the error is unrecoverable, and the node needs to be rebooted. write error - check the "write" man page for possible errors. read error - check the "read" man page for possible errors. socket failed - check the "socket" man page for possible errors. TCP_ANONPRIVBIND failed - check the "setsockopt" man page for possible errors. The gethostbyname failed for %s - make sure entries in /etc/hosts, /etc/nsswitch.conf and /etc/netconfig are correct to get information about this host. bind failed - check the "bind" man page for possible errors. SIOCGLIFFLAGS failed - check the "ioctl" man page for possible errors. SIOCSLIFFLAGS failed - check the "ioctl" man page for possible errors. SIOCSLIFADDR failed - check the "ioctl" man page for possible errors. open failed - check the "open" man page for possible errors. SIOCLIFADDIF failed - check the "ioctl" man page for possible errors. SIOCLIFREMOVEIF failed - check the "ioctl" man page for possible errors. SIOCSLIFNETMASK failed - check the "ioctl" 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. SIOCGLIFGROUPNAME failed - check the "ioctl" man page for possible errors. wrong address family - check the "ioctl" man page for possible errors. Cannot open libscconf - check that /usr/cluster/lib/libscconf.so.1 is properly installed. Cannot access libscconf function - check that /usr/cluster/lib/libscconf.so.1 is properly installed. Cannot access cluster configuration - check that you are in cluster mode. Failed to retrieve nodeid for %s. - Make sure that the name given is a valid node name.
544904 %s: exec failed for method %s: %s
Description:Cannot execute the specified method of the service fmri.
Solution:The exec call has errored out not being able to execute. Test and see if the method is able to be executed without sc_delegated_restarter.
544940 check_stdby: The database in %s is not configured as a standby database, create the recovery.conf command
Description:The database is not configured as a standby database.
Solution:Create an appropriate recovery.conf command, reload the primary, and restart the standby database.
546018 Class <%s> SubClass <%s> Vendor <%s> Pub <%s>
Description:The cl_eventd is posting an event locally with the specified attributes.
Solution:This message is informational only, and does not require user action.
546051 Error stopping the FED
Description:The FED service fails to stop.
Solution:Please reboot the node,
546524 dl_info ack bad len %d
Description:Sanity check. The message length in the acknowledgment to the info request is different from what was expected. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
546856 CCR: Could not find the CCR transaction manager.
Description:The CCR data server could not find the CCR transaction manager in the cluster.
Solution:Reboot the cluster. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.
547145 Initialization error. Fault Monitor username is NULL
Description:Internal error. Environment variable SYBASE_MONITOR_USER not set before invoking fault monitor.
Solution:Report this problem to your authorized Sun service provider.
547301 reservation error(%s) error. Unknown internal error returned from clconf_do_execution().
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.
547307 Initialization failed. Invalid command line %s
Description:This method is expected to be called the resource group manager. This method was not called with expected command line arguments.
Solution:This is an internal error. Save the contents of /var/adm/messages from all the nodes and contact your Sun service representative.
547532 "pmfadm -s": Can not stop <%s>: Monitoring is not resumed on pid %d
Description:The command 'pmfadm -s' 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.
548162 Error (%s) when reading standard property <%s>.
Description:Error occurred in API call scha_resource_get.
Solution:Check syslog messages for errors logged from other system modules. If the error persists, please report the problem.
548211 Error stopping gracefully the PNM in zone %s. Killing PNM
Description:The PNM service fails to stop.
Solution:No user action required
548237 Validation failed. Connect string contains 'sa' password.
Description:The 'Connect_String' extension property used for fault monitoring uses 'sa' as the account password combination. This is a security risk, because the extension properties are accessible by everyone.
Solution:Check the resource configuration and the value of the 'Connect_string'. property. Ensure that a dedicated account (with minimal privileges) is created for fault monitoring purposes.
548260 The ucmmd daemon will not be started due to errors in previous reconfiguration.
Description:Error was detected during previous reconfiguration of the RAC framework component. Error is indicated in the message. As a result of error, the ucmmd daemon was stopped and node was rebooted. On node reboot, the ucmmd daemon was not started on the node to allow investigation of the problem. RAC framework is not running on this node. Oracle parallel server/ Real Application Clusters database instances will not be able to start on this node.
Solution:Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Resolve the problem that resulted in reconfiguration error. Reboot the node to start RAC framework on the node. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters. If problem persists, contact your Sun service representative.
548445 Failed to refresh %s after property update.
Description:The Solaris service management facility failed to refresh the service instance that the fault management resource identifier (FMRI) in the /var/adm/messages specifies.
Solution:Run the command 'svcadm refresh <fmri>' to refresh the service instance. Then run the command 'svcs -x <service>' to verify that the service is online. If the problem persists, contact your Sun Support representative for further assistance.
548691 Delegating giveover request to resource group %s, due to a +++ affinity of resource group %s (possibly transitively).
Description:A resource from a resource group that declares a strong positive affinity with failover delegation (+++ affinity) attempted a giveover request via the scha_control command. The giveover request was forwarded to the delegate resource group.
Solution:This is an informational message; no user action is needed.
548977 Function: clear_zone - Killing processes with fuser -cs 15 on the file system %s
Description:The non-global zones shutdown command did not complete in time or zoneadm halt was not able to bring the non-global zone into state "installed". A fuser -cs 15 is submitted against each of the zones file systems. The reported processes will be send a SIGTERM.
Solution:No user action is required.
549190 Text server successfully started.
Description:The Sybase text server has been successfully started by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed.
549765 Preparing to start service %s.
Description:Sun Cluster is preparing to start the specified application
Solution:This is an informational message, no user action is needed.
550112 %s: Warning: The force option is being used to unmount %s
Description:An attempt to unmount a global filesystem using umount(2) was unsuccessful. The system will retry to unmount the global filesystem using umount2(2) with the force option (MS_FORCE).
Solution:No user action is required.
550126 Validate - The tftp testfile (%s) don't exist in directory (%s) or has filesize of zero bytes
Description:The file specified in TFTPTESTFILE= within /opt/SUNWscdhc/util/dhcp_config doesn't exist or has a zero length witihin /etc/inet/inetd.conf.
Solution:If TFTPTESTFILE= is required, then ensure file specified is correct.
550490 Function: start_mysql - clrs enable for (%s) was unsuccessful
Description:The clrs enable of the MySQL replication resource was unsuccessful.
Solution:Examine the /var/adm/messages for the additional error messages and fix the root cause
550770 The resource "%s" cannot be added while the UCMMD is running.
Description:An attempt was made to add a resource to the RAC framework resource group while the UCMM is running.
Solution:Bring the RAC framework resource group to an unmanaged state, reboot the cluster, and repeat the attempt to add a resource.
551094 reservation warning(%s) - Unable to open device %s, 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.
551285 %s not mounted, exiting
Description:The /usr/lib/krb5 path is not accessible.
Solution:Check this path and determine if /usr needs to be mounted.
551654 Port (%d) determined from Monitor_Uri_List is invalid
Description:The indicated port is not valid.
Solution:Correct the port specified in Monitor_Uri_List.
551893 Function: val_parfile - File %s does not exist
Description:The parameter file does not exist in the parameter file directory.
Solution:Restore the parameter file or reregister the resource.
552067 Waiting for Kerberos daemons to startup.
Description:Waiting for both the krb5kdc and kadmind daemons to start successfully under PMF.
Solution:This is for informational purposes only, no action is required.
552278 All WebSphere MQ Broker processes stopped
Description:The WebSphere MQ Broker has been successfully stopped.
Solution:No user action is needed.
553048 Cannot determine the nodeid
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
553443 clq_netapp: quorum open error: Failed to create door_call_thread --- quorum device %s will be unavailable.
Description:An internal error occurred when creating a thread to communicate with the NetApp NAS quorum device. The device will not be available.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
553590 User id %d not found in file %s.
Description:The program failed to locate a valid entry in /etc/passwd for the specified user ID.
Solution:Please verify that the specified user ID is valid. For Oracle, the specified user ID is obtained from the owner of the file $ORACLE_HOME/bin/oracle. Also ensure that both the Oracle user and dba group are declared locally in the /etc/passwd and /etc/group files.
555317 Could not restart telemetry data service
Description:The Telemetry data service could not be restarted.
Solution:This message is informational; no user action needed.
555780 Failed to clear active contract template: %s
Description:Not able to clear the active contract template.
Solution:Check the contract man page to know more about the error. Also make sure the basic contract functionalities are working. Contact your SUN vendor for more help.
555844 Cannot send reply: invalid socket
Description:The cl_apid experienced an internal error.
Solution:No user action is required. If the problem persists, 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.
556039 Validation failed. ORACLE_HOME/bin/srvctl not found ORACLE_HOME=%s
Description:The SUNW.scalable_rac_server_proxy agent could not find the srvctl binary in the indicated ORACLE_HOME/bin directory.
Solution:Check whether the $ORACLE_HOME/bin directory is accessible, and if so, whether the srvctl binary exists. If the problem persists, contact your Sun support representative for further assistance.
556113 Resource dependency on SAP enqueue server does not match the affinity setting on SAP enqueue server resource group.
Description:Both the dependency on a SAP enqueue server resource and the affinity on a SAP enqueue server resource group are set. However, the resource groups specified in the affinity property does not correspond to the resource group that the SAP enqueue server resource (specified in the resource dependency) belongs to.
Solution:Specify a SAP enqueue server resource group in the affinity property. Make sure that SAP enqueue server resource group contains the SAP enqueue server resource that is specified in the resource dependency property.
556434 Giveover attempt failed for %s: resource group is unable to bring online on a potential primary node. Will retry.
Description:An error occurred while attempting to switch over the QFS metadata resource group. This is probably a transient error because the node might have gone down when resource group was about to be brought online.
Solution:If this problem persists, verify that the resource group is configured correctly.
556466 clexecd: dup2 of stdout returned with errno %d while exec'ing (%s). Exiting.
Description:clexecd program has encountered a failed dup2(2) system call. The error message indicates the error number for the failure.
Solution:The clexecd program will exit and the 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.
556694 Nodes %u and %u have incompatible versions and will not communicate properly.
Description:This is an informational message from the cluster version manager and may help diagnose which systems have incompatible versions with each other during a rolling upgrade. This error may also be due to attempting to boot a cluster node in 64-bit address mode when other nodes are booted in 32-bit address mode, or vice versa.
Solution:This message is informational; no user action is needed. However, one or more nodes may shut down in order to preserve system integrity. Verify that any recent software installations completed without errors and that the installed packages or patches are compatible with the software installed on the other cluster nodes.
556800 Validation failed. Resource Group %s containing the Proxy Resource %s should have a strong positive affinity on the Resource Group %s containing an offline restart dependee resource %s.
Description:One or more resources that you are specifying as an offline restart dependee of the proxy resource does not belong to a resource group on which the resource group containing the proxy resource has a strong positive affinity.
Solution:Modify the resource group containing the proxy resource to have a strong positive affinity on the dependee resource's resource group.
556945 No permission for owner to execute %s.
Description:The specified path does not have the correct permissions as expected by a program.
Solution:Set the permissions for the file so that it is readable and executable by the owner.
557585 No filesystem mounted on %s.
Description:There is no filesystem mounted on the mount point.
Solution:No user action is required. This is a debug message.
558184 Validate - MySQL logdirectory for mysqld does not exist
Description:The defined (-L option) log directory does not exist.
Solution:Make sure that the defined log directory exists.
558350 Validation failed. Connect string is incomplete.
Description:The 'Connect_String' extension property used for fault monitoring has been incorrectly specified. This has the format "username/password".
Solution:Check the resource configuration and the value of the 'Connect_String' property. Ensure that there are no spaces in the 'Connect_String' specification.
558742 Resource group %s is online on more than one node.
Description:The named resource group should be online on only one node, but it is actually online on more than one node.
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.
558763 Failed to start the WebLogic server configured in resource %s
Description:The WebLogic Server configured in the resource could not be started by the agent.
Solution:Try to start the WebLogic Server manually and check if it can be started manually. Make sure the logical host is UP before starting the WLS manually. If it fails to start manually then check your configuration and make sure it can be started manually before it can be started by the agent. Make sure the extension properties are correct. Make sure the port is not already in use.
558769 Failed to get UCMM state; can not continue IO probing !
Description:The state of the UCMM could not be retrieved by the probe. This is an internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
559206 Either extension property <stop_signal> is not defined, or an error occurred while retrieving this property; using the default value of SIGTERM.
Description:Property stop_signal might not be defined in RTR file. The process continues with the default value of SIGTERM.
Solution:This is an informational message; no user action is needed.
559516 SCSLM <%s> ret %d
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
559857 Starting liveCache with command %s failed. Return code is %d.
Description:Starting liveCache failed.
Solution:Check SAP liveCache log files and also look for syslog error messages on the same node for potential errors.
560047 Unix DLM version (%d) and SUN Unix DLM library version (%d): compatible.
Description:The UNIX DLM is compatible with the installed version of libudlm.
Solution:No user action is required.
560241 Error: Can't run RGEVACUATE script outside of run control environment.
Description:The stoprgm init script was run manually (not automatically by init(1M)). This is not supported by Sun Cluster software. The "stoprgm" command was not successful. No action was performed.
Solution:This is an informational message; no user action is needed.
560630 SCSLM <%s> zone <%s> no groups
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
560781 Tag %s: could not allocate history.
Description:The rpc.pmfd server was not able to allocate memory for the history of the tag shown. Monitoring of he process associated with the tag is stopped and pmfadm returns an error. This problem can occur if the machine has low memory.
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.
560808 Derby data service start method timed out
Description:The derby data service could not start before the configured timeout elapsed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
561162 Failed to remove sci%d adapter
Description:The Sun Cluster Topology Manager (TM) has failed to remove the SCI adapter.
Solution:Make sure that the SCI adapter is installed correctly on the system or contact your authorized Sun service provider for assistance.
561299 Error: ${SERVER} is already running.
Description:The initfed init script found the rpc.fed already running. It will not start it again.
Solution:No user action is required.
561862 PNM daemon config error: %s
Description:A configuration error has occurred in the PNM daemon. This could be because of wrong configuration/format etc.
Solution:If the message is: IPMP group %s not found - either an IPMP group name has been changed or all the adapters in the IPMP group have been unplumbed. There would have been an earlier NOTICE which said that a particular IPMP group has been removed. The cl_pnmd has to be restarted. Send a KILL (9) signal to the PNM daemon. Because cl_pnmd is under PMF control, it will be restarted automatically. If the problem persists, restart the node with clnode evacuate and shutdown. IPMP group %s already exists - the user of libpnm is trying to auto-create an IPMP group with a groupname that is already being used. Typically, this should not happen so contact your authorized Sun service provider to determine whether a workaround or patch or suggestion is available. Make a note of all the IPMP group names on your cluster. wrong format for /etc/hostname.%s - the format of /etc/hostname.<adp> file is wrong. Either it has the keyword group but no group name following it or the file has multiple lines. Correct the format of the file after going through the IPMP Admin Guide. The cl_pnmd has to be restarted. Send a KILL (9) signal to cl_pnmd. Because cl_pnmd is under PMF control, it will be restarted automatically. If the problem persists, restart the node by using clnode evacuate and shutdown. We do not support multiline /etc/hostname.adp file in auto-create since it becomes difficult to figure out which IP address the user wanted to use as the non-failover IP address. All adps in %s do not have similar instances (IPv4/IPv6) plumbed—an IPMP group is supposed to be homogenous. If any adp in an IPMP group has a certain instance (IPv4 or IPv6) then all the adps in that IPMP group must have that particular instance plumbed in order to facilitate failover. Please see the Solaris IPMP docs for more details. %s is blank—this means that the /etc/hostname.<adp> file is blank. We do not support auto-create for blank v4 hostname files - since this will mean that 0.0.0.0 will be plumbed on the v4 address.
561896 Failed to create thread for probing. %s
Description:The thread that is used for the I/O probe could not be created.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
562040 Update_drv failed to re-read did.conf file for
Description:Update_drv command was NOT able to make did driver reread did.conf.
Solution:This is an informational message, no user action is needed.
562200 Application failed to stay up.
Description:The probe for the SUNW.Event data service found that the cl_apid application failed to stay 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.
562397 Failfast: %s.
Description:A failfast client has encountered a deferred panic timeout and is going to panic the node or zone. This might happen if a critical userland process, as identified by the message, dies unexpectedly.
Solution:Check for core files of the process after rebooting the node or zone and report these files to your authorized Sun service provider.
562700 unable to arm failfast.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
563025 XDR FE Buffer Shortfall while encoding arguments API num = %d, will retry
Description:A non-fatal error occurred while rpc.fed was marshalling arguments for a remote procedure call. The operation will be retried 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.
563343 resource type %s updated.
Description:This is a notification from the rgmd that the operator has edited a property of a resource type. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
563800 Failed to get all IPMP groups (request failed with %d).
Description:An unexpected error occurred while trying to communicate with the network monitoring daemon (cl_pnmd).
Solution:Make sure the network monitoring daemon (cl_pnmd) is running.
563847 INTERNAL ERROR: POSTNET_STOP method is not registered for resource <%s>
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
563976 Unable to get socket flags: %s.
Description:Failed to get status flags for the socket used in communicating with the application.
Solution:This is an internal error, no user action is required. Also contact your authorized Sun service provider.
564486 cl_execd: (thread %d): Error %d from read
Description:The cl_execd program encountered a failure while executing the read(2) system call.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
564643 Fault monitor detected error %s: %ld %s Action=%s : %s
Description:Fault monitor has detected an error. Error detected by fault monitor and action taken by fault monitor is indicated in message. This message also indicates whether the action taken is default or user-defined (custom).
Solution:No user action is required.
564810 Function: validate - Zone %s has brand type %s. No SMF available, sczsmf does not work for the configured Zone.
Description:The sczsmf component does not work with zones of brand type other than "native", since they have no SMF feature implemented.
Solution:Don't configure the sczsmf component for a zone of brand type other than "native". Use the sczsh component instead.
564883 The Data base probe %s also failed. Will restart or failover the WLS only if the DB is UP
Description:probing of the URL's set in the Server_url or the Monitor_uri_list failed. Before taking any action the WLS probe would make sure the DB is up (if a db_probe_script extension property is set). But, the DB probe also failed. The probe will not take any action till the DB is UP and the DB probe succeeds.
Solution:Start the Data Base and make sure the DB probe (the script set in the db_probe_script) returns 0 for success. Once the DB is started the WLS probe will take action on the failed WLS instance.
564960 qdmd: An error occurred while opening quorum device %s
Description:The quorum device monitoring daemon encountered an error while opening the indicated quorum device.
Solution:Unconfigure the quorum device and reconfigure it. If that fails, replace the quorum device.
565198 did subpath %s created for instance %d.
Description:Informational message from scdidadm.
Solution:No user action required.
565220 Derby start method failed for unknown reason
Description:The derby data service could not start for an unknown reason.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
565362 Transport heart beat timeout is changed to %s.
Description:The global transport heart beat timeout is changed.
Solution:No user action is required. This is only for information.
565368 Could not dlopen (%s)
Description:An error occurred during an attempt to open the library.
Solution:Ensure that the library is installed. Contact your authorized Sun service provider for assistance in diagnosing the problem.
565438 svc_run returned
Description:The rpc.pmfd server was not able to run, due to an rpc error. This happens while the server is starting up, at boot time. The server does not come up, 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.
565591 Failed to add CMM version key %s, version %d to the CCR infrastructure table
Description:The CMM failed to register the CMM version in the CCR. The result of this failure will be to continue using the old CMM version during the next reconfiguration.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
565857 cl_execd: Going down on signal %d.
Description:The cl_execd program got a SIGTERM signal and is exiting.
Solution:This is an informational message. No user action is required.
565943 %s group name is not found in the netiflist property for node %s. Current netiflist value is %s.
Description:Netiflist property value does not have an IPMP group name specified for the node.
Solution:Update the netiflist property to include the IPMP group name for the given node. Then, retry the resource group update operation.
565978 Home dir is not set for user %s.
Description:Home directory for the specified user is not set in the system.
Solution:Check and make sure the home directory is set up correctly for the specified user.
566045 Zone cluster %s is not authorized to access IPMP group %s
Description:The zone cluster PNM client is seeking information about an IPMP group that is not configured to be used for the zone cluster.
Solution:This message is informational. No user action is required.
566180 Failed to configure the private IP address for %s
Description:Failed to get the zone cluster ID for the given zone cluster name.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
566781 ORACLE_HOME %s does not exist
Description:Directory specified as ORACLE_HOME does not exist. ORACLE_HOME property is specified when creating Oracle_server and Oracle_listener resources.
Solution:Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.
567338 Error in scha_rg_open of rg:%s, Err: %s
Description:Cannot open the resource group
Solution:Take action depending on the error depending on the error code
567374 Failed to stop %s.
Description:Sun Cluster failed to stop the application.
Solution:Use process monitor facility (pmfadm (1M)) with -L option to retrieve all the tags that are running on the server. Identify the tag name for the application in this resource. This can be easily identified as the tag ends in the string ".svc" and contains the resource group name and the resource name. Then use pmfadm (1M) with -s option to stop the application. This problem may occur when the cluster is under load and Sun Cluster cannot stop the application within the timeout period specified. Consider increasing the Stop_timeout property. If the error still persists, then reboot the node.
567783 %s - %s
Description:The first %s refers to the calling program, whereas the second %s represents the output produced by that program. Typically, these messages are produced by programs such as strmqm, endmqm rumqtrm etc.
Solution:No user action is required if the command was successful. Otherwise, examine the other syslog messages occurring at the same time on the same node to see if the cause of the problem can be identified.
567819 clcomm: Fixed size resource_pool short server threads: pool %d for client %d total %d
Description:The system can create a fixed number of server threads dedicated for a specific purpose. The system expects to be able to create this fixed number of threads. The system could fail under certain scenarios without the specified number of threads. The server node creates these server threads when another node joins the cluster. The system cannot create a thread when there is inadequate memory.
Solution:There are two possible solutions. Install more memory. Alternatively, reduce memory usage. Application memory usage could be a factor, if the error occurs when a node joins an operational cluster and not during cluster startup.
568314 Failed to remove node %d from 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.
568392 check_dhcp - Dhcpclient test timed out exceeded %s seconds
Description:The dhcpclient has exceeded it's timeout allowance.
Solution:No user action is required. Informational message, an immediate failover is being requested.
568789 libsecurity, door_call: Fatal, could not allocate space for return arguments, Client is out of memory.
Description:The client (libpmf/libfe/libscha) has run out of memory and the door call could not complete.
Solution:Check for swap space and/or memory usage of the client process. Try rebooting the node and/or check the client process configuration. Save the /var/adm/messages files on each node. Contact your authorized Sun service provider for assistance.
569010 Can't open %s
Description:Cannot open the file provided the extended resource property
Solution:Check for the permission and path validity of the file
569046 Failed to unregister CZMM callbacks: Unknown Error
Description:The cznetd daemon has failed to unregister the callbacks with zone cluster membership infrastructure for unknown reason.
Solution:Search for messages from cznetd to determine the source of the error. Save a copy of the /var/adm/messages files on all nodes. If the problem persists, contact your authorized Sun service provider for assistance in diagnosing the problem.
569552 %s: Create failed for netpath "circuit_v".
Description:This program could not create the RPC server handle.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
569559 Start of %s completed successfully.
Description:The resource successfully started the application.
Solution:This message is informational; no user action is needed.
569780 %s: fork_event: ct_pr_event_get_pid: %s
Description:The pmmd was unable to retrieve the pid from a contract event. The pmmd will continue to monitor the process, but the pmmd may have missed an event of interest.
Solution: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.
569889 Function: validate - Zonebrand for zone %s is configured as native, but the zone is configured as brand type %s.
Description:Zonebrand is set to "native". But the Zone is configured as a different brand type (i.e. lx) according to zonecfg info.
Solution:Review the components configuration file and make sure the variable Zonebrand defines the actual zone brand type for the Zone.
570204 Resource group %s rebalanced successfully
Description:The named resource group was successfully brought online on the cluster node.
Solution:This is an informational message, no user action is needed.
570394 reservation warning(%s) - USCSI_RESET failed for device %s, returned %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.
570525 Stopping startup script initiated by agent.
Description:The agent is attempting to stop a previous instance startup instruction that was issued to it.
Solution:No user action is required. Informational message.
571642 ucm_callback for cmmreturn generated exception %d
Description:ucmm callback for step cmmreturn 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.
571734 Validation failed. ORACLE_SID is not set
Description:ORACLE_SID property for the resource is not set. HA-Oracle will not be able to manage Oracle server if ORACLE_SID is incorrect.
Solution:Specify correct ORACLE_SID when creating resource. If resource is already created, please update resource property 'ORACLE_SID'.
571825 Stopping listener %s.
Description:Informational message. HA-Oracle will be stopping Oracle listener.
Solution:No user action is required.
571838 Failed to get information for filer "%s"
Description:The call to scnas_get_one_filer() failed. This call is supposed to return information regarding the given filer. Possible reasons for the failure might be that the filer is not configured yet.
Solution:Check that the NAS device is ready to work with Sun Cluster.
571946 The %s command returned error %s, unable to determine the zone name.
Description:The command used to determine the zone name has failed.
Solution:Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Refer to the documentation of Sun Cluster support for Real Application Clusters. If the problem persists, contact your Sun service representative.
572181 SCSLM <%s> pool_to_elem error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
572398 HA: primary RM died during boot, no secondary available, must reboot.
Description:Primary and secondaries for Replica Manger service are all dead, remaining nodes which are booting cannot rebuild RM state and must reboot immediately, even if they were able to form a valid partition from the quorum point of view.
Solution:No user action is required
572885 Pathprefix %s for resource group %s is not readable: %s.
Description:A HA-NFS method attempted to access the specified Pathprefix but was unable to do so. The reason for the failure is also logged.
Solution:This could happen if the filesystem on which the Pathprefix directory resides is not available. Use the HAStorage resource in the resource group to make sure that HA-NFS methods have access to the file system at the time when they are launched. Check to see if the pathname is correct and correct it if not so. HA-NFS would attempt to recover from this situation by failing over to some other node.
572955 host %s: client is null
Description:The rgm is not able to obtain an rpc client handle to connect to the rpc.fed server on the named host. 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.
573446 The filesystem mount point %s is neither present in VFSTAB of zone cluster %s nor configured to zone cluster %s.
Description:Self explanatory.
Solution:This happens when user forgets to keep the file system information in appropriate location. Retry the operation after providing the filesystem mountpoint information. If the problem persists, contact your authorized Sun service provider.
573931 Validate_sbp - MySQL replication resource group is not specified in option %s
Description:The required mysql replication resource group is not specified.
Solution:Make sure that the required resource group is specified.
574542 clexecd: fork1 returned %d. Exiting.
Description:The clexecd program has encountered a failed fork1(2) system call. The error message indicates the error number for the failure.
Solution:If the error number is 12 (ENOMEM), install more memory, increase swap space, or reduce peak memory consumption. If error number is something else, contact your authorized Sun service provider to determine whether a workaround or patch is available.
574675 nodeid of ctxp is bad : %d
Description:The nodeid in the context pointer is bad.
Solution:No user action is required. The udlm takes appropriate action.
574906 start_samba - Could not start Samba server %s %s daemon
Description:The Samba resource could not start the Samba server nmbd process.
Solution:The Samba resource will be restarted, however examine the other syslog messages occurring at the same time on the same node, to see if the cause of the problem can be identified.
575351 Can't retrieve binding entries from node %d for GIF node %d
Description:Failed to maintain client affinity for some sticky services running on the named server node. Connections from existing clients for those services might go to a different server node as a result.
Solution:If client affinity is a requirement for some of the sticky services, say due to data integrity reasons, these services must be brought offline on the named node, or the node itself should be restarted.
575545 fatal: rgm_chg_freeze: INTERNAL ERROR: invalid value of rgl_is_frozen <%d> for resource group <%s>
Description:The in-memory state of the rgmd has been corrupted due to an internal 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: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.
575724 Resource '%s' is part of an unmanaged resource group '%s'. Skipping this resource ...
Description:The zone boot handler detected that specified resource is part of an unmanaged resource group and hence skipping processing the resource.
Solution:This is an informational message; no user action is needed.
575905 Failed to stop DNS using the custom stop command; trying SIGKILL now.
Description:The stop command failed to stop the application.
Solution:Refer to your data services documentation for configuring the stop command. If problem persists, contact your Sun service provider to determine whether a workaround or patch is available.
576169 Validate callback completed successfully.
Description:The validate callback was successful.
Solution:No user action is required.
576196 clcomm: error loading kernel module: %d
Description:The loading of the cl_comm module failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
576621 Command %s does not have execute permission set.
Description:The specified pathname, which was passed to a libdsdev routine such as scds_timerun or scds_pmf_start, refers to a file that does not have execute permission set. This could be the result of 1) misconfiguring the name of a START or MONITOR_START method or other property, 2) a programming error made by the resource type developer, or 3) a problem with the specified pathname in the file system itself.
Solution:Ensure that the pathname refers to a regular, executable file.
576769 Start command %s failed with error %s.
Description:The execution of the command for starting the data service failed.
Solution:No user action needed.
577088 Waiting for WLS to startup
Description:This is just a informational message that the WLS is still starting up.
Solution:No user action is required
577130 Failed to retrieve network configuration: %s.
Description:Attempt to get network configuration failed. The precise error strings is included with the message.
Solution:Check to make sure that the /etc/netconfig file on the system is not corrupted and it has entries for tcp and udp. Additionally, make sure that the system has enough resources (particularly memory). HA-NFS would attempt to recover from this failure by failing over to another node, by crashing the current node, if this error occurs during STOP or POSTNET_STOP method execution.
577140 clcomm: Exception during unmarshal_receive
Description:The server encountered an exception while unmarshalling the arguments for a remote invocation. The system prints the exception causing this error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
577179 Device '/dev/%s' is not configured for zone %s.
Description:The specified device is not configured for the zone.
Solution:Check whether the disk group or specified volumes set for the resource is configured to the specified zone. If the problem persists even though the devices are properly configured and available in the specified zone, contact your authorized Sun service provider with /var/adm/messages of cluster nodes and zone configuration information.
577241 %s: Warning: The force option was needed to unmount %s
Description:The scshutdown command broadcasts a warning message of an impending cluster shutdown and provides a grace period for users to desist usage of file systems. Subsequently, if scshutdown cannot unmount a global filesystem because of continued activity, scshutdown uses the force option for unmount, regardless of user activity.
Solution:No user action is required.
577688 SCSLM fe_run wrong args <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
578055 stop_mysql - Failed to flush MySQL tables for %s
Description:The mysqladmin command failed to flush MySQL tables.
Solution:Either was MySQL already down or the fault monitor user does not have the right permission to flush tables. The defined fault monitor should have Process-, Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges.
578979 SCSLM zone <%s> bind to pool.sys_id %llu, which is not pool_default (pool.sys_id %llu)
Description:Non-global zone configuration error. A non-global zone used to run resource groups under SLM control must use pool pool_default, (zonecfg) and dynamically (poolbind).
Solution:Set zone pool to pool_default in zonecfg and set zone binding to pool_default (poolbind) before launching a resource group under SLM control in this zone.
579190 INTERNAL ERROR: resource group <%s> state <%s> node <%s> contains resource <%s> in state <%s>
Description:The rgmd has discovered that the indicated resource group's state information appears to be incorrect. This may prevent any administrative actions from being performed on the resource group.
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.
579208 Global service %s associated with path %s is found to be in maintenance state.
Description:Self explanatory.
Solution:Check the global service configuration.
579367 Update_drv failed to re-read did.conf file
Description:Update_drv command was NOT able to make did driver reread did.conf file after one retry. Will use devfsadm command instead.
Solution:This is an informational message, no user action is needed.
579575 Will not start database. Waiting for %s (HADB node %d) to start resource.
Description:The specified Sun Cluster node must be running the HADB resource before the database can be started.
Solution:Bring the HADB resource online on the specified Sun Cluster node.
579818 No entry for file-system %s found in /etc/vfstab.
Description:The entry for the specified shared QFS file system is missing from the /etc/vfstab file.
Solution:Add a valid entry for this file system to /etc/vfstab and repeat the operation.
579987 Error binding '%s' in the name server. Exiting.
Description:clexecd program was unable to start because of some problems in the low-level clustering software.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
580015 WebSphere MQ Trigger Monitor %s started
Description:The specified WebSphere MQ Trigger Monitor has been started.
Solution:No user action is required. Informational message.
580105 MQSeriesIntegrator2%s file deleted
Description:The WebSphere Broker fault monitor checks to see if MQSeriesIntegrator2BrokerResourceTableLockSempahore or MQSeriesIntegrator2RetainedPubsTableLockSemaphore exists within /var/mqsi/locks and that their respective semaphore id exists.
Solution:No user action is needed. If either MQSeriesIntegrator2%s file exists without an IPC semaphore entry, then the MQSeriesIntegrator2%s file is deleted. This prevents (a) Execution Group termination on startup with BIP2123 and (b) bipbroker termination on startup with BIP2088.
580416 Cannot restart monitor: Monitor is not enabled.
Description:An update operation on the resource would have been restarted the fault monitor. But, the monitor is currently disabled for the resource.
Solution:This is informational message. Check whether the monitor is disabled for the resource. If not, consider it as an internal error and contact your authorized Sun service provider.
580750 Auto_recovery_command should be a regular file: %s
Description:The Auto_recovery_command extension property needs to be a regular file.
Solution:Give appropriate file name to the extension property. Make sure that the path name does not point to a directory or any other file type. Moreover, the Auto_recovery_command could be a link to a file also.
580802 Either extension property <network_aware> is not defined, or an error occurred while retrieving this property; using the default value of TRUE.
Description:Property Network_aware might not be defined in RTR file. Use the default value of true.
Solution:This is an informational message; no user action is needed.
580918 Validate - %s/bin/%s is not a valid onconfig file
Description:${INFORMIXDIR}/bin/${ONCONFIG} is not a valid onconfig file.
Solution:Ensure that ${INFORMIXDIR}/etc/${ONCONFIG} is a valid onconfig file.
580948 fatal: can't be run in a non-global zone.
Description:The cl_apid can't be executed from a non-global zone.
Solution:Run cl_apid only from the global zone.
581117 Cleanup with command %s.
Description:Cleanup the SAPDB database instance before starting up the instance in case the database crashed and was in a bad state with the command which is listed.
Solution:Informational message. No user action is required.
581180 launch_validate: call to rpc.fed failed for resource <%s>, method <%s>
Description:The rgmd failed in an attempt to execute a VALIDATE method, due to a failure to communicate with the rpc.fed daemon. If the rpc.fed process died, this might lead to a subsequent reboot of the node. Otherwise, this will cause the failure of a creation or update operation on a resource or resource group.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Retry the creation or update operation. If the problem recurs, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
581376 clcomm: solaris xdoor: too much reply data
Description:The reply from a user level server will not fit in the available space.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
581413 Daemon %s is not running.
Description:HA-NFS fault monitor checks the health of statd, lockd, mountd, and nfsd daemons on the node. It detected that one these are not currently running.
Solution:No user action is required. The monitor would restart these.
581586 Failfast timeout - unit "%s" of zone "%s" (zone ID %d) %s
Description:The specified failfast unit has timed out, and is going to panic the zone.
Solution:There might be other related messages on this node that can help diagnose the problem. Resolve the problem and reboot the zone if the zone panic is unexpected.
581775 rgmx_set_timestamp(): failed
Description:The rgmd has encountered an error that prevents the scha_control function from successfully setting a ping-pong time stamp on a farm node, probably because of a node death or network failure.
Solution:Usually, no action is required. If another node is available, services will be restarted automatically.
581898 Application failed to stay up. Start method Failure.
Description:The application being started under pmf has exited. Either the user has decided to stop monitoring this process, or the process exceeded the number of retries. An error message is output to syslog.
Solution:Check syslog messages and correct the problems specified in prior syslog messages. Try to start the WebLogic Server manually and check if it can be started manually. Make sure the logical host is UP before starting the DAS manually. If it fails to start manually then check your configuration and make sure it can be started manually before it can be started by the agent. Make sure the extension properties are correct. Make sure the port is not already in use. Save a copy of the /var/adm/messages files on all nodes. If the error still persists, report this problem.
581902 (%s) invalid timeout '%d'
Description:Invalid timeout value for a method.
Solution:Make sure udlm.conf file has correct timeouts for methods.
582353 Adaptive server shutdown with wait failed. STOP_FILE %s.
Description:The Sybase adaptive server failed to shutdown with the wait option using the file specified in the STOP_FILE property.
Solution:This is an informational message, no user action is needed.
582418 Validation failed. SYBASE ASE startserver file not found SYBASE=%s.
Description:The Sybase Adaptive server is started by execution of the "startserver" file. This file is missing. The SYBASE directory is specified as a part of this error message.
Solution:Verify the Sybase installation including the existence and proper permissions of the "startserver" file in the $SYBASE/$SYBASE_ASE/install directory.
582636 Failed to obtain the list of SUNW.qfs resources that are configured for this zone cluster.
Description:Failed to get the list of SUNW.qfs resources that are configured for this zone cluster.
Solution:Investigate using the log messages and rectify the problem. If problem persists after rebooting the zone contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
582651 tag %s: does not belong to caller
Description:The user sent a suspend/resume command to the rpc.fed server for a tag that was started by a different user. An error message is output to syslog.
Solution:Check the tag name.
582789 Function: check_sczbt - %s runlevel [%s] not online, runlevel is %s, try again in 5 seconds
Description:The runlevel is not equal to the configured LXrunlevel. The state is checked again in 5 seconds.
Solution:No user action is required.
583147 scf_service_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.
583224 Rebooting this node because daemon %s is not running.
Description:The rpcbind daemon on this node is not running.
Solution:No user action is required. Fault monitor would reboot the node. Also see message id 804791.
583542 clcomm: Pathend: would abort node because %s for %u ms
Description:The system would have aborted the node for the specified reason if the check for send thread running was enabled.
Solution:No user action is required.
583970 Failed to shutdown liveCache immediately with command %s.
Description:Stopping SAP liveCache with the specified command failed to complete.
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.
584022 zoneadm call failed for zone %s: %d
Description:The attempted zoneadm call failed. The zone will stay up, but the rgmd will not attempt to start services on the zone.
Solution:Reboot the zone. 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 the problem.
584207 Stopping %s.
Description:Sun Cluster is stopping the specified application.
Solution:This is an informational message, no user action is needed.
584386 PENDING_OFFLINE: bad resource state <%s> (%d) for resource <%s>
Description:The rgmd state machine has discovered a resource in an unexpected state on the local node. 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.
584425 Validation failed. CRS_HOME/bin/crs_start not found CRS_HOME=%s
Description:The SUNW.scalable_rac_server_proxy agent could not find the crs_start binary in the indicated $CRS_HOME/bin/ directory.
Solution:Check whether the $CRS_HOME/bin/ directory is accessible, and if so, whether the crs_start binary exists. If the problem persists, contact your Sun support representative for further assistance.
585276 Could not read configuration of zone cluster %s.
Description:The process_cmd_log was unable to read the zone cluster configuration.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
585295 Validate - getservbyname file does not exist or is not executable at %s/getservbyname
Description:The file 'getservbyname' can not be found, or is not executable.
Solution:Confirm the file '${SGE_ROOT}/utilbin/<arch>/getservbyname' both exists in that location, and is executable.
585726 pthread_cond_init: %s
Description:The cl_apid was unable to initialize a synchronization object, so it was not able to start up. The error message is specified.
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.
585843 open64 while retrieving template info: %s
Description:The libclcontract code was unable to open a file in the /system/contract/process/ directory. Consequently, the process that is using libclcontract was unable to launch the requested process under its control.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
586052 Derby data service Stop method timed out
Description:The derby data service could not stop before the configured timeout elapsed.
Solution:This message is informational; no user action needed.
586294 Thread creation error: %s
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
586298 clcomm: unknown type of signals message %d
Description:The system has received a signals message of unknown type.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
586410 %s: core_event: ct_pr_event_get_pid: %s
Description:The pmmd was unable to retrieve the pid from a contract event. The pmmd will continue to monitor the process, but the pmmd may have missed an event of interest.
Solution: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.
586608 cl_execd: Attempt to set to real time scheduling class returned %d. Exiting.
Description:cl_execd program failed to set the priority and the scheduling class to real time for the task in execution.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
586689 Cannot access the %s command <%s> : <%s>
Description:The command input to the agent builder is not accessible and executable. This may be due to the program not existing or the permissions not being set properly.
Solution:Make sure the program in the command exists, is in the proper directory, and has read and execute permissions set appropriately.
586807 Telemetry data service monitor check method succeeded
Description:The monitor program of the telemetry data service reported success.
Solution:This message is informational; no user action needed.
587554 Function: validate - Syntax errors in %s
Description:The parameter file is not a valid shell script.
Solution:Correct the parameter file. It must pass ksh -n <file name>.
587573 cm_getstate failed with error %d
Description:Unable to get the cluster state.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
588055 Failed to retrieve information for SAP xserver user %s.
Description:The SAP xserver user is not found on the system.
Solution:Make sure the user is available on the system.
588074 Function: validate - The standby host %s is not resolvable
Description:The host specified in the STDBY_HOST variable is not resolvable.
Solution:Add the host to one of your configured name services, so it can get listed with getent.
589035 Error in the mnttab entry for mount point '%s'.
Description:An error occurred while the mnttab entry for the specified mount point was being read.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
589373 scha_control RESOURCE_RESTART 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. If problem persists, fault monitor will make another attempt to restart the listener.
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.
589594 scha_control: warning, RESOURCE_IS_RESTARTED call on resource <%s> will not increment the resource_restart count because the resource does not have a Retry_interval property
Description:A resource monitor (or some other program) is attempting to notify the RGM that the indicated resource has been restarted, by calling scha_control(1ha),(3ha) with the RESOURCE_IS_RESTARTED option. This request will trigger restart dependencies, but will not increment the retry_count for the resource, because the resource type does not declare the Retry_interval property for its resources. To enable the NUM_RESOURCE_RESTARTS query, the resource type registration (RTR) file must declare the Retry_interval property.
Solution:Contact the author of the data service (or of whatever program is attempting to call scha_control) and report the warning.
589805 Fault monitor probe response times are back below 50%% of probe timeout. The timeout will be reduced to it's configured value
Description:The resource's probe timeout had been previously increased by 10% because of slow response, but the time taken for the last fault monitor probe to complete, and the average probe time, are both now less than 50% of the timeout. The probe timeout will therefore be reduced to it's configured value.
Solution:This is an informational message, no user action is required.
589817 clcomm: nil_sendstream::send
Description:The system attempted to use a "send" operation for a local invocation. Local invocations do not use a "send" operation.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
590147 Resource%s has reached the max retries of its services and will be failing over now
Description:The number of restarts of services under the resource has reached the max. So the resource will be failing over
Solution:No user action is required. This is an informational message.
590454 TCPTR: Machine with MAC address %s is using cluster private IP address %s on a network reachable from me. Path timeouts are likely.
Description:The transport at the local node detected an arp cache entry that showed the specified MAC address for the above IP address. The IP address is in use at this cluster on the private network. However, the MAC address is a foreign MAC address. A possible cause is that this machine received an ARP request from another machine that does not belong to this cluster, but hosts the same IP address using the above MAC address on a network accessible from this machine. The transport has temporarily corrected the problem by flushing the offending arp cache entry. However, unless corrective steps are taken, TCP/IP communication over the relevant subnet of the private interconnect might break down, thus causing path downs.
Solution:Make sure that no machine outside this cluster hosts this IP address on a network reachable from this cluster. If there are other Sun Clusters sharing a public network with this cluster, make sure that their private network adapters are not miscabled to the public network. By default all Sun Clusters use the same set of IP addresses on their private networks.
590700 ALERT_LOG_FILE %s doesn't exist
Description:File specified in resource property 'Alert_log_file' does no exist. HA-Oracle requires correct Alert Log file for fault monitoring.
Solution:Check 'Alert_log_file' property of the resource. Specify correct Oracle Alert Log file when creating resource. If resource is already created, please update resource property Alert_log_file'.
591719 Invalid error return (%d) from device group probe
Description:An unexpected error occurred in the probe of a disk set or disk group.
Solution:Contact your authorized Sun service provider for further assistance in diagnosing the problem.
592233 setrlimit(RLIMIT_NOFILE): %s
Description:The rpc.pmfd server was not able to set the limit of files open. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, 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.
592276 (%s) not owner of diskgroup (%s)
Description:This node is not the owner of the disk set or disk group.
Solution:Determine whether the SUNW.rac_framework resource is online. To obtain this information, run 'scstat -b'. Determine whether the node is in the node list of the disk set or disk group. To retrieve the node list of the disk set or disk group, run scstat -D or cldevicegroup show.
592285 clexecd: getrlimit returned %d
Description:clexecd program has encountered a failed getrlimit(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.
592305 Failed to retrieve the resource property %s on node %s: %s.
Description:The query for a property 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.
592352 SCSLM <%s> error pmin > pmax
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
592378 Resource %s is not online anywhere.
Description:The named resource is not online on any cluster node.
Solution:No user action is required. This is an informational message.
592920 sigemptyset: %s
Description:The rpc.pmfd server was not able to initialize a signal set. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
593143 Incorrect number of volumes!
Description:The number of volumes that a call to libvxvmsc.so returned differs from the number that an earlier call returned.
Solution:Check the status of the disk set or disk group. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
593330 Resource type name is null.
Description:This is an internal error. While attempting to retrieve the resource information, null value was retrieved for the resource type name.
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.
593406 Could not delete node %s from zone cluster %s.
Description:The process_cmd_log was unable to delete a node from the zone cluster configuration.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
593712 ORACLE_SID extension property must match the ORACLE_SID environment variable setting for Oracle.
Description:The value of the ORACLE_SID extension property should be a valid value, that is identical to the value of the ORACLE_SID environment variable set before starting up the Oracle database.
Solution:In order to bring the resource online, set the value of the ORACLE_SID extension property of the Sun Cluster resource to the value for that Oracle instance using appropriate Sun Cluster commands and retry bringing the resource online.
593855 Custom monitor actions found in %s. These will override the default actions.
Description:This message indicates that a custom monitor action file has been configured. The entries in this file will determine the actual action that is taken for the specified errors. In case any error is specified in both, the custom and the default action files, the action specified in the custom action file will be chosen.
Solution:No user action is required.
594348 About to umount %s.
Description:HAStoragePlus will umount the underlying device corresponding to the mount point that is specified in /etc/mnttab.
Solution:This is an informational message, no user action is needed.
594396 Thread creation failed for node %d.
Description:The cl_eventd failed to create a thread. This error may cause the daemon to operate in a mode of reduced functionality.
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.
595077 Error in hasp_check. Validation failed.
Description:Internal error occurred in hasp_check.
Solution:Check the errors logged in the syslog messages by hasp_check. Please verify the existence of /usr/cluster/bin/hasp_check binary. Please report this problem.
595101 t_sndudata in send_reply: %s
Description:Call to t_sndudata() failed. The "t_sndudata" man page describes possible error codes. udlm will try to re-send the message. abort.
Solution:No user action is required.
595131 The MDS for '%s' file system of resource '%s' is running on node '%s'.
Description:This is a notification from the handler about the location of the node where metadata server is running.
Solution:This is an informational message; no user action is needed.
595276 Membership: Could not create CMM membership API object. Membership API would not work.
Description:Could not create the CMM membership API object. 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.
595448 Validate - mysqld %s nonexistent executable
Description:The mysqld command does not exist or is not executable.
Solution:Make sure that MySQL is installed correctly or right base directory is defined.
595686 %s is %d for %s. It should be 1.
Description:The named property has an unexpected value.
Solution:Change the value of the property to be 1.
595774 cm_getclustmbyname failed
Description:Unable to get the cluster name.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
595926 Stopping Adaptive server with nowait option.
Description:The Sun Cluster HA for Sybase will retry the shutdown using the nowait option.
Solution:This is an informational message, no user action is needed.
596001 The fault monitor will not be restarted
Description:Fault Monitor will not be restarted when resource is configured to indicate Database role transition.
Solution:No user action is required. Informational message.
596326 Failed to retrieve Nameserver reference
Description:The pnm proxy daemon could not get a reference to the local nameserver.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
596447 UNIX DLM is asking for a reconfiguration to recover from a communication error.
Description:A reconfiguration has been requested by udlm.
Solution:No user action is required.
596604 clcomm: solookup on routing socket failed with error = %d
Description:The system prepares IP communications across the private interconnect. A lookup operation on the routing socket failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
596938 Could not restart the derby data service
Description:The Derby data service could be restarted.
Solution:For more detailed error message, check the syslog messages. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
597239 The weight portion of %s at position %d in property %s is not a valid weight. The weight should be an integer between %d and %d.
Description:The weight noted does not have a valid value. The position index, which starts at 0 for the first element in the list, indicates which element in the property list was invalid.
Solution:Give the weight a valid value.
597381 setrlimit before exec: %s
Description:The rpc.pmfd was unable to set the number of file descriptors before executing a process.
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.
598087 PCWSTOP: %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.
598115 Ignoring invalid expression <%s> in custom action file.
Description:This is an informational message indicating that an entry with an invalid expression was found in the custom action file and will be ignored.
Solution:Remove the invalid entry from the custom action file or correct it to be a valid regular expression.
598341 About to lofs mount of %s on %s in local zone '%s'. Underlying files and directories will be inaccessible.
Description:HAStoragePlus detected that the directory of local zone on which loopback mount is about to happen is not empty, hence once mounted, the underlying files will be inaccessible.
Solution:This is an informational message, no user action is needed.
598540 clcomm: solaris xdoor: completed invo: door_return returned, errno = %d
Description:An unusual but harmless event occurred. System operations continue unaffected.
Solution:No user action is required.
598554 launch_validate_method: getlocalhostname() failed for resource <%s>, resource group <%s>, method <%s>
Description:The rgmd daemon was unable to obtain the name of the local host, causing a VALIDATE method invocation to fail. This in turn will cause the failure of a creation or update operation on a resource or resource group.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Retry the creation or update operation. If the problem recurs, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
598979 tag %s: already suspended
Description:The user sent a suspend command to the rpc.fed server for a tag that is already suspended. An error message is output to syslog.
Solution:Check the tag name.
599371 Failed to stop the WebLogic server smoothly. Will try killing the process using sigkill.
Description:The Smooth shutdown of the WLS failed. The WLS stop method however will go ahead and kill the WLS process.
Solution:Check the WLS logs for more details. Check the /var/adm/messages and the syslogs for more details to fix the problem.
599430 Failed to retrieve the resource property %s: %s.
Description:An API operation has failed while retrieving the resource property. Low memory or API call failure might be the reasons.
Solution:In case of low memory, the problem will probably cured by rebooting. If the problem reoccurs, you might need to increase swap space by configuring additional swap devices. Otherwise, if it is API call failure, check the syslog messages from other components. For the resource name and property name, check the current syslog message.
Message IDs 600000–699999
This section contains message IDs 600000–699999.
600366 Validate - file %s does not exist
Description:validation that file indicated has not been found by the agent.
Solution:Check all required files are available on both nodes, readable and in the same location.
600398 validate - file %s does not exist
Description:The parameter file of option -N of the start, stop or probe command does not exist.
Solution:correct the filename and reregister the data service.
600552 validate: User is not set but it is required
Description:The user is not set in the parameter file, or in the start stop or probe command.
Solution:Set the user in the appropriate place. If it is from the master server use the parameter file, otherwise use the start, stop, or probe command.
600874 CCR: Can't access table %s (cluster %s) while updating it on node %s, errno = %d.
Description:The indicated error occurred while updating the indicated table on the indicated node. 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 file system on the node is full. Other values of errno can be returned when the root disk has failed (EIO) or some of the CCR tables have been deleted outside the control of the cluster software (ENOENT).
Solution:There may be other related messages on the node where the failure occurred. These 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 indicated table was accidently deleted, then boot the offending node in -x mode to restore the indicated table from other nodes in the cluster. The CCR tables are located at /etc/cluster/ccr/. If the root disk on the afflicted node has failed, then it needs to be replaced.
600885 Validate - User informix does not exist
Description:The userid informix does not exist.
Solution:You must create the userid informix.
600967 Could not allocate buffer for DBMS log messages: %m
Description:Fault monitor could not allocate memory for reading RDBMS log file. As a result of this error, fault monitor will not scan errors from log file. However it will continue fault monitoring.
Solution:Check if system is low on memory. If problem persists, please stop and start the fault monitor.
601609 Nameserver failed to register with cluster HA framework
Description:The Nameserver repl server failed to register with the cluster HA framework.
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.
601624 CMM: Quorum device %d (%s) with votecount = %d removed.
Description:The specified quorum device with the specified votecount has been removed from the cluster. A quorum device being placed in maintenance state is equivalent to it being removed from the quorum subsystem's perspective, so this message will be logged when a quorum device is put in maintenance state as well as when it is actually removed.
Solution:This is an informational message, no user action is needed.
601901 Failed to retrieve the resource property %s for %s: %s.
Description:The query for a property 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.
603092 An unknown value for the RG_mode property was found for resource group %s.
Description:The RG_mode of the specified resource group is neither Failover or Scalable.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
603096 resource %s disabled.
Description:This is a notification from the rgmd that the operator has disabled a resource. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
603149 Error reading file %s
Description:Specified file could not be read or opened.
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.
603192 The resource type version of resource %s is NULL.
Description:The HAStoragePlus resource type version of the specified resource was found to be NULL.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
603913 last probe failed, Tomcat considered as unavailable
Description:the last sanity check was unsuccessful, may be out of sessions
Solution:none required, it is recommended to observe Tomcats number of configured sessions
604016 Failed to open contract ctl file %s: %s
Description:Cannot open the contract control file.
Solution:Check the contract man page to know more about the error. Also make sure the basic contract functionalities are working. Contact your SUN vendor for more help.
604153 clcomm: Path %s errors during initiation
Description:Communication could not be established over the path. The interconnect might have failed or the remote node might be down.
Solution:Any interconnect failure should be resolved, and/or the failed node rebooted.
604333 The FilesystemCheckCommand extension property is set to %s.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
604554 Function: validate - The host %s is not resolvable
Description:The host specified in the PGHOST variable is not resolvable.
Solution:Create the host entry in /etc/hosts.
604784 Probing SAP xserver timed out with command %s.
Description:Probing the SAP xserver with the listed command timed out.
Solution:Other syslog messages occurring just before this one might indicate the reason for the failure. You might consider increase the time out value for the method error was generated from.
604841 %s - The user %s does not belongs to project %s
Description:The specified user does not belong to the project defined by Resource_project_name or Rg_project_name.
Solution:Add the user to the defined project in /etc/project.
604889 PNM proxy : Unable to get a reference to the version manager
Description:PNM proxy got a nil reference to the Version manager and hence failed to retrieve the version.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
605136 Command request "%s" came in on the public network (%s), rather than the private (%s)
Description:The rpc.scrcmd daemon received an illegal request to over the public network to execute a command. Command requests of this type are expected over the private network only.
Solution:Report this problem to you Sun service representative. It could be that an internal error in the Sun Cluster code has neglected to send the command request over the correct network.
605301 lkcm_sync: invalid handle was passed %s%d
Description:Invalid handle passed during lockstep execution.
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.
605502 Validate - DHCP is not enabled (DAEMON_ENABLED)
Description:The DHCP resource requires that the /etc/inet/dhcpsvc.conf file has DAEMON_ENABLED=TRUE.
Solution:Ensure that /etc/inet/dhcpsvc.conf has DAEMON_ENABLED=TRUE by configuring DHCP appropriately, i.e. as defined within the Sun Cluster Data Service for DHCP.
605879 Validate - CON_LIMIT=%s is incorrect, default CON_LIMIT=50 is being used
Description:The value specified for CON_LIMIT is invalid.
Solution:Either accept the default value of CON_LIMIT=50 or change the value of CON_LIMIT to be less than or equal to 100 when registering the resource. CON_LIMIT=50 will now be used.
606008 The special device %s of the filesystem mount point %s in vfstab of zone cluster %s is not mapped.
Description:The specified device is not authorized to use in specified zone cluster as it are not configured to zone cluster.
Solution:The operation needs to be retried after the specified device got configured to zone cluster. If the problem persists, contact your authorized Sun service provider with /var/adm/messages of cluster nodes.
606203 Couldn't get the root vnode: error (%d)
Description:The file system is corrupt or was not mounted correctly.
Solution:Run fsck, and mount the affected file system again.
606362 The stop command <%s> failed to stop the application. Will now use SIGKILL to stop the application.
Description:The stop command was unable to stop the application. The STOP method will now stop the application by sending it SIGKILL.
Solution:Look at application and system logs for the cause of the failure.
606412 Command '%s' failed: %s. The logical host of the database server might not be available. User_Key and related information cannot be verified.
Description:The command that is listed failed for the reason that is shown in the message. The failure might be caused by the logical host not being available.
Solution:Ensure the logical host that is used for the SAPDB database instance is online.
606758 SCSLM <%s> pool_value_alloc error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
607054 %s not found.
Description:Could not find the binary to startup udlm.
Solution:Make sure the UNIX dlm package is installed properly.
607452 cl_execd: memory allocation failed size = %d
Description:Could not allocate memory. Node is too low on memory.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
607541 Generic_Affinity and UDP_Affinity are mutually exclusive features.
Description:Generic_Affinity and UDP_Affinity are mutually exclusive features.
Solution:Enable either Generic_Affinity or UDP_Affinity for the resource.
607613 transition '%s' timed out for cluster, as did attempts to reconfigure.
Description:Step transition failed. udlmctl will exit.
Solution: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.
607678 clconf: No valid quorum_resv_key field for node %u
Description:Found the quorum_resv_key field being incorrect while converting the quorum configuration information into quorum table.
Solution:Check the quorum configuration information.
607726 sysevent_subscribe_event(): %s
Description:The cl_apid or cl_eventd 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.
608202 scha_control: resource group <%s> was frozen on Global_resources_used within the past %d seconds; exiting
Description:A scha_control call has failed with a SCHA_ERR_CHECKS error because the resource group has a non-null Global_resources_used property, and a global device group was failing over within the indicated recent time interval. The resource fault probe is presumed to have failed because of the temporary unavailability of the device group. A properly-written resource monitor, upon getting the SCHA_ERR_CHECKS error code from a scha_control call, should sleep for awhile and restart its probes.
Solution:No user action is required. Either the resource should become healthy again after the device group is back online, or a subsequent scha_control call should succeed in failing over the resource group to a new master.
608286 Stopping the text server.
Description:The Text server is about to be brought down by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed.
608414 The %s value should be greater than %d: Hence ignoring this value from %s file at line %d.
Description:The zone handler detected a bad value for the specified tunable in the specified configuration file.
Solution:Fix the specified tunable value so that it meets the restrictions.
608453 failfast disarm error: %d
Description:Error during a failfast device disarm operation.
Solution:No user action is required.
608587 Validate - smbclient %s nonexistent executable
Description:The Samba resource tries to validate that the smbclient exists and is executable.
Solution:Check the correct pathname for the Samba bin directory was entered when registering the resource and that the program exists and is executable.
608749 Failed to retrieve the resource handle of resource %s: %s.
Description:There was a failure while retrieving to retrieve a handle of the named resource. The reason that the error occurred is also provided in the message.
Solution:The operation will be retried after some time. But there might be a delay in failing over some HA-NFS resources. If this message is logged repeatedly, save a copy of the syslog and contact your authorized Sun service provider.
608876 PCRUN: %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.
609118 Error creating deleted directory: error (%d)
Description:While mounting this file system, PXFS was unable to create some directories that it reserves for internal use.
Solution:If the error is 28(ENOSPC), then mount this FS non-globally, make some space, and then mount it globally. If there is some other error, and you are unable to correct it, contact your authorized Sun service provider to determine whether a workaround or patch is available.
609401 The %s extension property is not set.
Description:While validating the extension properties, The HADBM_PASSWORDFILE extension property is found not to be set.
Solution:This is an informational message, The user has to provide the complete path to the hadbm admin password file if the domain is created with a password.
609730 clcomm: failed to create thread for monitor
Description:The system could not create the needed thread, because there is inadequate memory.
Solution:There are two possible solutions. Install more memory. Alternatively, reduce memory usage. Since this happens during system startup, application memory usage is normally not a factor.
609889 UNRECOVERABLE ERROR: %s file not present.
Description:/usr/cluster/lib/scadmin/ql/upgrade_partition file not present.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
610051 The device to fsck %s of the filesystem mount point %s in vfstab of zone cluster %s is not mapped.
Description:The specified device is not authorized to use in specified zone cluster as it are not configured to zone cluster.
Solution:The operation needs to be retried after the specified device got configured to zone cluster. If the problem persists, contact your authorized Sun service provider with /var/adm/messages of cluster nodes.
610273 IPMP group %s has failed, so scalable resource %s in resource group %s may not be able to respond to client requests. A request will be issued to relocate resource %s off of this node.
Description:The named IPMP group has failed, so the node may not be able to respond to client requests. It would be desirable to move the resource to another node that has functioning IPMP groups. A request will be issued on behalf of this resource to relocate the resource to another node.
Solution:Check the status of the IPMP group on the node. Try to fix the adapters in the IPMP group.
610633 %s: problem waiting for the daemon, read errno %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
610960 Failed to get the list of disks from CCR, line %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
610998 Membership : State machine for '%s' related to zone cluster '%s' entered an invalid state %s; previous state was %s, previous event was %s.
Description:The membership state machine for this membership related to a zone cluster has entered an invalid state.
Solution:Shut down the zone cluster and then boot it back. This series of actions will clear the immediate problem. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.
610998 validate: The N1 Grid Service Provisioning System remote agent start command does not exist, its not a valid remote agent installation
Description:The Basepath is set to a false value.
Solution:Fix the Basepath of the start, stop or probe command of the remote agent.
611315 PMF is not used, but validation failed. Cannot run stopsap command.
Description:Validation failed while PMF is not configured. Termination of the SAP processes might not be complete.
Solution:Informational message. No user action is needed.
611676 ct_pr_tmpl_set_param: %s
Description:The libclcontract code was unable to configure a process template in which to launch the requested service. Consequently, the process that is using libclcontract was unable to launch the process under its control.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
611732 statvfs failed on the mount point %s for zone cluster %s node : %s
Description:The file system specified on the mount point is not available for zone cluster.
Solution:Check the statvfs(2) man page for errors and try to resolve the problem. Otherwise contact your authorized Sun service provider.
611913 Updating configuration information.
Description:The HADB START method is updating it's configuration information.
Solution:This is an informational message, no user action is needed.
612117 Failed to stop Text server.
Description:Sun Cluster HA for Sybase failed to stop text server.
Solution:Please examine whether any Sybase server processes are running on the server. Please manually shutdown the server.
612124 Volume configuration daemon not running.
Description:Volume manager is not running.
Solution:Bring up the volume manager.
612436 Method <%s> on resource <%s>: Execution failed: SLM error
Description:Resource group is under SC SLM control and an SLM error occurred. Some errors might be configuration errors. Check fed SLM errors for more details.
Solution:Move RG_SLM_type to manual and restart the resource group.
612562 Error on line %ld
Description:Indicates the line number on which the error was detected.
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.
612689 Failed to register configuration callbacks for cznetd daemon
Description:The cznetd daemon was unable to register for configuration callbacks.
Solution:These callbacks are used only for enabling or disabling the private IP communication for zone clusters. So, this feature will be unavailable. To recover, it might be necessary to reboot this node or the entire cluster. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
612819 reservation warning(%s) - MHIOCGRP_PREEMPTANDABORT 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.
612931 Unable to get device major number for %s driver : %s.
Description:System was unable to translate the given driver name into device major number.
Solution:Check whether the /etc/name_to_major file is corrupted. Reboot the node if problem persists.
613298 Stopping %s timed out with command %s.
Description:An attempt to stop the application by the command that is listed was timed out.
Solution:Other syslog messages that occur shortly before this message might indicate the reason for the failure. A more severe command will be used to stop the application after the command in the message was timed out. No user action is needed.
613522 clexecd: Error %d from poll. Exiting.
Description:clexecd program has encountered a failed poll(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.
613814 SCSLM <%s> zone <%s> no users
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
613966 Error: attempted to run this script in global zone
Description:The svc:/system/cluster/sc_ng_zones:default SMF service should run only in non-global zones.
Solution:Disable the svc:/system/cluster/sc_ng_zones:default service in the global zone.
613984 scha_control: request failed because the given resource group <%s> does not contain the given resource <%s>
Description:A resource monitor (or some other program) is attempting to initiate a restart or failover on the indicated resource and group by calling scha_control(1ha),(3ha). However, the indicated resource group does not contain the indicated resource, so the request is rejected. This represents a bug in the calling program.
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.
614266 SVM is not properly installed, %s not found.
Description:Could not find the program that is required to support Solaris Volume Manager with Sun Cluster framework for Oracle Real Application Clusters.
Solution:Verify installation of Solaris Volume Manager and Solaris version. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure. If problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
614310 Function: validate - SLrunlevel not set in %s
Description:The SLrunlevel variable is not set in the parameter file sczbt_<resource name>.
Solution:Set the SLrunlevel variable in the parameter file sczbt_<resource name>.
614373 Membership: Unable to create CCR callback thread for membership subsystem. Zone cluster membership support would not be available fully
Description:A thread that supports dynamic addition/removal of zone clusters to the membership subsystem could not be created. Membership for dynamically added or removed zone clusters would not work properly. 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.
614556 sema_post 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: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.
614872 Create_configuration - MySQL replication resource group %s contains a MySQL database resource
Description:The MySQL replication resource group contains a MySQL database resource already
Solution:Specify a replication resource group without MySQL database resources
615120 fatal: unknown scheduling class '%s'
Description:An internal error has occurred. The daemon indicated in the message tag (rgmd or ucmmd) will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
615207 %s: ct_pr_event_get_exitstatus: %s
Description:The pmmd was unable to determine the exit status of a process under its control that exited. It will assume failure.
Solution: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.
616381 %s: renamed %s.db to %s
Description:The principal database was renamed from the old name "principal.db" to the new name "principal".
Solution:This is for informational purposes, no action is required.
617169 Error while unbinding '%s' in the name server. Exiting.
Description:The cl_execd program could not unbind the corba object from the global name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
617385 readdir_r: %s
Description:An error occurred when rpc.pmfd tried to use the readdir_r function. The reason for the failure is also given.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
617602 The SUNW.qfs resource '%s' is not online on this node. Skipping this resource ...
Description:The specified SUNW.qfs resource is not online on this node. That means the MDS server(s) of shared qfs file systems of this resource will not be running on this node. Hence skipping the resource.
Solution:This is an informational message; no user action is needed.
617716 SCSLM zone <%s> pool configuration error, pool <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
617876 clcomm: getzonenamebyid failed: %s
Description:The getzonenamebyid(3C) operation failed. The man page for getzonenamebyid describes possible error codes.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
617917 Initialization failed. Invalid command line %s %s
Description:Unable to process parameters passed to the call back method. This is an internal error.
Solution:Please report this problem.
618075 sig_handler sigfillset: %s
Description:Internal error.
Solution:Save the syslog messages file. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
618107 Path %s initiation encountered errors, errno = %d. Remote node may be down or unreachable through this path.
Description:Communication with another node could not be established over the path.
Solution:Any interconnect failure should be resolved, and/or the failed node rebooted.
618466 UNIX DLM no longer running
Description:UNIX DLM is expected to be running, but is not. This will result in a udlmstep1 failure.
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.
618585 clexecd: getmsg returned %d. Exiting.
Description:The clexecd program has encountered a failed getmsg(2) system call. The error message indicates the error number for the failure.
Solution:The clexecd program will exit and the 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.
618709 Failed to generate callback for add adapter event
Description:Cluster cannot generate a callback for the RDS module. Operation of RDS sockets might be affected.
Solution:If Reliable Datagram Sockets (RDS) is used by applications running on this cluster, contact your Sun Microsystems service representative to determine if a workaround or patch is available.
618764 fe_set_env_vars() failed for Resource <%s>, resource group <%s>, method <%s>
Description:The rgmd daemon was unable to set up environment variables for a method execution, causing the method invocation to fail. 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: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.
619059 sigaction(2) failed for pmmd_adm while querying disposition for signal SIG%s: error %s
Description:The pmmd_adm was unable to query the signal disposition for a signal number because the sigaction(2) function failed. The message contains the system error. pmmd_adm cannot do its requested action.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
619171 Failed to retrieve information for user %s for SAP system %s.
Description:Failed to retrieve home directory for the specified SAP user for the specified system ID.
Solution:Check the system ID for SAP. SAPSID is case sensitive.
619213 t_alloc (recv_request) failed with error %d
Description:Call to t_alloc() failed. The "t_alloc" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
619719 check_pgs: The PostgreSQL process %s is not running
Description:The PostgreSQL process is not running.
Solution:No user action is required.
619986 Invalid zone cluster id %d passed for zone %s
Description:Zone cluster id information that has been passed does not match the client credentials.
Solution:Someone has tampered with the Sun cluster code. This is a security violation. Shut down the identified zone.
620007 UCMM is not in a stable state; can not continue IO probing !
Description:Because the UCMM is in an unstable state, the probe cannot continue.
Solution:Check the state of the UCMM and, if required, restart the UCMM and repeat the operation.
620193 Validation failed.
Description:Validation of the ScalMountPoint resource failed.
Solution:Look for specific errors from the function 'validate_mountpoint_rs()' that caused validation to fail. Correct the error and repeat the operation.
620267 Starting SAP Central Service.
Description:This message indicates that the data service is starting the SCS.
Solution:No user action needed.
620599 The metadata server of configured SUNW.qfs resources either moved to other node or this node is acting as metadata server being last client of shared qfs file systems. Zone halt operation completed successfully.
Description:The zone halt handler completed its operation successfully.
Solution:This is an informational message; no user action is needed.
620784 MQSeriesIntegrator2%s exists without an IPC semaphore entry
Description:The WebSphere Broker fault monitor checks to see if MQSeriesIntegrator2BrokerResourceTableLockSempahore or MQSeriesIntegrator2RetainedPubsTableLockSemaphore exists within /var/mqsi/locks and that their respective semaphore id exists.
Solution:No user action is needed. If either MQSeriesIntegrator2%s file exists without an IPC semaphore entry, then the MQSeriesIntegrator2%s file is deleted. This prevents (a) Execution Group termination on startup with BIP2123 and (b) bipbroker termination on startup with BIP2088.
621426 %s is not an ordinary file.
Description:The path listed in the message is not an ordinary file.
Solution:Specify an ordinary file path for the extension property.
621686 CCR: Invalid checksum length %d in table %s, expected %d.
Description:The checksum of the indicated table has a wrong size. This causes the consistency check of the indicated table to fail.
Solution:Boot the offending node in -x mode to restore the indicated table from backup or other nodes in the cluster. The CCR tables are located at /etc/cluster/ccr/.
622011 SCSLM exec <%s> strlen is zero
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
622352 Could not kill the derby data service monitor
Description:The monitor program of the derby data service could not be stopped. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
622839 Failed to retrieve the extension property %s: %s.
Description:The extension property could not be retrieved for the reason that is stated in the message.
Solution:For details of the failure, check for other messages in /var/adm/messages.
622945 fork_event: ct_pr_event_get_pid: %s
Description:The rpc.pmfd was unable to retrieve the pid from a contract event. The rpc.pmfd will continue to monitor the process, but the rpc.pmfd may have missed an event of interest.
Solution: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.
622951 Membership : Could not create event packet for membership (%s); node is low on memory
Description:Data structures required for membership reconfiguration could not be created. This hints at real shortage of memory.
Solution:Lack of memory can lead to other problems on the node. This node will now halt to avoid more problems. Add more memory to the node and boot it back.
622960 Failed to lookup command log for zone cluster %s
Description:The CCR raised an exception while looking up the command log table.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
623159 %s: Hostname not set.
Description:The hostname of the cluster node has not been set.
Solution:Check if the hostname has been set for the node. Contact your authorized Sun service provider for further assistance.
623528 clcomm: Unregister of adapter state proxy failed
Description:The system failed to unregister an adapter state proxy.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
623635 Warning: Failed to configure client affinity for 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.
623669 Internal Error. Failed to check status of SUNW.HAStoragePlus resource.
Description:This is an internal error during SUNW.HAStoragePlus resource dependencies status validation.
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.
624265 Text server terminated.
Description:Text server processes were stopped in STOP method.
Solution:No user action is required.
624447 fatal: sigaction: %s (UNIX errno %d)
Description:The rgmd has failed to initialize signal handlers by a call to sigaction(2). The error message indicates the reason for the failure. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
624484 metastat output is empty for %s/%s.
Description:Output from metastat command is empty. Either the metaset is empty or the node is not the owner of the metaset.
Solution:Determine why the node is not hosting the disk set or disk group. Examine the output from metaset. Determine whether the SUNW.rac_framework resource and either the SUNW.rac_svm resource or the SUNW.rac_cvm resource are online.
624617 Tag %s: could not get retry count
Description:The rpc.pmfd server was not able to allocate memory for the history of the tag shown. Monitoring of the process associated with the tag is stopped and pmfadm returns an error. This problem can occur if the machine has low memory.
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.
624622 Notifying cluster that this node is panicking
Description:The node is notifying the other remaining cluster nodes that the node is going down due to a system panic.
Solution:No user action is required.
625493 Error: ${PROCESS} is not running.
Description:The initfed init script found that the rpc.pmfd is not running. The rpc.fed will not be started, which will prevent the rgmd from starting, and which will prevent this node from participating as a full member of the cluster.
Solution:Examine other syslog messages occurring at about the same time to determine why the rpc.pmfd is not running. 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.
625862 ct_event_read error'd out: %d
Description:Not able to read the event from the file descriptor obtained from the pbundle.
Solution:Check the contract man page to know more about the error. Also make sure the basic contract functionalities are working. Contact your SUN vendor for more help.
626478 stat of file %s failed: <%s>.
Description:There was a failure to stat the specified file.
Solution:Make sure that the file exists.
626904 cl_execd: Attempt to set scheduling class to Fair share returned %d. Exiting.
Description:cl_execd program failed to set the priority and the scheduling class to Fair share for the task in execution.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
627169 Function: val_parfile - Directory %s does not exist or is not a directory
Description:The parameter file directory you specified in the config file does not exist.
Solution:Fix the appropriate config file, either sczbt_config or sczsh_config with an existing directory.
627220 scvxvmlg warning - found no match for %s, removing it
Description:The program responsible for maintaining the VxVM device namespace has discovered inconsistencies between the VxVM device namespace on this node and the VxVM configuration information stored in the cluster device configuration system. If configuration changes were made recently, then this message should reflect one of the configuration changes. If no changes were made recently or if this message does not correctly reflect a change that has been made, the VxVM device namespace on this node may be in an inconsistent state. VxVM volumes may be inaccessible from this node.
Solution:If this message correctly reflects a configuration change to VxVM diskgroups then no action is required. If the change this message reflects is not correct, then the information stored in the device configuration system for each VxVM diskgroup should be examined for correctness. If the information in the device configuration system is accurate, then executing '/usr/cluster/lib/dcs/scvxvmlg' on this node should restore the device namespace. If the information stored in the device configuration system is not accurate, it must be updated by executing '/usr/cluster/bin/scconf -c -D name=diskgroup_name' for each VxVM diskgroup with inconsistent information.
627280 INTERNAL ERROR: usage: `basename $0` <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.
627500 Invalid upgrade callback from version manager: new version %d.%d is not the expected new version %d.%d from callback step 1.
Description:Version manager delivered upgrade callback to rgmd about a new version that is not the expected new version after callback step 1 for rgmd.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
627610 clconf: Invalid clconf_obj type
Description:An invalid clconf_obj type has been encountered while converting an clconf_obj type to group name. Valid objtypes are "CL_CLUSTER", "CL_NODE", "CL_ADAPTER", "CL_PORT", "CL_BLACKBOX", "CL_CABLE", "CL_QUORUM_DEVICE".
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.
627736 Error while unpacking data: %s
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.
627890 Unhandled error from probe command %s: %d
Description:The data service detected an internal error.
Solution:Informational message. No user action is needed.
628075 Start of HADB node %d completed successfully.
Description:The HADB resource successfully started the specified node.
Solution:This is an informational message, no user action is needed.
628155 DB_name, %s, does not match last component of Confdir_list, %s.
Description:The db_name extension property does not match the database name in the confdir_list path.
Solution:Check to see if the db_name and confdir_list extension properties are correct.
628473 Verify SVM installation. metaclust binary %s not found
Description:Could not find the program that is required to support Solaris Volume Manager with Sun Cluster framework for Oracle Real Application Clusters.
Solution:Verify installation of Solaris Volume Manager and updates. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure. If problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
628545 %s:error in method %s: %d
Description:Problem in the execution of the smf method.
Solution:The waitpid which was waiting on the completion of the process exited because of some problem. The error will describe the reason. Contact your SUN vendor for help.
628771 CCR: Can't read CCR metadata.
Description:Reading the CCR metadata failed on this node during the CCR data server initialization.
Solution:There may be other related messages on this node, which may help diagnose the problem. For example: If the root disk on the afflicted node has failed, then it needs to be replaced. If the cluster repository is corrupted, then boot this node in -x mode to restore the cluster repository from backup or other nodes in the cluster. The cluster repository is located at /etc/cluster/ccr/. Contact your authorized Sun service provider for assistance.
629085 Validation failed. Resource group property RG_AFFINITIES should specify a SCALABLE resource group containing the RAC framework resource.
Description:The resource being created or modified must belong to a resource group that has a strong positive affinity with the scalable resource group containing the RAC framework resource.
Solution:If not already created, create the scalable resource group containing the RAC framework resource and its associated resources. Specify a strong positive (++) affinity with the scalable resource group containing the RAC framework resource by using RG_AFFINITIES property of the resource group.
629355 None of the SUNW.HAStoragePlus resources that this resource depends on are online on the local node. Skipping the checks for the existence and permissions of the start/stop/probe commands.
Description:Some checks are only performed when the SUNW.HAStoragePlus resource is online on the local node.
Solution:This message is informational; no user action is needed.
629584 pthread_mutex_init: %s
Description:The cl_apid was unable to initialize a synchronization object, so it was not able to start up. The error message is specified.
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.
630096 Check_switchover - the check for switchover failed because of replication issues on the MySQL resource %s
Description:The check for the replication status failed
Solution:Fix the replication issues
630317 UNRECOVERABLE ERROR: Sun Cluster boot: /usr/cluster/lib/sc/clexecd not found
Description:/usr/cluster/lib/sc/clexecd is missing.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
630462 Error trying to get logical hostname: <%s>.
Description:There was an error while trying to get the logical hostname. The reason for the error is specified.
Solution:Save a copy of /var/adm/messages from all nodes of the cluster and contact your Sun support representative for assistance.
631303 start_qmgr - WebSphere MQ %s was manually started
Description:The specified WebSphere MQ queue manager has been started manually.
Solution:No user action is required. Informational message.
631373 Fatal error; aborting the rpc.fed daemon.
Description:The rpc.fed server experienced an unrecoverable error, and is aborting the node.
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. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
631408 PCSET: %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.
631506 start_ssh_agent: The passphrase %s is wrong
Description:The ssh passphrase passed to the start_ssh_agent function is wrong
Solution:Fix the ssh passphrase entry in your parameters
631648 Retrying to retrieve the resource group information.
Description:An update to cluster configuration occurred while resource group properties were being retrieved
Solution:Ignore the message.
631859 IO to file-system %s, through mountpoint %s failed.
Description:The file system is in a bad state and requires maintenance.
Solution:Check the condition of the file system and restart the ScalMountPoint resource.
631884 Ifconfig proxy: Could not initialize the ORB. Exiting.
Description:The ifconfig proxy program was unable to initialize its interface to the low-level cluster machinery.
Solution:Make sure the nodes are booted in cluster mode. If so, contact your authorized Sun service provider to determine whether a workaround or patch is available.
632027 Not stopping HADB node %d which is in state %s
Description:The specified HADB node is already in a non running state and does not need to be stopped.
Solution:This is an informational message, no user action is needed.
632337 cl_execd: dup2 of stdin returned with errno %d while executing (%s). Exiting.
Description:cl_execd program has encountered a failed dup2(2) system call. The error message indicates the error number for the failure.
Solution:The cl_execd program will exit and the node will be halted to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
632391 zc_member(%d): Could not get zone name. Exiting.
Description:Failed to get the current zonename. Support for the current zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
632435 Error: attempting to copy larger list to smaller
Description:The cl_apid experienced an internal error.
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.
632524 Command failed: /bin/rm -f %s/pid/%s
Description:An attempt to remove the directory and all the files in the directory failed. This command is being executed as the user that is specified by the extension property DB_User.
Solution:No user action is required.
632524 Failed to add the sci%d adapter
Description:The Sun Cluster Topology Manager (TM) has failed to add the SCI adapter.
Solution:Make sure that the SCI adapter is installed correctly on the system or contact your authorized Sun service provider for assistance.
633010 sv_get_zone_iptype: Could not get zone handle for zone %s,error = %d
Description:During initialization, there was a failure to get information about a specific zone in the system.
Solution:This is an informational message. No user action is required.
633745 pthread_kill: %s
Description:The rpc.fed server encountered an error with the pthread_kill function. The message contains the system error.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
634437 Function: validate - Global zones mountpoint %s does not exist
Description:The directory used as a mountpoint in the global zone is missing.
Solution:Create the mountpoint in the global zone.
634576 SCSLM open <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
634693 Waiting for the PMF to stop
Description:The PMF service is being stopped.
Solution:Please wait. No user action is required. This is an informational message.
634957 thr_keycreate failed in init_signal_handlers
Description:The ucmmd failed in a call to thr_keycreate(3T). ucmmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
Solution:Save a copy of the /var/adm/messages files on all nodes and of the ucmmd core. Contact your authorized Sun service provider for assistance in diagnosing the problem.
635163 scdidadm: ftw(/dev/rmt) failed attempting to discover new paths: %s, ignoring it
Description:Error in accessing /dev/rmt directory when trying to discover new paths under that directory. Because of the error, we may not discover any new tape devices added to this system.
Solution:If the error is "No such file or directory" or "Not a directory" and there are tape devices attached to this host intended for access, create /dev/rmt directory by hand and run scgdevs command. If the error is "Permission denied" and there are tape devices attached to this host intended for access, check and fix the permissions in /dev/rmt and run scgdevs command. If there are no tape devices attached to this host, no action is required. For complete list of errors, refer to the ftw(3C) man page.
635342 QUORUM_GENERIC: quorum_reserve error: Read check found node's key is absent on quorum device %s.
Description:An error was encountered when placing the node's reservation key on the specified quorum device. The write operation of the key succeeded, but the read operation to confirm the presence of the key failed. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
635546 Unable to access the executable %s associated with the FilesystemCheckCommand extension property: %s.
Description:Self explanatory.
Solution:Check and correct the rights of the specified filename by using the chown/chmod commands.
635655 All the sQFS file systems configured to this node through SUNW.qfs resources might not be available. Zone boot operation is not successful.
Description:The zone boot handler failed to make the shared qfs file systems configured for this node available.
Solution:Investigate the zone boot log messages and rectify the problem. If problem persists after rebooting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
635839 first probe was unsuccessful, try again in 5 seconds
Description:the first sanity check was unsuccessful, may be out of sessions
Solution:none required, it is recommended to observe Tomcats number of configured sessions
635928 Role change %s detected.
Description:The role of the Oracle instance does not match the role that is indicated by the combination of the extension properties dataguard_role and standby_mode.
Solution:Update the extension properties dataguard_role and standby_mode to reflect the actual role of the Oracle instance. If the problem persists, contact your Sun support representative for further assistance.
636146 Cannot retrieve user id %s.
Description:The data service is not able to retrieve the user id of the SAP admin user under which SAP is started.
Solution:Ensure that the user was created on all relevant cluster nodes.
636963 WARNING, Dependency between resource %s and its MDS resource %s has not been defined.
Description:The specified ScalMountPoint resource requires an explicit dependency on the metadata server resource that represents the mount point. Validation of the ScalMountPoint resource succeeded, but the dependency must be defined before any attempt to start the ScalMountPoint resource.
Solution:Before you attempt to start the ScalMountPoint resource, define the required dependency between the ScalMountPoint resource and the metadata server resource.
637070 start_winbind - Could not start winbind
Description:The Winbind could not be started.
Solution:No user action is needed. The Winbind server will be restarted.
637220 Function: validate_options - %s Option %s not set
Description:The option is not specified in the start, stop or probe command.
Solution:Make sure that the appropriate config file is correct and reregister the resource.
637372 invalid IP address in hosts list: %s
Description:The allow_hosts or deny_hosts for the CRNP service contained an invalid IP address. This error may cause the validate method to fail or prevent the cl_apid from starting up.
Solution:Remove the offending IP address from the allow_hosts or deny_hosts property.
637466 Function: start_sczbt - Running command %s %s failed. Unable to start zone.
Description:Unable to perform platform specific setup for the solaris8 or solaris9 zone.
Solution:Disable the resource and manually run '/usr/lib/brand/solaris8/s8_p2v <zonename>' for solaris8 or '/usr/lib/brand/solaris9/s9_p2v <zonename>' for solaris9 on the node where the start failed. Correct any errors reported, then restart the resource.
637561 The hostname %s is not authorized to be used in this zone cluster %s.
Description:Given hostname is not authorized to be used for this zone cluster.
Solution:User the clzonecluster(1M) command to configure the hostnames to be used for this zone cluster and then rerun this command to create the resource.
637677 (%s) t_alloc: tli error: %s
Description:Call to t_alloc() failed. The "t_alloc" man page describes possible error codes. udlmctl will exit.
Solution: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.
637886 Error: Unable to start ${SERVER}.
Description:Unable to start Quorum Device monitoring daemon
Solution:Contact your authorized Sun service provider to determine whether a workaround or a patch is available.
637975 Stop of HADB node %d completed successfully.
Description:The resource was able to successfully stop the specified HADB node.
Solution:This is an informational message, no user action is required.
638544 clcomm: Adapter %s has been disabled
Description:A network adapter has been disabled.
Solution:No user action is required.
638833 scha_resourcegroup_open() failed for RG %s: %s
Description:A call to scha_resourcegroup_open() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
638966 Failed to start fault-monitor
Description:An error prevented a resource's fault monitor from starting.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
639176 Resource <%s> Update method suppressed because a resource is restarting in resource group <%s>
Description:Following the update of a resource group or resource property, rgmd is unable to execute an Update method on the indicated resource because the resource group is currently busy on this node executing a resource restart. This should not occur, and might indicate a logic error in rgmd. The rgmd suppresses execution of the Update method on this resource. Depending on what property was updated, this might prevent this resource or its monitor from functioning properly on this node.
Solution:To recover from this error, execute another update of a resource group or resource property. You may re-execute the same update that produced the error. Save a copy of the /var/adm/messages files on all nodes, and contact your Sun service provider to determine whether a workaround or patch is available.
639390 Failed to create a temporary filename.
Description:HAStoragePlus was not able to create a temporary filename in /var/cluster/run.
Solution:Check that permissions are right for directory /var/cluster/run. If the problem persists, contact your authorized Sun service provider.
639855 IPMP group %s has status %s. Assuming this node cannot respond to client requests.
Description:The state of the IPMP group named is degraded.
Solution:Make sure all adapters and cables are working. Look in the /var/adm/messages file for message from the network monitoring daemon (cl_pnmd).
640029 PENDING_ONLINE: bad resource state <%s> (%d) for resource <%s>
Description:The rgmd state machine has discovered a resource in an unexpected state on the local node. 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.
640087 udlmctl: incorrect command line
Description:udlmctl will not startup because of incorrect command line options.
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.
640366 Entry for file system mount point %s is absent from global zone %s.
Description:HAStoragePlus looked for the specified mount point in the specified file (usually /etc/vfstab) but didn't find it.
Solution:Usually, this means that a typo has been made when filling the FilesystemMountPoints property or that the entry for the file system and mount point does not exist in the specified file.
640408 INTERNAL ERROR: Command %s Failed.
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.
640484 clconf: No valid votecount field for quorum device %d
Description:Found the votecount field for the quorum device being incorrect while converting the quorum configuration information into quorum table.
Solution:Check the quorum configuration information.
640521 UNRECOVERABLE ERROR: /usr/cluster/lib/scadmin/ql/data_change file not present.
Description:/usr/cluster/lib/scadmin/ql/data_change file not present.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
640542 %s - the sql command %s failed
Description:The mysql command failed.
Solution:Consult the mysql error logs to determine the root cause
640673 SCSLM <%s> pool_associate error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
640718 cl_execd: Could not resolve '%s' in the name server. Exiting.
Description:The cl_execd program could not resolve the cl_exec server object from the global name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
640799 pmf_alloc_thread: ENOMEM
Description:The rpc.pmfd server was not able to allocate a new monitor thread. As a consequence, the rpc.pmfd server was not able to monitor a process. This problem can occur if the machine has low memory. An error message is output to syslog.
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.
641293 fatal: could not start infrastructure table callback handler thread
Description:Could not start the rgmd thread that will service infrastructure table callbacks from CCR. This might be due to 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.
641686 sigaction: %s
Description:The rpc.pmfd server was not able to set its signal handler. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
641900 UNRECOVERABLE ERROR: Unable to synchronize critical Sun Cluster files after Live Upgrade.
Description:An error was encountered while trying to synchronize critical Sun Cluster files after a Live Upgrade was performed on the system.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
642075 reservation notice(%s) - MHIOCGRP_RESERVE success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action required.
642220 There is already an instance of this daemon running
Description:The server did not start because there is already another identical server running
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
642286 Stop of HADB database did not complete.
Description:The resource was unable to successfully run the hadbm stop command either because it was unable to execute the program, or the hadbm command received a signal.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.
642451 This resource doesn't depend on any SUNW.HAStoragePlus resources. Proceeding with the normal checks.
Description:The data service normally checks for the status of its dependent SUNW.HAStoragePlus resources. The check is not done because there is not dependency on an HAStoragePlus resource in your configuration.
Solution:This message is informational; no user action is needed.
643118 Sun Cluster HA for NFS is not supported in a non-global zone
Description:The SUNW.nfs service can't be hosted in a non-global zone.
Solution:Host the service only in the global zone.
643802 Resource group is online on more than one node.
Description:An internal error has occurred. Resource group should be online on only one node.
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.
644313 Unable to stop HADB nodes on %s
Description:The resource was unable to successfully run the hadbm stopnode command either because it was unable to execute the program, or the hadbm command received a signal.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.
644715 Diskgroup (%s) not multi-owner!
Description:The disk set that is specified is not a multi-owner disk set, or the disk group that is specified is not a shared-disk group.
Solution:Specify a multi-owner disk set or a shared-disk group. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
644850 File %s is not readable: %s.
Description:Unable to open the file in read only mode.
Solution:Make sure the specified file exists and have correct permissions. For the file name and details, check the syslog messages.
644941 Probe failed, HTTP GET Response Code for %s is %d.
Description:The status code of the response to a HTTP GET probe that indicates the HTTP server has failed. It will be restarted or failed over.
Solution:This message is informational; no user action is needed.
645309 Thread already running for node %d.
Description:The cl_eventd does not need to create a thread because it found one that it could use.
Solution:This message is informational only, and does not require user action.
645463 More than one matching zpool for '%s': zpools configured to HAStoragePlus must be unique.
Description:Self explanatory.
Solution:Ensure there is a unique zpool for the specified zpool name by renaming the duplicate zpools.
645501 %s initialization failure
Description:Failed to initialize the hafoip or hascip callback method.
Solution:Retry the operation. If the error persists, contact your Sun service representative.
646037 Probe timed out.
Description:The data service fault monitor probe could not complete all actions in Probe_timeout. This may be due to an overloaded system or other problems. Repeated timeouts will cause a restart or failover of the data service.
Solution:This problem might occur when the cluster is under heavy load. Consider increasing the Probe_timeout property.
646199 Resource %s has failed on node %s. Resource group %sis being switched offline by the RGM on this node; the resource group remains online on other nodes.
Description:The resource group was brought OFFLINE on the node specified, probably because of a public network failure on that node. Although there is no spare node on which to relocate this instance of the resource group, the resource group is currently mastered by at least one other healthy node.
Solution:No user action is required. If desired, examine other syslog messages on the node in question to determine the cause of the network failure.
646392 sigfillset returned %d. Exiting.
Description:The rtreg server program has encountered a failed sigfillset(3C) call. The error message contains the error number for the failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
646622 ucmmd got stale upgrade callback from version manager: upgrade version is %d.%d while current version is %d.%d
Description:Version manager delivered upgrade callback to ucmmd about a new version that is not higher than the current version of ucmmd.
Solution:No user action is required. This message is for informational purposes only.
646664 Online check Error %s: %ld: %s
Description:Error detected when checking ONLINE status of RDBMS. Error number is indicated in message. This can be because of RDBMS server problems or configuration problems.
Solution:Check RDBMS server using vendor-provided tools. If server is running properly, this can be a fault monitor setup error.
646815 PCUNSET: %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.
646865 Monitor probe time of %0.2f seconds is %0.2f percent of Probe timeout.
Description:This message indicates that the probe time of the monitor exceeded the probe timeout threshold(50%) for the resource.
Solution:This message suggests that the Probe_timeout extension property for this resource might be set too low. If the indicated probe execution time is typical for your level of system load, consider increasing the value of Probe_timeout to avoid extraneous restarts or failovers that would be triggered by exceeding the configured probe timeout.
646950 clcomm: Path %s being cleaned up
Description:A communication link is being removed with another node. The interconnect might have failed or the remote node might be down.
Solution:Any interconnect failure should be resolved, and/or the failed node rebooted.
647021 Waiting for mount operation on QFS file systems to complete.
Description:This is a notification from the handler that it is waiting for the completion of the request to RGM to mount shared qfs file systems.
Solution:This is an informational message; no user action is needed.
647187 Function: start_sczsh - %s does not exist or is not executable in zone %s - early End
Description:The command specified for variable ServiceStartCommand 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 ServiceStartCommand 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 reregister the resource, make sure the variable ServiceStartCommand is properly set within the ${PARAMETERDIR}/sczsh_${RS} parameter file.
648057 Successful auto recovery of HADB database.
Description:The database was successfully reinitialized.
Solution:This is an informational message, no user action is needed.
648187 sckrb5 successfully stopped.
Description:The HA-KDC's stop method had completed with out error.
Solution:This is for informational purposes only, no action is required.
649584 Modification of resource group <%s> failed because none of the nodes on which VALIDATE would have run for resource <%s> are currently up
Description:Before it will permit the properties of a resource group to be edited, the rgmd runs the VALIDATE method on each resource in the group for which a VALIDATE method is registered. For each such resource, the rgmd must be able to run VALIDATE on at least one node. However, all of the candidate nodes are down. "Candidate nodes" are either members of the resource group's Nodelist or members of the resource type's Installed_nodes list, depending on the setting of the resource's Init_nodes property.
Solution:Boot one of the resource group's potential masters and retry the resource creation operation.
649648 svc_probe used entire timeout of %d seconds during read operation and exceeded the timeout by %d seconds. Attempting disconnect with timeout %d
Description:The probe timed out while reading from the application.
Solution:If the problem persists investigate why the application is responding slowly or if the Probe_timeout property needs to be increased.
649799 SCSLM strdup error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
650231 The quorum configuration task succeeded on node ${nodename}
Description:Quorum disk was configured and the cluster was initialized on the last of the 2 nodes to join the cluster.
Solution:No user action is required.
650825 Method <%s> on resource <%s> terminated due to receipt of signal <%d>
Description:A resource method was terminated by a signal, most likely resulting from an operator-issued kill(1). The method is considered to have failed.
Solution:No user action is required. The operator can choose to issue a clresourcegroup command to bring resource groups onto desired primaries, or retry the administrative action that was interrupted by the method failure.
651091 INTERNAL ERROR: Invalid upgrade-from tunablity flag <%d>; aborting node
Description:A fatal internal error has occurred in the RGM.
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.
651093 reservation message(%s) - Fencing node %d from disk %s
Description:The device fencing program is taking access to the specified device away from a non-cluster node.
Solution:This is an informational message, no user action is needed.
651327 Failed to delete 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.
651450 All WebSphere MQ (%s) processes stopped
Description:All the WebSphere MQ processes for the specified Queue Manager have been stopped.
Solution:No user action is required. Informational message.
651848 Failed to halt the nodes of the partition
Description:The upgrade process halts the nodes of the second partition. It then waits till all the nodes of the partition have halted. The upgrade process was unable to ping all nodes of the partition.
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.
651865 Failed to stop liveCache gracefully with command %s. Will stop it immediately with db_stop.
Description:Failed to stop liveCache with 'lcinit stop'. Will shutdown immediately with 'dbmcli db_stop'.
Solution:Informative message. No user action is needed.
652019 Executing in zones context with id %d that does not match id %d in the door header
Description:Zone information that has been passed does not match the client credentials.
Solution:Someone has tampered with the Sun cluster code. This is a security violation. Shut down the identified zone.
652399 Ignoring the SCHA_ERR_SEQID while retrieving %s
Description:An update to the cluster configuration tables occurred while trying to retrieve certain cluster related information. However, the update does not affect the property that is being retrieved.
Solution:Ignore the message
652517 Unable to open device %s. %s
Description:The device could not be opened.
Solution:Run the command metaset to determine if the metaset is online on the node. Run metastat to determine the state of the volume.
652662 libsecurity: program %s (%lu) rpc_createerror: %s
Description:A client of the specified server was not able to initiate an rpc connection. The error message generated with a call to clnt_spcreateerror(3NSL) is appended.
Solution:Save the /var/adm/messages file. Check the messages file for earlier errors related to the rpc.pmfd, rpc.fed, or rgmd server.
652764 libsecurity, door_call: %s; will retry
Description:A door_call failed with the specified reason.
Solution:No user action is required.
653062 Syntax error on line %s in dfstab file.
Description:The specified share command is incorrect.
Solution:Correct the share command using the dfstab(4) man pages.
653151 The specified zone cluster name '%s' does not exist.
Description:The specified zone cluster name does not exist.
Solution:Check the zone cluster support on the current running version of cluster and then check the existence of the specified zone cluster. If zone cluster name exists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
653316 Unable to execute %s : %s (%d), HA-SAP will continue to start SAP.
Description:The system(3C) call returned an error, vfork or exec failed for example.
Solution:This may be due to lack of system resources. Check whether the system is low on memory, also check /var/adm/messages.
653776 Shutdown - can't execute %s/checkprog binaries
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.
654006 Error occurred during instance shutdown (%s).
Description:An error occurred during an attempt by the agent to shutdown an Oracle instance.
Solution:Check the /var/adm/messages file for details of the error. If this does not provide sufficient information, refer to the alert log file of the Oracle instance for details on the error. Contact your Sun support representative for further assistance.
654276 realloc failed with error code: %d
Description:The call to realloc(3C) in the cl_apid failed with the specified error code.
Solution:Increase swap space, install more memory, or reduce peak memory consumption.
654520 INTERNAL ERROR: rgm_run_state: bad state <%d> for resource group <%s>
Description:The rgmd state machine on this node has discovered that the indicated resource group's state information is corrupted. The state machine will not launch any methods on resources in this resource group. This may indicate an internal logic error in the rgmd.
Solution:Other syslog messages occurring before or after this one might provide further evidence of the source of the problem. If not, save a copy of the /var/adm/messages files on all nodes, and (if the rgmd crashes) a copy of the rgmd core file, and contact your authorized Sun service provider for assistance.
654567 Failed to retrieve SAP binary path.
Description:Cannot retrieve the path to SAP binaries.
Solution:This is an internal error. There may be prior messages in syslog indicating specific problems. Make sure that the system has enough memory and swap space available. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
654659 SCSLM <%s> zone <%s> weak while strong running
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
654749 Ifconfig proxy daemonize() : fork1 failed, errno = %d. Exiting.
Description:The ifconfig proxy program has encountered failure of fork1(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.
655203 Invalid upgrade callback from version manager: unrecognized ucc_name %s
Description:Version manager delivered upgrade callback to rgmd passing an upgrade callback object name that was not registered by rgmd.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
655410 getsockopt: %s
Description:The cl_apid received the following error while trying to deliver an event to a CRNP client. This error probably represents a CRNP client error or temporary network congestion.
Solution:No user action is required, unless the problem persists (ie. there are many messages of this form). In that case, 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.
655416 setsockopt: %s
Description:The cl_apid experienced an error while configuring a socket. This error may prohibit event delivery to CRNP clients.
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.
655523 Write to server failed: server %s port %d: %s.
Description:The agent could not send data to the server at the specified server and port.
Solution:This is an informational message, no user action is needed. If the problem persists the fault monitor will restart or failover the resource group the server is part of.
655966 Error: pmfadm could not stop fault monitor, tag "%s" error="%s"
Description:The CRS framework monitor failed to stop or is not running.
Solution:Check for other errors on the system and correct them before restarting the CRS framework resource. If you cannot resolve this problem, contact your Sun service representative for assistance.
655969 Stop command %s failed with error %s.
Description:The execution of the command for stopping the data service failed.
Solution:No user action needed.
656416 libsecurity, door_call: Fatal, the server is not available.
Description:The client (libpmf/libfe/libscha) is trying to communicate with the server (rpc.pmfd/rpc.fed/rgmd) but is failing because the server might be down.
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.
656764 fatal: rgmx_update_configured_nodes() : failed
Description:The RGM couldn't update membership information for farm nodes and will abort to avoid undesired results.
Solution:Contact your authorized SUN representatives for resolution of the problem.
656795 CMM: Unable to bind <%s> to nameserver.
Description:An instance of the userland CMM encountered an internal initialization error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
656898 Start command %s returned error, %d.Aborting startup of resource.
Description:The data service failed to run the start command.
Solution:Ensure that the start command is in the expected path (/usr/sap/<SID>/SYS/exe/run) and is executable.
657495 Tag %s: error number %d in throttle wait; process will not be requeued.
Description:An internal error has occurred in the rpc.pmfd server while waiting before restarting the specified tag. rpc.pmfd will delete this tag from its tag list and discontinue retry attempts.
Solution:If desired, restart the tag under pmf using the 'pmfadm -c' command.
657750 File-system type "%s" is not allowed.
Description:The value of the property FileSystemType is not "nas" or "s-qfs".
Solution:Specify the correct value for the property and repeat the operation.
657759 Error: An instance of ${SERVER} is already running.
Description:Quorum Device monitoring daemon is already running.
Solution:No user action is required.
657885 sigwait: %s
Description:The daemon was unable to configure its signal handling functionality, so it is unable to run.
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.
658049 dl_bind: DL_ERROR_ACK protocol error
Description:Could not bind to the physical device. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
658325 check_winbind - User <%s> can't be retrieved by the nameservice
Description:The Winbind userid cannot be retrieved.
Solution:No user action is needed. The Samba server will be restarted.
658329 CMM: Waiting for initial handshake to complete.
Description:The userland CMM has not been able to complete its initial handshake protocol with its counterparts on the other cluster nodes, and will only be able to join the cluster after this is completed.
Solution:This is an informational message, no user action is needed.
658555 Retrying to retrieve the resource information.
Description:An update to cluster configuration occurred while resource properties were being retrieved
Solution:Ignore the message.
659369 ct_status_read: %s
Description:The libclcontract code was unable to retrieve the status of the newly created process template. The libclcontract code will kill the newly forked process because the process using the libclcontract code is unable to monitor the forked process.
Solution:If the message is isolated, it was probably a transient error. Retry the requested action. 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.
659665 kill -KILL: %s
Description:The rpc.fed server is not able to stop a tag that timed out, and the error message is shown. An error message is output to syslog.
Solution:Save the /var/adm/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.
659683 check_dhcp - Active interface has changed from %s to %s
Description:The DHCP resource's fault monitor has detected that the active interface has changed.
Solution:No user action is needed. The fault monitor will restart the DHCP server.
659827 CCR: Can't access CCR metadata on node %s errno = %d.
Description:The indicated error occurred when CCR is trying to access the CCR metadata on the indicated node. 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. These 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 cluster repository is corrupted, boot the indicated node in -x mode to restore it from backup. The cluster repository is located at /etc/cluster/ccr/.
660332 launch_validate: fe_set_env_vars() failed for resource <%s>, resource group <%s>, method <%s>
Description:The rgmd daemon was unable to set up environment variables for method execution, causing a VALIDATE method invocation to fail. This in turn will cause the failure of a creation or update operation on a resource or resource group.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Retry the creation or update operation. If the problem recurs, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
660368 CCR: CCR service not available, service is %s.
Description:The CCR service is not available due to the indicated failure.
Solution:Reboot the cluster. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.
660752 Validation failed in the start method.
Description:The resource did not pass the validation checks.
Solution:Determine whether the properties of the resource are valid. Verify the status of the disk set or disk group. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
660974 file specified in USER_ENV %s does not exist
Description:'User_env' property was set when configuring the resource. File specified in 'User_env' property does not exist or is not readable. File should be specified with fully qualified path.
Solution:Specify existing file with fully qualified file name when creating resource. If resource is already created, please update resource property 'User_env'.
661075 Validate - Group mqm does not exist
Description:The group mqm does not exist.
Solution:The group mqm must exist within /etc/group.
661077 dl_info: DL_INFO_ACK protocol error
Description:Could not get a DLPI info_ack message from 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.
661084 liveCache was stopped by the user outside of Sun Cluster. Sun Cluster will suspend monitoring until liveCache is again started up successfully outside of Sun Cluster.
Description:When Sun Cluster tries to bring up liveCache, it detects that liveCache was brought down by user intendedly outside of Sun Cluster. Sun Cluster will not try to restart it under the control of Sun Cluster until liveCache is started up successfully again by the user. This behavior is enforced across nodes in the cluster.
Solution:Informative message. No user action is required.
661087 Validate - %s does not contain %s
Description:${INFORMIXSQLHOSTS} does not contain ${INFORMIXSERVER}.
Solution:Ensure that ${INFORMIXSQLHOSTS} is contains ${INFORMIXSERVER}.
661560 All the SUNW.HAStoragePlus resources that this resource depends on are online on the local node. Proceeding with the checks for the existence and permissions of the start/stop/probe commands.
Description:The SUNW.HAStoragePlus resource that this application resource depends on is online on the local node and therefore the validation checks related to start/stop/probe commands will be carried out on the local node.
Solution:This message is informational; no user action is required.
661778 clcomm: memory low: freemem 0x%x
Description:The system is reporting that the system has a very low level of free memory.
Solution:If the system fails soon after this message, then there is a significantly greater chance that the system ran out of memory. In which case either install more memory or reduce system load. When the system continues to function, this means that the system recovered and no user action is required.
661977 Validate - Infrastructure user <%s> does not exist
Description:The value of the Oracle Application Server Infrastructure user id within the xxx_config file is wrong, where xxx_config is either 9ias_config for Oracle 9iAS or 10gas_config for Oracle 10gAS.
Solution:Specify the correct OIAS_USER in the appropriate xxx_config file and reregister xxx_register, where xxx_register is 9ias_register for Oracle 9iAS or 10gas_register for Oracle 10gAS.
662507 Could not run %s. User program did not execute cleanly.
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.
662516 SIOCGLIFNUM: %s
Description:The ioctl command with this option failed in the cl_apid. 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.
662622 Failed to take sckrb5 out of PMF control; trying to send SIGKILL now.
Description:HA-KDC's stop method was not able to stop krb5kdc or kadmind through PMF.
Solution:This is for informational purposes, no action is required. The stop method will subsequently try to forcefully kill these processes through SIGKILL.
662761 <%s>:<%s>:Process core dump at <%s> for method <%s> may fail.
Description:The rpc.fed couldn't ensure a writable directory in which to dump process cores. The exact message indicates the nature of the error.
Solution:Low memory might be a transient error. If it persists, rebooting might help. If that fails to help, swap space might need to be increased. If it is a different error, it might be due to insufficient privileges for ensuring a writable directory to store the core. Check and correct the permissions for path indicated in the message.
663056 asadmin list-domains command lists the status of %s domain as not running
Description:The probe method checked the status of DAS by running the asadmin list-domains command. The command lists the status of the DAS as "not running". This is considered complete failure and the probe will take action.
Solution:No user action is required.
663089 clexecd: %s: sigwait returned %d. Exiting.
Description:clexecd program has encountered a failed sigwait(3C) system call. The error message indicates the error number for the failure.
Solution:The clexecd program will exit and the 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.
663293 reservation error(%s) - do_status() error for disk %s
Description:The device fencing program has encountered errors while trying to access a device. All retry attempts have failed.
Solution:The action which failed is a scsi-2 ioctl. These can fail if there are scsi-3 keys on the disk. To remove invalid scsi-3 keys from a device, use 'scdidadm -R' to repair the disk (see scdidadm man page for details). If there were no scsi-3 keys present on the device, then this error is 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, 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, you can retry the desired action.
663458 Failed to add qfs name '%s' to qfs list for resource '%s'.
Description:The zone boot handler failed to generate the list of shared qfs file systems for a resource.
Solution:Investigate using zone boot log messages and try to rectify the problem. If problem persists after rebooting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
663692 failback attempt failed on resource group <%s> with error <%s>
Description:The rgmd daemon was unable to failback the specified resource group to a more preferred node. The additional error information in the message explains why.
Solution:Examine other syslog messages occurring around the same time on the same node. These messages may indicate further action.
663851 Failover %s data services must have exactly one value for extension property %s.
Description:Failover data services must have one and only one value for Confdir_list.
Solution:Create a failover resource group for each configuration file.
663897 clcomm: Endpoint %p: %d is not an endpoint state
Description:The system maintains information about the state of an Endpoint. The Endpoint state is invalid.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
663943 CMM: Unable to reset node information on quorum disk.
Description:This node was unable to reset some information on the quorum device. This will lead the node to believe that its partition has been preempted. This is an internal error. 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:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
664065 DID reconfiguration discovered an invalid disk path. You must remove this path before you can add a new path. Run 'cldevice clear' then rerun 'cldevice refresh'.
Description:Invalid disk path found during DID reconfiguration.
Solution:Remove the invalid disk path and run 'cldevice clear' and rerun 'cldevice refresh'.
664089 All global device services successfully switched over to this node.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
664371 %s: Not in cluster mode. Exiting...
Description:Must be in cluster mode to execute this command.
Solution:Reboot into cluster mode and retry the command.
664658 Waiting for the RGM to stop
Description:The RGM service is being stopped.
Solution:Please wait. No user action is required. This is an informational message.
664741 Failed to execute zoneadm reboot for zone %s
Description:The rgmd failed in an attempt to execute a zoneadm reboot call, due to a failure to communicate with the rpc.fed daemon. The zone will stay up, but the rgmd will not attempt to start services on the zone.
Solution:Reboot the zone. 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 the problem.
665015 Scalable service instance [%s,%s,%d] registered on node %s.
Description:The specified scalable service has been registered on the specified node. Now, the gif node can redirect packets for the specified service to this node.
Solution:This is an informational message, no user action is needed.
665090 libsecurity: program %s (%lu); getnetconfigent error: %s
Description:A client of the specified server was not able to initiate an rpc connection, because it could not get the network information. The pmfadm or scha command exits with error. The rpc 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.
665368 Failed to wake up probing thread (ID %d) : %s
Description:The thread that is used for the I/O probe could not be sent the wake-up signal.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
665564 Failed to commit the %s to the CCR table %s.
Description:An unknown error has occurred while updating the CCR with the current zone cluster name.
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.
665931 Initialization error. CONNECT_STRING is NULL
Description:Error occurred in monitor initialization. Monitor is unable to get resource property 'Connect_string'.
Solution:Check syslog messages for errors logged from other system modules. Check the resource configuration and value of 'Connect_string' property. Check syslog messages for errors logged from other system modules. Stop and start fault monitor. If error persists then disable fault monitor and report the problem.
666205 INTERNAL ERROR usage: $0 <validate/stop> <weblogic_home> <server_url> <server_start_script>
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.
666368 SCSLM unknown method 0x%x
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
666391 clcomm: invalid invocation result status %d
Description:An invocation completed with an invalid result status.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
666443 Unix DLM already running
Description:UNIX DLM is already running. Another dlm will not be started.
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.
666603 clexecd: Error %d in fcntl(F_GETFD). Exiting.
Description:The 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.
666617 Invalid global device path %s detected for SAMFS mount point %s.
Description:The specified global device path used by the SAM-FS file system is not valid.
Solution:Check the SAM-FS file system configuration.
666907 Logical kadmin principal does not exist in %s.
Description:The logical host name associated with the "kadmin" service principal does not exist in the /etc/krb5/kadm5.keytab file.
Solution:Create and/or add the "kadmin/<logical host name>" service principal's keys in the /etc/krb5/kadm5.keytab file. Note: that the logical host name must be fully qualified.
667067 sv_get_zone_iptype: Could not init zone handle
Description:During initialization, there was a failure to get information about configured zones in the system.
Solution:There might be other related error messages which might be helpful. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
667314 CMM: Enabling failfast on quorum device %s failed.
Description:An attempt to enable failfast on the specified quorum device failed.
Solution:Check if the specified quorum disk has failed. This message may also be logged when a node is booting up and has been preempted from the cluster, in which case no user action is necessary.
667451 clq_scsi3: Ioctl MHIOCGRP_RESERVE returned error(%d) also the reservation key was not found on quorum device %s
Description:An error was encountered while trying to place node's reservation key on specified quorum device. Cluster software read the reservation key and found another node's key present. This error occurs because of unexpected behavior from device driver or multipathing driver or device's firmware.
Solution:Please look for updates in device driver, multipathing driver or device firmware. If no updates are available please contact Sun device driver support team.
667613 start_mysql - myisamchk found errors in some index in %s, perform manual repairs
Description:The mysiamchk found errors in MyISAM based tables.
Solution:Consult MySQL documentation when repairing MyISAM tables.
667957 %s: pipe returned %d. Exiting.
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
668074 Successfully failed-over resource group.
Description:This message indicates that the rgm successfully failed over a resource group, as expected.
Solution:This is an informational message.
668209 Function: lofsmount - Non-global zones mount from %s to %s with options %s failed
Description:The mount of the directory into the root path of the non-global zone failed.
Solution:Watch the verbose error message in the zones start messages and fix the issue with appropriate methods.
668763 Failed to retrieve information on %s: %s.
Description:HAStoragePlus was not able to retrieve the specified information from the cluster configuration.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
668866 Successful shutdown; terminating daemon
Description:The cl_apid daemon is shutting down normally due to a SIGTERM.
Solution:No user action is required.
668883 Entry in the global zone %s for file system mount point %s is incorrect: %s.
Description:The format of the entry for the specified mount point in the specified file is invalid.
Solution:Edit the file (usually /etc/vfstab) and check that entries conform to its format.
668986 Failed to stop sckrb5 with SIGTERM; retry with SIGKILL.
Description:HA-KDC's stop method was not able to stop krb5kdc or kadmind by using the SIGTERM signal.
Solution:This is for informational purposes, no action is required. The stop method will subsequently try to forcefully kill these processes through SIGKILL.
669026 fcntl(F_SETFD) failed in close_on_exec
Description:A fcntl operation failed. The "fcntl" man page describes possible error codes.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
669632 Cleanup after upgrade has failed on the nodes that have the joined the cluster
Description:Cluster upgrade has completed on all the nodes that have joined the cluster. However cleanup of the upgrade state has failed.
Solution:Retry cleanup of the upgrade state by running /usr/cluster/lib/scadmin/ql/ql_cleanup on any node of the cluster.
669680 fatal: rpc_control() failed to set the maximum number of threads
Description:The rgmd failed in a call to rpc_control(3N). This error should never occur. If it did, it prevent to dynamically adjust the maximum number of threads that the RPC library can create, and as a result could prevent a maximum number of some scha_call to be handled at the same time.
Solution:Examine other syslog messages occurring at about the same time to see if the source of 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 the problem. Reboot the node to restart the clustering daemons.
669693 The Oracle instance was found to be disabled. Instance startup will not be attempted.
Description:The Oracle RAC instance has been disabled.
Solution:If the instance needs to be brought online, run the Sun Cluster enable command on the resource. This will internally enable the RAC instance and bring it online.
669742 Successfully obtained the list of SUNW.qfs resources that are configured for this zone cluster.
Description:This is a notification message about successful retrieval of configured SUNW.qfs resources for this zone cluster.
Solution:This is an informational message; no user action is needed.
670107 Error in getting the contract id from repository for svc:%s
Description:Cannot read the contract id from SMF repository
Solution:The previous messages should give more details for the reason. Make sure the basic SMF functionalities are working. Contact your SUN vendor for more help.
670283 Issuing a resource restart request because the application exited.
Description:This message indicates that the fault monitor is about to request a resource restart because the application exited. If the request fails, refer to the syslog messages that appear after this message.
Solution:This is an informational message.
670303 The zpool '%s' is not available from this node.
Description:The device that you added to the zpool is not accessible from this node.
Solution:Check the zpools that can be accessed from this node by doing "zpool list" and "zpool import". If the zpool that is listed in the error message is among them, contact your authorized Sun service provider. Otherwise, remove the zpool from the resource group or remove the specified node from the resource group.
670753 reservation fatal error(%s) - unable to determine node id for node %s
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.
670799 CMM: Registering reservation key on quorum device %s failed with error %d.
Description:An error was encountered while trying to place the local node's reservation key on the specified quorum device. This node will ignore this quorum device.
Solution:There may be other related messages on this and other nodes connected to this quorum device that may indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.
670814 Blocking in RGM
Description:The RGM is blocked until all cluster file systems are available.
Solution:This is an informational message, no user action is needed.
671376 cl_apid internal error: unable to update client registrations.
Description:The cl_apid experienced in internal error that prevented it from modifying the client registrations as requested.
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.
671508 validate: The command wget is not fund under %s
Description:The specified wget command is not found.
Solution:Fix the wget pathname in the parameter file.
671553 Unsupported task ${task} in ${POSTCONFIGFILE}
Description:A task was found on the post-configuration CCR file that was not understood. This probably indicated that the CCR file was corrupt.
Solution:Manually configure quorum disks and initialize the cluster by using clsetup and scsetup after all nodes have joined the cluster.
671602 pid %u <%s> project <%s> user <%s> setproject() success after %d retry
Description:A warning message.
Solution:No user action is required.
671793 Could not stop telemetry data service monitor (resource: %s)
Description:The monitor program of the telemetry data service could not stop. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
671954 waitpid: %s
Description:The rpc.pmfd or rpc.fed server was not able to wait for a process. 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.
672264 Ifconfig proxy server Killed(sigterm) Exiting.
Description:The ifconfig program got a SIGTERM signal and is exiting.
Solution:This is an informational message. No user action is required.
672511 Failed to start Text server.
Description:Sun Cluster HA for Sybase failed to start the text server. 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, text server log files and setup.
672525 Resource <%s> of Resource Group <%s> failed monitor check on node <%s>
Description:Message logged for failed scha_control monitor check methods on specific node.
Solution:No user action required.
673880 clq_netapp: quorum open error: No matching device found in CCR --- quorum device %s will be unavailable.
Description:The CCR does not contain the necessary configuration information for the NetApp NAS device. The device will not be available.
Solution:Remove the device using scconf, and try adding it again.
673922 WARNING: %s affinity property for %s resource group is not set.
Description:The specified affinity has not been set for the specified resource group.
Solution:Informational message, no action is needed if the SAP enqueue server is running without the SAP replica server. However, if the SAP replica server will also be running on the cluster, the specified affinity must be set on the specified resource group.
673965 INTERNAL ERROR: starting_iter_deps_list: invalid dependency type <%d>
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
674163 Failfast: timeout - unit "%s"%s.
Description:A failfast client has encountered a timeout and is going to panic the node.
Solution:There may be other related messages on this node which may help diagnose the problem. Resolve the problem and reboot the node if node panic is unexpected.
674214 rebalance: no primary node is currently found for resource group <%s>.
Description:The rgmd is currently unable to bring the resource group online because all of its potential masters are down or are ruled out because of strong resource group affinities.
Solution:As a cluster reconfiguration is completed, additional nodes become eligible and the resource group may go online without the need for any user action. If the resource group remains offline, repair and reboot broken nodes so they can rejoin the cluster; or use clresourcegroup to edit the Nodelist or RG_affinities property of the resource group, so that the Nodelist contains nodes that are cluster members and on which the resource group's strong affinities can be satisfied.
674359 load balancer deleted
Description:This message indicates that the service group has been deleted.
Solution:This is an informational message, no user action is needed.
674415 svc_restore_priority: %s
Description:The rpc.pmfd or rpc.fed server was not able to run the application in the correct scheduling mode, 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.
674848 fatal: Failed to read CCR
Description:The rgmd is unable to read the cluster configuration repository. 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: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.
675065 ERROR: sort_candidate_nodes: <%s> is pending_methods on node <%d>
Description:An internal error has occurred in the locking logic of the rgmd. This error should not occur. It may prevent the rgmd from bringing the indicated 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.
675221 clcomm:Cannot fork1() after ORB server initialization.
Description:A user level process attempted to fork1 after ORB server initialization. This is not allowed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
675353 Stop Proxy monitor using pmfadm failed. tag %s error=%s
Description:The agent's attempt to stop the Monitor whose internal id is %s of a resource of type SUNW.scalable_rac_server_proxy failed with error %s.
Solution:Contact your Sun support representative for further assistance.
675432 pmf_monitor_suspend: poll: %s
Description:The rpc.pmfd server was not able to monitor a process. and the system error is shown. This error occurred for a process whose monitoring had been suspended. The monitoring of this process has been aborted and can not be resumed.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
675480 Could not create zone cluster %s due to CCR exception %s
Description:libzccfg was not able to create the specified zone cluster due to an internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
675548 Error reading line from %s command: %s.
Description:An error was encountered while reading the output from the specified disp+work/jlaunch command.
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.
675748 clq_scsi3: Ioctl to register node's key returned success but read check found that key is not present on quorum device %s.
Description:Ioctl to register node's key on specified quorum device returned success but read check found that key is not present. This error occurs because of unexpected behavior from device driver or multipathing driver or device's firmware.
Solution:Please look for updates in device driver, multipathing driver or device firmware. If no updates are available please contact Sun device driver support team.
675776 Stopped the fault monitor.
Description:The fault monitor for this data service was stopped successfully.
Solution:No user action is required.
676558 WARNING: Global_resources_used property of resource group <%s> is set to non-null string, assuming wildcard
Description:The Global_resources_used property of the resource group was set to a specific non-null string. The only supported settings of this property in the current release are null ("") or wildcard ("*").
Solution:No user action is required; the rgmd will interpret this value as wildcard. This means that method timeouts for this resource group will be suspended while any device group temporarily goes offline during a switchover or failover. This is usually the desired setting, except when a resource group has no dependency on any global device service or pxfs file system.
676787 SCSLM munmap <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
677273 cl_execd: Unable to create thread. Exiting.
Description:The cl_execd program encountered a failure while executing thr_create(3C).
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
677278 No network address resource in resource group.
Description:A resource has no associated network address.
Solution:For a failover data service, add a network address resource to the resource group. For a scalable data service, add a network resource to the resource group referenced by the RG_dependencies property.
677428 %s can't UP %s.
Description:This means that the Logical IP address could not be set to UP.
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.
677759 Unknown status code %d.
Description:Checking for HAStoragePlus resources returned an unknown status code.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
677788 Cannot determine the node name
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
678041 lkcm_sync: cm_reconfigure failed: %s
Description:The ucmm reconfiguration failed.
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.
678073 IPMP group %s is incapable of hosting %s addresses
Description:The cluster is undergoing a reconfiguration.
Solution:No user action is required. This is an informational message only.
678290 The output of the command \'%s\' was not as expected.
Description:The output of 'metastat' was not as expected.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
678493 Failure running cleanipc; %d.
Description:The data service could not execute cleanipc command.
Solution:Ensure cleanipc is in the expected path (/usr/sap/<SID>/SYS/exe/run) and is executable.
678648 reservation notice(%s) - MHIOCTKOWN success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action required.
678985 cl_execd: dup2 of stdout returned with errno %d while exec'ing (%s). Exiting.
Description:cl_execd program has encountered a failed dup2(2) system call. The error message indicates the error number for the failure.
Solution:The cl_execd program will exit and the node will be halted to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
679060 Internal error, trying to add a string to an invalid string array.
Description:An internal programming error has been detected.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
679115 getprinc of %s failed.
Description:An attempt was made to add a test principal to the Kerberos database, but this failed during a complete probe for the HA-KDC service.
Solution:Check the state of the /var/krb5/principal database.
679264 Starting auto recovery of HADB database.
Description:All the Sun Cluster nodes able to run the HADB resource are running the resource, but the database is unable to be started. The database will be reinitialized by running hadbm clear and then the command, if any, specified by the auto_recovery_command extension property.
Solution:This is an informational message, no user action is needed.
679874 Unable to execvp %s: %s
Description:The libclcontract code was not able to exec the specified process, possibly due to bad arguments. The message contains the system error. The server process (which is using libclcontract) does not perform the action requested by the client, and an error message is output to syslog.
Solution:Verify that the file path to be executed exists. 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.
679912 uaddr2taddr: %s
Description:Call to uaddr2taddr() failed. The "uaddr2taddr" man page describes possible error codes. udlm will exit 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.
680088 The entry in mnttab for mount point '%s' has too few fields.
Description:The entry in mnttab for the specified mount point has fewer fields than are defined for a single mnttab entry.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
680960 Unable to write data: %s.
Description:Failed to write the data to 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 application.
681520 dl_attach: DL_OK_ACK protocol error
Description:Could not attach to the private interconnect interface.
Solution:Reboot of the node might fix the problem.
681535 check_pgs: The ssh-agent process %s is not running
Description:The ssh-agent process associated with the PostgreSQL database is not running.
Solution:No user action is required.
681723 Failed to create nonexistent mount point %s: %s.
Description:HAStoragePlus detected that the mount point was missing and failed to create the mount point.
Solution:Check the error message. Rectify the problem and retry the operation. If the problem persists, contact your authorized Sun service provider.
683231 Could not start server.
Description:The Oracle instance could not be started by the agent.
Solution:Check the /var/adm/messages file for details of the error. If this does not provide sufficient information, refer to the alert log file of the Oracle instance for details on the error. Contact your Sun support representative for further assistance.
683997 Failed to retrieve the resource group property %s: %s
Description:Unable to retrieve the resource group property.
Solution:For the property name and the reason for failure, check the syslog message. For more details about the api failure, check the syslog messages from the RGM .
684056 Failed to build path to status message file.
Description:An error occurred when the path to the status message file was being built.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
684306 check_nmbd - Nmbd for <%s> is not working, failed to retrieve ipnumber for %s
Description:The nmblookup could not be performed.
Solution:No user action is needed. The Samba server will be restarted.
684383 Development system shut down successfully.
Description:Informational message.
Solution:No user action is required.
684753 store_binding: <%s> bad bind type <%d>
Description:During a name server binding store an unknown binding type was encountered.
Solution:No user action is required. This is informational message.
684810 svc_restore_priority: Could not set required scheduling parameters: %s. Diagnostic information (%s).
Description:The server was not able to restore the original scheduling mode. The system error message 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.
685155 default port:<%d> will be used to probe ma
Description:While parsing the mgt.cfg configuration file ,the ma server port field was not found or an error occurred in parsing the port field within the file.
Solution:This is an informational message, no user action is needed. The ma server will start up with default port.
685270 Failed to retrieve the resource handle for (%s in cluster %s): %s.
Description:Unable to get a handle to this resource's configuration data.
Solution:Internal error. Contact user support for assistance.
685816 scds_get_rs_resource_dependencies() failed.
Description:A call to scds_get_rs_resource_dependencies() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
685886 Failed to communicate: %s.
Description:While determining the health of the data service, fault monitor is failed to communicate with the process monitor facility.
Solution:This is internal error. Save /var/adm/messages file and contact your authorized Sun service provider. For more details about error, check the syslog messages.
686182 Unknown status code %s.
Description:The hasp_check returned an unknown status code.
Solution:This is an internal error. No user action needed. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
686419 %s: Unblock parent, write errno %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
687198 Validate_sbp - MySQL resource group is not specified in option %s
Description:The required real mysql resource group is not specified.
Solution:Make sure that the required resource group is specified.
687457 Attempting to kill pid %d name %s resulted in error: %s.
Description:HA-NFS callback method attempted to stop the specified NFS process with SIGKILL but was unable to do so because of the specified error.
Solution:The failure of the method would be handled by Sun Cluster. If the failure happened during starting of a HA-NFS resource, the resource would be failed over to some other node. If this happened during stopping, the node would be rebooted and HA-NFS service would continue on some other node. If this error persists, please contact your local SUN service provider for assistance.
687496 fatal: cannot send mappings to remote nodes
Description:This node encountered an unexpected error while communicating with other cluster nodes during a cluster reconfiguration. The rgmd 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 rgmd core file. Contact your authorized Sun service provider for assistance in diagnosing the problem.
687543 shutdown abort did not succeed.
Description:HA-Oracle failed to shutdown Oracle server using 'shutdown abort'.
Solution:Examine log files and syslog messages to determine the cause of failure.
687580 Unable to get zonename for zone id %d, errno = %d. Exiting.
Description:The pnm proxy program encountered a failure when trying to get the zone name.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
687929 daemon %s did not respond to null rpc call: %s.
Description:HA-NFS fault monitor failed to ping an nfs daemon.
Solution:No user action is required. The fault monitor will restart the daemon if necessary.
688163 clexecd: pipe returned %d. Exiting.
Description:clexecd program has encountered a failed pipe(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.
688262 Failover of the derby data service failed.
Description:The failover attempt of the derby data service was rejected or encountered an error.
Solution:For more detailed error message, check the syslog messages. Check whether the Pingpong_interval has appropriate value. If not, adjust it by using clresourcegroup show. Otherwise, use clresourcegroup switch to switch the resource group to a healthy node.
688990 Giveover attempt failed for %s: resource group is unable to bring online on a potential primary node. retries exhausted.
Description:An error occurred while attempting to switch over the QFS meta data resource group. This error persisted until all retries were exhausted.
Solution:Verify that the cluster is correctly configured. If it is, contact your authorized Sun service provider to determine whether a workaround or patch is available.
689538 Listener %s did not stop.(%s)
Description:Failed to stop Oracle listener using 'lsnrctl' command. HA-Oracle will attempt to kill listener process.
Solution:No user action is required.
689677 can't start cl_pnmd due to lock.
Description:An attempt was made to start multiple instances of the PNM daemon cl_pnmd(1M), or cl_pnmd(1M) has problem acquiring a lock on the file (/var/cluster/run/pnm_lock).
Solution:Check if another instance of cl_pnmd is already running. If not, remove the lock file (/var/cluster/run/pnm_lock) and start cl_pnmd by sending KILL (9) signal to cl_pnmd. PMF will restart cl_pnmd automatically.
689837 RGM is deferring the relocation of resource group <%s> from node <%s>, because resource %s depends on another resource which is currently offline.
Description:A scha_control(1HA,3HA) GIVEOVER attempt failed on all potential masters, because the resource requesting the GIVEOVER has unsatisfied dependencies. A properly-written resource monitor, upon getting the SCHA_ERR_CHECKS error code from a scha_control call, should sleep for awhile and restart its probes.
Solution:Usually no user action is required, because the dependee resource is switching or failing over and will come back online automatically. At that point, either the probes will start to succeed again, or the next GIVEOVER attempt will succeed. If that does not appear to be happening, you can use clresource to determine the resources on which the specified resource depends that are not online, and bring them online.
690196 Failed to retrieve the sap version
Description:The data service cannot retrieve the sap version.
Solution:Ensure disp+work/jlaunch is in the expected path (/usr/sap/<SID>/SYS/exe/run) and is executable.
690417 Protocol is missing in system defined property %s.
Description:The specified system property does not have a valid format. The value of the property must include a protocol.
Solution:Use clresource to specify the property value with protocol. For example: TCP.
690463 Cannot bring server online on this node.
Description:Oracle server is running but it cannot be brought online on this node. START method for the resource has failed.
Solution:Check if Oracle server can be started manually. Examine the log files and setup. Clear START_FAILED flag on the resource and bring the resource online.
691005 retval = %d)
Description:The task execution by the cl_execd interface failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
691489 Fault with resource detected. Disabling resource %s.
Description:The fault monitor has detected an unrecoverable fault with the specified resource. As a result, the fault monitor issues a request to the RGM to disable the resource.
Solution:No user action required.
691493 One or more of the SUNW.HAStoragePlus resources that this resource depends on is in a different resource group. Failing validate method configuration checks.
Description:The HAStoragePlus resource that this resource depends on must be configured into the same resource group.
Solution:Move the HAStoragePlus resource into this resource's resource group.
692203 Failed to stop development system.
Description:Stopping the development system failed.
Solution:Informational message. Check previous messages in the system log for more details regarding why it failed.
692466 Error while unbinding 'rtreg_proxy_server' in the name server. Exiting.
Description:The rtreg server program could not register the corba object in the name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
692486 Could not initialize the ORB. Exiting.
Description:The rtreg server program was unable to initialize its interface to the low-level cluster machinery.
Solution:Make sure the nodes are booted in cluster mode. If so, contact your authorized Sun service provider to determine whether a workaround or patch is available.
692939 CMM: Unable to get reference to membership engine.
Description:An instance of the userland CMM encountered an internal initialization error. The userland CMM could not obtain a reference to the membership engine object.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
693339 File system associated with mount point %s %s %s is global. Global file systems are not supported inside Zone Cluster.
Description:Global file systems are not supported inside zone cluster. Check the release notes for supported file systems in zone cluster.
Solution:Modify the configured file system mount points such that there are no global file systems and repeat the operation.
693579 stop_mysql - Failed to flush MySql logfiles for %s
Description:The mysqladmin command failed to flush MySQL log files.
Solution:Either was MySQL already down or the fault monitor user does not have the right permission to flush log files. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges.
695340 scf_handle_bind 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.
695728 Skipping checks dependant on HAStoragePlus resources on this node.
Description:This resource will not perform some filesystem specific checks (during VALIDATE or MONITOR_CHECK) on this node because at least one SUNW.HAStoragePlus resource that it depends on is online on some other node.
Solution:No user action is required.
695895 ping_timeout out of bound. The timeout must be between %d and %d: using the default value
Description:The scdpmd config file (/etc/cluster/scdpm/scdpmd.conf) has a bad ping_timeout value. The default ping_timeout value is used.
Solution:Fix the value of ping_timeout in the config file.
696100 The resource type version of resource type %s is NULL.
Description:The HAStoragePlus resource type version of the specified resource type was found to be NULL.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
696207 scvxvmlg error - service %s has service_class %s, not %s, ignoring it
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.
696463 rgm_clear_util called on resource <%s> with incorrect flag <%d>
Description:An internal rgmd error has occurred while attempting to carry out an operator request to clear an error flag on a resource. The attempted clear action will fail.
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.
696903 Failed to configure the private IP address for a zone
Description:The private IP address assigned to a zone was not configured correctly.
Solution:The private IP address assigned to the zone is used for private IP communication for the zone. So, this feature may not work as expected as a result of this error. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
697026 did instance %d created.
Description:Informational message from scdidadm.
Solution:No user action required.
697108 t_sndudata in send_reply failed.
Description:Call to t_sndudata() failed. The "t_sndudata" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
697334 Memory allocation failure.
Description:Unable to allocate memory.
Solution:No user action required.
697340 Giveover attempt failed: no other node is currently available to host the resource group. Should be OK as no other node should be accessing the QFS file system if this is the last MDS node.
Description:No other node found that can host this RG. This is Ok, since this is the last node sharing the QFS if this is a properly configured cluster. Just let Solaris unmount the QFS file system.
Solution:Informational message.
697588 Nodeid must be less than %d. Nodeid passed: '%s'
Description:Incorrect nodeid passed to Oracle UNIX dlm. Oracle UNIX dlm will not start.
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.
698239 Monitor server stopped.
Description:The Monitor server has been stopped by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed.
698258 Function: validate - Failed to get service state for %s
Description:The SMF service state for %s is not known.
Solution:Review the /opt/SUNWsczone/sczsmf/util/sczsmf_config configuration file and make sure you have specified the correct SMF service name.
698272 Probing thread for mountpoint %s is hanging for timeout period %d seconds
Description:The test for performing I/O operations is hanging. One possible reason for this could be network connectivity failure.
Solution:Check the network connectivity and restart the ScalMountPoint resource.
698587 sig2str(3C) failed for pmmd_adm while converting signal number %d to a signal name.
Description:The pmmd_adm was unable to convert a valid signal number to its signal name, because the sig2str(3C) function failed.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
699104 VALIDATE failed on resource <%s>, resource group <%s>, time used: %d%% of timeout <%d, seconds>
Description:The resource's VALIDATE method exited with a non-zero exit code. This indicates that an attempted update of a resource or resource group is invalid.
Solution:Examine syslog messages occurring just before this one to determine the cause of validation failure. Retry the update.
699413 PMF is restarting tag <%s>, cmd_path="%s"
Description:The process with the given tag failed to stay up and exceeded the allowed number of retry attempts (given by the 'pmfadm -n' option), and the action (given by the 'pmfadm -a' option) was initiated by rpc.pmfd. The action succeeded (i.e., returned zero), and rpc.pmfd restarted the exited process. For more information, see pmfadm(1M).
Solution:This message is informational; no user action is needed.
699455 Error in creating udlmctl link: %s. Error (%s)
Description:The udlmreconfig program received error when creating link using /bin/ln. This error will prevent startup of RAC framework on this node.
Solution:Check the error code, correct the error and reboot the cluster node to start UNIX Distributed Lock Manager on this node.
699689 (%s) poll failed: %s (UNIX errno %d)
Description:Call to poll() failed. The "poll" man page describes possible error codes. udlmctl will exit.
Solution: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.
Message IDs 700000–799999
This section contains message IDs 700000–799999.
700065 Validate - %s/etc/%s does not exist
Description:${INFORMIXDIR}/etc/${ONCONFIG} does not exist.
Solution:Ensure that ${INFORMIXDIR}/etc/${ONCONFIG} exists.
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.
700975 Failfast : Fixed priority class not configured in this system
Description:Fixed scheduling class is not configured in this system, but a task needs to run in fixed scheduling class.
Solution:Configure Fixed scheduling class for the system.
701035 Failed to obtain the global service name of device %s for mount point %s.
Description:The DCS was not able to find the global service name.
Solution:Check the global service configuration.
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.
702018 Waiting for the SAP Application server to come online.
Description:Waiting for the SAP application to startup.
Solution:Informational message. No user action is needed.
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.
702341 Error while binding 'rtreg_proxy_server' in the name server. Exiting.
Description:The rtreg server program could not bind the corba object from the local name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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 reregister the resource, make sure the variable ServiceStopCommand is properly set within the ${PARAMETERDIR}/sczsh_${RS} parameter file.
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 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. The currently attempted failover is deferred and might be retried.
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 occurred 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 recreate 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:The 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.
706478 Membership: Could not create membership engine object.
Description:Could not create the membership engine object. 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.
706962 Membership: Got nil reference to CMM control object.
Description:Got a nil reference to the CMM control object on the local node.
Solution:No user action needed.
707639 Ifconfig proxy : block_allsignals() : thr_sigsetmask returned %d. Exiting.
Description:ifconfig proxy program has encountered a failed thr_sigsetmask(3C) 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.
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 fault monitor can't connect to the specified MySQL instance.
Solution:No user action is required.
708901 Error in abandoning Contract:%d
Description:Cannot abandon the displayed contract.
Solution:Check the contract man page to know more about the error.Also make sure the basic contract functionalities are working.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.
709171 start_DB_SAA - Command %s does not exist
Description:The command /usr/swa/apply_alliance_ports does not exist but is required for SWIFTAlliance Access to properly function.
Solution:Verify the SWIFTAlliance Access installation and make sure /usr/swa/apply_alliance_ports does exist.
709251 Unexpected signal, Exiting.
Description:The rtreg server program got an unexpected signal and is exiting.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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: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.
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 validity 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.
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:No user action is 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 its 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.
715975 Failed to retrieve the global service name(s) for mount point %s %s zone cluster %s.
Description:HAStoragePlus failed to obtain the global service name(s) for the specified mount point.
Solution:Usually this happens when the devices specified for the mountpoint are not valid. Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
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.
716620 %s: fork1 returned %d. Exiting.
Description:The pmmd program was unable to fork and daemonize because fork1() system call failed.
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 resource 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.
717104 Failed to generate callback for remove adapter event
Description:Cluster cannot generate a callback for the RDS module. Operation of RDS sockets might be affected.
Solution:If Reliable Datagram Sockets (RDS) is used by applications running on this cluster, contact your Sun Microsystems service representative to determine if a workaround or patch is available.
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.
718060 Could not update the dependent resource <%s> info on the inter-cluster depended on resource <%s>
Description:Failed to update the information of the depended-on resource. Possible cause could be that the remote zone cluster is down or the containing rg of the depended on resource is switching or the remote depended on resource itself is invalid.
Solution:No user action is required.
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 user action is required. 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 user action is required. 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:No user action is 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.
720104 cl_execd: fork1 returned %d. Exiting.
Description:The cl_execd program has encountered failure of fork1(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.
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.
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.
720887 set_fx_prio : Unable to get ff_admin_v
Description:cl_execd program couldn't get a reference to the CORBA failfast server object.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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: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.
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.
722035 Mounting the device %s on path %s failed in zone cluster %s : %s
Description:HAStoragePlus was not able to mount the specified file system inside zone cluster.
Solution:Check the system configuration. Also check if the FilesystemCheckCommand is not empty (it is not advisable to have it empty since file system inconsistency may occur).
722136 Error in opening temporary RGM cache file %s: %s
Description:RGM is unable to open the file used for caching the data between the rgmd and the scha_cluster_get.
Solution:Since this file is used only for improving the communication between the rgmd and scha_cluster_get, failure to open it doesn't cause any significant harm. rgmd will retry to open this file on a subsequent occasion.
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 user action is required.
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 goingd down.
Solution:No user action is 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.
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: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 the problem.
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.
723558 cl_execd: thr_sigsetmask returned %d. Exiting.
Description:cl_execd program has encountered a failed thr_sigsetmask(3C) 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.
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.
725356 sigprocmask(2) failed while querying current signal mask: error %s
Description:The rgmd_starter was unable to query its current signal mask because the sigprocmask(2) function failed. The message contains the system error. rgmd_starter cannot launch an rgmd daemon.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
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.
725652 PNM proxy : Unable to retrieve version from version manager: %s
Description:PNM proxy got a nil reference to the Version manager and hence failed to retrieve the version.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
725852 zc_rgm_halt for zone %s: Could not get clconf tree. Exiting.
Description:The zc_rgm_halt could not get the clconf tree for the zone cluster and thus cannot determine the hostname of the zone going down. Hence zc_rgm_halt will not be able to evacuate resource groups for this zone which belongs to a zone cluster. Support for this zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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: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.
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:The udlmctl received an illegal message.
Solution:No user action is required. The 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:The 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: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.
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 application.
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.
729377 Unable to determine my hostname. Errno %d. Exiting.
Description:process_cmd_log was unable to determine the hostname of the node.
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:No user action is required.
730960 Membership: Unable to change number of threads in membership callback threadpool.
Description:Threads could not be added to the membership callback threadpool. 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.
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.
731185 Failed to set core location properties for the method tag <%s>. Error:<%d>
Description:The RGM could not query the zonepath for setting the location where cores for the data service process tree can get stored, if the method times out.
Solution:The core collection facility will be disabled for this method tag. Save a copy of /var/adm/messages files on this node and Contact your authorized Sun service provider for assistance in diagnosing the problem.
731228 validate_options: %s Option -G not set
Description:The option -G of the agent command $COMMANDNAME is not set,
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.
731847 ${PROG}: Internal error - bad call to get_new_ipnodes_line().
Description:An internal error has occurred while updating nsswitch.conf files on the zone cluster nodes.
Solution:Save the /var/adm/messages and the output of nsswitch.conf file the zone cluster nodes and contact your authorized Sun service provider for further assistance.
732569 reservation error(%s) error. Not found clexecd on node %d.
Description:The device fencing code was unable to communicate with another cluster node.
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.
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 re-execute the method and see if the signal is terminating the process. Contact your SUN vendor for help.
733157 %s/krb5kdc not started, exiting
Description:The 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.
734765 Membership : invalid event occurred for the state machine of '%s' membership on receiving membership from leader, current state is %s, leader says incarnation = %d, local incarnation known to state machine = %d.
Description:An invalid event has occurred for the state machine of a particular membership.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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:The rgm didn't process a restart request, most likely due to the configuration settings.
Solution:This is an informational message. No user action is required.
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.
735009 Function: validate_probe - Directory for the socket file %s does not exist any more, a failover will occur
Description:The directory specified in the PGHOST variable does not exist any more.
Solution:Create the directory. None if it was a lost mount.
735336 Media error encountered, but Auto_end_bkp is disabled.
Description:The HA-Oracle start method identified that one or more data files 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 data files being left in hot backup mode, the Auto_end_bkp extension property should be enabled or the data files should be recovered manually.
735531 Failed to determine the resource group '%s' leader.
Description:The zone boot handler failed to determine a leader for the specified resource group. This should not happen as the booting node at least will be leader.
Solution:Contact your Sun service provider to determine whether a workaround or patch is available.
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.
736485 start_DB_SAA - Command %s does not exist or is not executable
Description:The referenced command is not executable or does not exist, but is required for SWIFTAlliance Access to properly function.
Solution:Verify the SWIFTAlliance Access installation and make sure the referenced command does exist and is executable.
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 HAStoragePlus 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.
736741 Membership : Node '%s' (node id %d) of cluster '%s' joined.
Description:A node has joined the zone cluster.
Solution:This message is for information. No user action is required.
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.
737041 WARNING: Sun Cluster boot: Could not load module $m
Description:A kernel module for RDS failed to load.
Solution:If RDS is required by the application running on the cluster, contact your Sun Microsystems service representative to determine if a workaround or patch is available.
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: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.
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 libclcontract code was not able to act on a semaphore. The message contains the system error. The server process (which is using libclcontract) 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.
740691 Zone cluster PNM interface invoked from a non-global zone that does not belong to a zone cluster
Description:The PNM proxy subsystem interface for a zone cluster is being used from a client in non-global zones.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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.
741078 Switchover error (%s): failed to mount FS (%d)
Description:The file system specified in the message could not be hosted on the node the message came from.
Solution:Check /var/adm/messages to make sure there were no device errors. If not, contact your authorized Sun service provider to determine whether a workaround or patch is available.
741384 Failed to stop %s with SIGINT. Will try to stop it with SIGKILL.
Description:The attempt to stop the specified application with signal SIGINT failed. Will attempt to stop it with signal SIGKILL.
Solution:No user action is needed.
741451 INTERNAL ERROR: usage: `basename $0` <dbmcli-command> <User_Key> <Pid_Dir_Path> <DB_Name>
Description:An internal error has occurred.
Solution:Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
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:No user action is required.
743400 Successful in binding 'pnm_proxy_server' in the name server.
Description:The pnm proxy program could bind CORBA object in the all cluster context of the global name server.
Solution:This is an informational message. No user action is required.
743719 The resource type version of the resource %s is NULL.
Description:Self explanatory.
Solution:Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem with copy of the /var/adm/messages files on all nodes.
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:HAStoragePlus 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.
744371 qdmd: Quorum device type registry for node %d not found
Description:The quorum device monitoring daemon encountered an error while fetching information from the device type registry.
Solution:Contact service support.
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 communication, but each time the error EAGAIN occurred.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
744794 Failed to retrieve the resource property %s : %s.
Description:Unable to get a handle to read the value of the PRENET_START_TIMEOUT property for this resource.
Solution:Internal error. Contact user support for assistance.
744956 mmap failure: %s
Description:The libclcontract code was not able to allocate shared memory for a semaphore, possibly due to low memory, and the system error is shown. The server does not perform the action requested by the client. An error message is also output to syslog.
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.
745275 PNM daemon system error: %s
Description:A system error has occurred 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.
746692 libpnm proxy system error: %s
Description:A system error has occurred in libpnmproxy. This could be because of the resources on the system being very low, such as low memory.
Solution:The user of libpnmproxy should handle these errors. However, if the message is out of memory, increase the swap space, install more memory, or reduce peak memory consumption. Otherwise the error is unrecoverable, and the node needs to be rebooted.
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.
748059 Invalid upgrade callback from version manager: new version %d.%d is not the expected new version %d.%d from callback step 2.
Description:Version manager delivered upgrade callback to rgmd about a new version that is not the expected new version after callback step 2 for rgmd.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
748065 Disk %s not found in CCR. Internal error. Line %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
748206 Unsupported service class (%s) for global service %s associated with path %s.
Description:HAStoragePlus recognized an unsupported service class for a specified global service. It supports only the service classes of type DISK, SUNWmd and SUNWvxvm.
Solution:Specify global devices of supported type and repeat the operation. If the problem persists, contact your authorized Sun service provider.
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.
749083 Creation of resource <%s> failed because the inter-cluster restart dependencies could not be set
Description:Resource creation failed due to specification of invalid inter cluster dependencies.
Solution:Check the remote cluster name or remote resource name and retry the same command.
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.
750698 SUNW.ScalMountPoint resource does not support to configure NAS for Zone Cluster.
Description:SUNW.ScalMountPoint prevented to create resource with NAS configured for a zone cluster as NAS is not supported inside Zone Cluster.
Solution:Check the release notes on the status of support of NAS for Zone Cluster.
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.
751833 Membership : Cluster '%s' shutdown completed.
Description:The zone cluster has been shutdown completely on this node.
Solution:This message is for information. No user action is required.
751949 scswitch: rgm_change_mastery() failed with NOREF, UNKNOWN, or invalid error on node %s
Description:An internode 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: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.
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.
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.
754129 sigaddset(3C) failed for pmmd_adm while adding signal SIG%s to ignored signal set: error %s
Description:The pmmd_adm was unable to add a signal number to a signal set, because the sigaddset(3C) function failed. The message contains the system error. pmmd_adm cannot do its requested action.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
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:No user action is required.
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.
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.
757287 Could not create command log for zone cluster %s
Description:The CCR raised an exception while creating the command log table.
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 Sun Cluster 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 online 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.
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 postinstallation 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 interconnect 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.
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.
762437 CMM: Unable to notify membership subsystem.
Description:An instance of the userland CMM encountered an internal initialization error. The userland CMM could not tell the membership subsystem that it has come up.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
762902 Failed to restart fault monitor.
Description:The resource property that was updated needed the fault monitor to be restarted in order 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.
762925 Membership: Unable to get cluster ID for cluster '%s'.
Description:Membership subsystem was unable to convert a zone cluster name to a cluster ID when processing a Solaris notification that the specified zone went down.
Solution:If the zone belongs to a valid zone cluster, reboot the machine hosting the zone. Contact your authorized Sun service provider to determine whether a workaround or patch is available to prevent future occurrences of this problem.
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 retried 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.
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.
764006 %s: ct_pr_event_get_ppid: %s
Description:The pmmd was unable to retrieve the parent pid from a contract event. The pmmd will continue to monitor the process, but the pmmd may have missed an event of interest.
Solution: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.
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 reason 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:No user action is required.
764923 Failed to initialize the DCS.
Description:HAStoragePlus 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.
765975 qdmd: Cannot determine nodeid of this node. Exiting.
Description:The quorum device monitoring daemon cannot determine nodeid.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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:No user action is required.
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: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.
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: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.
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: rebooted: 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: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.
767629 lkcm_reg: UNIX DLM version (%d) and the OSD library version (%d) are not compatible. UNIX DLM versions acceptable to this library are: %d
Description:UNIX DLM and Oracle DLM are not compatible. 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.
768230 Failed to construct command %s.
Description:HAStoragePlus failed to construct command path using dynamic memory allocation.
Solution:Usually, this happens when the system has exhausted its resources. Check if the swap file is big enough to run Sun Cluster software.
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: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.
768937 perform_switchover - the promotion to primary failed for %s
Description:The promotion to primary for the replicated object failed on the secondary side
Solution:Evaluate the root cause for the failed promotion and retry the operation
769367 Got nil reference to version manager
Description:RGM got a nil reference to the Version manager and hence cannot register for version upgrade callbacks.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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: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.
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.
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 specified 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.
771747 INTERNAL ERROR : Failed to register with zone cluster membership for zone cluster '%s'.
Description:A error occurred while registering for zone cluster membership update with zone cluster member monitor(ZCMM).
Solution: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 content 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:No user action is required.
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.
773093 PNM proxy : Unexpected signal, Exiting.
Description:The pnm proxy program received an unexpected signal and is exiting.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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:No user action is required. 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: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.
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.
774994 Membership: Got nil reference to version manager.
Description:Got a nil reference to the version manager on the local node.
Solution:No user action needed.
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: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.
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.
776661 INTERNAL ERROR: Failed to get clconf handle for zone cluster '%s'.
Description:A error occurred while reading the zone cluster information.
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.
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: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.
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.
779412 check_qmgr - <%s>
Description:The Queue Manager check has failed.
Solution:No user action is 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 user action is required.
779755 Failed to add %s entry to the CCR table %s.
Description:An unknown error has occurred while updating the CCR with the current zone cluster name.
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.
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 recreating 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:No user action is required.
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.
782168 There are no device (of pattern %s) that is associated with the global device path %s that is configured to zone cluster %s.
Description:The specified device is not authorized to use in the specified zone cluster as they are not configured to that zone cluster.
Solution:The operation needs to be retried after the devices associated with specified global device path is configured to zone cluster. If the problem persists, contact your authorized Sun service provider with /var/adm/messages of all cluster nodes.
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.
782497 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 $(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 user action is 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 agent command $COMMANDNAME is not set,
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 daemon uses default values.
Solution:Check the config file.
784591 Telemetry data service start method completed sucessfuly
Description:The telemetry data service started successfully.
Solution:This message is informational; no user action needed.
784607 Couldn't fork1.
Description:The fork(1) 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: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.
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 problem. Otherwise contact your authorized Sun service provider.
785567 check_mysql_slave - Couldn't get SHOW SLAVE STATUS for instance %s (%s)
Description:The fault monitor can't retrieve the MySQL slave status for the specified instance.
Solution:Either was MySQL already down or the faultmonitor user does not have the right permission. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges. Check also the MySQL log files for any other errors.
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: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.
786611 Validation of VFSTAB entry for filesystem mount point %s in zone cluster %s is failed.
Description:HAStoragePlus failed while validating the vfstab entry for the specified mountpoint.
Solution:Usually, this happens due to incorrect entries in vfstab. Check the log messages for specified error case and repeat the operation.
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.
787850 Error deleting PidLog <%s> (%s) for Sun Java System Web Server service with config file <%s>.
Description:The data service was not able to delete the specified PidLog file.
Solution:Delete the PidLog file manually and start the resource group.
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.
788409 Unable to contact sc_zonesd.
Description:Unable to contact cluster process. 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.
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 received 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 last probe failed, the data service will be restarted of failed over.
Solution:No user action is required.
790080 Global service %s associated with path %s is unable to become a primary on node %d.
Description:HAStoragePlus 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.
790500 Failed to lookup the zone cluster configuration in the CCR
Description:The CCR returned an exception when trying to lookup the zone cluster configuration table.
Solution:Verify if the zone cluster CCR is corrupted. If not, contact your authorized Sun service provider to determine whether a workaround or patch is available.
790716 scha_resource_open() failed for Resource %s : %s
Description:A call to scha_resource_open() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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: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.
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.
791120 clcomm: solaris xdoor: Failed to get zoneid from credentials, returned errno = %d
Description:Failed to get the zone information associated with the client of the current door invocation.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
791721 PNM proxy : block_allsignals() : sigfillset returned %d. Exiting.
Description:pnm proxy program has encountered a failed sigfillset(3C) 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.
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 user action is 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.
792310 cl_execd: setrlimit returned %d
Description:The cl_execd program has encountered a failed setrlimit(2) system call. The error message indicates the error number of failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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 occurred 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.
793439 start_ids - Informix Server (%s) failed to start rc(%s)
Description:The specified Informix Server failed to start.
Solution:Check the syslog for further messages. If possible the Solaris Cluster will attempt to restart the Informix Server.
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.
793647 Failed to add '%s' to MDS resource group list.
Description:The zone halt handler failed to generate the SUNW.qfs resource group list.
Solution:Investigate the zone halt log messages and try to rectify the problem. If problem persists after halting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
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: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.
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.
796649 INTERNAL ERROR: Failed to initialize ORB.
Description:ORB initialization failure.
Solution:Make sure that the nodes are booted in cluster mode. If so, contact your authorized Sun service provider to determine whether a workaround or patch is available.
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:No user action is required.
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.
798499 set_fss_prio : Unable to get ff_admin_v
Description:cl_execd program couldn't get a reference to the CORBA failfast server object.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
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:No user action is required.
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.
799193 check_ids - Database Instance %s has failed mode(%s) blocked(%s), contact your DBA
Description:The Informix Dynamic Server database has failed.
Solution:Check the system log for error messages and contact your DBA. Solaris Cluster will restart the Informix Server.
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.
Message IDs 800000–899999
This section contains message IDs 800000–899999.
801260 Failfast : Time shared class not configured in this system
Description:Time shared class is not configured in this system, but a task needs to run in time shared scheduling class.
Solution:Configure Time shared priority class for the system.
801519 connect: %s
Description:The cl_apid received the specified error while attempting to deliver an event to a CNRP client.
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.
801577 sv_get_zone_iptype: Could not get iptype for zone %s,error = %d
Description:There was a failure to get information about the IP type of a configured zone in the system.
Solution:There might be other related error messages which might be helpful. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
801715 clq_scsi3: More than one reservation key was found on quorum device %s
Description:More than one reservation key was found on the specified quorum device. This occurs because of unexpected behavior from device driver or multipathing driver or device's firmware.
Solution:Please look for updates in device driver, multipathing driver or device firmware. If no updates are available please contact Sun device driver support team.
801738 remote node %s died
Description:An internode communication failed because another cluster node died.
Solution:No user action is required. The cluster will reconfigure automatically. Examine syslog output on the rebooted node to determine the cause of node death.
801855 Error in scha_cluster_get
Description:Error in getting all the resource groups in the cluster
Solution:Check if the RGM functionalities are working fine and if the resource group is present. Contact your SUN vendor for more help.
802295 monitor_check: resource group <%s> changed while running MONITOR_CHECK methods
Description:An internal error has occurred in the locking logic of the rgmd, such that a resource group was erroneously allowed to be edited while a failover was pending on it, causing the scha_control call to return early with an error. This in turn will prevent the attempted failover of the resource group from its current master to a new master. This should not occur and may indicate an internal logic error in the rgmd.
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.
802363 Failed to read from test-file %s : %s
Description:A read operation on the test file for I/O operations failed. One possible cause of this error is that the test file has been deleted. The deletion of this file might be caused by malicious activity in your system.
Solution:Restart the ScalMountPoint resource.
802539 No permission for owner to read %s.
Description:The owner of the file does not have read permission on it.
Solution:Set the permissions on the file so the owner can read it.
802796 UPDATE failed with error %d
Description:An UPDATE operation failed with error indicated.
Solution:Contact your Sun support representative for further assistance.
803179 CRS is detected to be down, oracle instance %s is DOWN.
Description:The shutdown of the Oracle instance is considered a success since CRS is detected to be down.
Solution:Typically, none required, since if CRS is down, the RAC instance is down as well. However, if this is not the true scenario, contact your Sun support representative for further assistance.
803391 Could not validate the settings in %s. It is recommended that the settings for host lookup consult `files` before a name server.
Description:Validation callback method has failed to validate the hostname list. There may be syntax error in the nsswitch.conf file.
Solution:Check for the following syntax rules in the nsswitch.conf file. 1) Check if the lookup order for "hosts" has "files". 2) "cluster" is the only entry that can come before "files". 3) Everything in between '[' and ']' is ignored. 4) It is illegal to have any leading whitespace character at the beginning of the line; these lines are skipped. Correct the syntax in the nsswitch.conf file and try again.
803570 lkcm_parm: invalid handle was passed %s %d
Description:This is an internal error.
Solution:Save the contents of the following files from all nodes: /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log, and /var/cluster/ucmm/dlm*/*logs/*. After saving the contents of these files, contact your Sun service representative for assistance in diagnosing and correcting the problem.
803719 host %s failed, and clnt_spcreateerror returned NULL
Description:The rgm is not able to establish an rpc connection to the rpc.fed server on the host shown, and the rpc error could not be read. 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.
803888 SCSLM <%s> pool_get_property <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
804002 Function: stop_sczbt - Manual intervention needed for non-global zone %s - unable to get into state installed.
Description:The non-global zones shutdown command did not complete in time or zoneadm halt was not able to bring the non-global zone into state "installed". In order to prevent failed starts of the non-global zone on this node, manual cleanup is necessary.
Solution:Follow the Solaris System Administrator Guide for Zones to bring the non-global zone into state "installed" before trying to restart the resource on this node.
804457 Error reading properties; using old properties
Description:The cl_apid was unable to read all the properties correctly. It will use the versions of the properties that it read previously.
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.
804658 clexecd: close returned %d while exec'ing (%s). Exiting.
Description:clexecd program has encountered a failed close(2) system call. The error message indicates the error number for the failure.
Solution:The clexecd program will exit and the 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.
805428 check_smbd - Couldn't retrieve faultmonitor-user <%s> from the nameservice
Description:The Samba resource could not validate that the fault monitor userid exists.
Solution:Check that the correct fault monitor userid was used when registering the Samba resource and that the userid really exists.
805627 Stop command %s timed out.
Description:The command for stopping the data service timed out.
Solution:No user action needed.
805694 Error while binding '%s' in the name server. Exiting.
Description:The cl_execd program couldn't bind the corba object from the global name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
805735 Failed to connect to the host <%s> and port <%d>.
Description:An error occurred the while fault monitor attempted to make a connection to the specified hostname and port.
Solution:Wait for the fault monitor to correct this by doing restart or failover. For more error descriptions, look at the syslog messages.
805741 Dependency between resource %s and its MDS resource %s has not been defined.
Description:The specified HAStoragePlus resource requires an explicit dependency on the metadata server resource that represents the mount point.
Solution:Define the required dependency between the HAStoragePlus resource and the metadata server resource.
806137 %s called with invalid parameters
Description:The function was called with invalid parameters.
Solution:Save all resource information (clresource show -v) and contact the vendor of the resource.
806359 Checking of file system configuration failed.
Description:The master configuration file /etc/opt/SUNWsamfs/mcf for the specified file system contains incorrect entries. A misconfiguration is one possible cause of incorrect entries in this file.
Solution:Correct the entries in the master configuration file and repeat the operation.
806902 clutil: Could not create lwp during respawn
Description:There was insufficient memory to support this operation.
Solution:Install more memory, increase swap space, or reduce peak memory consumption.
806982 Create_configuration - MySQL replication resource group %s creation unsuccessful
Description:The creation of the MySQL replication resource group was unsuccessful.
Solution:Consult /var/adm/messages and fix the errors outlined there.
807015 Validation of URI %s failed
Description:The validation of the uri entered in the monitor_uri_list failed.
Solution:Make sure a proper uri is entered. Check the syslog and /var/adm/messages for the exact error. Fix it and set the monitor_uri_list extension property again.
807070 cl_pnmd has requested an immediate failover of all HA IP addresses hosted on IPMP group %s
Description:All network interfaces in the IPMP group have failed. All of these failures were detected by the hardware drivers for the network interfaces, and not in.mpathd. In such a situation cl_pnmd requests all highly available IP addresses (LogicalHostname and SharedAddress) to fail over to another node without any delay.
Solution:No user action is needed. This is an informational message that indicates that the IP addresses will be failed over to another node immediately.
807223 Failed to retrieve the IPMP group name for adapter %s.
Description:Failed to retrieve the IPMP group name for the adapter.
Solution:Make sure that all the adapters on the system are part of an IPMP group.
807249 CMM: Node %s (nodeid = %d) with votecount = %d removed.
Description:The specified node with the specified votecount has been removed from the cluster.
Solution:This is an informational message, no user action is needed.
807547 MDS server nodename '%s' of file system '%s' is not in the nodelist of the resource group '%s'.
Description:The zone boot handler found that the MDS is running on different node which is not part of configured resource-group node list.
Solution:Check the location of the MDS and see whether it is running on the node which is in the resource-group node list. If that is the case contact your Sun service provider to determine whether a workaround or patch is available.
807560 The entry in vfstab for mount point '%s' has too many fields.
Description:The entry in vfstab for the specified mount point has more fields than are defined for a single vfstab entry.
Solution:Remove the extraneous fields from the entry in vfstab for the mount point and repeat the operation.
807860 reservation notice(%s) - MHIOCRELEASE success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action required.
808444 lkcm_reg: UNIX DLM version (?) and the OSD library version (%d) are not compatible. UNIX DLM versions acceptable to this library are: %d
Description:UNIX DLM and Oracle DLM are not compatible. 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.
808746 Node id %d is higher than the maximum node id of %d in the cluster.
Description:In one of the scalable networking properties, a node id was encountered that was higher than expected.
Solution:Verify that the nodes listed in the scalable networking properties are still valid cluster members.
808763 cl_execd: execl returned %d.
Description:The cl_execd program failed to execute the task. The error message indicates the error number of failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
809026 sge_schedd already running; start_sge_schedd aborted.
Description:An attempt was made to start sge_schedd by bringing the sge_schedd-rs resource online, with a sge_schedd process already running.
Solution:Terminate the running sge_schedd process and retry bringing the resource online.
809038 No active replicas for the service %s.
Description:The DCS was not able to find any replica for the specified global service.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
809387 Starting UFS quotas for %s
Description:The quotas for the UFS mountpoint specified by %s are going to be enabled.
Solution:This is an informational message. No user action is required.
809554 Unable to access directory %s:%s.
Description:A HA-NFS method attempted to access the specified directory but was unable to do so. The reason for the failure is also logged.
Solution:If the directory is on a mounted filesystem, make sure the filesystem is currently mounted. If the pathname of the directory is not what you expected, check to see if the Pathprefix property of the resource group is set correctly. If this error occurs in any method other then VALIDATE, HA-NFS would attempt to recover the situation by either failing over to another node or (in case of Stop and Postnet_stop) by rebooting the node.
809742 HTTP GET response from %s:%d has no status line
Description:The response to the GET request did not start or had a malformed status line.
Solution:Check that the URI being probed is correct and functioning correctly.
809796 lookup_c1: unknown binding type <%d>
Description:During a name server lookup an unknown binding type was encountered.
Solution:No user action is required. This is informational message.
809844 scvxvmlg error - rmdir(%s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
809858 ERROR: method <%s> timeout for resource <%s> is not an integer
Description:The indicated resource method timeout, as stored in the CCR, is not an integer value. This might indicate corruption of CCR data or rgmd in-memory state. The method invocation will fail; 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:Use clresource show -v to examine resource properties. If the values appear corrupted, the CCR might have to be rebuilt. If values appear correct, this might indicate an internal error in the rgmd. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
809956 PCSEXIT: %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.
809985 Elements in Confdir_list and Port_list must be 1-1 mapping.
Description:The Confdir_list and Port_list properties must contain the same number of entries, thus maintaining a 1-1 mapping between the two.
Solution:Using the appropriate scrgadm command, configure this resource to contain the same number of entries in the Confdir_list and the Port_list properties.
810219 stopstate file does not exist on this node.
Description:The stopstate file is used by HADB to start the database. This file will exists on the Sun Cluster node that last stopped the HADB database. That Sun Cluster node will start the database, and the others will wait for that node to start the database.
Solution:This is an informational message, no user action is needed.
810551 fatal: Unable to bind president to nameserver
Description:The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.
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.
810937 CMM: Reconfiguration delaying for %d milliseconds to allow larger partitions to win race for quorum devices.
Description:In the case of potential split brain scenarios, the CMM allows larger partitions to win the race to acquire quorum devices by forcing the smaller partitions to sleep for a time period proportional to the number of nodes not in that partition.
Solution:This is an informational message, no user action is needed.
811194 Derby data service start method completed successfully
Description:The derby data service started successfully.
Solution:This message is informational; no user action needed.
812033 Probe for J2EE engine timed out in scds_fm_tcp_write().
Description:The data service could not send to the J2EE engine port.
Solution:Informational message. No user action is needed.
812110 WARNING !!! RG of MDS Resource %s needs to be manually failed over!
Description:The metadata server resource could not be failed over from the current node to another suitable node. This attempt occurred because the ScalMountPoint resource on the node that hosts metadata server resource is going offline.
Solution:Manually switch over the metadata server resource to another suitable node.
812339 Devfsadm -i did
Description:Devfsadm command failed to configure did devices. This node might face problems with mounting /global/.devices/node@... file system(s).
Solution:If this node faces problems with mounting /global/.devices/node@... file system(s), run "/usr/sbin/devfsadm -i did" command. If mount problem persists, contact your authorized Sun service provider for assistance in diagnosing the problem.
812742 read: %s
Description:The rpc.fed server was not able to execute the read system call properly. The message contains the system error. The server will not capture the output from methods it runs.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
812928 dl_attach: DL_ERROR_ACK protocol error
Description:Could not attach to the physical device.
Solution:Check the documentation for the driver associated with the private interconnect. It might be that the message returned is too small to be valid.
813071 No usable address for hostname %s. IPv6 addresses were ignored because protocol tcp was specified in PortList. Enable IPv6 lookups by using tcp6 instead of tcp in PortList.
Description:The hostname maps to IPv6 address(es) only and tcp6 flag was not specified in PortList property of the resource. The IPv6 address for the hostname is being ignored because of that.
Solution:Specify tcp6 in PortList property of the resource.
813232 Message from invalid nodeid <%d>.
Description:The cl_eventd received an event delivery from an unknown remote node.
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.
813317 Failed to open the cluster handle: %s.
Description:HAStoragePlus was not able to access the cluster configuration.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
813803 door_call: %s; (skip) aborting
Description:The door_call failed with the specified reason. The program will be terminated and the node will be rebooted or halted.
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.
813866 Property %s has no hostnames for resource %s.
Description:The named property does not have any hostnames set for it.
Solution:Recreate the named resource with one or more hostnames.
814232 fork() failed: %m.
Description:The fork() system call failed for the given reason.
Solution:If system resources are not available, consider rebooting the node.
814382 Mountpoint %s for zone cluster %s falls outside its zone root.
Description:HAStoragePlus detected that the mount point for specified zone cluster falls outside of zone root. HAStoragePlus avoid such mount points for security reasons.
Solution:Change the specified zone cluster mount point so that it falls inside the zone root.
814388 Error in scha_res_get of project name prop,res:%s, Err: %s
Description:Cannot read the project name property of the resource
Solution:Take action depending on the error and contact SUN vendor for more help
814420 bind: %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.
814751 zone %s died on node %s
Description:The RGM has detected that the indicated zone has halted or rebooted. If any resource groups were online in that zone, they might fail over to alternate zones or nodes.
Solution:This is an informational message; no user action is needed.
814905 Could not start up DCS client because major numbers on this node do not match the ones on other nodes. See /var/adm/messages for previous errors.
Description:Some drivers identified in previous messages do not have the same major number across cluster nodes, and devices owned by the driver are being used in global device services.
Solution:Look in the /etc/name_to_major file on each cluster node to see if the major number for the driver matches across the cluster. If a driver is missing from the /etc/name_to_major file on some of the nodes, then most likely, the package the driver ships in was not installed successfully on all nodes. If this is the case, install that package on the nodes that don't have it. If the driver exists on all nodes but has different major numbers, see the documentation that shipped with this product for ways to correct this problem.
815148 Monitor check for sckrb5 successful.
Description:The node to be failed over to for HA-KDC is ready.
Solution:This is for informational purposes, no action is required.
815427 Unable to create the lock file (%s): %s
Description:The server was not able to start because it was not able to create the lock file used to ensure that only one such daemon is running at a time. 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.
815494 Validate - Samba log directory %s does not exist
Description:The Samba log directory does not exist.
Solution:Check the correct pathname for the Samba log directory was entered when registering the Samba resource and that the directory exists.
815617 time in wait(): %s
Description:The time(2) function failed with the specified error. This error will cause the process that is using libclcontract to return immediately from a wait() command.
Solution: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.
815729 CCR: Could not remove the CCR directory for cluster %s errno = %d.
Description:The error occurred while removing the CCR directory for a removed cluster on this node. The errno value indicates the nature of the problem.
Solution:There may be other related messages on this node, which may help diagnose the problem. The directory has to be manually removed outside of CCR control. Contact your authorized Sun service provider for assistance.
815869 %s is already online.
Description:Informational message. The application in the message is already running on the cluster.
Solution:No user action is required.
816154 Error in res %s execution Start
Description:Not able to process the resource to start all the services. Previous messages to this should give the reason.
Solution:Stop the resource and try starting again. If it fails after couple of retries, the resource can be manually failed over to another node or delegated restarter does it after the expiration of retry counts. Contact SUN vendor for more help
816300 Validate - can't resolve local hostname
Description:${SGE_ROOT}/utilbin/<arch>/gethostname when executed does not return a name for the local host.
Solution:Make certain the /etc/hosts and/or /etc/nsswitch.conf file(s) is/are properly configured.
817025 Zettabyte File System (ZFS) is not available in this release.
Description:Packages that contain ZFS are not installed.
Solution:Upgrade to a release that contains ZFS. If ZFS is available and you see this message, contact your authorized Sun service provider.
817325 zc_rgm_halt for zone %s: Failed to initialize the ORB. Exiting.
Description:The zc_rgm_halt failed to initialize ORB and will not be able to evacuate resource groups for this zone which belongs to a zone cluster. Support for this zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
817592 HA: rma::admin_impl failed to bind
Description:An HA framework component failed to register with the name server.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
817657 validate_options: HA N1 Grid Service Provisioning System %s Option %s is not set
Description:There is an option missing in the start stop or probe command.
Solution:Set the specified option
818472 repl_check fatal error - did_initlibrary() failure
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.
818604 reservation notice(%s) - MHIOCGRP_INKEYS success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action required.
818627 CMM: data read does not match data just written.
Description:After writing to a sector, the sector was read successfully. But the data just written and the data just read do not match. The error could be either in the driver or the hardware.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available for this driver/hardware error.
818776 Failed to open the temporary file '%s' while reporting the error status of failure to find MDS node of '%s' file system : %s.
Description:The zone boot handler failed to open specific temporary file.
Solution:Check the log messages to rectify the problem. If the problem persists, contact your authorized Sun service provider.
818824 HA: rma::reconf can't talk to RM
Description:An HA framework component failed to register with the Replica Manager.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
818830 fatal: Cannot get local nodeid/nodename
Description:An internal error has occurred. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
819319 SID <%s> is smaller than or exceeds 3 digits.
Description:The specified SAP SID is not a valid SID. 3 digit SID, starting with none-numeric digit, needs to be specified.
Solution:Specify a valid SID.
819642 fatal: unable to register RPC service; aborting node
Description:The rgmd daemon was unable to start up successfully because it failed to register an RPC service. It will produce a core file and will force the node to halt or reboot.
Solution:If rebooting the node doesn't fix the problem, examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
819721 Failed to start %s.
Description:Sun Cluster could not start the application. It would attempt to start the service on another node if possible.
Solution:1) Check prior syslog messages for specific problems and correct them. 2) This problem may occur when the cluster is under load and Sun Cluster cannot start the application within the timeout period specified. You may consider increasing the Start_timeout property. 3) If the resource was unable to start on any node, resource would be in START_FAILED state. In this case, use scswitch to bring the resource ONLINE on this node. 4) If the service was successfully started on another node, attempt to restart the service on this node using scswitch. 5) If the above steps do not help, disable the resource using scswitch. Check to see that the application can run outside of the Sun Cluster framework. If it cannot, fix any problems specific to the application, until the application can run outside of the Sun Cluster framework. Enable the resource using scswitch. If the application runs outside of the Sun Cluster framework but not in response to starting the data service, contact your authorized Sun service provider for assistance in diagnosing the problem.
819736 PMF is restarting process that died: tag=%s, cmd_path=%s, max_retries=%d, num_retries=%d
Description:A process monitored by PMF has exited and is being restarted. tag represents the name tag under which this process is registered. cmd_path represents the full path and arguments of the command being executed. max_retries represents the total number of retry attempts allowed. If the value of max_retries is -1 then unlimited restarts are allowed. num_retries represents the current retry attempt number. If num_retries is zero, this indicates that the number of retries was exceeded but the pmf action program decided to continue restarting the monitored process. For more information, see pmfadm(1M).
Solution:This message is informational; no user action is needed.
819738 Property %s is not set - %s.
Description:The property has not been set by the user and must be.
Solution:Reissue the scrgadm command with the required property and value.
820143 Stop of HADB node %d did not complete: %s.
Description:The resource was unable to successfully run the hadbm stop command either because it was unable to execute the program, or the hadbm command received a signal.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.
820160 Device group type is svm-sc
Description:The disk set type is Solaris Volume Manager for Sun Cluster. This message is an informational message.
Solution:No user action is required.
820394 Cannot check online status. Server processes are not running.
Description:HA-Oracle could not check online status of Oracle server. Oracle server processes are not running.
Solution:Examine 'Connect_string' property of the resource. Make sure that user id and password specified in connect string are correct and permissions are granted to user for connecting to the server. Check whether Oracle server can be started manually. Examine the log files and setup.
821134 %s: Cannot get transport info
Description:This program could not get transport information for the specified NLSPROVIDER.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
821143 Failed to create the thread event_listen_thr: %d
Description:Not able to start the thread to listen for events
Solution:The error code will tell the reason for not being able to start the thread. Check the pthread man pages for more info. Contact SUN vendor for more help.
821271 Failed to read nodes of first 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.
821354 scf_handle_decode_fmri 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.
821491 Zero length volume name. Ignoring.
Description:The value of the property 'LogicalDeviceList' is incorrect. A zero-length volume was specified.
Solution:Ensure that the property 'LogicalDeviceList' specifies a valid list of volumes.
821502 Function: validate: User %s does not exist, an existing user is required
Description:The user mentioned in the parameter file is not defined in the OS.
Solution:Fix the parameter file and provide an existing user for the variable USER.
821557 scslm_fe_run: FE_SLM_ERROR %d
Description:Resource group is under SC SLM control and an SLM error occurred. Check fed SLM errors for more details.
Solution:Move RG_SLM_type to manual and restart the resource group.
821614 Failed to restart the fault-monitor
Description:An error prevented a restart of a resource's fault monitor.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
822035 Failed to initialize the ORB. Exiting.
Description:The pnm proxy program was unable to initialize its interface to the low-level cluster machinery.
Solution:Make sure the nodes are booted in cluster mode. If so, contact your authorized Sun service provider to determine whether a workaround or patch is available.
822385 Failed to retrieve process monitor facility tag.
Description:Failed to create the tag that is used to register with the process monitor facility.
Solution:Check the syslog messages that occurred just before this message. In case of internal error, save the /var/adm/messages file and contact authorized Sun service provider.
822916 Contract Initialization Failed
Description:Not able to initialize the contract for contract event delivery
Solution:The previous messages should explain the reason. Make sure the basic contract functionality is working. Contact your SUN vendor for more help.
822922 Failed to create/open test-file %s : %s
Description:The test file could not be created or opened.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
823132 Failed to obtain the global service name of device %s: %s.
Description:The DCS was not able to find the global service name.
Solution:Check the global service configuration.
823207 Not ready to start local HADB nodes.
Description:The HADB database has not been started so the local HADB nodes can not be started.
Solution:Online the HADB resource on more Sun Cluster nodes so that the database can be started.
823318 Start of HADB database did not complete.
Description:The resource was unable to successfully run the hadbm start command either because it was unable to execute the program, or the hadbm command received a signal.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.
823490 scha_resource_open() failed for MDS Resource %s : %s
Description:A call to scha_resource_open() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
823553 Function: validate - Zonebrand for zone %s is configured as %s on a non-sparc system. It is only supported on sparc systems.
Description:The solaris8 and solaris9 brand for zones is only supported on the sparc platform.
Solution:Review the components configuration file and make sure the variable Zonebrand defines "solaris8" or "solaris9" only on a SPARC system.
823847 No callbacks registered for cluster %s
Description:The cznetd daemon was attempting to unregister configuration callbacks when no such callback was registered.
Solution:These callbacks are used for enabling or disabling the private IP communication for zone cluster zones. So, this feature will be unavailable. To recover, it might be necessary to reboot this node or the entire cluster. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
824550 clcomm: Invalid flow control parameters
Description:The flow control policy is controlled by a set of parameters. These parameters do not satisfy guidelines. Another message from validay_policy will have already identified the specific problem.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
824645 Error reading line from hadbm command: %s.
Description:An error was encountered while reading the output from the specified hadbm command.
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.
824975 scf_entry_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.
825120 CMM: Quorum device %d (gdevname %s) can not be acquired by the current cluster members. This quorum device is held by node%s %s.
Description:This node does not have its reservation key on the specified quorum device, which has been reserved by the specified node or nodes that the local node can not communicate with. This indicates that in the last incarnation of the cluster, the other nodes were members whereas the local node was not, indicating that the CCR on the local node may be out-of-date. In order to ensure that this node has the latest cluster configuration information, it must be able to communicate with at least one other node that was a member of the previous cluster incarnation. These nodes holding the specified quorum device may either be down or there may be up but the interconnect between them and this node may be broken.
Solution:If the nodes holding the specified quorum devices are up, then fix the interconnect between them and this node so that communication between them is restored. If the nodes are indeed down, boot one of them.
825232 repl_check fatal error - clconf_lib_init() error
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.
825267 clq_scsi3: Ioctl MHIOCGRP_RESERVE returned success but the reservation key was not found on quorum device %s
Description:An error was encountered while trying to place node's reservation key on specified quorum device. This error occurs because of unexpected behavior from device driver or multipathing driver or device's firmware.
Solution:Please look for updates in device driver, multipathing driver or device firmware. If no updates are available please contact Sun device driver support team.
825274 idl_scha_control_checkall(): IDL Exception on node <%d>
Description:During a failover attempt, the scha_control function was unable to check the health of the indicated node, because of an error in internode communication. This was probably caused by the death of the indicated node during scha_control execution. The RGM will still attempt to master the resource group on another node, if available.
Solution:No user action is required; the rgmd should recover automatically. Identify what caused the node to die by examining syslog output. The syslog output might indicate further remedial actions.
825347 Telemetry data service start method returned with error %s
Description:The telemetry data service could not start for an unknown reason.
Solution:This message is informational; no user action needed.
826050 Failed to retrieve the cluster property %s for %s: %s.
Description:The query for a property 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.
826353 Unable to open /dev/console: %s
Description:While starting up, one of the rgmd daemons was not able to open /dev/console. The message contains the system error. This will prevent the daemon from starting on this node.
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.
826614 Filer component of property %s can't start with a "/"
Description:The value of the property TargetFileSystem starts with a slash (/). For an NFS file system that is exported from a NAS device, the value of the property TargetFileSystem must begin with the NAS device name. A NAS device name must not start with a slash (/).
Solution:Correct the value of the property and repeat the operation.
826674 clexecd: Exiting as error '%s' occurred while receiving control fd from parent. Parent could be dead.
Description:Parent process in the clexecd program is dead.
Solution:If the node is shutting down, ignore the message. If not, the node on which this message is seen, will shutdown to prevent to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
826747 reservation error(%s) - do_scsi3_inkeys() 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.
826800 Error in processing file %s
Description:Unexpected error found while processing the specified file.
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.
826917 cl_execd: Attempt to set scheduling class to Time shared returned %d. Exiting.
Description:cl_execd program failed to set the priority and the scheduling class to Time shared for the task in execution.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
826952 Failed to initialize ZFS library
Description:HAStoragePlus failed to initialize the libzfs library.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
827525 reservation message(%s) - Fencing other node from disk %s
Description:The device fencing program is taking access to the specified device away from a non-cluster node.
Solution:This is an informational message, no user action is needed.
827766 Not a cluster member.
Description:The node is not a cluster member.
Solution:Check if the command was run when the node was out of cluster. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
828140 Starting %s.
Description:Sun Cluster is starting the specified application.
Solution:This is an informational message, no user action is needed.
828170 CCR: Unrecoverable failure while updating table %s.
Description:CCR encountered an unrecoverable error while updating the indicated table on this node.
Solution:The node needs to be rebooted. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.
828171 stat of file %s failed.
Description:Status of the named file could not be obtained.
Solution:Check the permissions of the file and all components in the path prefix.
828283 clconf: No memory to read quorum configuration table
Description:Could not allocate memory while converting the quorum configuration information into quorum table.
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.
828407 WARNING: lkcm_sync failed: unknown message type %d
Description:An message of unknown type was sent to udlm. This will be ignored.
Solution:No user action is required.
828474 resource group %s property changed.
Description:This is a notification from the rgmd that the operator has edited a property of a resource group. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
828615 Failed to retrieve the resource group handle of %s: %s.
Description:An error occurred while the handle for the resource group was being retrieved.
Solution:Investigate possible RGM errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
828661 Error was detected in previous reconfiguration: "%s"
Description:Error was detected during previous reconfiguration of the RAC framework component. Error is indicated in the message. As a result of error, the ucmmd daemon was stopped and node was rebooted. On node reboot, the ucmmd daemon was not started on the node to allow investigation of the problem. RAC framework is not running on this node. Oracle parallel server/ Real Application Clusters database instances will not be able to start on this node.
Solution:Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Resolve the problem that resulted in reconfiguration error. Reboot the node to start RAC framework on the node. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters. If problem persists, contact your Sun service representative.
828716 Replication is enabled in enqueue server, but the replica server is not running. See %s/ensmon%s.out.%s for output.
Description:Replication is configured to be enabled. However, the SAP replica server is not running on the cluster. The output file listed in the warning message shows the complete output from the SAP command 'ensmon'.
Solution:This is an informational message, no user action is needed. The data service for SAP replica server is responsible for making the replica server highly available.
828739 transition '%s' timed out for cluster, forcing reconfiguration.
Description:Step transition failed. A reconfiguration will be initiated.
Solution: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.
829132 scha_control GIVEOVER failed. error %s
Description:Fault monitor had detected problems in RDBMS server. Attempt to switchover resource to another node failed. Error returned by API call scha_control is indicated in the message.
Solution:No user action is required.
829384 INTERNAL ERROR: launch_method: state machine attempted to launch invalid method <%s> (method <%d>) for resource <%s>; aborting node
Description:An internal error occurred when the rgmd attempted to launch an invalid method for the named resource. The rgmd will produce a core file and will force the node to halt or reboot.
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.
829528 XDR Error while decoding arguments.
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.
830211 Failed to accept connection on socket: %s.
Description:While determining the health of the data service, fault monitor is failed to communicate with the process monitor facility.
Solution:This is internal error. Save /var/adm/messages file and contact your authorized Sun service provider. For more details about error, check the syslog messages.
830709 Error: unable to retrieve zone state change event registration symbol: zones functionality will not work correctly on this node
Description:The sc_zonesd is unable to retrieve zone state change event registration symbol: zones functionality will not work correctly on this node.
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.
831031 File system check of %s (%s) successful.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
831036 Service object [%s, %s, %d] created in group '%s'
Description:A specific service known by its unique name SAP (service access point), the three-tuple, has been created in the designated group.
Solution:This is an informational message, no user action is needed.
831072 Issuing a resource restart request because of probe failures.
Description:This message indicates that the fault monitor is about to request a resource restart because of probe failures. If the request fails, refer to the syslog messages that appear after this message.
Solution:This is an informational message; no user action is required.
831483 CCR: Create cluster %s failed.
Description:The CCR failed to create the indicated cluster.
Solution:The failure can happen due to many reasons, for some of which no user action is required because the CCR client in that case will handle the failure. The cases for which user action is required depends on other messages from CCR on the node, and include: If it failed because the cluster lost quorum, reboot the cluster. 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 cluster repository is corrupted as indicated by other CCR messages, then boot the offending node(s) in -x mode to restore the cluster repository backup. The cluster repository is located at /etc/cluster/ccr/.
832007 Current node is hosting MDSResource %s.
Description:The current node is hosting the metadata server resource that represents the specified shared QFS file system. This message is an informational message.
Solution:No user action is required.
832278 Error: Unable to create scha_control timestamp file <%s> for resource <%s> node <%s>
Description:The rgmd has failed in an attempt to create a file used for the anti-"pingpong" feature. This may prevent the anti-pingpong feature from working, which may permit a resource group to fail over repeatedly between two or more nodes. The failure to create the file might indicate a more serious problem on the 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.
832380 All Informix non-attached IPC shared memory segments removed
Description:All the Informix shared memory segments that were not being used have been removed.
Solution:No user action is required. Informational message.
832830 CMM: Open failed for quorum device %s with error %d.
Description:The open operation on the specified quorum device failed, and this node will mark the quorum device as inaccessible for now.
Solution:The quorum device has failed or the path to this device may be broken. Refer to the quorum disk repair section of the administration guide for resolving this problem.
833045 dl_info: bad ACK header %u
Description:An unexpected error occurred. The acknowledgment header for the info request (to bind to the physical device) is bad. We are trying to open a fast path to the private transport adapters.
Solution:Reboot of the node might fix the problem.
833126 Monitor server successfully started.
Description:The Sybase Monitor server has been successfully started by Sun Cluster HA for Sybase.
Solution:This is an information message, no user action is needed.
833212 Attempting to start the data service under process monitor facility.
Description:The function is going to request the PMF to start the data service. If the request fails, refer to the syslog messages that appear after this message.
Solution:This is an informational message, no user action is required.
833229 Couldn't remove deleted directory file, '%s' error: (%d)
Description:The file system is unable to create temporary copies of deleted files.
Solution:Mount the affected file system as a local file system, and ensure that there is no file system entry with name "._" at the root level of that file system. Alternatively, run fsck on the device to ensure that the file system is not corrupt.
833261 munmap failure: %s
Description:The libclcontract code was not able to delete shared memory for a semaphore, possibly due to low memory, and the system error is shown. This is part of the cleanup after a client call, so the operation might have gone through. An error message is output to syslog.
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.
833557 dl_attach: DL_OK_ACK rtnd prim %u
Description:Wrong primitive returned to the DL_ATTACH_REQ.
Solution:Reboot the node. If the problem persists, check the documentation for the private interconnect.
833970 clcomm: getrlimit(RLIMIT_NOFILE): %s
Description:During cluster initialization within this user process, the getrlimit call failed with the specified error.
Solution:Read the man page for getrlimit for a more detailed description of the error.
834457 CMM: Resetting quorum device %s failed.
Description:When a node connected to a quorum device goes down, the surviving node tries to reset the quorum device. The reset can have different effects on different device types.
Solution:Check to see if the device identified above is accessible from the node the message was seen on. If it is accessible, then contact your authorized Sun service provider to determine whether a workaround or patch is available.
834530 Failed to parse xml: invalid element %s
Description:The cl_apid was unable to parse an xml message because of an invalid attribute. This message probably represents a CRNP client error.
Solution:No user action is required.
834544 Unable to read from device %s. %s
Description:The device could not be read from.
Solution:Run the command metaset to determine if the metaset is online on the node. Run metastat to determine the state of the volume.
834589 Error while executing scsblconfig.
Description:There was an error while attempting to execute (source) the specified file. This may be due to improper permissions, or improper settings in this file.
Solution:Please verify that the file has correct permissions. If permissions are correct, verify all the settings in this file. Try to manually source this file in korn shell (". scsblconfig"), and correct any errors.
834749 Validate - sge_qmaster file does not exist or is not executable at %s/sge_qmaster
Description:The file sge_qmaster cannot be found, or is not executable.
Solution:Confirm the file ${SGE_ROOT}/bin/<arch>/sge_qmaster both exists at that location, and is executable.
834829 clcomm: failed to create thread for resource_thread
Description:The system could not create the needed thread, because there is inadequate memory.
Solution:There are two possible solutions. Install more memory. Alternatively, reduce memory usage. Since this happens during system startup, application memory usage is normally not a factor.
834841 Validate - myisamchk %s nonexistent or nonexecutable
Description:The mysqladmin command does not exist or is not executable.
Solution:Make sure that MySQL is installed correctly or right base directory is defined.
834904 fork1 failed, errno = %d. Exiting.
Description:The rtreg server program has encountered failure of fork1(2) system call. The error message contains the error number for the failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
835739 validate: Host is not set but it is required
Description:-2 The host variable is not set in the parameter file.
Solution:-2 Set the host variable to the logical hostname in the parameter file.
836692 CCR: Could not remove the CCR tables for cluster %s errno = %d.
Description:The error occurred while removing the CCR tables for a removed cluster on this node. The errno value indicates the nature of the problem.
Solution:There may be other related messages on this node, which may help diagnose the problem. The tables have to be manually removed outside of CCR control. Contact your authorized Sun service provider for assistance.
836825 validate: TestCmd is not set but it is required
Description:-2 The variable TesCmd is not set in the parameter file.
Solution:-2 Set the test command in the parameter file. you may try "get /index.jsp"
836985 Probe for dispatcher returned %d
Description:The data service received the displayed return code from the dpmon command.
Solution:Informational message. No user action is needed.
837169 Starting listener %s.
Description:Informational message. HA-Oracle will be starting Oracle listener.
Solution:No user action is required.
837211 Resource is already online.
Description:While attempting to restart the resource, an error has occurred. The resource is already online.
Solution:This is an internal error. Save the /var/adm/messages file from all the nodes. Contact your authorized Sun service provider.
837223 NFS daemon %s died. Will restart in 100 milliseconds.
Description:While attempting to start the specified NFS daemon, the daemon started up, however it exited before it could complete its network configuration.
Solution:This is an informational message. No user action is required. HA-NFS would attempt to correct the problem by restarting the daemon again. HA-NFS imposes a delay of milliseconds between restart attempts.
837346 UNRECOVERABLE ERROR: Execution of %s failed with error code %s
Description:Execution of ${QL_UPGRADE_PARTITION} failed with error code ${retval}
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
837595 Error: unknown error code
Description:The cl_apid encountered an internal error.
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.
837704 scnetapp fatal error - Cannot resolve ccr_directory
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
837752 Failed to retrieve the resource group handle for %s while querying for property %s: %s.
Description:Access to the object named 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.
837760 monitored processes forked failed (errno=%d)
Description:The rpc.pmfd server was not able to start (fork) the application. This problem can occur if the machine has low memory. The system error number is shown, and an error message is output to syslog.
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.
838032 %s: Couldn't run method tag. Error in %s: %s.
Description:The rpc.fed server was not able to run the method with the tag specified. The cause of the error is specified by the exact error message.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
838270 HA: exception %s (major=%d) from process_to().
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.
838570 Failed to unmount %s: (%d) %s.
Description:HAStoragePlus was not able to unmount the specified file system. The return code and output of the umount command is also embedded in the message.
Solution:Check the system configuration. If the problem persists, contact your authorized Sun service provider.
838688 validate: Startwait is not set but it is required
Description:-2 The variable StartWait is not set in the parameter file.
Solution:-2 Set the variable StartWait in the parameter file.
838695 Unable to process client registration
Description:The cl_apid experienced an internal error (probably a memory error) that prevented it from processing a client registration request.
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.
838811 INTERNAL ERROR: error occurred while launching command <%s>
Description:The data service detected an internal error from SCDS.
Solution:Informational message. No user action is needed.
838960 Switchover of RG %s failed: %s
Description:The resource group that contains the metadata server resource could not be switched over to any other node in the resource group's node list. One possible cause of this error is that all nodes in the node list are being reconfigured.
Solution:When possible, manually switch over the resource group to a node in the node list of the resource group. After switching over the resource group, manually unmount the file system.
839031 Method <%s> on resource <%s> node <%s>: Execution failed: no such method tag.
Description:An internal error has occurred in the rpc.fed daemon which prevents method execution. This is considered a method failure. 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, or it might cause an attempted edit of a resource group or its resources to fail.
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 the problem. Retry the edit operation.
839641 t_alloc (reqp): %s
Description:Call to t_alloc() failed. The "t_alloc" man page describes possible error codes. udlm will exit and the node will abort.
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.
839649 t_alloc (resp): %s
Description:Call to t_alloc() failed. The "t_alloc" man page describes possible error codes. udlm will exit and the node will abort.
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.
839744 UNRECOVERABLE ERROR: Sun Cluster boot: clexecd not started
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
839881 Media error encountered, but Auto_end_bkp failed.
Description:The HA-Oracle start method identified that one or more data files is in need of recovery. This was caused by the file(s) being left in hot backup mode. The Auto_end_bkp extension property is enabled, but failed to recover the database.
Solution:Examine the log files for the cause of the failure to recover the database.
839936 Some ip addresses may not be plumbed.
Description:Some of the ip addresses managed by the LogicalHostname resource were not successfully brought online on this node.
Solution:Use ifconfig command to make sure that the ip addresses are indeed absent. Check for any error message before this error message for a more precise reason for this error. Use clresourcegroup to move the resource group to some other node.
839983 Ignoring the line %d of file %s as it exceeds %s characters.
Description:The number of characters in specified file has exceeded and hence ignoring the line.
Solution:Rectify the line if it contains tunable variable.
840542 OFF_PENDING_BOOT: bad resource state <%s> (%d) for resource <%s>
Description:The rgmd state machine has discovered a resource in an unexpected state on the local node. 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.
840619 Invalid value was returned for resource group property %s for %s.
Description:The value returned for the named property was not valid.
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.
840696 DNS database directory %s is not readable: %s
Description:The DNS database directory is not readable. This may be due to the directory not existing or the permissions not being set properly.
Solution:Make sure the directory exists and has read permission set appropriately. Look at the prior syslog messages for any specific problems and correct them.
840725 %s: sig2str(3C) failed for signal %d
Description:The pmmd daemon was unable to get the signal name for a signal number because the sig2str(3C) function failed. The pmmd daemon will not do the requested action.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
841104 Could not set gid to '%d': %s
Description:The program failed to change the group ID to the specified value. The reason for the failure is also specified in the above message.
Solution:Please verify that the specified group ID is valid. For Oracle, the specified group ID is obtained from the owner of the file $ORACLE_HOME/bin/oracle.
841616 CMM: This node has been preempted from quorum device %s.
Description:This node's reservation key was on the specified quorum device, but is no longer present, implying that this node has been preempted by another cluster partition. 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 quorum was lost. Determine why quorum was lost on this node, resolve the problem and reboot this node.
841858 popen failed on sharectl: %s.Will attempt to read config from %s file.
Description:The popen failed while getting NFS parameters using "sharectl".
Solution:This is a warning message. An attempt will be made to read the properties directly from the file. Examine syslog messages to determine the cause of failure. Take corrective action based on any related messages. If the problem persists, report it to your Sun support representative for further assistance.
841899 Error parsing stopstate file at line %d: %s.
Description:An error was encountered on the specified line while parsing the stopstate file.
Solution:Examine the stopstate file to determine if it is corrupted. Also examine other syslog messages occurring around the same time on the same node, to see if the source of the problem can be identified.
842059 Cannot create monitor child process. fork failed with %m
Description:Fault monitor is not able to create child process. Fault monitor will be restarted. If problem persists, fault monitor will be stopped.
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.
842084 thr_sigsetmask returned %d. Exiting.
Description:The rtreg server program has encountered a failed thr_sigsetmask(3C) 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.
842313 clexecd: Sending fd on common channel returned %d. Exiting.
Description:The clexecd program has encountered a failed fcntl(2) system call. The error message indicates the error number for the failure.
Solution:The node will halt or reboot itself to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
842382 fcntl: %s
Description:A server (rpc.pmfd or rpc.fed) was not able to execute the action shown, and the process associated with the tag is not started. The error message is shown.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
842386 WebSphere MQ Listener for port %s restarted.
Description:The specified WebSphere MQ Listener has been restarted.
Solution:No user action is required. Informational message.
842514 Failed to obtain the status of global service %s associated with path %s: %s.
Description:The DCS was not able to obtain the status of the specified global service.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
842712 clcomm: solaris xdoor door_create failed
Description:A door_create operation failed. Refer to the "door_create" man page for more information.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
842823 %s exception occurred during execution of %s on node %d
Description:An exception occurred while a remote command is being executed.
Solution:Check the message to determine what might be wrong. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
842893 The stop command "%s" failed to stop %s. Using SIGKILL.
Description:The specified stop command was unable to stop the specified resource. A SIGKILL signal will be sent to all the processes associated with the resource.
Solution:No user action is required. This is an informational message.
842993 scf_pg_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.
843013 Data service failed to stay up. Start method failed.
Description:The data service may have failed to startup completely.
Solution:Look in /var/adm/messages for the cause of failure. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
843070 Failed to disconnect from port %d of resource %s.
Description:An error occurred while fault monitor attempted to disconnect from the specified hostname and port.
Solution:Wait for the fault monitor to correct this by doing restart or failover. For more error descriptions, look at the syslog messages.
843127 Extension properties %s and %s and %s are empty.
Description:HAStoragePlus detected that no devices, file systems or zpools are to be managed.
Solution:This is an informational message, no user action is needed.
843876 Media error encountered, and Auto_end_bkp was successful.
Description:The HA-Oracle start method identified that one or more data files was in need of recovery. This was caused by the file(s) being left in hot backup mode. The Auto_end_bkp extension property is enabled, and successfully recovered and opened the database.
Solution:No user action is required. This is an informational message. Oracle server is online.
843983 CMM: Node %s: attempting to join cluster.
Description:The specified node is attempting to become a member of the cluster.
Solution:This is an informational message, no user action is needed.
844812 check_for_ccrdata failed strdup for (%s)
Description:Call to strdup failed. The "strdup" man page describes possible reasons.
Solution:Install more memory, increase swap space or reduce peak memory consumption.
844900 The hostname in %s is not a network address resource in this resource group.
Description:The resource group does not contain a network address resource with the hostname contained in the indicated URI.
Solution:Check that the resource group contains a network resource with a hostname that corresponds with the hostname in the URI.
845305 DNS not already running
Description:The DNS service is not running.
Solution:No user action is required.
845358 Failed to add resource group '%s' to the MDS resource group list.
Description:The zone boot handler failed to generate the list resource groups containing SUNW.qfs resources.
Solution:Investigate the zone boot log messages and try to rectify the problem. If problem persists after rebooting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
845431 Aborting fault monitor child process %d. Check for the core file in the / directory. If not present, enable setid core dumps with coreadm.
Description:This message indicates that fault monitor timed out and would be aborted. If core dumps are enabled, a core file is dumped in the / directory for diagnostics. The process ID of the aborted process is listed in the message.
Solution:Determine whether the timeout of the fault monitor occurred due to some abnormal event. If the timeout occurred due to normal and expected system load, consider increasing the Probe_timeout and the Start_timeout for the resource.
845504 door_call: %s
Description:The door_call failed with the specified reason. The libsczones was unable to register with the sc_zonesd for zone state change callbacks.
Solution:Search for messages from sc_zonesd to determine the source of the error. Save a copy of the /var/adm/messages files on all nodes. If the problem persists, contact your authorized Sun service provider for assistance in diagnosing the problem.
845525 Encountered an exception during unblock invocation
Description:The upgrade process on the root node resumes the upgrade process on each node after nodes in the second partition are shut down. If this fails, the upgrade process on each node might be hung or receive an exception on a blocked invocation.
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.
845866 Failover attempt failed: %s.
Description:The failover attempt of the resource is rejected or encountered an error.
Solution:For more detailed error message, check the syslog messages. Check whether the Pingpong_interval has appropriate value. If not, adjust it by using clresourcegroup. Otherwise, use clresourcegroup switch to switch the resource group to a healthy node.
846376 fatal: Got error <%d> trying to read CCR when making resource group <%s> unmanaged; aborting node
Description:Rgmd failed to read updated resource 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.
846420 CMM: Nodes %ld and %ld are disconnected from each other; node %ld will abort using %s rule.
Description:Due to a connection failure between the two specified non-local nodes, one of the nodes 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.
846813 Switchover (%s) error (%d) converting to primary
Description:The file system specified in the message could not be hosted on the node the message came from.
Solution:Check /var/adm/messages to make sure there were no device errors. If not, contact your authorized Sun service provider to determine whether a workaround or patch is available.
847065 Failed to start listener %s.
Description:Failed to start Oracle listener.
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.
847124 getnetconfigent: %s
Description:The call to getnetconfigent in udlm port setup failed.udlm fails to start and the node will eventually 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.
847496 CMM: Reading reservation keys from quorum device %s failed with error %d.
Description:An error was encountered while trying to read reservation keys on the specified quorum device.
Solution:There may be other related messages on this and other nodes connected to this quorum device that may indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.
847656 Command %s is not executable.
Description:The specified pathname, which was passed to a libdsdev routine such as scds_timerun or scds_pmf_start, does not refer to an executable file. This could be the result of 1) misconfiguring the name of a START or MONITOR_START method or other property, 2) a programming error made by the resource type developer, or 3) a problem with the specified pathname in the file system itself.
Solution:Ensure that the pathname refers to a regular, executable file.
847916 (%s) netdir error: uaddr2taddr: %s
Description:Call to uaddr2taddr() failed. The "uaddr2taddr" man page describes possible error codes. udlmctl will exit.
Solution: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.
847949 Validate_replication_rs - MySQL resource group %s does not exist
Description:The defined real MySQL resource group (-g option) does not exist.
Solution:Make sure that defined resource group exists.
847978 reservation fatal error(UNKNOWN) - cluster_get_quorum_status() error, returned %d
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.
847994 Plumb failed. Tried to unplumb %s%d, unplumb failed with rc %d
Description:Topology Manager failed to plumb an adapter for private network. A possible reason for plumb to fail is that it is already plumbed. Solaris Clustering tries to unplumb the adapter and plumb it for private use but it could not unplumb the adapter.
Solution:Check if the adapter by that name exists.
848024 XDR Error while encoding arguments.
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. This zone will not be able to host applications.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
848033 SharedAddress online.
Description:The status of the sharedaddress resource is online.
Solution:This is informational message. No user action required.
848057 Validation succeeded.
Description:Validation of this ScalMountPoint resource succeeded. This message is an informational message.
Solution:No user action is required.
848288 The command '%s' to find MDS of '%s' file system failed : %s.
Description:The zone boot handler failed to determine the MDS node of a file system.
Solution:Try running the command manually and see the execution status. If the command execution succeeds contact your Sun service provider to determine whether a workaround or patch is available. In case the execution fails investigate the failure and reboot the zone after rectifying the problem.
848580 Restarting on signal %d.
Description:The cl_eventlogd daemon has received a SIGHUP signal, which indicates that it must reconfigure.
Solution:This message is informational only, and does not require user action.
848652 CMM aborting.
Description:The node is going down due to a decision by the cluster membership monitor.
Solution:This message is preceded by other messages indicating the specific cause of the abort, and the documentation for these preceding messages will explain what action should be taken. The node should be rebooted if node failure is unexpected.
848854 Failed to retrieve WLS extension properties.
Description:The WLS Extension properties could not be retrieved.
Solution:Check for other messages in syslog and /var/adm/messages for details of failure.
848943 clconf: No valid gdevname field for quorum device %d
Description:Found the gdevname field for the quorum device being incorrect while converting the quorum configuration information into quorum table.
Solution:Check the quorum configuration information.
848988 libsecurity: NULL RPC to program %s (%lu) failed; will retry %s
Description:A client of the specified server was not able to initiate an rpc connection, because it could not execute a test rpc call, and the program will retry to establish the connection. The message shows the specific rpc error. The program number is shown. To find out what program corresponds to this number, use the rpcinfo command. 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.
849138 Validate method for resource %s completed successfully.
Description:HA-KDC's validate method has successfully completed.
Solution:This is for informational purposes only, no action is required.
849445 Stopping Oracle CRS nodeapps using: "%s".
Description:This is to show the command that the CRS Framework used to stop Oracle CRS nodeapps in the event that Oracle CRS does not stop.
Solution:No user action is required.
849793 Lookup of QL object failed
Description:Cluster upgrade is in progress but lookup of QL object failed. This can happen if the node hosting the name-server registry goes down or if an earlier attempt to register the upgrade object fails.
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.
850108 Validation failed. PARAMETER_FILE: %s does not exist
Description:Oracle parameter file (typically init<sid>.ora) specified in property 'Parameter_file' does not exist or is not readable.
Solution:Please make sure that 'Parameter_file' property is set to the existing Oracle parameter file. Reissue command to create/update
850140 Unable to create server thread for failfast: rebooting zone %s with zone ID %d
Description:A server thread that is needed for failfast to work properly could not be created. This might be due to lack of memory.
Solution:This is an informational message, no user action is needed.
850260 <%s> project <%s> user <%s> inproj() ret %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.
850298 Validation of global zone %s entry for filesystem mount point %s is failed.
Description:HAStoragePlus failed while validating the global zone vfstab entry for the specified mountpoint.
Solution:Usually, this happens due to incorrect entries in vfstab. Check the log messages for specified error and repeat the operation.
850474 reservation warning(%s) - MHIOCRELEASE 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.
850580 Desired_primaries must equal Maximum_primaries.
Description:The resource group properties desired_primaries and maximum_primaries must be equal.
Solution:Set the desired and maximum primaries to be equal.
850743 Start of HADB database failed with exit code %d.
Description:The resource encountered an error trying to start the HADB database.
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.
851225 Domain Admin Server resource needs a restart by an admin. The Agent probe will not take any action.
Description:Domain Admin Server resource requires a restart by cluster admin. DAS agent probe will not take any action.
Solution:Restart the Domain Admin Server resource.
851292 Error: ${SERVER} is running but not accessible.
Description:The initpmf init script was unable to verify the availability of the rpc.pmfd server, even though it successfully started. This error may prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.
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.
852212 reservation message(%s) - Taking ownership of disk %s away from non-cluster node
Description:The device fencing program is taking access to the specified device away from a non-cluster node.
Solution:This is an informational message, no user action is needed.
852615 reservation error(%s) - Unable to gain access to device '%s'
Description:The device fencing program has encountered errors while trying to access a device.
Solution:Another cluster node has fenced this node from the specified device, preventing this node from accessing that device. Access should have been reacquired when this node joined the cluster, but this must have experienced problems. If the message specifies the 'node_join' transition, this node will be unable to access the specified device. If the failure occurred during the 'make_primary' transition, then this will be unable to access the specified device and a device group that contains the specified device might have failed to start on this node. An attempt can be made to acquire access to the device by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on this node. If a device group failed to start on this node, the cldevicegroup command can be used to start the device group on this node if access can be reacquired. If the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
852664 clcomm: failed to load driver module %s - %s paths will not come up.
Description:Sun Cluster was not able to load the said network driver module. Any private interconnect paths that use an adapter of the corresponding type will not be able to come up. If all private interconnect adapters on this node are of this type, the node will not be able to join the cluster at all.
Solution:Install the appropriate network driver on this node. If the node could not join the cluster, boot the node in the non cluster mode and then install the driver. Reboot the node after the driver has been installed.
852822 Error retrieving configuration information.
Description:An error was encountered while running hadbm status.
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. Try running the hadbm status command manually for the HADB database.
853225 Method <%s> on resource <%s>, node <%s>: unknown command.
Description:An internal logic error in the rgmd has prevented it from successfully executing a resource method.
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.
853478 Received non interrupt heartbeat on %s - path timeouts are likely.
Description:Solaris Clustering requires network drivers to deliver heartbeat messages in the interrupt context. A heartbeat message has unexpectedly arrived in non interrupt context.
Solution:Check if the right version of the driver is in use.
853822 INTERNAL ERROR: zone_enter() failed for zoneid %d : %s
Description:An internal error occurred when the system attempted to execute the method inside the specified zone.
Solution:Save a copy of the /var/adm/messages on all nodes and contact your authorized Sun service provider for assistance in diagnosing the problem.
853956 INTERNAL ERROR: WLS extension properties structure is NULL.
Description:This is an internal Error.
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.
854255 Completed checking the SUNW.qfs resources status configured for this zone cluster.
Description:This is a notification message that the checking for the SUNW.qfs resources is completed.
Solution:This is an informational message; no user action is needed.
854390 Resource state of %s is changed to offline. Note that RAC framework will not be stopped by STOP method.
Description:The stop method of the resource was called by the resourcegroup manager. The stop method is called in the following conditions: - Disabling a resource - Changing state of the resource group to offline on a node - Shutdown of cluster If RAC framework was running prior to calling the stop method, it will continue to run even if resource state is changed to offline.
Solution:If you want to stop the RAC framework on the node, you may need to reboot the node.
854468 failfast arm error: %d
Description:Error during failfast device arm operation.
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.
854595 Diskgroup (%s) does not have any volumes.
Description:The diskgroup does not have any volumes.
Solution:Create volumes on the device group.
854645 Invalid value for property %s, it does not start with a leading "/"
Description:The property MountPointDir does not specify the absolute path to the mount-point directory. An absolute path must start with a slash (/).
Solution:Correct the value of the property and repeat the operation.
854792 clcomm: error in copyin for cl_change_threads_min
Description:The system failed a copy operation supporting a flow control state change.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
854894 No LogicalHostname resource in resource group.
Description:The probe method for this data service could not find a LogicalHostname resource in the same resource group as the data service.
Solution:Use scrgadm to configure the resource group to hold both the data service and the LogicalHostname.
855060 Resource group %s is undergoing reconfiguration, will check again in %ds
Description:The named resource group, or some other part of the cluster is undergoing reconfiguration. Due to this, a request to migrate this resource group or to rebalance it did not work. The utility will recheck the state of the resource group after the time duration specified in the message.
Solution:This is an informational message, no user action is needed.
855306 Required package %s is not installed on this node.
Description:Incomplete installation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters. RAC framework will not function correctly on this node due to incomplete installation.
Solution:Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.
855423 scslm_init error.
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
855761 %s usage error : %s
Description:An internal error has occurred.
Solution:Contact your Sun service representative for assistance in diagnosing and correcting the problem.
855877 There are no services of class %s.
Description:There are no registered DCS services.
Solution:No user action is required.
855907 cm_getcluststate() failed
Description:An error prevented the state of the UCMM from being retrieved.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
855946 Config file: %s error line %d
Description:An error occurs in the scdpmd config file (/etc/cluster/scdpm/scdpmd.conf) has failed.
Solution:Fix the config file.
856360 QUORUM_GENERIC: quorum_read_keys error: Reading the registration keys failed on quorum device %s with error %d.
Description:An error was encountered when reading a node's registration key on a specified quorum device. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
856492 waitpid() failed: %m.
Description:The waitpid() system call failed for the given reason.
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.
856800 cl_execd: getrlimit returned %d
Description:The cl_execd program has encountered a failed getrlimit(2) system call. The error message indicates the error number of failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
856859 Beginning cluster upgrade
Description:The upgrade procedure has begun.
Solution:This is an informational message, no user action is needed.
856919 INTERNAL ERROR: process_resource: resource group <%s> is pending_methods but contains resource <%s> in STOP_FAILED state
Description:During a resource creation, deletion, or update, the rgmd has discovered a resource in STOP_FAILED state. This may indicate an internal logic error in the rgmd, since updates are not permitted on the resource group until the STOP_FAILED error condition is cleared.
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.
857088 Failed to open file %s: %s.
Description:Unable to open sharetab file.
Solution:No user action required.
857620 Resource "%s" could not be disabled: %s, will retry.
Description:The scha_control() call to disable this ScalMountPoint resource failed, will retry disabling.
Solution:No user action is required.
857792 UNIX DLM initiating cluster abort.
Description:Due to an error encountered, UNIX dlm is initiating an abort.
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.
858256 Stopping %s with command %s.
Description:Sun Cluster is stopping the specified application with the specified command.
Solution:This is an informational message, no user action is needed.
858364 Function: validate: Directory for log file %s does not exist, an existing directory is required
Description:The path to the filename variable PGLOGFILE does not exist.
Solution:Qualify the filename of the parameter files PGLOGFILE variable in an existing directory.
859377 at or near: %s
Description:Indicates the location where (or near which) the error was detected.
Solution:Please ensure that the entry at the specified location is valid and follows the correct syntax. After the file is corrected, validate it again to verify the syntax.
859607 Reachable nodes are %llx
Description:The cl_eventd has references to the specified nodes.
Solution:This message is informational only, and does not require user action.
859614 Failed to register configuration callbacks
Description:The scprivipd daemon was unable to register for configuration callbacks.
Solution:These callbacks are used only for enabling or disabling the private IP communication for local zones. So, this feature will be unavailable. To recover, it may be necessary to reboot this node or the entire cluster. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
859686 Error: rpc.pmfd is not running.
Description:The initfed init script found that the rpc.pmfd is not running. The rpc.fed will not be started, which will prevent the rgmd from starting, and which will prevent this node from participating as a full member of the cluster.
Solution:Examine other syslog messages occurring at about the same time to determine why the rpc.pmfd is not running. 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.
859783 Function: validate: Return code for failed connections %s is greater 100
Description:The value of the NOCONRET variable in the parameter file exceeds 100.
Solution:Fix the parameter file with a value below 100.
860514 sc_zonesd couldn't service the request.
Description:The sc_zonesd in the global zone was unable to service the request. This zone will not be able to host applications.
Solution:Verify that the system is not running on low memory. Save a copy of the /var/adm/messages file on the node. Contact your authorized Sun service provider for assistance in diagnosing the problem.
860640 Function: validate - Zonepath %s needs to be a directory
Description:The zone path extracted from the zones configuration is not present or not a directory.
Solution:Make sure that the filesystem for the zone path is mounted. Consider using a SUNW.HAStoragePlus resource. If already used, check if the resource dependency to it is in place.
861044 Failed to retrieve the resource handle of %s: %s.
Description:An error occurred while the handle for the resource was being retrieved.
Solution:Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
861134 Initialization failed. Invalid command line %s %s
Description:Unable to process parameters passed to the call back method. This is an internal error.
Solution:Please report this problem.
861260 statvfs failed on the mount point %s : %s
Description:The file system specified on the mount point is not available.
Solution:Check the statvfs(2) man page for errors and try to resolve the problem. Otherwise contact your authorized Sun service provider.
861489 Validate - %s/etc/%s does not contain %s
Description:${INFORMIXDIR}/etc/${ONCONFIG} does not contain ${INFORMIXSERVER}.
Solution:Ensure that ${INFORMIXDIR}/etc/${ONCONFIG} contains ${INFORMIXSERVER}.
861642 Function: clear_zone - Killing processes with fuser -ck on the file system %s
Description:The non-global zones shutdown command did not complete in time or zoneadm halt was not able to bring the non-global zone into state "installed". A fuser -ck is submitted against each of the zones file systems. The reported processes will be send a SIGKILL.
Solution:No user action is required.
861818 in libsecurity for program %s ; unable to register service
Description:The specified daemon was not able to start because it could not initialize a door for communication with its clients. This causes the node to be rebooted or halted.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
862414 About to mount on %s for zone cluster '%s'.
Description:HAStoragePlus will mount the file system for zone cluster on specified path name onto a specified mount point.
Solution:This is an informational message, no user action is needed.
862716 sema_init: %s
Description:The rpc.pmfd server was not able to initialize a semaphore, possibly due to low memory, and the system error is shown. The server does not perform the action requested by the client, and pmfadm returns error. An error message is also output to syslog.
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.
862999 Siebel server components maybe unavailable or offline. No action will be taken.
Description:Not all of the enabled Siebel server components are running.
Solution:This is an informative message. Fault Monitor will not take any action. Please manually start the Siebel component(s) that may have gone down to ensure complete service.
863007 URI (%s) must be an absolute http URI.
Description:The Universal Resource Identifier (URI) must be an absolute http URI. It must start http://
Solution:Specify an absolute http URI.
864151 Failed to enumerate instances for IPMP group %s
Description:There was a failure while trying to determine the instances (v4, v6 or both) that the IPMP group can host.
Solution:Contact your authorized Sun service provider.
864161 QUORUM_GENERIC: quorum_reserve error: this node's registration key was not found on the quorum device %s.
Description:When reserving the quorum device, the node's registration key was not found on the device. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
864516 SCSLM getprojidbyname <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
864715 check_stdby: The database in %s is reconfigured to run as a primary database, reload the primary and restart the standby database.
Description:The database is running as a standby database, but is currently reconfigured to run as a primary.
Solution:If you want to start the old primary database, reload the primary and restart the standby database.
865130 Probe - Fatal: %s/qconf not found or not executable
Description:The binary file qconf can not be found, or is not executable.
Solution:Confirm the binary file ${SGE_ROOT}/bin/<arch>/qconf both exists in that location, and is executable.
865183 Cannot open pipe to child process. pipe() failed with %m
Description:Fault monitor is not able to communicate to it's child process. Fault monitor will be restarted. If problem persists, fault monitor will be stopped.
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.
865292 File %s should be owned by %s.
Description:A program required the specified file to be owned by the specified user.
Solution:Use chown command to change to owner as suggested.
865635 lkcm_act: caller is not registered
Description:udlm is not currently 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.
865834 Command failed: %s/bin/dbmcli -U %s db_clear: %s. Will continue to start up SAPDB database.
Description:The cleanup SAP command failed for the reason stated in the message. The Sun Cluster software continues to try to start the SAPDB database instance.
Solution:Check the SAPDB log file for the possible cause of this failure.
865963 stop_mysql - Pid is not running, let GDS stop MySQL for %s
Description:The saved Pid didn't exist in process list.
Solution:No user action is required.
866316 cl_orb: not booted in cluster mode.
Description:Attempted to load the cl_comm module when the node was not booted as part of a cluster.
Solution:Users should not explicitly load this module.
866371 The listener %s is not running; retry_count <%s> exceeded. Attempting to switchover resource group.
Description:Listener is not running. Listener monitor has reached the restart limit specified in 'Retry_count' and 'Retry_interval' properties. Listener and the resource group will be moved to another node.
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.
866624 clcomm: validate_policy: threads_low not big enough low %d pool %d
Description:The system checks the proposed flow control policy parameters at system startup and when processing a change request. The low server thread level must not be less than twice the thread increment level for resource pools whose number threads varies dynamically.
Solution:No user action required.
867059 Could not shutdown replica for device service (%s). Some file system replicas that depend on this device service may already be shutdown. Future switchovers to this device service will not succeed unless this node is rebooted.
Description:See message.
Solution:If mounts or node reboots are on at the time this message was displayed, wait for that activity to complete, and then retry the command to shutdown the device service replica. If not, then contact your authorized Sun service provider to determine whether a workaround or patch is available.
867543 Validate_replication_rs - MySQL resource group %s is the same as the MySQL replication resource group %s
Description:The defined real MySQL resource group (-G option) must not be the same resource as the mysql replication resource group
Solution:Make sure that defined resource group names differ.
867556 check_mysql_slave - MySQL slave instance %s has the io_thread status %s and the sql_thread status %s
Description:The fault monitor has detected that the MySQL slave instance has a different status for the slaves io_thread and the sql_thread
Solution:Check MySQL log files to determine why the slaves status for the io_thread and the sql thread do not match
868064 Resource %s does not have the property DB_PORT defined
Description:The property DB_PORT is a mandatory property of the data service. Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
868245 Unable to process dbms log file.
Description:Error occurred when processing DBMS log file. As a result of this error, fault monitor could not scan errors from log file. This error can occur as a result of memory allocation problems.
Solution:This is an internal error possibly caused by shortage of memory resources. Ensure that your system has sufficient memory and if the problem persists even when sufficient free memory is available, contact your Sun support representative for help.
868277 CMM: Erstwhile online quorum device %s (qid %d) is inaccessible now.
Description:An erstwhile online quorum device has become inaccessible now. This node will mark the quorum device as inaccessible. The quorum device is considered offline now.
Solution:Check if something has gone wrong with the quorum device. The quorum device could have failed or the path to the device could have broken down. Refer to the quorum disk repair section of the administration guide for resolving this problem.
868329 scnetapp fatal error - Missing user name from table %s
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
868467 Process %s did not die in %d seconds.
Description:HA-NFS attempted to stop the specified process id but was unable to stop the process in a timely fashion. Since HA-NFS uses the SIGKILL signal to kill processes, this indicates a serious overload or kernel problem with the system.
Solution:HA-NFS would take appropriate action. If this error occurs in a STOP method, the node would be rebooted. Increase timeout on the appropriate method.
869196 Failed to get IPMP status for group %s (request failed with %d).
Description:A query to get the state of a IPMP group failed. This may cause a method failure to occur.
Solution:Make sure the network monitoring daemon (cl_pnmd) is running. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
869406 Failed to communicate with server %s port %d: %s.
Description:The data service fault monitor probe was trying to read from or write to the service specified and failed. Sun Cluster will attempt to correct the situation by either doing a restart or a failover of the data service. The problem may be due to an overloaded system or other problems, causing a timeout to occur before communications could be completed.
Solution:If this problem is due to an overloaded system, you may consider increasing the Probe_timeout property.
869698 scvxvmlg warning - found no matching volume for device node %s, removing it
Description:The program responsible for maintaining the VxVM device namespace has discovered inconsistencies between the VxVM device namespace on this node and the VxVM configuration information stored in the cluster device configuration system. If configuration changes were made recently, then this message should reflect one of the configuration changes. If no changes were made recently or if this message does not correctly reflect a change that has been made, the VxVM device namespace on this node may be in an inconsistent state. VxVM volumes may be inaccessible from this node.
Solution:If this message correctly reflects a configuration change to VxVM diskgroups then no action is required. If the change this message reflects is not correct, then the information stored in the device configuration system for each VxVM diskgroup should be examined for correctness. If the information in the device configuration system is accurate, then executing '/usr/cluster/lib/dcs/scvxvmlg' on this node should restore the device namespace. If the information stored in the device configuration system is not accurate, it must be updated by executing '/usr/cluster/bin/scconf -c -D name=diskgroup_name' for each VxVM diskgroup with inconsistent information.
870181 Failed to retrieve the resource handle for %s while querying for property %s: %s.
Description:Access to the object named 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.
870317 INTERNAL ERROR: START method is not registered for resource <%s>
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
870566 clutil: Scheduling class %s not configured
Description:An attempt to change the thread scheduling class failed, because the scheduling class was not configured.
Solution:Configure the system to support the desired thread scheduling class.
870650 %s: Cannot create closedown thread
Description:This program could not create the closedown thread.
Solution:Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.
870753 Failed to get parent directory of %s
Description:A call to dirname() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
871084 Stop of HADB database failed with exit code %d.
Description:The resource encountered an error trying to stop the HADB database.
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.
871165 Not attempting to start Resource Group <%s> on node <%s>, because the Resource Groups <%s> for which it has strong positive affinities are not online.
Description:The rgmd is enforcing the strong positive affinities of the resource groups. This behavior is normal and expected.
Solution:No user action is required. If desired, use clresourcegroup to change the resource group affinities.
871529 Validate - can't determine Qmaster Spool dir
Description:The qmaster spool directory could not be determined, using the 'QmasterSpoolDir' function.
Solution:Use the command 'qconf -sconf' to determine the value of '${qmaster_spool_dir}'. Update/correct the value if necessary using the command 'qconf -mconf'.
871642 Validation failed. Invalid command line %s %s
Description:Unable to process parameters passed to the call back method. This is an internal error.
Solution:Please report this problem.
872503 The number of supplementary groups for user id %d exceeds the limit of %d. Only the first %d groups can be set. Please correct the file %s.
Description:There is a limit to the number of supplementary groups a single user ID can belong to, and this limit has been exceeded for the specified user ID.
Solution:Correct the /etc/group file so that the Oracle user ID's supplementary group list does not exceed the limit.
872603 WebSphere MQ Listener for port %s started
Description:The specified WebSphere MQ Listener has been started.
Solution:No user action is required. Informational message.
873300 fatal: unable to check for fencing completion.
Description:The RGM was unable to detect whether or not a node that left the cluster was properly fenced. This is an unrecoverable error so the RGM will abort the node.
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.
873473 Unable to determine whether the node can safely join the cluster. Giving up after %s retries. The ucmmd daemon will not be started on this node.
Description:After retrying the operation, the RAC framework cannot determine whether the node can safely join the cluster. The node is not allowed to join the cluster now.
Solution:Wait for all reconfiguration activity to stop on existing cluster members. Then repeat the attempt to enable the node to join the cluster. If the node is still unable to join, contact your Sun service representative for assistance in diagnosing and correcting the problem.
873991 clexecd: too big cmd size %d cmd <%s>
Description:clexecd program has encountered a problem with a client requesting a too big command.
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.
874012 Command %s timed out. Will continue to start up liveCache.
Description:The listed command timed out. Will continue to start up liveCache.
Solution:Informative message. HA-liveCache will continue to start up liveCache. No immediate action is required. This could be caused by heavy system load. However, if the system load is not heavy, user should check the installation and configuration of liveCache. Make sure the same listed command can be ran manually on the system.
874133 Issuing a failover request because the application exited.
Description:This message indicates that the fault monitor is about to make a failover request because the application exited. If the request fails, refer to the syslog messages that appear after this message.
Solution:This is an informational message.
874199 Validate_sbp - The long ping timeout %s is not numeric
Description:The long ping timeout is not numeric
Solution:Make sure that the specified long ping timeout is numeric
874550 Error killing <%d>: %s
Description:An error occurred while rpc.pmfd attempted to send SIGKILL to the specified process. The reason for the failure is also given.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
874578 zc_rgm_halt for zone %s: Could not shut down all resource groups: %s
Description:The zc_rgm_halt failed to evacuate all resource groups from this zone which belongs to a zone cluster. Support for this zone cluster might not work properly.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
874681 UNRECOVERABLE ERROR: Sun Cluster boot: Could not load module $m
Description:A kernel module is missing or is corrupted.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
874790 Not attempting to start resource group <%s> on node <%s> because a Resource Group that would be forced offline due to affinities is in an error state.
Description:The rgmd is unable to bring the specified resource group online on the specified node because one or more resource groups related to it by strong affinities are in an error state.
Solution:Find the errored resource groups by using clresourcegroup status, and clear their error states by using clresourcegroup clear. If desired, use clresourcegroup to change the resource group affinities.
874879 clcomm: Path %s being deleted
Description:A communication link is being removed with another node. The interconnect might have failed or the remote node might be down.
Solution:Any interconnect failure should be resolved, and/or the failed node rebooted.
875171 clcomm: Pathend %p: %d is not a pathend state
Description:The system maintains state information about a path. The state information is invalid.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
875345 None of the shared paths in file %s are valid.
Description:All the paths specified in the dfstab.<resource_name> file are invalid.
Solution:Check that those paths are valid. This might be a result of the underlying disk failure in an unavailable file system. The monitor_check method would thus fail and the HA-NFS resource would not be brought online on this node. However, it is advisable that the file system be brought online soon.
875401 Hosting member %s of instance %s does not match with hostname %s.
Description:The node specified to the SUNW.scalable_rac_server_proxy resource as hosting the RAC instance does not match with the node configured as the hosting member for that RAC instance, with CRS.
Solution:This error occurs during resource creation. Specify the same node the particular ORACLE_SID, that is configured for it with CRS. This node value can be found by inspecting the HOSTING_MEMBERS CRS attribute for this RAC instance.
875595 CMM: Shutdown timer expired. Halting.
Description:The node could not complete its shutdown sequence within the halt timeout, and is aborting to enable another node to safely take over its services.
Solution:This is an informational message, no user action is needed.
875796 CMM: Reconfiguration callback timed out; node aborting.
Description:One or more CMM client callbacks timed out and the node will be aborted.
Solution:There may be other related messages on this node which may help diagnose the problem. Resolve the problem and reboot the node if node failure is unexpected. If unable to resolve the problem, contact your authorized Sun service provider to determine whether a workaround or patch is available.
875939 ERROR: Failed to initialize callbacks for Global_resources_used, error code <%d>
Description:The rgmd encountered an error while trying to initialize the Global_resources_used mechanism on this node. This is not considered a fatal error, but probably means that method timeouts will not be suspended while a device service is failing over. This could cause unneeded failovers of resource groups when device groups are switched over.
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. This error might be cleared by rebooting the node.
876080 cm_getclustmbyname() failed.
Description:An error prevented the state of the UCMM from being retrieved.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
876090 fatal: must be superuser to start %s
Description:The rgmd can only be started by the superuser.
Solution:This probably occurred because a non-root user attempted to start rgmd manually. Normally the rgmd is started automatically when the node is booted.
876120 init_signal_handlers pthread_create: %s
Description:Internal error.
Solution:Save the syslog messages file. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
876324 CCR: CCR transaction manager failed to register with the cluster HA framework.
Description:The CCR transaction manager failed to register with the cluster HA framework.
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.
876386 Failed to stop DNS with SIGTERM; retry with SIGKILL
Description:The data service failed to stop the application by sending it a SIGTERM in the allotted time. Will retry with SIGKILL.
Solution:This problem may occur when the cluster is under load and Sun Cluster cannot stop the application within the timeout period specified. You may consider increasing the Stop_timeout property.
876437 Could not bring the source affinity resource group %s offline
Description:Failed to bring the inter-cluster source RG affinity offline. Possible cause could be that the remote zone cluster is down.
Solution:No user action is required.
876689 (%s) getenv of "%s" failed.
Description:Failed to get the value of an environmental variable. udlm will fail to go through a transition.
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.
876834 Could not start server
Description:HA-Oracle failed to start Oracle server. Syslog messages and log file will provide additional information on possible reasons of failure.
Solution:Check whether Oracle server can be started manually. Examine the log files and setup.
876906 %s/kadmind not started, exiting
Description:The kadmind 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), kdc.conf(4), and kadm5.acl(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.
876961 RGM isn't failing resource group <%s> off of node <%s>, because no current or potential master is healthy enough
Description:A scha_control(1HA,3HA) GIVEOVER attempt failed on all potential masters, because no candidate node was healthy enough to host the resource group.
Solution:Examine other syslog messages on all cluster members that occurred about the same time as this message, to see if the problem that caused the MONITOR_CHECK failure can be identified. Repair the condition that is preventing any potential master from hosting the resource.
877653 ct_pr_event_get_exitstatus: %s
Description:The rpc.pmfd was unable to determine the exit status of a process under its control that exited. It will assume failure.
Solution: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.
878089 fatal: realloc: %s (UNIX error %d)
Description:The rgmd failed to allocate memory, most likely because the system has run out of swap space. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
Solution:The problem was probably cured by rebooting. If the problem recurs, you might need to increase swap space by configuring additional swap devices. See swap(1M) for more information.
878101 Switch over the MDS for '%s' file system from '%s' node to node '%s'.
Description:This is a notification from the handler that it is trying to switch over the MDS for the specified file system.
Solution:This is an informational message; no user action is needed.
878135 WARNING: udlm_update_from_saved_msg
Description:There is no saved message to update udlm.
Solution:No user action is required. This is a warning only.
878486 %s: fsync_core_files: %s open <%s> failed, error %s
Description:The pmmd was unable to open the core file dumped by a monitored process. The pmmd will continue to monitor the process, but the pmmd has missed information of interest.
Solution: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.
878692 repl_check fatal error - Device group not specified
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.
879106 Failed to complete command %s. Will continue to start up liveCache.
Description:The listed command failed to complete. HA-liveCache will continue to start up liveCache.
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.
879190 door_callback: invalid argument
Description:The zone state change callback from the sc_zonesd was improperly formatted. The callback will be ignored.
Solution:Save a copy of the /var/adm/messages files on all nodes. If the problem persists, contact your authorized Sun service provider for assistance in diagnosing the problem.
879380 pmf_monitor_children: Error stopping <%s>: %s
Description:An error occurred while rpc.pmfd attempted to send a KILL signal to one of the processes of the given tag. The reason for the failure is also given. rpc.pmfd attempted to kill the process because a previous error occurred while creating a monitor process for the process to be monitored.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
879592 %s affinity property for %s resource group is not set.
Description:The specified affinity has not been set for the specified resource group.
Solution:Set the specified affinity on the specified resource group.
880080 No MDS resource found for mount-point %s.
Description:No metadata server resource has been created to represent the specified file system.
Solution:Ensure that a metadata server resource for the file system is created. For information about how to configure the shared QFS file system with Sun Cluster, see your Sun Cluster and documentation your Sun StorEdge QFS documentation.
880651 No hostnames specified.
Description:An attempt was made to create a Network resource without specifying a hostname.
Solution:At least one hostname must be specified by using the -h option to clreslogicalhostname or clressharedaddress.
880789 Failed to retrieve the resource '%s' information. Skipping this resource ...
Description:The zone boot handler failed to retrieve the specified resource information.
Solution:Investigate the zone boot log messages and rectify the problem. If problem persists after rebooting the zone, contact your authorized Sun service provider with copy of /var/adm/messages files on all nodes.
880835 pmf_search_children: Error stopping <%s>: %s
Description:An error occurred while rpc.pmfd attempted to send a KILL signal to one of the processes of the given tag. The reason for the failure is also given. rpc.pmfd attempted to kill the process because a previous error occurred while creating a monitor process for the process to be monitored.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
880921 %s is confirmed as mounted.
Description:HAStoragePlus certifies that the specified file system is in /etc/mnttab.
Solution:This is an informational message, no user action is needed.
881106 Validation failed for IPMP groups name <%s> : No entry found in <%s.%s>
Description:An IP address resource (of type LogicalHostname or SharedAddress) has been misconfigured. The indicated IPMP group name is not found in the indicated file on this node. This will cause errors in any attempted operation upon the IP address resource. Additional related failure messages are likely to be found near this one in the syslog output.
Solution:Check the configuration of network resources using the "clresourcegroup show -v +" command, and make any necessary corrections.
881808 shared QFS file system associated with mount point %s cannot be specified with failover resources.
Description:The specified HAStoragePlus resource is a failover resource, hence shared QFS file systems cannot be specified in the FilesystemMountPoints extension property.
Solution:Correct either the resource group type or remove the shared QFS file system from the FilesystemMountPoints extension property.
882451 Shared address resource %s is DISABLED. Its strong/restart dependents will be brought OFFLINE
Description:The resource being disabled is a SHARED ADDRESS resource. The strong and the restart dependents of this resource will be brought offline. The dependents will automatically be brought ONLINE once this resource is re-enabled.
Solution:No user action is required. This is an informational message.
882651 INTERNAL ERROR: PENDING_OFF_STOP_FAILED or ERROR_STOP_FAILED in sort_candidate_nodes
Description:An internal error has occurred in the rgmd. This may prevent the rgmd from bringing affected resource groups 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.
882793 Function: validate - Zonebrand for zone %s is configured as %s on a non-i386 system. It is only supported on i386 systems.
Description:The lx brand for zones is only supported on the i386 platform.
Solution:Review the components configuration file and make sure the variable Zonebrand defines "lx" only on a i386 system.
883414 Error: unable to bring Resource Group <%s> ONLINE, because the Resource Groups <%s> for which it has a strong negative affinity are online.
Description:The rgmd is enforcing the strong negative affinities of the resource groups. This behavior is normal and expected.
Solution:No user action is required. If desired, use clresourcegroup to change the resource group affinities.
883453 exception %s raised while attempting to get the status of cluster shutdown flag in CMM.
Description:An exception occurred when retrieving the status of the cluster shutdown flag in CMM.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
883465 Successfully delivered event %lld to remote node %d.
Description:The cl_eventd was able to deliver the specified event to the specified node.
Solution:This message is informational only, and does not require user action.
883690 Failed to start Monitor server.
Description:Sun Cluster HA for Sybase failed to start the monitor server. 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, monitor server log files and setup.
883823 Either extension property <Stop_signal> is not defined, or an error occurred while retrieving this property. The default value of SIGINT is being used.
Description:Property stop_signal may not be defined in RTR file. Continue the process with the default value of SIGINT.
Solution:No user action is needed.
884114 clcomm: Adapter %s constructed
Description:A network adapter has been initialized.
Solution:No user action is required.
884156 reservation warning(%s) - MHIOCGRP_RESERVE 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.
884252 INTERNAL ERROR: usage: `basename $0` <Independent_Program_Path> <DB_Name> <User_Key> <Pid_Dir_Path>
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.
884482 clconf: Quorum device ID %ld is invalid. The largest supported ID is %ld
Description:Found the quorum device ID being invalid while converting the quorum configuration information into quorum table.
Solution:Check the quorum configuration information.
884495 Could not get service parameters for device service %s, error = %d
Description:No service by this name was found when executing scdidadm -C. This service might have been removed by another instance of this command that was issued from another node.
Solution:No user action required.
884821 Unparsable registration
Description:A CRNP client submitted a registration message that could not be parsed.
Solution:No user action is required. This message represents a CRNP client error.
884979 (%s) aborting, but got a message of type %d
Description:Going through udlm abort and received an unexpected message of the mentioned type.
Solution:No user action is required.
885546 Function: check_sczbt - Zone scheduler for %s not running
Description:The zsched process of the referenced zone is not running. The zone is not operable.
Solution:No user action is required. The resource will be restarted or the resource group will be failed over.
885688 Mounting the file systems is completed successfully.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
885719 Telemetry data service monitor successfully stopped (resource: %s)
Description:The monitor program of the telemetry data service stopped successfully.
Solution:This message is informational; no user action needed.
885997 ucmmd got invalid upgrade callback from version manager: new version %d.%d is not the expected new version %d.%d from callback step 1.
Description:Version manager delivered upgrade callback to ucmmd about a new version that is not the expected new version after callback step 1 for ucmmd.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
886033 fatal: unable to determine if resource type %s exists.
Description:The rgmd failed to detect the existence of the specified resource type, so was unable to complete the administrative request. The node will be aborted.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified which is preventing the CCR access. 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.
886247 Function: check_sczbt - Zones %s ip address %s is not running
Description:The referenced zones ip address is unplumbed.
Solution:No user action is required. The resource will be restarted or the resource group will be failed over.
886919 CMM: Callback interface versions do not match.
Description:Interface version of an instance of userland CMM does not match the kernel version.
Solution:Ensure that complete software distribution for a given release has been installed using recommended install procedures. Retry installing same packages if previous install had been aborted. If the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
886983 HADB mirror nodes %d and %d are on the same Sun Cluster node: %s.
Description:The specified HADB nodes are mirror nodes of each and they are located on the same Sun Cluster node. This is a single point of failure because failure of the Sun Cluster node would cause both HADB nodes, which mirror each other, to fail.
Solution:Recreate the HADB database with mirror HADB nodes on separate Sun Cluster nodes.
887086 Unable to determine database status.
Description:An error occurred while trying to read the output of the hadbm status command.
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.
887138 Extension property <Child_mon_level> has a value of <%d>
Description:Resource property Child_mon_level is set to the given value.
Solution:This is an informational message, no user action is required.
887282 Mode for file %s needs to be %03o
Description:The file needs to have the indicated mode.
Solution:Set the mode of the file correctly.
887656 Process: tag="%s", cmd="%s", Failed to stay up.
Description:The tag shown, being run by the rpc.pmfd server, has exited. Either the user has decided to stop monitoring this process, or the process exceeded the number of retries. An error message is output to syslog.
Solution:This message is informational; no user action is needed.
887666 clcomm: sxdoor: op %d fcntl failed: %s
Description:A user level process is unmarshalling a door descriptor and creating a new door. The specified operation on the fcntl operation fails. The "fcntl" man page describes possible error codes.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
887669 clcomm: coalesce_region request(%d) > MTUsize(%d)
Description:While supporting an invocation, the system wanted to create one buffer that could hold the data from two buffers. The system cannot create a big enough buffer. After generating another system error message, the system will panic. This message only appears on debug systems.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
887853 The service can't be hosted in non-global zone
Description:The SUNW.Event service can't be hosted in a non-global zone.
Solution:Host the service only in the global zone.
887981 No Inter RG-dependency found, using internal dependency
Description:-3 Informational : no inter rg dependency defined in the config
Solution:-3 none required
888259 clcomm: Path %s being deleted and cleaned
Description:A communication link is being removed with another node. The interconnect might have failed or the remote node might be down.
Solution:Any interconnect failure should be resolved, and/or the failed node rebooted.
888476 SCSLM <%s> pool_destroy error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
889303 Failed to read from kstat:%s
Description:See 176151
Solution:See 176151
889414 Unexpected early exit while performing: '%s' result %d revents %x
Description:clexecd program got an error while executing the program indicated in the error message.
Solution:Please check the error message. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
889899 scha_control RESTART failed. error %s
Description:Fault monitor had detected problems in RDBMS server. Attempt to restart RDBMS server on the same node failed. Error returned by API call scha_control is indicated in the message.
Solution:No user action is required.
890413 %s: state transition from %s to %s.
Description:A state transition has happened for the IPMP group. Transition to DOWN happens when all adapters in an IPMP group are determined to be faulty.
Solution:If an IPMP group transitions to DOWN state, check for error messages about adapters being faulty and take suggested user actions accordingly. No user action is required for other state transitions.
890927 HA: repl_mgr_impl: thr_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.
891225 cl_execd: sigfillset returned %d. Exiting.
Description:cl_execd program has encountered a failed sigfillset(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.
891362 scha_resource_open error (%d)
Description:Error occurred in API call scha_resource_open.
Solution:Check syslog messages for errors logged from other system modules. Stop and start fault monitor. If error persists then disable fault monitor and report the problem.
891424 Starting %s with command %s.
Description:Sun Cluster is starting the specified application with the specified command.
Solution:This is an informational message, no user action is needed.
891462 in libsecurity caller is %d, not the desired uid %d
Description:A server (rpc.pmfd, rpc.fed or rgmd) refused an rpc connection from a client because it has the wrong uid. The actual and desired uids are 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.
891542 Diskgroup (%s) is in degraded state
Description:The disk group is degraded. Although the disk group is usable it requires maintenance.
Solution:To prevent further degradation, perform the required maintenance on the disk group as soon as possible.
891608 Failed to determine type of storage (%s): %s
Description:An error occurred while the type of the underlying volume manager was being retrieved. The type of the volume manager is determined from the resource's dependency on a resource of type SUNW.rac_svm or of type SUNW.rac_cvm.
Solution:Ensure that the ScalDeviceGroup resource has a dependency on a resource either of type SUNW.rac_svm or of type SUNW.rac_cvm.
891745 Unable to register for upgrade callbacks with version manager: %s
Description:An exception was raised when PNM proxy tried to register for upgrade callbacks with the Version Manager.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
892076 Waiting for the PNM in zone %s to stop
Description:The PNM service is being stopped.
Solution:Please wait. No user action is required. This is an informational message.
892197 Sending to node %d.
Description:The cl_eventd is forwarding an event to the specified node.
Solution:This message is informational only, and does not require user action.
892269 Failed to configure sci%d adapter
Description:The Sun Cluster Topology Manager (TM) has failed to add or remove a path using the SCI adapter.
Solution:Make sure that the SCI adapter is installed correctly on the system. Also ensure that the cables have been setup correctly. If required contact your authorized Sun service provider for assistance.
892316 Error: The RAC Framework resource does not exist.
Description:The RAC framework resource does not exist. The Oracle CRS framework resource depends on the RAC framework resource.
Solution:Ensure that the RAC framework resource has been created and repeat the attempt to create the CRS framework resource.
893019 %d-bit saposcol is running on %d-bit Solaris.
Description:The architecture of saposcol is not compatible to the current running Solaris version. For example, you have a 64-bit saposcol running on a 32-bit Solaris machine or vice verse.
Solution:Make sure the correct saposcol is installed on the cluster.
893268 RAC framework did not start on this node. The ucmmd daemon is not running.
Description:RAC framework is not running on this node. Oracle parallel server/ Real Application Clusters database instances will not be able to start on this node. One possible cause is that installation of Sun Cluster support for Oracle Parallel Server/Real Application clusters is incorrect. When RAC framework fails during previous reconfiguration, the ucmmd daemon and RAC framework is not started on the node to allow investigation of the problem.
Solution:Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters. If problem persists, contact your Sun service representative.
893639 Invalid zone state: %s
Description:The sc_zonesd received an invalid zone state notification from Solaris.
Solution:This message can be ignored and the user need not take any action
893971 in libsecurity, authorization failed
Description:A cluster daemon refused a door connection from a client because of improper credentials. This might happen if a caller program is required to run as superuser or as a specific user ID, and fails to do so.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified. Check that the clustering software is properly installed, and that no unauthorized user processes are running on the cluster. If these checks cannot explain the error, contact your authorized Sun service provider to determine whether a workaround or patch is available.
894418 reservation warning(%s) - Found invalid key, preempting
Description:The device fencing program has discovered an invalid scsi-3 key on the specified device and is removing it.
Solution:This is an informational message, no user action is needed.
894711 Could not resolve '%s' in the name server. Exiting.
Description:clexecd program was unable to start due to an error in registering itself with the low-level clustering software.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
894831 Error reading caapi_reg CCR table
Description:The cl_apid was unable to read the specified CCR table. This error will prevent the cl_apid from starting.
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.
895149 (%s) t_open: tli error: %s
Description:Call to t_open() failed. The "t_open" man page describes possible error codes. udlmctl will exit.
Solution: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.
895159 clcomm: solaris xdoor dup failed: %s
Description:A dup operation failed. The "dup" man page describes possible error codes.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
895266 DID reconfiguration discovered an invalid disk path. You must remove this path before you can add a new path. Run 'scdidadm -C' then rerun 'scdidadm -r'.
Description:Invalid disk path found during DID reconfiguration.
Solution:Remove the invalid disk path and run 'scdidadm -C' and rerun 'scdidadm -r'.
895389 start_dependency: Exceeded ${MAX_START_TIMEOUT} seconds for waiting on dependent resource for resource ${RESOURCE} to come online
Description:The start of a dependent resource takes too long.
Solution:No user action is required.
895418 stop_mysql - Failed to stop MySQL through mysqladmin for %s, send TERM signal to process
Description:The mysqladmin command failed to stop MySQL instance.
Solution:Either was MySQL already down or the fault monitor user does not have the right permission to stop MySQL. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges.
895493 metaset command failed with error %d.
Description:An error occurred when the command 'metaset' was run.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
896252 clcomm: failed to create thread for autom_thread
Description:The system could not create the needed thread, because there is inadequate memory.
Solution:There are two possible solutions. Install more memory. Alternatively, reduce memory usage. Since this happens during system startup, application memory usage is normally not a factor.
896275 CCR: Ignoring override field for table %s on joining node %s.
Description:The override flag for a table indicates that the CCR should use this copy as the final version when the cluster is coming up. If the cluster already has a valid copy while the indicated node is joining the cluster, then the override flag on the joining node is ignored.
Solution:This is an informational message, no user action is needed.
896441 Unknown scalable service method code: %d.
Description:The method code given is not a method code that was expected.
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.
896532 Invalid variable name in Environment_file. Ignoring %s
Description:HA-Sybase reads the Environment_file and exports the variables declared in the Environment file. Syntax for declaring the variables is : VARIABLE=VALUE Lines starting with " with "export" are ignored. VARIABLE is expected to be a valid Korn shell variable that starts with alphabet or "_" and contains alphanumerics and "_".
Solution:Please check the syntax and correct the Environment_file
896853 Membership: Unable to create automaton callback thread for membership subsystem.
Description:A thread that is part of the membership subsystem could not be created. This might be due to lack of memory. Membership subsystem will not work properly.
Solution:Lack of memory might lead to other problems on the node. You must free up memory on the node.
897830 This node is not in the replica node list of global service %s associated with path %s. Although AffinityOn is set to TRUE, device switchovers cannot be performed to this node.
Description:Self explanatory.
Solution:Remove the specified node from the resource group.
898001 launch_fed_prog: getlocalhostname() failed for program <%s>
Description:The ucmmd was unable to obtain the name of the local host. Launching of a method failed.
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 the problem.
898028 Service failed and the fault monitor is not running on this node. Not restarting service because failover_enabled is set to false.
Description:The probe has quit previously because failover_enabled is set to false. The action script for the process is trying to contact the probe, and is unable to do so. Therefore, the action script is not restarting the application.
Solution:This is an informational message, no user action is needed.
898457 Function: validate: The %s variable is not set, but it is required
Description:A mandatory variable is unset in the parameter file.
Solution:Fix the parameter file and provide a value for the variable in the parameter file
898507 reservation notice(%s) - MHIOCGRP_REGISTER success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action required.
898620 Validate - Unable to determine the SUNW.LogicalHostname resource for %s
Description:Unable to determine the SUNW.LogicalHostname resource within the Resource_dependencies list for the resource being created.
Solution:Check that you have specified a value for the LH keyword within the /opt/SUNWscebs/xxx/util/xxx_config, where xxx represents the Oracle E-Business Suite component - cmg, cmglsr, frm, opmn and rep.
898738 Aborting node because pm_tick delay of %lld ms exceeds %lld ms
Description:The system is unable to send heartbeats for a long time. (This is half of the minimum of timeout values of all the paths. If the timeout values for all the paths is 10 secs then this value is 5 secs.) There is probably heavy interrupt activity causing the clock thread to get delayed, which in turn causes irregular heartbeats. The node is aborted because it is considered to be in 'sick' condition and it is better to abort this node instead of causing other nodes (or the cluster) to go down.
Solution:Check to see what is causing high interrupt activity and configure the system accordingly.
898802 ping_interval out of bound. The interval must be between %d and %d seconds: using the default value
Description:The scdpmd config file (/etc/cluster/scdpm/scdpmd.conf) has a bad ping_interval value. The default ping_interval value is used.
Solution:Fix the value of ping_interval in the config file.
898960 Failed to generate callback for path down event
Description:Cluster cannot generate a callback for the RDS module. Operation of RDS sockets might be affected.
Solution:If Reliable Datagram Sockets (RDS) is used by applications running on this cluster, contact your Sun Microsystems service representative to determine if a workaround or patch is available.
899278 Retry_count exceeded in Retry_interval
Description:Fault monitor has detected problems in RDBMS server. Number of restarts through fault monitor exceed the count specified in 'Retry_count' parameter in 'Retry_interval'. Database server is unable to survive on this node. Switching over the resource group to other node.
Solution:Please check the RDBMS setup and server configuration.
899305 clexecd: Daemon exiting because child died.
Description:Child process in the clexecd program is dead.
Solution:If this message is seen when the node is shutting down, ignore the message. If that is not the case, the node will halt or reboot itself to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
899648 Failed to process the resource information.
Description:A Sun cluster data service is unable to retrieve the resource property information. 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.
899877 time in throttle wait: %s
Description:The time(2) function failed with the specified error. The program will exit and the node might halt or reboot.
Solution: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.
899940 check_mysql - Couldn't drop table %s from database %s (%s)
Description:The fault monitor can't drop specified table from the test database.
Solution:Either was MySQL already down or the fault monitor user does not have the right permission. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges. Check also the MySQL logfiles for any other errors.
Message IDs 900000–999999
This section contains message IDs 900000–999999.
900058 Failed to write to test-file %s : %s
Description:A write operation on the test file for I/O operations failed. One possible cause of this error is that the test file has been deleted. The deletion of this file might be caused by malicious activity in your system.
Solution:Restart the ScalMountPoint resource.
900102 Failed to retrieve the resource type property %s: %s.
Description:An API operation has failed while retrieving the resource type 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.
900184 Error in scha_resource_get: %s
Description:Error in reading the resource type of the resource
Solution:Check if the RGM functionalities are working and if the resources are present. Contact your SUN vendor for more help.
900198 validate: Port is not set but it is required
Description:The parameter Port is not set in the parameter file
Solution:set the variable Port in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.
900304 UNRECOVERABLE ERROR: Sun Cluster boot: cl_execd not started
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
900499 Error: low memory
Description:The rpc.fed or cl_apid server was not able to allocate memory. If the message if from the rpc.fed, the server might not be able to capture the output from methods it runs.
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.
900501 pthread_sigmask: %s
Description:The daemon was unable to configure its signal handler, so it is unable to run.
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.
900508 Internal error; SAP instance id set to NULL.
Description:Extension property could not be retrieved and is set to NULL. Internal error.
Solution:No user action needed.
900626 Volume (%s) not valid!
Description:The volume is not a valid volume.
Solution:Ensure that the volumes that are specified for monitoring are valid.
900675 cluster volume manager shared access mode enabled
Description:Message indicating shared access availability of the volume manager.
Solution:No user action is required.
900709 pid %u <%s> project <%s> user <%s> setproject() ret %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.
900843 Retrying to retrieve the cluster information.
Description:An update to cluster configuration occurred while cluster properties were being retrieved
Solution:Ignore the message.
900954 fatal: Unable to open CCR
Description:The rgmd daemon was unable to open the cluster configuration repository (CCR). The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
901425 Create_configuration - the affinity specification of the MySQL replication resource group %s failed
Description:The MySQL setting of the affinity failed for the MySQL replication rg
Solution:Pick a different replication resource group
901546 SCTP services should depend on SharedAddress resources belonging to the same resource group
Description:The shared addresses used by the SCTP service belong to different resource groups.
Solution:Make sure the shared addresses belong to the same resource group.
902017 clexecd: can allocate execit_msg
Description:Could not allocate memory. Node is too low on memory.
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.
902721 Switching over resource group using scha_control GIVEOVER
Description:Fault monitor has detected problems in RDBMS server. Fault monitor has determined that RDBMS server cannot be restarted on this node. Attempt will be made to switchover the resource to any other node, if a healthy node is available.
Solution:Check the cause of RDBMS failure.
902897 PNM proxy invoked for a global zone PNM client.
Description:The PNM proxy subsystem is being used for a global zone PNM client.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
903007 txmit_common: udp is null!
Description:Can not transmit a message and communicate with udlmctl because the address to send to is null.
Solution:No user action is required.
903317 Entry at position %d in property %s was invalid.
Description:An invalid entry was found in the named property. The position index, which starts at 0 for the first element in the list, indicates which element in the property list was invalid.
Solution:Make sure the property has a valid value.
903370 Command %s failed to run: %s.
Description:HA-NFS attempted to run the specified command to perform some action which failed. The specific reason for failure is also provided.
Solution:HA-NFS will take action to recover from this failure, if possible. If the failure persists and service does not recover, contact your service provider. If an immediate repair is desired, reboot the cluster node where this failure is occurring repeatedly.
903626 Internal Error: Could not validate the SCTP bind address list due to array overflow.
Description:The number of scalable services multiplied by the number of shared addresses exceeds the maximum allowed value of 1024.
Solution:Either reduce the number of scalable applications in the cluster or reduce the number of shared addresses that are used.
903666 Some other object bound to <%s>.
Description:The cl_eventd found an unexpected object in the nameserver. It may be unable to forward events to one or more nodes in the cluster.
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.
903734 Failed to create lock directory %s: %s.
Description:This network resource failed to create a directory in which to store lock files. These lock files are needed to serialize the running of the same callback method on the same adapter for multiple resources.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action. For specific error information, check the syslog message.
904284 cl_execd: waitpid returned %d.
Description:The cl_execd program has encountered a failed waitpid(3C) system call. The error message indicates the error number of failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
904778 Number of entries exceeds %ld: Remaining entries will be ignored.
Description:The file being processed exceeded the maximum number of entries permitted as indicated in this message.
Solution:Remove any redundant or duplicate entries to avoid exceeding the maximum limit. Too many entries will cause the excess number of entries to be ignored.
904914 fatal: Aborting this node because method <%s> on resource <%s> for node <%s> is unkillable
Description:The specified callback method for the specified resource became stuck in the kernel, and could not be killed with a SIGKILL. The RGM reboots the node to force the data service to fail over to a different node, and to avoid data corruption.
Solution:No user action is required. This is normal behavior of the RGM. Other syslog messages that occurred just before this one might indicate the cause of the method failure.
905020 %s is already running on this node outside of Sun Cluster. The start of %s from Sun Cluster will be aborted.
Description:The specified application is already running on the node outside of Sun Cluster software. The attempt to start it up under Sun Cluster software will be aborted.
Solution:No user action is needed.
905023 clexecd: dup2 of stderr returned with errno %d while exec'ing (%s). Exiting.
Description:clexecd program has encountered a failed dup2(2) system call. The error message indicates the error number for the failure.
Solution:The clexecd program will exit and the 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.
905056 Validate - Only SUNWfiles or SUNWbinfiles are supported
Description:The DHCP resource requires that the /etc/inet/dhcpsvc.conf file has RESOURCE=SUNWfiles or SUNWbinfiles.
Solution:Ensure that /etc/inet/dhcpsvc.conf has RESOURCE=SUNWfiles or SUNWbinfiles by configuring DHCP appropriately, i.e. as defined within the Sun Cluster Data Service for DHCP.
905112 %s: unable to arm failfast.
Description:The pmmd program was not able to arm the failfast unit.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
905151 Unable to lock device %s. Error (%s).
Description:Sun Cluster was unable to lock a device.
Solution:Check the error returned for why this happened. In cases like an interrupted system call, no user action is required.
905363 Function: start_pgs - the standby host %s is not answering on ping
Description:The standby host is not up and running.
Solution:Consult the logs on the standby host and insure, that the standby host is answering on ping requests of the primary host.
905591 Could not determine volume configuration daemon mode
Description:Could not get information about the volume manager daemon mode.
Solution:Check if the volume manager has been started up right.
906044 get_cluster_name() call failed.
Description:An error prevented the cluster name from being retrieved.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
906368 Validate - /opt/SUNWscebs/.%s_passwd is not restricted to be read only by root
Description:The restricted passwd file used to start and stop the Concurrent Manager is not restricted to be read only by root.
Solution:Change the owner and permissions so that the restricted file is only readable by owner root.
906589 Error retrieving network address resource in resource group.
Description:An error occurred reading the indicated extension property.
Solution:Check syslog messages for errors logged from other system modules. If error persists, please report the problem.
906838 reservation warning(%s) - do_scsi3_registerandignorekey() error for disk %s, attempting do_scsi3_register()
Description:The device fencing program has encountered errors while trying to access a device. Now trying to run do_scsi3_register() This is an informational message, no user action is needed
Solution:This is an informational message, no user action is needed.
906922 Started NFS daemon %s.
Description:The specified NFS daemon has been started by the HA-NFS implementation.
Solution:This is an informational message. No user action is required.
907356 Method <%s> on resource <%s>, node <%s>: authorization error: %s.
Description:An attempted method execution failed, apparently due to a security violation; this error should not occur. The last portion of the message describes the error. This failure is considered a method failure. 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:Correct the problem identified in the error message. If necessary, examine other syslog messages occurring at about the same time to see if the problem can be diagnosed. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing the problem.
907626 Could not initialize the contract info for svc :%s
Description:Problem in initializing the contract for the service specified
Solution:Depending on the error, check the SMF man page. Contact your SUN vendor for help.
907960 Attempting to restart listener %s.
Description:Listener monitor has either timed out or detected failure of listener. Monitor will attempt to restart the listener.
Solution:No user action is required.
908240 in libsecurity realloc failed
Description:A server (rpc.pmfd, rpc.fed or rgmd) was not able to start, or a client was not able to make an rpc connection to the server. This problem can occur if the machine has low memory. An error message is output to syslog.
Solution:Determine if the host is low on memory. If not, save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
908387 ucm_callback for step %d generated exception %d
Description:ucmm callback for a step 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.
908591 Failed to stop fault monitor.
Description:An attempt was made to stop the fault monitor and it failed. There may be prior messages in syslog indicating specific problems.
Solution:If there are prior messages in syslog indicating specific problems, these should be corrected. If that doesn't resolve the issue, the user can try the following. Use process monitor facility (pmfadm (1M)) with -L option to retrieve all the tags that are running on the server. Identify the tag name for the fault monitor of this resource. This can be easily identified as the tag ends in string ".mon" and contains the resource group name and the resource name. Then use pmfadm (1M) with -s option to stop the fault monitor. This problem may occur when the cluster is under load and Sun Cluster cannot stop the fault monitor within the timeout period specified. You may consider increasing the Monitor_Stop_timeout property. If the error still persists, then reboot the node.
909280 Validate_sbp - MySQL resource %s is not specified in option %s
Description:The required real mysql resource is not specified.
Solution:Make sure that the required resource group is specified.
909656 Unable to open /dev/kmem:%s
Description:HA-NFS fault monitor attempt to open the device but failed. The specific cause of the failure is logged with the message. The /dev/kmem interface is used to read NFS activity counters from kernel.
Solution:No user action is required. HA-NFS fault monitor would ignore this error and try to open the device again later. Since it is unable to read NFS activity counters from kernel, HA-NFS would attempt to contact nfsd by means of a NULL RPC. A likely cause of this error is lack of resources. Attempt to free memory by terminating any programs which are using large amounts of memory and swap. If this error persists, reboot the node.
909728 Start command %s timed out.
Description:Start up of the data service timed out.
Solution:No user action needed.
909731 Failed to get service state %s:%s
Description:The Solaris service management facility failed to get the name of the service instance's current state that the fault management resource identifier (FMRI) in the /var/adm/messages specifies.
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.
909737 Error loading dtd for %s
Description:The cl_apid was unable to load the specified dtd. No validation will be performed on CRNP xml messages.
Solution:No user action is required. If you want to diagnose the problem, 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.
910155 WebSphere MQ Trigger Monitor %s restarted
Description:The specified WebSphere MQ Trigger Monitor has been restarted.
Solution:No user action is required. Informational message.
910284 libscha XDR Buffer Shortfall while encoding arguments API num : %d, will retry
Description:A non-fatal error occurred in a libscha.so function while marshalling arguments for a remote procedure call. The operation will be retried 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.
910339 scvxvmlg error - remove(%s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
910758 Membership: Could not get cluster state from CMM.
Description:Could not get cluster state from CMM.
Solution:No user action needed.
911450 Probe failed in the prenet start method. Diskgroup (%s) not available.
Description:The disk set or disk group failed its availability check.
Solution:Verify the status of the disk set or disk group and perform maintenance if required.
911550 Method <%s> failed to execute on resource <%s> in resource group <%s>, on node <%s>, error: <%s>
Description:A resource method failed to execute, due to a system error described in the message. For an explanation of the error message, consult intro(2). This is considered a method failure. 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, or it might cause an attempted edit of a resource group or its resources to fail.
Solution:If the error message is not self-explanatory, other syslog messages occurring at about the same time might provide evidence of the source of the problem. If not, save a copy of the /var/adm/messages files on all nodes, and (if the rgmd did crash) a copy of the rgmd core file, and contact your authorized Sun service provider for assistance.
912247 Failed to add the %s to the CCR table %s.
Description:An unknown error has occurred while updating the CCR with the current zone cluster name.
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.
912386 Membership: Unable to get zone reference from Solaris for running zone %s.
Description:Membership subsystem was unable to get the zone reference structure from Solaris for a zone that is running.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
912393 This node is not in the replica node list of global service %s associated with path %s. This is acceptable because the existing affinity settings do not require resource and device co-location.
Description:Self explanatory.
Solution:This is an informational message, no user action is needed.
912563 fatal: could not start ccr change thread
Description:Could not start ccr change thread. This may be due to 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.
912747 Failed to unmount file-system %s from mountpoint %s : %s
Description:The specified file system could not be unmounted from its mount point during a postnet-stop operation.
Solution:Manually unmount the file system.
912866 Could not validate CCR tables; halting node
Description:The rgmd daemon was unable to check the validity of the CCR tables representing Resource Types and Resource Groups. The node will be halted to prevent further errors.
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.
913638 Resource type %s does not exist.
Description:The SUNW.qfs resource type is not registered in the cluster.
Solution:Register the SUNW.qfs resource type, create the required instances of this resource type, and repeat the operation. 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.
913776 Error: unable to register for zone state change events: zones functionality will not work correctly on this node
Description:The sc_zonesd is unable to register for zone state change events: zones functionality will not work correctly on this node.
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.
913907 Failed to retrieve extension property %s : %s.
Description:An error occurred while extension property of the resource is retrieved.
Solution:Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
914248 Listener status probe timed out after %s seconds.
Description:An attempt to query the status of the Oracle listener using command 'lsnrctl status <listener_name>' did not complete in the time indicated, and was abandoned. HA-Oracle will attempt to kill the listener and then restart it.
Solution:No user action is required. HA-Oracle will attempt to restart the listener. However, the cause of the listener hang should be investigated further. Examine the log file and syslog messages for additional information.
914260 Failed to retrieve global fencing status from the global name server
Description:An error was encountered when run_reserve was retrieving the global fencing status from the global name server. It will then try to read it from the CCR directly.
Solution:This is an informational message, no user action is needed.
914440 %s has been deleted. If %s was hosting any HA IP addresses then these should be restarted.
Description:We do not allow deleting of an IPMP group which is hosting Logical IP addresses registered by RGM. Therefore we notify the user of the possible error.
Solution:This message is informational; no user action is needed.
914519 Error when sending message to child %m
Description:Error occurred when communicating with fault monitor child process. Child process will be stopped and restarted.
Solution:If error persists, then disable the fault monitor and report the problem.
914866 Unable to complete some unshare commands.
Description:HA-NFS postnet_stop method was unable to complete the unshare(1M) command for some of the paths specified in the dfstab file.
Solution:The exact pathnames which failed to be unshared would have been logged in earlier messages. Run those unshare commands by hand. If problem persists, reboot the node.
915051 Failed to register zone state change notification callbacks
Description:The scprivipd failed to register with sc_zonesd for zone state change notification.
Solution:The private IP communication for local zones depends on scprivipd and the registration for zone state change notification. So, this feature will not work as expected as a result of this error. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
915091 Probe - Fatal: %s/checkprog not found or not executable
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.
915389 Failed to create socket: %s.
Description:Failure in communication between fault monitor and process monitor facility.
Solution:This is internal error. Save /var/adm/messages file and contact the Sun service provider.
915652 %s group %s can host %s addresses only. Host %s has no mapping of this type.
Description:The IPMP group can not host IP addresses of the type that the hostname maps to. For example, if the hostname maps to IPv6 address(es) only and the IPMP group is setup to host IPv4 addresses only.
Solution:Use ifconfig -a to determine if the network adapter in the resource's IPMP group can host IPv4, IPv6 or both kinds of addresses. Make sure that the hostname specified has at least one IP address that can be hosted by the underlying IPMP group.
915691 DATAGUARD_ROLE has been set to IN_TRANSITION. Switchover operation may be in progress on the database. Database shutdown will not be attempted.
Description:The DATAGUARD_ROLE extension property of the HA Oracle resource has been set to the value IN_TRANSITION, indicating that a role switchover may be in progress on the database. The HA Oracle data service will not proceed with a database shutdown during this time.
Solution:If you are sure that the database is not undergoing a switchover operation, set the DATAGUARD_ROLE and STANDBY_MODE extension properties to reflect the current dataguard mode of the Oracle database. Since the database is not shutdown by the data service, clear the STOP_FAILED flag on the Sun Cluster resource and bring the resource online again. Then bring the Sun Cluster resource offline. This operation will shut down the database.
916067 validate: Directory %s does not exist but it is required
Description:The directory with the name $Directoryname does not exist
Solution:set the variable Basepath in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.
916361 in libsecurity for program %s (%lu); could not find any tcp transport
Description:A client was not able to make an rpc connection to the specified server because it could not find a tcp transport. 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.
916556 The zfs pool '%s' requires delegation of all its datasets to use in zone cluster %s. Use clzc(1CL)'s "add dataset" subcommand and do "set name = %s" to delegate.
Description:The specified zpool is not delegated to zone cluster and hence not authorized to configure in resource.
Solution:Delegate the complete zpool to the zone cluster and repeat the operation. If the problem persists, contact your authorized Sun service provider with /var/adm/message and zone cluster configuration.
917103 %s has the keyword group already.
Description:This means that auto-create was called even though the /etc/hostname.adp file has the keyword "group". Someone might have hand edited that file. This could also happen if someone deletes an IPMP group - A notification should have been provided for this.
Solution:Change the file back to its original contents. Try the clreslogicalhostname or clressharedaddress command again. We do not allow IPMP groups to be deleted once they are configured. If the problem persists contact your authorized Sun service provider for suggestions.
917145 Only one Sun Cluster node will be offline, stopping node.
Description:The resource will be offline on only one node so the database can continue to run.
Solution:This is an informational message, no user action is needed.
917173 fatal: Invalid node ID in infrastructure table
Description:The internal cluster configuration is erroneous and a node carries an invalid ID. RGMD will exit causing the node to reboot.
Solution:Report the problem to your authorized Sun service provider.
917467 Got cluster_stop from cluster node %d
Description:This can be seen only on DEBUG binaries. When a CL_PANIC or ASSERT failure happens on any cluster node, the other nodes are also forced to go down to help in analyzing the root cause.
Solution:Save the cores from all the nodes to check for a potential bug.
917591 fatal: Resource type <%s> update failed with error <%d>; aborting node
Description:Rgmd failed to read updated resource type 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.
917682 Invalid name size for CVM
Description:The length of the name of a VxVM shared-disk group is less than or equal to zero.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
917991 scf_pg_update 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.
918018 load balancer for group '%s' released
Description:This message indicates that the service group has been deleted.
Solution:This is an informational message, no user action is needed.
918488 Validation failed. Invalid command line parameter %s %s.
Description:Unable to process parameters passed to the call back method specified. This is a Sun Cluster HA for Sybase internal error.
Solution:Report this problem to your authorized Sun service provider
918861 Could not get the cluster context from the name server. Exiting.
Description:The pnm proxy program could not get the ALL_CLUSTER context from the global nameserver.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
919740 WARNING: error in translating address (%s) for nodeid %d
Description:Could not get address for a node.
Solution:Make sure the node is booted as part of a cluster.
919904 Global devices are not supported in local zone : %s.
Description:Global devices paths are not supported in the specified zone.
Solution:Remove the global device paths and repeat creating the resource. If problem persists, contact your authorized Sun service provider.
920103 created %d threads to handle resource group switchback; desired number = %d
Description:The rgmd daemon was unable to create the desired number of threads upon starting up. This is not a fatal error, but it might cause RGM reconfigurations to take longer because it will limit the number of tasks that the rgmd can perform concurrently.
Solution:Make sure that the hardware configuration meets documented minimum requirements. Examine other syslog messages on the same node to see if the cause of the problem can be determined.
920286 Peer node %d attempted to contact us with an invalid version message, source IP %s.
Description:Sun Cluster software at the local node received an initial handshake message from the remote node that is not running a compatible version of the Sun Cluster software.
Solution:Make sure all nodes in the cluster are running compatible versions of Sun Cluster software.
920429 Deferring tcp_rio_client %p with generation %x
Description:The replyio subsystem detected an out-of-sequence arrival of replyio segments.
Solution:This message is for diagnostic purposes only; no action required.
921054 door_callback: invalid argument size
Description:The zone state change callback from the sc_zonesd daemon was improperly formatted. The callback will be ignored.
Solution:Save a copy of the /var/adm/messages files on all nodes. If the problem persists, contact your authorized Sun service provider for assistance in diagnosing the problem.
921455 Failed to obtain service class information for global service %s associated with path %s: %s.
Description:The DCS was not able to obtain the service class information for the specified global service.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
921508 Failed to activate contract template: %s
Description:Not able to activate the contract template.
Solution:Check the contract man page to know more about the error. Also make sure the basic contract functionalities are working. Contact your SUN vendor for more help.
921584 sigwaitinfo returned %d. Exiting.
Description:The rtreg server program has encountered a failed sigwaitinfo(3RT) system call. The error message contains the error number for the failure.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
921782 sema_init failure: %s
Description:The libclcontract code was not able to initialize a semaphore, possibly due to low memory, and the system error is shown. The server does not perform the action requested by the client. An error message is also output to syslog.
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.
922085 INTERNAL ERROR CMM: Memory allocation error.
Description:The CMM failed to allocate memory during initialization.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
922150 Regular expression compile error %s: %s
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.
922276 J2EE probe determined wrong port number, %d.
Description:The data service detected an invalid port number for the J2EE engine probe.
Solution:Informational message. No user action is needed.
922363 resource %s status msg on node %s change to <%s>
Description:This is a notification from the rgmd that a resource's fault monitor status message has changed.
Solution:This is an informational message; no user action is needed.
922442 Failed to open contract ctl file to ack%s: %s
Description:Not able to open the contract control file to acknowledge the event
Solution:Check the contract man page to know more about the error. Also make sure the basic contract functionalities are working. Contact your SUN vendor for more help. This should not seriously effect the working of delegated restarter.
922726 The status of device: %s is set to MONITORED
Description:A device is monitored.
Solution:No user action is required.
922870 tag %s: unable to kill process with SIGKILL
Description:The rpc.fed server is not able to kill the process with a SIGKILL. This means the process is stuck in the kernel.
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.
923046 Could not initialize dcs library. Error %d
Description:An error prevented the initialization of the DCS library.
Solution:Contact your authorized Sun service provider for assistance in diagnosing the problem.
923106 sysevent_bind_handle(): %s
Description:The cl_apid or cl_eventd 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.
923412 The path name %s associated with the FilesystemCheckCommand extension property is detected to be a relative pathname. Only absolute path names are allowed.
Description:Self explanatory. For security reasons, this is not allowed.
Solution:Correct the FilesystemCheckCommand extension property by specifying an absolute path name.
923618 Prog <%s>: unknown command.
Description:An internal error in ucmmd has prevented it from successfully executing a program.
Solution:Save a copy of /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
923675 Resource "%s" could not be disabled: %s
Description:The scha_control() call to disable this ScalMountPoint resource failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
923712 CCR: Table %s on the joining node %s has the same version but different checksum as the copy in the current membership. The table on the joining node will be replaced by the one in the current membership.
Description:The indicated table on the joining node has the same version but different contents as the one in the current membership. It will be replaced by the one in the current membership.
Solution:This is an informational message, no user action is needed.
924059 Validate - MySQL database directory %s does not exist
Description:The defined database directory (-D option) does not exist.
Solution:Make sure that defined database directory exists.
924070 clq_scsi3: Ioctl MHIOCGRP_RESERVE returned failure (error = %d) but reservation key was found on quorum device %s
Description:The ioctl to place node's reservation key on the specified quorum device returned failure. This is unexpected behavior from device driver, multipathing driver or device firmware. Cluster software read the reservation key and found that node's key is present on the device.
Solution:No user action is required since the read check has succeeded.
924303 Failed to update the upgrade state in the CCR
Description:The upgrade process on the root node has failed to update the CCR.
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.
924578 File system associated with mount point %s is to be locally mounted in zone cluster %s. Local file systems cannot be specified with scalable service resources.
Description:HAStoragePlus detected an inconsistency in its configuration: the resource group has been specified as scalable, hence local file systems cannot be specified in the FilesystemMountPoints extension property.
Solution:Correct either the resource group type or remove the local file system from the FilesystemMountPoints extension property.
924950 No reference to any remote nodes: Not queueing event %lld.
Description:The cl_eventd does not have references to any remote nodes.
Solution:This message is informational only, and does not require user action.
925337 Stop of HADB database did not complete: %s.
Description:The resource was unable to successfully run the hadbm stop command either because it was unable to execute the program, or the hadbm command received a signal.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.
925379 resource group <%s> in illegal state <%s>, will not run %s on resource <%s>
Description:While creating or deleting a resource, the rgmd discovered the containing resource group to be in an unexpected state on the local node. As a result, the rgmd did not run the INIT or FINI method (as indicated in the message) on that resource on the local node. This should not occur, and may indicate an internal logic error in the rgmd.
Solution:The error is non-fatal, but it may prevent the indicated resource from functioning correctly on the local node. Try deleting the resource, and if appropriate, recreating it. If those actions succeed, then the problem was probably transitory. Since this problem may indicate an internal logic error in the rgmd, save a copy of the /var/adm/messages files on all nodes, and the output of clresourcegroup status +, clresourcetype show -v and clresourcegroup show -v +. Report the problem to your authorized Sun service provider.
925692 scha_control failed. %s: %s
Description:The scha_control (SCHA_RESOURCE_IS_RESTARTED) in the PMF action script supplied by DSDL failed.
Solution:Check syslog to see if there is any message from RGM which could explain why this failed.
925780 Creation of temporary file failed.
Description:Was not able to create a temporary keytab file used in thorough probing of the HA-KDC service.
Solution:Check the state of /etc/krb5.
925799 Failed to generate callback for path up event
Description:Cluster cannot generate a callback for the RDS module. Operation of RDS sockets might be affected.
Solution:If Reliable Datagram Sockets (RDS) is used by applications running on this cluster, contact your Sun Microsystems service representative to determine if a workaround or patch is available.
925953 reservation error(%s) - do_scsi3_register() 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.
926201 RGM aborting
Description:A fatal error has occurred in the rgmd. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
926749 Resource group nodelist is empty.
Description:Empty value was specified for the nodelist property of the resource group.
Solution:Any of the following situations might have occurred. Different user action is required for these different scenarios. 1) If a resourcegroup is created or updated, check the value of the nodelist property. If it is empty or not valid, then provide valid value by using clresourcegroup command. 2) For all other cases, treat it as an Internal error. Contact your authorized Sun service provider.
927042 Validation failed. SYBASE backup server startup file RUN_%s not found SYBASE=%s.
Description:Backup server was specified in the extension property Backup_Server_Name. However, Backup server startup file was not found. Backup server startup file is expected to be: $SYBASE/$SYBASE_ASE/install/RUN_<Backup_Server_Name>
Solution:Check the Backup server name specified in the Backup_Server_Name property. Verify that SYBASE and SYBASE_ASE environment variables are set property in the Environment_file. Verify that RUN_<Backup_Server_Name> file exists.
927088 Failed to analyze the device file %s: %s.
Description:HAStoragePlus was not able to analyze the device file.
Solution:Check that this device is valid.
927753 Fault monitor does not exist or is not executable : %s
Description:Fault monitor program specified in support file is not executable or does not exist. Recheck your installation.
Solution:Please report this problem.
927788 Validate - %s does not exist
Description:${INFORMIXSQLHOSTS does not exist.
Solution:Ensure that ${INFORMIXSQLHOSTS} exists.
927836 The file %s which the telemetry data service needs to execute is not executable
Description:A program or script of the telemetry data service could not execute because a file is not executable. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
927846 fatal: Received unexpected result <%d> from rpc.fed, aborting node
Description:A serious error has occurred in the communication between rgmd and rpc.fed while attempting to execute a VALIDATE method. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.
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.
928126 Membership : State machine for '%s' entered an invalid state %s; previous state was %s, previous event was %s.
Description:The membership state machine for this membership related to global cluster has entered an invalid state. The local global-cluster node will go down.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
928235 Validation failed. Adaptive_Server_Log_File %s not found.
Description:File specified in the Adaptive_Server_Log_File extension property was not found. The Adaptive_Server_Log_File is used by the fault monitor for monitoring the server.
Solution:Please check that file specified in the Adaptive_Server_Log_File extension property is accessible on all the nodes.
928339 Syntax error in file %s
Description:Specified file contains syntax errors.
Solution:Please ensure that all entries in the specified file are valid and follow the correct syntax. After the file is corrected, repeat the operation that was being performed.
928382 CCR: Failed to read table %s on node %s.
Description:The CCR failed to read the indicated table on the indicated node. The CCR will attempt to recover this table from other nodes in the cluster.
Solution:This is an informational message, no user action is needed.
928448 Failed to retrieve property "Resource_name".
Description:The name of the ScalMountPoint resource that represents the specified file system could not be retrieved.
Solution:Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.
928455 clcomm: Couldn't write to routing socket: %d
Description:The system prepares IP communications across the private interconnect. A write operation to the routing socket failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
928943 scha_cluster_get() failed: %s
Description:A call to scha_cluster_get() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
929100 No permission for others to execute %s.
Description:The specified path does not have the correct permissions as expected by a program.
Solution:Set the permissions for the file so that it is readable and executable by others (world).
929252 Failed to start HA-NFS system fault monitor.
Description:Process monitor facility has failed to start the HA-NFS system fault monitor.
Solution:Check whether the system is low in memory or the process table is full and correct these problems. If the error persists, use scswitch to switch the resource group to another node.
929266 clq_sq_disk: callback_failfast: succeeded in reading keys on quorum device %s after some failures.
Description:The quorum subsystem was able to read keys from a quorum device after several failures. This type of erroneous behavior might occur because of unexpected transient errors from the device driver or disk.
Solution:Check for firmware or driver updates.
929697 fatal: Got error <%d> trying to read CCR when <%s> <%s> resource <%s>; aborting node
Description:Rgmd failed to read updated resource 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.
929846 Error getting service names of class (%s) from DCS.
Description:An error prevented DCS service names from being retrieved.
Solution:Determine whether the node is in cluster mode. Contact your authorized Sun service provider for assistance in diagnosing the problem.
930037 sigignore(3C) of signal SIG%s failed for child (pid %d) forked by pmmd: error %s
Description:The child that was forked by the pmmd daemon was unable to set the signal disposition for a signal to SIG_IGN, because the sigignore(3C) function failed. The message contains the system error. The child that was forked by the pmmd daemon will not set up its signal handling settings as specified.
Solution:Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Sun service provider.
930059 %s: %s.
Description:HA-SAP failed to access to a file. The file in question is specified with the first '%s'. The reason it failed is provided with the second '%s'.
Solution:Check and make sure the file is accessible via the path list.
930073 getzonenamebyid failed: %s
Description:The getzonenamebyid failed for the specified reason.
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.
930151 Found another active instance of rtreg proxy server. Exiting rtreg_serverd.
Description:The rtreg server program found another active rtreg program already in execution.
Solution:This is an information message. No user action is required.
930284 SCSLM fopen <%s> error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
930322 reservation fatal error(%s) - malloc() error
Description:The device fencing program has been unable to allocate required memory.
Solution:Memory usage should be monitored on this node and steps taken to provide more available memory if problems persist.
930339 cl_event_bind_channel(): %s
Description:The cl_eventd 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.
930535 Ignoring string with misplaced quotes in the entry for %s
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 VALUE may be a single-quoted or double-quoted string. The string itself may not contain any quotes.
Solution:Please check the environment file and correct the syntax errors.
930636 Sun Cluster boot: reset vote returns $res
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
930851 ERROR: process_resource: resource <%s> is pending_fini but no FINI method is registered
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
931362 RGMD XDR Buffer Shortfall while encoding return arguments API num = %d. Will retry
Description:A non-fatal error occurred while rgmd daemon was marshalling arguments for a remote procedure call. The operation will be retried 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.
931543 Failed to get zone cluster name from zone cluster id %d,error = %d
Description:There was a failure to map a zone cluster ID to a zone cluster name. This can happen if the zone cluster with the corresponding id has been removed from the system.
Solution:Verify if there was any administration related to a zone cluster that was just removed. If not, contact your authorized Sun service provider to determine whether a workaround or patch is available.
931652 scha_cluster_open failed with %d
Description:Call to initialize the cluster information handle failed. The second part of the message gives the error code.
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.
931662 Verifying the SUNW.qfs resources metadata server status.
Description:This is a notification message that the handler is going to verify the status of metadata servers of SUNW.qfs resources.
Solution:This is an informational message; no user action is needed.
931734 The %s value should be greater than %d seconds: Hence ignoring this value from %s file at line %d.
Description:The zone handler detected a bad value for the specified tunable in the specified configuration file.
Solution:Fix the specified tunable value so that it meets the restrictions.
931921 Unable to allocate memory at door server
Description:The rgmd process has failed to allocate new memory, most likely because the system has run out of swap space.
Solution:Investigate the cause of swap space depletion and correct the problem, if possible. Reboot your system. If the problem recurs, you might need to increase swap space by configuring additional swap devices. See swap(1M) for more information.
932126 CCR: Quorum regained.
Description:The cluster lost quorum at sometime after the cluster came up, and the quorum is regained now.
Solution:This is an informational message, no user action is needed.
933582 Bringing the resource groups containing SUNW.qfs resources offline.
Description:This is a notification message that zone halt handler is bringing the SUNW.qfs resource groups offline.
Solution:This is an informational message; no user action is needed.
934271 The directory %s needed by the telemetry data service does not exist
Description:A program or script of the telemetry data service could not execute because a directory does not exist. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
934822 %s: fsync_core_files: %s fsync <%s> failed, error %s
Description:The pmmd was unable to sync the core file dumped by a monitored process. The pmmd will continue to monitor the process, but the pmmd has missed information of interest.
Solution: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.
934965 Error: Can't stop ${SERVER} outside of run control environment.
Description:The initrgm init script was run manually (not automatically by init(1M)). This is not supported by Sun Cluster software. The "initrgm stop" command was not successful. No action was performed.
Solution:This is an informational message; no user action is needed.
935088 Error %d starting quota for %s
Description:The /usr/sbin/quotaon command failed for the UFS mount point specified by %s.
Solution:Contact your Sun service representative.
935470 validate: EnvScript not set but it is required
Description:The parameter EnvScript is not set in the parameter file
Solution:set the variable EnvScript in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.
935729 <%s>:<%s>: Core location couldn't be configured for method <%s>.
Description:The rpc.fed was unable to modify coredump settings for the indicated method.
Solution:Low memory might be a transient error. If it persists, rebooting might help. If that fails to help, swap space might need to be increased. If it is a popen() failure, refer to coreadm(1M)/popen(3C), or contact your authorized Sun service provider.
937669 CCR: Failed to update table %s.
Description:The CCR data server failed to update the indicated table.
Solution:There may be other related messages on this node, which 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.
937795 Nodelist of RG "%s" is empty.
Description:The node list of the resource group that contains the specified metadata server resource is empty.
Solution:Ensure that the node list of the resource group that contains the metadata server resource is correct. 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.
938083 match_online_key failed strdup for (%s)
Description:Call to strdup failed. The "strdup" man page describes possible reasons.
Solution:Install more memory, increase swap space or reduce peak memory consumption.
938180 INTERNAL ERROR: Failed to validate the zone cluster '%s'. Check whether the current cluster version supports zone clusters.
Description:An error occurred while validating the specified zone cluster name.
Solution:Check the zone cluster support on the current running version of cluster. If the version of cluster software does support zone clusters, contact your authorized Sun service provider to determine whether a workaround or patch is available.
938189 rpc.fed: program not registered or server not started
Description:The rpc.fed daemon was not correctly initialized, or has died. This has caused a step invocation failure, and may cause the node to reboot.
Solution:Check that the Solaris Clustering software has been installed correctly. Use ps(1) to check if rpc.fed is running. If the installation is correct, the reboot should restart all the required daemons including rpc.fed.
938318 Method <%s> failed on resource <%s> in resource group <%s> [exit code <%d>, time used: %d%% of timeout <%d seconds>] %s
Description:A resource method exited with a non-zero exit code; this is considered a method failure. Depending on which method is 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. Note that failures of FINI, INIT, BOOT, and UPDATE methods do not cause the associated administrative actions (if any) to fail.
Solution:Consult resource type documentation to diagnose the cause of the method failure. Other syslog messages occurring just before this one might indicate the reason for the failure. If the failed method was one of START, PRENET_START, MONITOR_START, STOP, POSTNET_STOP, or MONITOR_STOP, you can issue a clresourcegroup command to bring resource groups onto desired primaries after fixing the problem that caused the method to fail. If the failed method was UPDATE, note that the resource might not take note of the update until it is restarted. If the failed method was FINI, INIT, or BOOT, you may need to initialize or de-configure the resource manually as appropriate on the affected node.
938626 All PostgreSQL non-attached IPC shared memory segments removed
Description:Remaining IPC shared memory segments have been removed. These segements are a leftover of the previous PostgreSQL instance.
Solution:No user action is required.
938701 Could not kill the telemetry data service monitor
Description:The monitor program of the telemetry data service could not be stopped. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
938773 Pid_Dir_Path %s is not readable: %s.
Description:The path which is listed in the message is not readable. The reason for the failure is also listed in the message.
Solution:Make sure the path which is listed exists. Use the HAStoragePlus resource in the same resource group of the HA-SAPDB resource. So that the HA-SAPDB method have access to the file system at the time when they are launched.
939122 startebs - %s was manually started
Description:The specified Oracle E-Business Suite component has been started manually.
Solution:No user action is required. Informational message.
939198 Validation failed. The ucmmd daemon will not be started on this node.
Description:At least one of the modules of Sun Cluster support for Oracle OPS/RAC returned error during validation. The ucmmd daemon will not be started on this node and this node will not be able to run Oracle OPS/RAC.
Solution:This message can be ignored if this node is not configured to run Oracle OPS/RAC. Examine other syslog messages logged at about the same time to determine the configuration errors. Examine the ucmm reconfiguration log file /var/cluster/ucmm/ucmm_reconf.log. Correct the problem and reboot the node. If problem persists, save a copy of the of the log files on this nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
939374 CCR: Failed to access cluster repository during synchronization. ABORTING node.
Description:This node failed to access its cluster repository when it first came up in cluster mode and tried to synchronize its repository with other nodes in the cluster.
Solution:This is usually caused by an unrecoverable failure such as disk failure. There may be other related messages on this node, which may help diagnose the problem. If the root disk on the afflicted node has failed, then it needs to be replaced. If the root disk is full on this node, boot the node into non-cluster mode and free up some space by removing unnecessary files. Contact your authorized Sun service provider for assistance.
939575 Method <%s> on resource <%s>, node <%s>: RPC connection error.
Description:An attempted method execution failed, due to an RPC connection problem. This failure is considered a method failure. 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; or it might cause an attempted edit of a resource group or its resources 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 same error recurs, you might have to reboot the affected node. After the problem is corrected, the operator can choose to issue a clresourcegroup command to bring resource groups onto desired primaries, or retry the resource group update operation.
939614 Incorrect resource group properties for RAC framework resource group %s. Value of RG_mode must be Scalable.
Description:The RAC framework resource group must be a scalable resource group. The RG_mode property of this resource group must be set to 'scalable'. RAC framework will not function correctly without this value.
Solution:Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.
939851 Failed to open contract ctlfile %s: %s
Description:Not able to open the contract control file.
Solution:Check the contract man page to know more about the error. Also make sure the basic contract functionalities are working. Contact your SUN vendor for more help.
940350 Found another active instance of pnm proxy server. Exiting pnm_serverd.
Description:The pnm server program found another active pnm program already in execution.
Solution:This is an information message. No user action is required.
940545 scnetapp fatal error - Unable to open output file
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
940924 Validate_replication_rs - MySQL resource %s is the same as the MySQL replication resource %s
Description:The defined real MySQL resource (-r option) must not be the same resource as the MySQL replication resource -R
Solution:Make sure that defined resource names differ.
940969 Failed to remove the private IP address for a zone
Description:The private IP address assigned to a zone was not unplumbed correctly.
Solution:The private IP address assigned to the zone is used for private IP communication for the zone. So, this feature may not work as expected as a result of this error. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
941071 Cannot retrieve service <%s>.
Description:The data service cannot retrieve the required service.
Solution:Check the service entries on all relevant cluster nodes.
941267 Cannot determine command passed in: <%s>.
Description:An invalid pathname, displayed within the angle brackets, was passed to a libdsdev routine such as scds_timerun or scds_pmf_start. This could be the result of misconfiguring the name of a START or MONITOR_START method or other property, or a programming error made by the resource type developer.
Solution:Supply a valid pathname to a regular, executable file.
941367 open failed: %s
Description:Failed to open /dev/console. The "open" man page describes possible error codes.
Solution:No user action is required. The ucmmd will exit.
941416 One or more of the SUNW.HAStoragePlus resources that this resource depends on is not online anywhere. Failing validate method.
Description:The HAStoragePlus resource this resource needs is not online anywhere in the cluster.
Solution:Bring the SUNW.HAStoragePlus resource online before creating the application resource that depends on them and then try the command again.
941891 Validate_sbp - MySQL resource %s is not configured in one of the specified resource groups %s
Description:The defined real MySQL resource is not configured in the specified resource group.
Solution:Make sure that defined resource is configured in the real MySQL resource group.
941997 Validate - Userid %s is not a valid userid
Description:The specified userid does not exist within /etc/passwd.
Solution:Ensure that the userid has been added.
942076 Ifconfig proxy : wait_for_signals() : sigwaitinfo returned %d. Exiting.
Description:ifconfig proxy program has encountered a failed sigwaitinfo(3RT) 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.
942679 Failed to retrieve the resource property %s of %s: %s.
Description:An error occurred while determining the resource property of specified resource.
Solution:Investigate possible RGM errors or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem with copy of the /var/adm/messages files on all nodes.
942844 Resource <%s> of Resource Group <%s> failed sanity check on node <%s>
Description:Message logged for failed scha_control sanity check methods on specific node.
Solution:No user action required.
942855 check_mysql - Couldn't do show tables for defined database %s (%s)
Description:The faultmonitor can't issue show tables for the specified database.
Solution:Either was MySQL already down or the fault monitor user does not have the right permission. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges. Check also the MySQL log files for any other errors.
942859 qdmd: An error occurred while reading quorum reservation key from quorum device %s
Description:The quorum device monitoring daemon encountered an error while performing the quorum_read_reservations operation on the indicated quorum device.
Solution:Unconfigure the quorum device and reconfigure it. If that fails, replace the quorum device.
943168 pmf_monitor_suspend: pmf_add_triggers: %s
Description:The rpc.pmfd server was not able to resume the monitoring of a process, and the monitoring of this process has been aborted. An error message is output to syslog.
Solution:Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
943599 %z Failed to retrieve the resource handle for %s while querying for property %s: %s.
Description:The query for a property failed. The reason for failure is given in the message.
Solution:Save a copy of the /var/adm/messages file on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.
943746 Function: validate - Zonebrand for zone %s is configured as %s, but the zone is configured as brand type %s.
Description:Zonebrand is set to "solaris8" or "solaris9". But the Zone is not configured as brand type solaris8 or solaris9 according to zonecfg info.
Solution:Review the components configuration file and make sure the variable Zonebrand defines "solaris8" or "solaris9" only for a Zone that got really setup with brand type "solaris8" or "solaris9".
944068 clcomm: validate_policy: invalid relationship moderate %d high %d pool %d
Description:The system checks the proposed flow control policy parameters at system startup and when processing a change request. The moderate server thread level cannot be higher than the high server thread level.
Solution:No user action required.
944096 Validate - This version of MySQL <%s> is not supported with this data service
Description:An unsupported MySQL version is being used.
Solution:Make sure that supported MySQL version is being used.
944121 Incorrect permissions set for %s.
Description:This file does not have the expected default execute permissions.
Solution:Reset the permissions to allow execute permissions using the chmod command.
944181 HA: exception %s (major=%d) from flush_to().
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.
944630 Membership: Unable to create membership callback threadpool.
Description:The membership callback threadpool 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.
944973 Unrecoverable error: unable to read contract events.
Description:The libclcontract code is permanently unable to read contract events. The process that is using libclcontract will exit.
Solution: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.
945235 Failed to execute vxprint command successfully : %s.
Description:An error occurred when the command 'vxprint' was run.
Solution:Ensure that the VxVM packages are installed correctly and check the syslog messages. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
945739 %s has been removed from %s. Make sure that all HA IP addresses hosted on %s are moved.
Description:We do not allow removing of an adapter from an IPMP group. The correct way to DR an adapter is to use if_mpadm(1M). Therefore we notify the user of the potential error.
Solution:This message is informational; no user action is needed if the DR was done properly (using if_mpadm).
946447 The path of mapped global device file %s does not exists in zone cluster %s : %s.
Description:The specified global device path entry does not exist in the zone cluster even though the device is configured.
Solution:Check if the device configuration is done correctly. Reboot the zone cluster and see whether the problem is resolved. If the problem persists, contact your authorized Sun service provider.
946660 Failed to create sap state file %s:%s Might put sap resource in stop-failed state.
Description:If SAP is brought up outside the control of Sun Cluster, HA-SAP will create the state file to signal the stop method not to try to stop sap via Sun Cluster. Now if SAP was brought up outside of Sun Cluster, and the state file creation failed, then the SAP resource might end in the stop-failed state when Sun Cluster tries to stop SAP.
Solution:This is an internal error. No user action needed. Save the /var/adm/messages from all nodes. Contact your authorized Sun service provider.
946807 Only a single path to the WLS Home directory has to be set in Confdir_list
Description:Each WLS resource can handle only a single installation of WLS. You cannot create a resource to handle multiple installations.
Solution:Create a separate resource for making each installation of WLS Highly Available.
946839 Failed to open the pbundle event listener FD: %s
Description:Cannot open the contract file for event listening
Solution:Check the contract man page to know more about the error. Also make sure the basic contract functionalities are working. Contact your SUN vendor for more help.
947007 Error initializing the cluster version manager (error %d).
Description:This message can occur when the system is booting if incompatible versions of cluster software are installed.
Solution:Verify that any recent software installations completed without errors and that the installed packages or patches are compatible with the rest of the installed software. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.
947217 Reading root node of second partition from CCR failed
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.
947401 reservation error(%s) - Unable to open device %s, errno %d
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.
947719 Validate - %s/bin/oninit does not exist
Description:The oninit was not found in ${INFORMIXDIR}/bin.
Solution:Ensure that ${INFORMIXDIR} is the directory path where the Informix files are installed.
948424 Stopping NFS daemon %s.
Description:The specified NFS daemon is being stopped by the HA-NFS implementation.
Solution:This is an informational message. No user action is required.
948847 ucm_callback for start_trans generated exception %d
Description:ucmm callback for start transition failed. Step may have timed out.
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.
948865 Unblock parent, write errno %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
948872 Errors detected in %s. Entries with error and subsequent entries may get ignored.
Description:The custom action file that is specified contains errors which need to be corrected before it can be processed completely. This message indicates that entries after encountering an error may or may not be accepted.
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. If all errors are not corrected, the acceptance of entries from this file may not be guaranteed.
949565 reservation error(%s) - do_scsi2_tkown() error for disk %s
Description:The device fencing program has encountered errors while trying to access a device. All retry attempts have failed.
Solution:The action which failed is a scsi-2 ioctl. These can fail if there are scsi-3 keys on the disk. To remove invalid scsi-3 keys from a device, use 'scdidadm -R' to repair the disk (see scdidadm man page for details). If there were no scsi-3 keys present on the device, then this error is 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, 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, you can retry the desired action.
949621 Derby data service requested a failover
Description:The Derby data service requested a failover.
Solution:This message is informational; no user action needed.
949924 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.
949937 Out of memory.
Description:A process has failed to allocate new memory, most likely because the system has run out of swap space.
Solution:The problem will probably be cured by rebooting. If the problem reoccurs, you might need to increase swap space by configuring additional swap devices. See swap(1M) for more information.
949979 Validation failed. Oracle_config_file %s not found
Description:Unable to locate the file specified in Oracle_config_file property. This message is given by the validate method, when creating the resource for UNIX Distributed Lock Manager or modifying the property value. This file created when ORCLudlm package is installed on the node.
Solution:Verify the file name specified in Oracle_config_file property. Verify installation of ORCLudlm package on this node.
950747 resource %s monitor disabled.
Description:This is a notification from the rgmd that the operator has disabled monitoring on a resource. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
951501 CCR: Could not initialize CCR data server.
Description:The CCR data server could not initialize on this node. This usually happens when the CCR is unable to read its metadata entries on this node. There is a CCR data server per cluster node.
Solution:There may be other related messages on this node, which may help diagnose this problem. If the root disk failed, it needs to be replaced. If there was cluster repository corruption, then the cluster repository needs to be restored from backup or other nodes in the cluster. Boot the offending node in -x mode to restore the repository. The cluster repository is located at /etc/cluster/ccr/.
951520 Validation failed. SYBASE ASE runserver file RUN_%s not found SYBASE=%s.
Description:Sybase Adaptive Server is started by specifying the Adaptive Server "runserver" file named RUN_<Server Name> located under $SYBASE/$SYBASE_ASE/install. This file is missing.
Solution:Verify that the Sybase installation includes the "runserver" file and that permissions are set correctly on the file. The file should reside in the $SYBASE/$SYBASE_ASE/install directory.
951634 INTERNAL ERROR CMM: clconf_get_quorum_table() returned error %d.
Description:The node encountered an internal error during initialization of the quorum subsystem object.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
951733 Incorrect usage: %s.
Description:The usage of the program was incorrect for the reason given.
Solution:Use the correct syntax for the program.
951914 Error: unable to initialize CCR.
Description:The cl_apid was unable to initialize the CCR during startup. This error will prevent the cl_apid from starting.
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.
952006 received signal %d: exiting
Description:The cl_apid daemon is terminating abnormally due to receipt of a signal.
Solution:No user action is required.
952226 Error with allow_hosts or deny_hosts
Description:The allow_hosts or deny_hosts for the CRNP service contains an error. 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.
952237 Method <%s>: unknown command.
Description:An internal error has occurred in the interface between the rgmd and fed daemons. This in turn will cause a method invocation to fail. 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.
952465 HA: exception adding secondary
Description:A failure occurred while attempting to add a secondary provider for an HA service.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
952811 Validation failed. CONNECT_STRING not in specified format
Description:CONNECT_STRING property for the resource is specified in the correct format. The format could be either 'username/password' or '/' (if operating system authentication is used).
Solution:Specify CONNECT_STRING in the specified format.
952827 Starting Oracle instance %s
Description:Oracle instance startup is in progress.
Solution:No user action is required. Informational message.
952942 Retrying retrieve of resource information: %s.
Description:An update to resource configuration occurred while resource properties were being retrieved.
Solution:This is an informational message, no user action is needed.
952974 %s: cannot open directory %s
Description:The ucmmd was unable to open the directory identified. Contact your authorized Sun service provider for assistance in diagnosing the problem.
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.
953277 monitor_check: the failover requested by scha_control for resource <%s>, resource group <%s>, node <%s> was not completed because of error: <%s>
Description:A scha_control(1HA,3HA) GIVEOVER attempt failed, due to the error listed.
Solution:Examine other syslog messages on all cluster members that occurred about the same time as this message, to see if the problem that caused the error can be identified and repaired.
953470 SCSLM file <%s> duplicate project name
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
953614 %s: Could not signal all contract members: %s
Description:During the stopping of the resource, could not clear all the contracts that belong to the services under that resource.
Solution:This should not cause much problem. Contact your SUN vendor for more help.
953642 Server is not running. Calling shutdown abort to clear shared memory (if any)
Description:Informational message. Oracle server is not running. However if Oracle processes are aborted without clearing shared memory, it can cause problems when starting Oracle server. Clearing leftover shared memory if any.
Solution:No user action is required.
953818 There are no disks to monitor
Description:An attempt to start the scdpmd failed.
Solution:The node should have a least a disk. Check the local disk list with the scdidadm -l command.
954103 ${PROG}: WARNING: ${file} does not include a ${db} entry
Description:The nsswitch.conf file on the zone cluster does not have this entry already. A new entry has been added for this.
Solution:No user action is required.
954788 cl_pnmd has requested an immediate failover of all scalable resources dependent on IPMP group %s
Description:All network interfaces in the IPMP group have failed. All of these failures were detected by the hardware drivers for the network interfaces, and not by in.mpathd probes. In such a situation, cl_pnmd requests all scalable resources to fail over to another node without any delay.
Solution:No user action is needed. This is an informational message that indicates that the scalable resources will be failed over to another node immediately.
954831 Start of HADB node %d did not complete: %s.
Description:The resource was unable to successfully run the hadbm start command either because it was unable to execute the program, or the hadbm command received a signal.
Solution:This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.
955269 Mountpoint %s in zone %s falls outside its zone root.
Description:HAStoragePlus detected that the local zone mount point falls outside of zone root. HAStoragePlus avoid such mount points for security reasons.
Solution:Change the specified local zone mount point so that it falls inside the zone root.
955366 scvxvmlg error - stat(%s) failed with errno %d
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
955441 The file %s which the derby data service needs to execute is not executable
Description:A program or script of the derby data service could not execute because a file is not executable. This should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
955633 Memory allocation failure
Description:Unable to allocate memory.
Solution:No user action required.
955895 Function: validate - ServiceStartCommand (%s) not a fully qualified path.
Description:The command specified for variable ServiceStartCommand 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 ServiceStartCommand, 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.
955930 Attempt to connect from addr %s port %d.
Description:There was a connection from the named IP address and port number (> 1024) which means that a non-privileged process is trying to talk to the PNM daemon.
Solution:This message is informational; no user action is needed. However, it would be a good idea to see which non-privileged process is trying to talk to the PNM daemon and why?
956004 PNM proxy : block_all_signals() : thr_sigsetmask returned %d. Exiting.
Description:pnm proxy program has encountered a failed thr_sigsetmask(3C) 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.
956110 Restart operation failed: %s.
Description:This message indicated that the rgm didn't process a restart request, most likely due to the configuration settings.
Solution:This is an informational message.
956324 Failed to do dual-partition upgrade tasks on second partition
Description:During a dual-partition upgrade in a live upgrade scenario, some dual-partition upgrade related tasks have failed. Upgrade process has stopped and cannot proceed.
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.
956501 Issuing a failover request.
Description:This message indicates that the fault monitor is about to make a failover request to the RGM. If the request fails, refer to the syslog messages that appear after this message.
Solution:This is an informational message, no user action is required.
956821 cl_execd: Could not allocate memory size = %d
Description:Could not allocate memory. Node is too low on memory.
Solution:cl_execd 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.
957086 Prog <%s> failed to execute step <%s> - error=<%d>
Description:ucmmd failed to execute a step.
Solution:Examine other syslog messages occurring at about the same time to see if the problem can be identified and if it recurs. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.
957314 Cannot import '%s' : pool may be in use from other system.
Description:Self explanatory.
Solution:Check the cluster node that has imported the specified pool. Try to export the zpool again by issuing "zpool export -f <poolname>". If the problem persists, contact your authorized Sun service provider.
957535 Smooth_shutdown flag is not set to TRUE. The WebLogic Server will be shutdown using sigkill.
Description:This is a information message. The Smooth_shutdown flag is not set to true and hence the WLS will be stopped using SIGKILL.
Solution:No user action is required. If the smooth shutdown has to be enabled then set the Smooth_shutdown extension property to TRUE. To enable smooth shutdown the username and password that have to be passed to the "java weblogic.Admin .." has to be set in the start script. Refer to your Admin guide for details.
958280 Invalid fsck device path %s detected for mount point %s %s zone cluster %s.
Description:The specified fsck device path is not valid.
Solution:Check the path and correct the entry with a valid global device path.
958395 Validate - qconf file does not exist or is not executable at %s/qconf
Description:The binary file qconf can not be found, or is not executable.
Solution:Confirm the binary file ${SGE_ROOT}/bin/<arch>/qconf both exists in that location, and is executable.
958832 INTERNAL ERROR: monitoring is enabled, but MONITOR_STOP method is not registered for resource <%s>
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
958888 clcomm: Failed to allocate simple xdoor client %d
Description:The system could not allocate a simple xdoor client. This can happen when the xdoor number is already in use. This message is only possible on debug systems.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
959261 Error parsing node status line (%s).
Description:The resource had an error while parsing the specified line of output from the hadbm status --nodes command.
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. Otherwise contact your authorized Sun service provider to determine whether a workaround or patch is available.
959384 Possible syntax error in hosts entry in %s.
Description:Validation callback method has failed to validate the hostname list. There may be syntax error in the nsswitch.conf file.
Solution:Check for the following syntax rules in the nsswitch.conf file. 1) Check if the lookup order for "hosts" has "files". 2) "cluster" is the only entry that can come before "files". 3) Everything in between '[' and ']' is ignored. 4) It is illegal to have any leading whitespace character at the beginning of the line; these lines are skipped. Correct the syntax in the nsswitch.conf file and try again.
959610 Property %s should have only one value.
Description:A multi-valued (comma-separated) list was provided to the scrgadm command for the property, while the implementation supports only one value for this property.
Solution:Specify a single value for the property on the scrgadm command.
959930 Desired_primaries must equal the number of nodes in Nodelist.
Description:The resource group properties desired_primaries and maximum_primaries must be equal and they must equal the number of Sun Cluster nodes in the nodelist of the resource group.
Solution:Set the desired and maximum primaries to be equal and to the number of Sun Cluster nodes in the nodelist.
959964 Validate - Concurrent Manager password not set
Description:A password used to start and stop the Concurrent Manager was not set.
Solution:Either define the password within /opt/SUNWscebs/cmg/cmg_config as the value to the APPS_PASSWD keyword or define the password within the restricted file /opt/SUNWscebs/.${APP_SID}_passwd that is only readable by root.
960228 HADB node %d for host %s does not match any Sun Cluster interconnect hostname.
Description:The HADB database must be created using the hostnames of the Sun Cluster private interconnect, the hostname for the specified HADB node is not a private cluster hostname.
Solution:Recreate the HADB and specify cluster private interconnect hostnames.
960344 ERROR: process_resource: resource <%s> is pending_init but no INIT method is registered
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
960359 Diskgroup (%s) is available
Description:The disk group is available. This message is an informational message.
Solution:No user action is required.
960472 Ifconfig proxy Unable to create thread, errno = %d. Exiting\n.
Description:The ifconfig proxy program encountered a failure while executing thr_create(3C).
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
960862 (%s) sigaction failed: %s (UNIX errno %d)
Description:The udlm has failed to initialize signal handlers by a call to sigaction(2). The error message indicates the reason for the failure.
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.
960870 Command %s timed out. Will continue to start up %s.
Description:The listed command failed to complete. HA-SAPDB will continue to start up SAPDB.
Solution:Informational message. No user action is required.
961070 SCSLM pool_set_binding <%s> zone <%d> error PO_FAIL
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
961669 Error in processing and creating fmri
Description:Cannot process the smf fmri under the resource by sc delegated restarter.
Solution:The previous messages that gets displayed should help. Contact the SUN vendor for more info.
962775 Node %u attempting to join cluster has incompatible cluster software.
Description:A node is attempting to join the cluster but it is either using an incompatible software version or is booted in a different mode (32-bit vs. 64-bit).
Solution:Ensure that all nodes have the same clustering software installed and are booted in the same mode.
963000 Devfsadm successfully configured did
Description:Devfsadm command successfully configured did devices.
Solution:This is an informational message, no user action is needed.
963068 Successfully switched over the resource group '%s' of resource '%s' from this node.
Description:The zone halt handler successfully switched over the specified SUNW.qfs resource group.
Solution:This is an informational message; no user action is needed.
963309 Monitor for sckrb5 successfully stopped. PMF will restart it.
Description:The HA-KDC's update method was able to stop the monitor.
Solution:PMF will restart the monitor, so no intervention is required.
963375 gethostbyname failed for (%s)
Description:Failed to get information about a host. The "gethostbyname" man page describes possible reasons.
Solution:Make sure entries in /etc/hosts, /etc/nsswitch.conf and /etc/netconfig are correct to get information about this host.
963465 fatal: rpc_control() failed to set automatic MT mode; aborting node
Description:The rgmd failed in a call to rpc_control(3N). This error should never occur. If it did, it would cause the failure of subsequent invocations of scha_cmds(1HA) and scha_calls(3HA). This would most likely lead to resource method failures and prevent RGM reconfigurations from occurring. The rgmd will produce a core file and will force the node to halt or reboot.
Solution:Examine other syslog messages occurring at about the same time to see if the source of 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 the problem. Reboot the node to restart the clustering daemons.
963755 lkcm_cfg: 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.
964072 Unable to resolve %s.
Description:The data service has failed to resolve the host information.
Solution:If the logical host and shared address entries are specified in the /etc/inet/hosts file, check that these entries are correct. If this is not the reason, then check the health of the name server. For more error information, check the syslog messages.
964083 t_open (open_cmd_port) failed
Description:Call to t_open() failed. The "t_open" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
964399 udlm seq no (%d) does not match library's (%d).
Description:Mismatch in sequence numbers between udlm and the library code is causing an abort.
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.
964521 Failed to retrieve the resource handle: %s.
Description:An API operation on the resource has failed.
Solution:For the resource name, check the syslog tag. For more details, check the syslog messages from other components. If the error persists, reboot the node.
964829 Failed to add events to client
Description:The cl_apid experienced an internal error that prevented proper updates to a CRNP client.
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.
965174 Function: validate - %s configured with autoboot true, it needs to be false
Description:The referenced zone is configured with autoboot = true. This option needs to be set to false.
Solution:Configure the autoboot variable of the configured zone to false. You need to run the zonecfg command to complete this task.
965261 HTTP GET probe used entire timeout of %d seconds during connect operation and exceeded the timeout by %d seconds. Attempting disconnect with timeout %d
Description:The probe used it's entire timeout time to connect to the HTTP port.
Solution:Check that the web server is functioning correctly and if the resources probe timeout is set too low.
965278 The probe has requested an immediate failover. Attempting to failover this resource group subject to other property settings.
Description:An immediate failover will be performed.
Solution:This is an informational message, no user action is needed.
965299 %s:scslm_stop. FE_SLM_ERROR %d
Description:Resource group is under SC SLM control and an SLM error occurred. Check fed SLM errors for more details.
Solution:Move RG_SLM_type to manual and restart the resource group.
965554 scnetapp fatal error - CCR references are not NULL
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
965722 Failed to retrieve the resource group Failback property: %s.
Description:HAStoragePlus was not able to retrieve the resource group Failback property from the CCR.
Solution:Check the cluster configuration. If the problem persists, contact your authorized Sun service provider.
965873 CMM: Node %s (nodeid = %d) with votecount = %d added.
Description:The specified node with the specified votecount has been added to the cluster.
Solution:This is an informational message, no user action is needed.
966112 UNRECOVERABLE ERROR: Sun Cluster boot: /usr/cluster/lib/sc/failfastd not found
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
966335 SAP enqueue server is not running. See %s/ensmon%s.out.%s for output.
Description:The SAP enqueue server is down. See the output file listed in the error message for details. The data service will fail over the SAP enqueue server.
Solution:No user action is needed.
966670 did discovered faulty path, ignoring: %s
Description:The scdidadm has discovered a suspect logical path under /dev/rdsk. It will not add it to subpaths for a given instance.
Solution:Check to see that the symbolic links under /dev/rdsk are correct.
966682 WARNING: Share path %s may be on a root file system or any file system that does not have an /etc/vfstab entry.
Description:The path indicated is not on a non-root mounted file system. This could be damaging as upon failover NFS clients will start seeing ESTALE err's. However, there is a possibility that this share path is legitimate. The best example in this case is a share path on a root file systems but that is a symbolic link to a mounted file system path.
Solution:This is a warning. However, administrator must make sure that share paths on all the primary nodes access the same file system. This validation is useful when there are no HAStorage/HAStoragePlus resources in the HA-NFS RG.
966842 in libsecurity unknown security flag %d
Description:This is an internal error which shouldn't happen. An error message is output to syslog.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
966894 init_signal_handlers sigfillset: %s
Description:Internal error.
Solution:Save the syslog messages file. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
967050 Validation failed. Listener binaries not found ORACLE_HOME=%s
Description:Oracle listener binaries not found under ORACLE_HOME. ORACLE_HOME specified for the resource is indicated in the message. HA-Oracle will not be able to manage Oracle listener if ORACLE_HOME is incorrect.
Solution:Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.
967080 This resource depends on a HAStoragePlus resouce that is not online on this node. Ignoring validation errors.
Description:The resource depends on a HAStoragePlus resource. Some of the files required for validation checks are not accessible from this node, because HAStoragePlus resource in not online on this node. Validations will be performed on the node that has HAStoragePlus resource online. Validation errors are being ignored on this node by this callback method.
Solution:Check the validation errors logged in the syslog messages. Please verify that these errors are not configuration errors.
967139 IO to file-system %s, through mountpoint %s failed due to UCMM being not in good state.
Description:The UCMM is hanging and is not responding.
Solution:Determine whether another problem with the cluster caused the UCMM to hang. Bring online the UCMM again and restart the ScalMountPoint resource.
967417 validate_options - Fatal: SGE_CELL %s/%s not a directory
Description:The ${SGE_ROOT}/${SGE_CELL} combination variable produces a value whose location does not exist.
Solution:The SGE_CELL value is decided when the Sun Grid Engine data service is installed. The default value is 'default' and can be configured in /opt/SUNWscsge/util/sge_config. Run sge_remove and then sge_register after verifying the value in /opt/SUNWscsge/util/sge_config is correct.
967645 Starting the JSAS Domian Admin Server under pmf
Description:This is just an info message indicating that the Sun Cluster PMF is now starting the Domain Admin Server.
Solution:No user action is required.
967970 Modification of resource <%s> failed because none of the nodes on which VALIDATE would have run are currently up
Description:In order to change the properties of a resource whose type has a registered VALIDATE method, the rgmd must be able to run VALIDATE on at least one node. However, all of the candidate nodes are down. "Candidate nodes" are either members of the resource group's Nodelist or members of the resource type's Installed_nodes list, depending on the setting of the resource's Init_nodes property.
Solution:Boot one of the resource group's potential masters and retry the resource change operation.
968152 Membership : Node '%s' (node id %d) of cluster '%s' died.
Description:A node has left the zone cluster.
Solution:This message is for information. No user action is required.
968427 Applied dual-partition upgrade changes successfully
Description:Changes required for Dual Partition Software Swap were done successfully on this node.
Solution:This is an informational message, no user action is needed.
968557 Could not unplumb any ipaddresses.
Description:Failed to unplumb any ip addresses. The resource cannot be brought offline. Node will be rebooted by Sun cluster.
Solution:Check the syslog messages from other components for possible root cause. Save a copy of /var/adm/messages and contact Sun service provider for assistance in diagnosing and correcting the problem.
968853 scha_resource_get error (%d) when reading system property %s
Description:Error occurred in API call scha_resource_get.
Solution:Check syslog messages for errors logged from other system modules. Stop and start fault monitor. If error persists then disable fault monitor and report the problem.
968858 SCSLM <%s> pool_conf_commit static error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
968941 Failed to bind delegated restarter handle: %s
Description:The sc delegated restarter is not able to bind the handle with the SMF.
Solution:Check if the SMF default restarter "svc:/system/svc/restarter:default" is online. Check if other SMF services are functioning properly. Contact SUN vendor for more help.
969008 t_alloc (open_cmd_port-T_ADDR) %d
Description:Call to t_alloc() failed. The "t_alloc" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
969264 Unable to get CMM control.
Description:The cl_eventd was unable to obtain a list of cluster nodes from the CMM. It will exit.
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.
969578 Internal error: trying to start nametag %s that is already running
Description:libclcontract code encountered an internal logic error. There should be no impact on the processes being monitored by the process that is using libclcontract.
Solution: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.
969827 Failover attempt has failed.
Description:LogicalHostname resource was unable to register with IPMP for status updates.
Solution:Most likely it is result of lack of system resources. Check for memory availability on the node. Reboot the node if problem persists.
969961 The raw device to fsck is not specified in mapped filesystem information for mount point %s in zone cluster %s.
Description:The 'raw device to fsck' field is missing from filesystem mapping information for the specified mount point.
Solution:Specify the 'raw device to fsck' field to the mapping information for specified mount point and repeat the operation.
970364 Command %s returned with non-zero exit status %d, HA-SAP will continue to start SAP.
Description:Command exited normally but the exit status was set to a non-zero value.
Solution:Contact your authorized Sun service provider.
970567 CMM: Quorum server %s cannot be reached. Check if qshost %s is specified in /etc/hosts file, /etc/inet/ipnodes file, or both.
Description:The quorum server hostname could not be resolved to an address.
Solution:Add the quorum server hostname to the /etc/hosts file, /etc/inet/ipnodes file, or both. Verify that the settings in the /etc/nsswitch.conf file include "files" for host lookup.
970705 scnetapp fatal error - Cannot bind to nameserver
Description:The program responsible for retrieving NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.
Solution:Contact your authorized Sun service provider as soon as possible to determine whether a workaround or patch is available.
971233 Property %s is not set.
Description:The property has not been set by the user and must be.
Solution:Reissue the clresource or the scrgadm command with the required property and value.
972479 ucmm is undergoing reconfiguration.
Description:The UCMM is being reconfigured.
Solution:No user action is required.
972580 CCR: Highest epoch is < 0, highest_epoch = %d.
Description:The epoch indicates the number of times a cluster has come up. It should not be less than 0. It could happen due to corruption in the cluster repository.
Solution:Boot the cluster in -x mode to restore the cluster repository on all the members of the cluster from backup. The cluster repository is located at /etc/cluster/ccr/.
972610 fork: %s
Description:The rgmd, or rpc.pmfd daemon was not able to fork a process, possibly due to low swap space. The message contains the system error. This can happen while the daemon is starting up (during the node boot process), or when executing a client call. If it happens when starting up, the daemon does not come up. If it happens during a client call, the server does not perform the action requested by the client.
Solution:Determine if the machine is running out of swap space. 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.
972716 Failed to stop the application with SIGKILL. Returning with failure from stop method.
Description:The stop method failed to stop the application with SIGKILL.
Solution:Use pmfadm(1M) with the -L option to retrieve all the tags that are running on the server. Identify the tag name for the application in this resource. This can be easily identified as the tag ends in the string ".svc" and contains the resource group name and the resource name. Then use pmfadm(1M) with the -s option to stop the application. If the error persists, reboot the node.
973102 ucmm in stable state.
Description:The UCMM is in stable state. This message is an informational message.
Solution:No user action is required.
973243 Validation failed. USERNAME missing in CONNECT_STRING
Description:USERNAME is missing in the specified CONNECT_STRING. The format could be either 'username/password' or '/' (if operating system authentication is used).
Solution:Specify CONNECT_STRING in the specified format.
973299 Error in scha_res_get of retry intvl prop,res:%s, Err: %s
Description:Cannot read the resource retry interval property in sc delegated restarter
Solution:Take action depending on the error and contact Sun vendor for more help.
973615 Node %s: weight %d
Description:The load balancer set the specified weight for the specified node.
Solution:This is an informational message, no user action is needed.
973933 resource %s added.
Description:This is a notification from the rgmd that the operator has created a new resource. This message can be used by system monitoring tools.
Solution:This is an informational message; no user action is needed.
974106 lkcm_parm: 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.
974129 Cannot stat %s: %s.
Description:The stat(2) system call failed on the specified pathname, which was passed to a libdsdev routine such as scds_timerun or scds_pmf_start. The reason for the failure is stated in the message. The error could be the result of 1) misconfiguring the name of a START or MONITOR_START method or other property, 2) a programming error made by the resource type developer, or 3) a problem with the specified pathname in the file system itself.
Solution:Ensure that the pathname refers to a regular, executable file.
974664 HA: no valid secondary provider in rmm - aborting
Description:This node joined an existing cluster. Then all of the other nodes in the cluster died before the HA framework components on this node could be properly initialized.
Solution:This node must be rebooted.
974898 %s->In scf_simple_prop_get:%s, method: %s
Description:There is no property in the service or there was an error in reading the property.
Solution:Check the SMF man page to know more about the error. Also make sure the basic SMF functionalities are working. Contact your SUN vendor for more help.
975654 Failover %s data service must have exactly one value for extension property %s.
Description:Failover data service must have one and only one value for Confdir_list.
Solution:Create a failover resource group for each configuration file.
975775 Publish event error: %d
Description:Internal error.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
975809 Create_configuration - the creation/modification of the MySQL replication resource %s failed
Description:The MySQL creation/modification of the MySQL replication resource failed
Solution:Fix the errors outlined in /var/adm/messages
976495 fork failed: %s
Description:Failed to run the "fork" command. The "fork" man page describes possible error codes.
Solution:Some system resource has been exceeded. Install more memory, increase swap space or reduce peak memory consumption.
976914 fctl: %s
Description:The cl_apid received the specified error while attempting to deliver an event to a CNRP client.
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.
977371 Backup server terminated.
Description:Graceful shutdown did not succeed. Backup server processes were killed in STOP method. It is likely that adaptive server terminated prior to shutdown of backup server.
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.
977379 Failed to reboot the nodes of the partition
Description:The upgrade process will reboot the nodes of second partition in the alternate boot environment. Rebooting the nodes failed.
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.
977412 The state of the path to device: %s has changed to FAILED
Description:A device is seen as FAILED.
Solution:Check the device.
978005 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.
978081 rebalance: resource group <%s> is quiescing.
Description:The indicated resource was quiesced as a result of clresourcegroup quiesce or scswitch -Q being executed on a node.
Solution:Use clresourcegroup status to determine the state of the resource group. If the resource group is in ERROR_STOP_FAILED state on a node, you must manually kill the resource and its monitor, and clear the error condition, before the resource group can be started. Refer to the procedure for clearing the ERROR_STOP_FAILED condition on a resource group in the Sun Cluster Administration Guide. If the resource group is in ONLINE_FAULTED or ONLINE state then you can switch it offline or restart it. If the resource group is OFFLINE on all nodes then you can switch it online. If the resource group is in a non-quiescent state such as PENDING_OFFLINE or PENDING_ONLINE, this indicates that another event, such as the death of a node, occurred during or immediately after execution of the clresourcegroup quiesce command. In this case, you can re-execute the clresourcegroup quiesce command to quiesce the resource group.
978125 in libsecurity setnetconfig failed when initializing the server: %s - %s
Description:A server (rpc.pmfd, rpc.fed or rgmd) was not able to start because it could not establish a rpc connection for the network specified. 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.
978812 Validation failed. CUSTOM_ACTION_FILE: %s does not exist
Description:The file specified in property 'Custom_action_file' does not exist.
Solution:Please make sure that 'Custom_action_file' property is set to an existing action file. Reissue command to create/update.
978829 t_bind, did not bind to desired addr
Description:Call to t_bind() failed. The "t_bind" man page describes possible error codes. udlm will exit and the node will abort.
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.
979343 Error: duplicate prog <%s> launched step <%s>
Description:Due to an internal error, uccmd has attempted to launch the same step by duplicate programs. ucmmd will reject the second program and treat it as a step failure.
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.
979659 Validate - User %s is not a valid userid
Description:The user is not a valid userid.
Solution:Ensure the user name is correct.
979803 CMM: Node being shut down.
Description:This node is being shut down.
Solution:This is an informational message, no user action is needed.
980226 File %s is missing or not executable.
Description:The specified file does not exist or does not have it's executable bit set.
Solution:Ensure that the file exists and is executable.
980307 reservation fatal error(%s) - Illegal command
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.
980425 Aborting startup: could not determine whether failover of NFS resource groups is in progress.
Description:Startup of an NFS resource was aborted because it was not possible to determine if failover of any NFS resource groups is in progress.
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.
980477 LogicalHostname online.
Description:The status of the logicalhost resource is online.
Solution:This is informational message. No user action required.
980935 The zone cluster name in extension property %s is not specified.
Description:Zone cluster name is not specified in the resource extension property.
Solution:Try recreating the resource with a valid zone cluster name in ZCName extension property.
980935 start_ids - Informix Server (%s) was manually started
Description:The specified Informix Server has been manually started.
Solution:No user action is required. Informational message.
980942 CMM: Cluster doesn't have operational quorum yet; waiting for quorum.
Description:Not enough nodes are operational to obtain a majority quorum; the cluster is waiting for more nodes before starting.
Solution:If nodes are booting, wait for them to finish booting and join the cluster. Boot nodes that are down.
980981 Entry for the mount point %s in not found in %s.
Description:The zone boot handler failed to find the mount point for the specified file system.
Solution:Check the /etc/vfstab file for the entry of the specified file system. If the entry does not exists add the file system entry and reboot the zone cluster node. Contact your Sun service provider if the problem persists after you add the file system entry in /etc/vfstab.
981211 'ensmon 2' timed out. Enqueue server is running. But status for replica server is unknown. See %s/ensmon%s.out.%s for output.
Description:SAP utility 'ensmon' with option 2 cannot be completed. However, 'ensmon' with option 1 finished successfully. This can happen if the network of the cluster node where the SAP replica server was running becomes unavailable.
Solution:No user action is needed.
981931 INTERNAL ERROR: postpone_start_r: meth type <%d>
Description:A non-fatal internal error has occurred in the rgmd state machine.
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.
983613 INTERNAL ERROR: error occurred while launching the probe command <%s>
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.
983924 Method timeouts are being suspended for Resource group <%s> until device group switchovers have completed.
Description:Timeout monitoring for resource methods in the resource group is being suspended while disk device groups are reconfiguring. This prevents unnecessary failovers that might be caused by the temporary unavailability of a device group.
Solution:This is just an informational message.
984139 Failed to issue vxprint command: %s
Description:An error occurred when the command 'vxprint' was run.
Solution:Ensure that the VxVM packages are installed correctly. Contact your authorized Sun service provider for further assistance in diagnosing the problem.
984337 check_pgs: The ssh-agent information file %s is unavailable
Description:The file /tmp/<resourcename>-ssh containing the necessary information to manage the ssh-agent together with the PostgreSQL database is unavailable.
Solution:No user action is required.
984438 File system has got unmounted! Please check if it needs maintenance and then re-mount it.
Description:The I/O probe detected that the file system is not mounted. One possible cause of this error is that the mount-point directory was deleted.
Solution:Check the condition of the file system and determine whether the mount-point directory exists. If the mount-point directory exists, restart the ScalMountPoint resource.
984634 reservation notice(%s) - MHIOCGRP_INRESV success during retry attempt: %d
Description:Informational message from reserve on ioctl success during retry.
Solution:No user action is required.
984673 Mount of %s failed in zone cluster %s: (%d) %s.
Description:HAStoragePlus was not able to mount the specified file system for zone cluster.
Solution:Check the system configuration. Also check if the FilesystemCheckCommand is not empty (it is not advisable to have it empty since file system inconsistency may occur).
984776 Instance %s already running.
Description:The agent has detected that the Oracle instance is already running, when attempting to startup the instance.
Solution:No user action is required. Informational message.
985103 scvxvmlg error - readlink(%s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
985111 lkcm_reg: illegal %s value
Description:Cluster information that is being used during udlm registration with ucmm is incorrect.
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.
985158 SCSLM <%s> pool_conf_close() error <%s>
Description:Should never occur.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
985291 Monitor for the telemetry data service stopped successfully. 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 needed.
985352 Unhandled return code from scds_timerun() for %s
Description:The data service detected an error from scds_timerun().
Solution:Informational message. No user action is needed.
985417 %s: Invalid arguments, restarting service.
Description:The PMF action script supplied by the DSDL while launching the process tree was called with invalid arguments.
Solution:This is an internal error. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
986079 Remove_configuration - The deletion of the MySQL replication resource %s failed
Description:The MySQL replication resource was not deleted
Solution:Evaluate the root cause for the failed deletion and retry the operation
986150 check_mysql - Sql-command %s returned error (%s)
Description:The fault monitor can't execute the specified SQL command.
Solution:Either was MySQL already down or the fault monitor user does not have the right permission. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges. Check also the MySQL log files for any other errors.
986157 Validate - can't determine path to Grid Engine binaries
Description:The Sun Grid Engine binary qstat was not found in ${binary_path} nor ${binary_path}/<arch>. qstat is used only representatively. If it is not found, the other Sun Grid Engine binaries are presumed misplaced also. ${binary_path} is reported by the command 'qconf -sconf'.
Solution:Find 'qstat' in the Sun Grid Engine installation. Then update ${binary_path} using the command 'qconf -mconf' if appropriate.
986190 Entry at position %d in property %s with value %s is not a valid node identifier or node name.
Description:The value given for the named property has an invalid node specified for it. The position index, which starts at 0 for the first element in the list, indicates which element in the property list was invalid.
Solution:Specify a valid node for the property.
986197 reservation fatal error(%s) - malloc() error, errno %d
Description:The device fencing program has been unable to allocate required memory.
Solution:Memory usage should be monitored on this node and steps taken to provide more available memory if problems persist. Once memory has been made available, the following steps may need to taken: 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, access to shared devices 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 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. The device group can be switched back to this node if desired by using the cldevicegroup command. If no other node was available, then the device group will not have been started. Use the cldevicegroup command 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. You can retry the desired action.
986904 Unable to retrieve name server version from version manager
Description:There was a failure to retrieve the name server version from the version manager.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
987357 check_dhcp - tftp transfer test timed out exceeded %s seconds
Description:The tftp transfer has exceeded it's timeout allowance.
Solution:No user action is required. Informational message, an immediate failover is being requested.
987412 Error in creating svc_fmri %s
Description:Could not create the named smf service fmri to mage under SC delegated restarter
Solution:Check the previous messages for the reason.
987452 cl_execd: unable to arm failfast.
Description:The cl_execd program was not able to arm the failfast unit.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
987543 functions - Fatal: %s/util/arch not found or not executable
Description:The file '${SGE_ROOT}/util/arch' was not found or is not executable.
Solution:Make certain the shell script file '${SGE_ROOT}/util/arch' is both in that location, and executable.
987592 Telemetry data service validate method completed successfully
Description:The telemetry data service could be validated.
Solution:This message is informational; no user action is needed.
987637 Failed to save old mount points.
Description:The online update of the HAStoragePlus resource is not successful because of failure in saving the old mount points of file systems that were present before updating the resource.
Solution:Check the syslog messages and try to resolve the problem. Try again to update the resource. If the problem persists, contact your authorized Sun service provider.
988233 CCR: CCR data server on node %s unreachable while updating table %s in cluster %s.
Description:While the TM was updating the indicated table in the cluster, the specified node went down and has become unreachable.
Solution:The specified node needs to be rebooted.
988416 t_sndudata (2) in send_reply: %s
Description:Call to t_sndudata() failed. The "t_sndudata" man page describes possible error codes.
Solution:No user action is required.
988762 Invalid connection attempted from %s: %s
Description:The cl_apid received a CRNP client connection attempt from an IP address that it could not accept because of its allow_hosts or deny_hosts.
Solution:If you wish to allow access to the CRNP service for the client at the specified IP address, modify the allow_hosts or deny_hosts as required. Otherwise, no action is required.
988779 File system %s mounted on %s is healthy
Description:An I/O probe of the file system succeeded. The file system is available. This message is an informational message.
Solution:No user action is required.
988802 UNRECOVERABLE ERROR: Cluster Configuration Repository transformation failed with error code %s
Description:Cluster Configuration Repository transformation failed with error code ${retval}.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
988885 libpnm error: %s
Description:This means that there is an error either in libpnm being able to send the command to the PNM daemon or in libpnm receiving a response from the PNM daemon.
Solution:The user of libpnm should handle these errors. However, if the message is: network is too slow - it means that libpnm was not able to read data from the network - either the network is congested or the resources on the node are dangerously low. The scha_cluster_open failed - it means that the call to initialize a handle to get cluster information failed. This means that the command will not be sent to the PNM daemon. The scha_cluster_get failed - it means that the call to get cluster information failed. This means that the command will not be sent to the PNM daemon. can't connect to PNMd on %s - it means that libpnm was not able to connect to the PNM daemon through the private interconnect on the given host. It could be that the given host is down or there could be other related error messages. wrong version of PNMd - it means that we connected to a PNM daemon which did not give us the correct version number. no LOGICAL PERNODE IP for %s - it means that the private interconnect LOGICAL PERNODE IP address was not found. IPMP group %s not found - either an IPMP group name has been changed or all the adapters in the IPMP group have been unplumbed. There would have been an earlier NOTICE which said that a particular IPMP group has been removed. The cl_pnmd has to be restarted. Send a KILL (9) signal to the PNM daemon. Because cl_pnmd is under PMF control, it will be restarted automatically. If the problem persists, restart the node with clnode evacuate and shutdown. no adapters in IPMP group %s - this means that the given IPMP group does not have any adapters. Please look at the error messages from LogicalHostname/SharedAddress. no public adapters on this node - this means that this node does not have any public adapters. Please look at the error messages from LogicalHostname/SharedAddress.
989577 (%s) scan of seqnum failed on "%s", ret = %d
Description:Could not get the sequence number from the udlm message received.
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.
989693 thr_create failed
Description:Could not create a new thread. The "thr_create" man page describes possible error codes.
Solution:Some system resource has been exceeded. Install more memory, increase swap space or reduce peak memory consumption.
989846 ERROR: unpack_rg_seq(): rgname_to_rg failed <%s>
Description:Due to an internal error, the rgmd daemon was unable to find the specified resource group data in memory.
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.
989958 wrong command length received %d.
Description:This means that the PNM daemon received a command from libpnm, but all the bytes were not received.
Solution:This is not a serious error. It could be happening due to some network problems. If the error persists send KILL (9) signal to cl_pnmd. PMF will restart cl_pnmd automatically. If the problem persists, restart the node with clnode evacuate and shutdown.
990215 HA: repl_mgr: exception while invoking RMA reconf object
Description:An unrecoverable failure occurred in the HA framework.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
990226 WebSphere MQ Listener for port %s stopped
Description:The specified WebSphere MQ Listener has been stopped.
Solution:No user action is required. Informational message.
990418 received signal %d
Description:The daemon indicated in the message tag (rgmd or ucmmd) 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.
990711 %s: Could not call Disk Path Monitoring daemon to add path(s)
Description:scdidadm -r was run and some disk paths may have been added, but DPM daemon on the local node may not have them in its list of paths to be monitored.
Solution:Kill and restart the daemon on the local node. If the status of new local disks are not shown by local DPM daemon check if paths are 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.
991103 Cannot open /proc directory
Description:The rpc.pmfd server was unable to open the /proc directory to find a list of the current processes.
Solution:Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
991108 uaddr2taddr (open_cmd_port) failed
Description:Call to uaddr2taddr() failed. The "uaddr2taddr" man page describes possible error codes. ucmmd will exit and the node will abort.
Solution:Save the files /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
991130 pthread_create: %s
Description:The sc_zonesd daemon was not able to allocate a new thread. This problem can occur if the machine has low memory.
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.
991800 in libsecurity transport %s is not a loopback transport
Description:A server (rpc.pmfd, rpc.fed or rgmd) refused an rpc connection from a client because the named transport is not a loopback. 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.
991864 putenv: %s
Description:The rpc.pmfd server was not able to change environment variables. 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.
991954 clexecd: wait_for_ready daemon
Description:clexecd program has encountered a problem with the wait_for_ready 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.
992415 Validate - Couldn't retrieve MySQL-user <%s> from the nameservice
Description:Couldn't retrieve the defined user from nameservice.
Solution:Make sure that the right user is defined or the user exists. Use getent passwd 'username' to verify that defined user exists.
992912 clexecd: thr_sigsetmask returned %d. Exiting.
Description:clexecd program has encountered a failed thr_sigsetmask(3THR) 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.
994417 %s database(s) is/are not present in Adpative Server.
Description:Sybase Adaptive server does not contain the configured database(s).
Solution:Check the correctness of the configured database names(s). Examine the HA-Sybase log files, syslog message files and setup.
994776 check_broker - sc3inq %s CURDEPTH(%s)
Description:The WebSphere Broker fault monitor checks to see if the message flow was successful, by inquiring on the current queue depth for the output queue within the simple message flow.
Solution:No user action is needed. The fault monitor displays the current queue depth until it successfully checks that the simple message flow has worked.
994926 Mount of %s failed: (%d) %s.
Description:HAStoragePlus was not able to mount the specified file system.
Solution:Check the system configuration. Also check if the FilesystemCheckCommand is not empty (it is not advisable to have it empty since file system inconsistency may occur).
995026 lkcm_cfg: invalid handle was passed %s %d
Description:Handle for communication with udlmctl during a call to return the current DLM configuration is invalid.
Solution:This error 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.
995249 You cannot specify zpools in a scalable service resource.
Description:HAStoragePlus detected an inconsistency in its configuration: you defined the resource group as a scalable service. HAStoragePlus supports zpools that are defined only as a failover service. You cannot specify in this case.
Solution:Remove the zpools from the service or change the scalable service for the zpool to a failover service.
995339 Restarting using scha_control 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.
995839 validate_options: HA N1 Grid Service Provisioning System Local Distributor %s Option %s is not set
Description:A required option is not set in the start, stop, validate or probe command.
Solution:Fix the appropriate command in example by registering.
996075 fatal: Unable to resolve %s from nameserver
Description:The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.
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.
996230 scvxvmlg error - mknod(%s) failed
Description:The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. 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:Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. 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 further 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.
996389 Fault-monitor successfully re-started.
Description:The fault monitor of this ScalMountPoint Resource was restarted successfully. This message is an informational message.
Solution:No user action is required.
996522 scha_resourcetype_get() failed: %s
Description:A call to scha_resourcetype_get() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
996887 reservation message(%s) - attempted removal of scsi-3 keys from non-scsi-3 device %s
Description:The device fencing program has detected scsi-3 registration keys on a device which is not configured for scsi-3 PGR use. The keys have been removed.
Solution:This is an informational message, no user action is needed.
996902 Stopped the HA-NFS system fault monitor.
Description:The HA-NFS system fault monitor was stopped successfully.
Solution:No user action is required.
996942 Stop of HADB database completed successfully.
Description:The resource was able to successfully stop the HADB database.
Solution:This is an informational message, no user action is needed.
998022 Failed to restart the service: %s.
Description:Restart attempt of the data service has failed.
Solution:Check the syslog messages that are occurred just before this message to check whether there is any internal error. In case of internal error, contact your Sun service provider. Otherwise, any of the following situations may have happened. 1) Check the Start_timeout and Stop_timeout values and adjust them if they are not appropriate. 2) This might be the result of lack of the system resources. Check whether the system is low in memory or the process table is full and take appropriate action.
998351 <Monitor_Uri_List> extension property is not set. Fault Monitor will not do HTTP probing. asadmin list-domains command will be used for probing the health of the server
Description:This is just an info message. If the Monitor_uri_list extension property is set, the JSAS Domain Admin Server probe will do thorough probing by sending an HTTP request to DAS and then reading the response. If this extension property is not set, the asadmin list-domains command will be used to get the status of DAS.
Solution:If HTTP probing is desired, create a HTTP listener for the DAS and then set the Monitor_uri_list extension property.
998374 Validate - winbindd %s nonexistent executable
Description:The Samba executable winbindd either doesn't exist or is not executable.
Solution:Check the correct pathname for the Samba (s)bin directory was entered when registering the resource and that the program exists and is executable.
998478 start_sge_schedd failed
Description:The process sge_schedd failed to start for reasons other than it was already running.
Solution:Check /var/adm/messages for any relevant cluster messages. Respond accordingly, then retry bringing the resource online.
998495 scha_resource_get() failed for Resource %s : %s
Description:A call to scha_resource_get() failed.
Solution:Contact your authorized Sun service provider to determine whether a workaround or patch is available.
998759 Database is ready for auto recovery but the Auto_recovery property is false.
Description:All the Sun Cluster nodes able to run the HADB resource are running the resource, but the database is unable to be started. If the auto_recovery extension property was set to true the resource would attempt to start the database by running hadbm clear and the command, if any, specified in the auto_recovery_command extension property.
Solution:The database must be manually recovered, or if autorecovery is desired the auto_recovery extension property can be set to true and auto_recovery_command can optionally also be set.
998781 start_dhcp - %s %s failed
Description:The DHCP resource has tried to start the DHCP server using in.dhcpd, however this has failed.
Solution:The DHCP server will be restarted. Examine the other syslog messages occurring at the same time on the same node, to see if the cause of the problem can be identified.
999010 Function: start_pgs - resource %s on host %s is not configured/running as a standby database
Description:The PostgreSQL resource on the standby host is not configured as a standby or acting as a primary.
Solution:Consult the logs on the standby host and insure, that the standby host is configured as a standby database, if it is running as a primary, reconfigure and restart it.
999536 scf_transaction_property_new failed error %d: %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.
999827 QUORUM_GENERIC: quorum_register error: registration key read check failed on quorum device %s.
Description:An error was encountered when placing the node's registration key on a specified quorum device. The write operation was successful, but a read check to confirm the presence of the key failed to match the key. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.
Solution:Contact your authorized Sun service provider to determine if a workaround or patch is available.
999960 NFS daemon %s has registered with TCP transport but not with UDP transport. Will restart the daemon.
Description:While attempting to start the specified NFS daemon, the daemon started up. However it registered with TCP transport before it registered with UDP transport. This indicates that the daemon was unable to register with UDP transport.
Solution:This is an informational message, no user action is needed. Make sure that the order of entries in /etc/netconfig is not changed on cluster nodes where HA-NFS is running.
- © 2010, Oracle Corporation and/or its affiliates