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 intgrity. The nameserver was not locatable on this node, so this node will be halted in order to gurantee 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 occured 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 occured on this node. For example, if the root disk on the afflicted node has failed, then it needs to be replaced.
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.
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 utililty '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 action 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.
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 deregister 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.
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 atleast 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.
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.
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.
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.
115617 Error in failing over the resource group:%s
Description:The number of restarts of services under the resource has reached the max. Hence a fail over 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.
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 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.
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 installaton 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 sucessfully (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.
119696 clq_scsi2: quorum preempt error in CMM: Error %d --- SCSI2 Tkown ioctl failed on quorum device %s.
Description:This node encountered an error while issuing a SCSI2 Tkown operation on a quorum device. This will cause the node to conclude that it has been unsuccessful in preempting keys from the quorum device, and therefore the partition to which it belongs has been preempted. 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 will be other related messages that will identify the quorum device for which this error has occurred. If the error encountered is EACCES, then the SCSI2 command could have failed due to the presence of SCSI3 keys on the quorum device. Scrub the SCSI3 keys off of it, and reboot the preempted nodes.
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 occured reading the indicated property.
Solution:Check syslog messages for errors logged from other system modules. If error persists, please report the problem.
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.
121513 Successfully restarted service.
Description:This message indicates that the RGM successfully restarted the resource.
Solution:This is an informational message, no user action is required.
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:None required. 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 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 seperate message which includes the same command.
Solution:Refer to a seperate 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. Re-try 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 subsequesnt 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 runlevel is not equal to the configured SLrunlevel. The state is checked again in 5 seconds.
Solution:None.
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 manpage to know more about the error.Also make sure the basic SMF functionalities are working fine.Contact 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:None
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:HA Storage Plus 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.
127386 Entry in %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.
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:None.
127624 must be superuser to start %s
Description:Process ucmmd did not get started by superuser. ucmmd is going to exit now.
Solution:None. 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:None required. Informational message.
127930 About to mount %s.
Description:HA Storage Plus 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.
129575 Failed to set core location properties for the method tag <%s>.
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.
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.
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.
131640 CMM: Reading reservation keys from quorum device %s failed.
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.
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.
132692 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.
133146 Unable to execve %s: %s
Description:The rpc.pmfd server was not able to exec the specified process, possibly due to bad arguments. 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: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.
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.
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 resouce 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 trasnport 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 action needed. 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 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.
138261 File system associated with mount point %s is to be locally mounted. The AffinityOn value cannot be FALSE.
Description:HA Storage Plus 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 re-tried with a larger buffer.
Solution:No user action is required. If the message recurs frequently, contact your authorized Sun service provider to determine whether a workaround or patch is available.
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 sytems. 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.
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.
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.
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.
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.
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.
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:Error trying to retrieve network address associated with a 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.
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 action 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.
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.
152159 WARNING: lkcm_sync: udlm_send_reply failed, forcing reconfiguration
Description:A reconfiguration will start.
Solution:None.
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 using 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:None.
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.
154007 Error stopping gracefully the PNM. Killing PNM
Description:The PNM service fails to stop.
Solution:No user action required
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. Re-try 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. Re-try 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:HAStoargePlus 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.
156643 Entry for file system mount point %s absent from %s.
Description:HA Storage Plus 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.
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.
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.
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.
160032 ping_retry %d
Description:The ping_retry value used by scdpmd.
Solution:No action required.
160167 Server successfully started.
Description:Informational message. Oracle server has been successfully started by HA-Oracle.
Solution:None
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 action 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.
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>". Or, the whole resource group can be restarted using "clresourcegroup restart <group>". If 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 rpc.pmfd was unable to configure a process template in which to launch the requested service. Consequently, the rpc.pmfd was unable to launch the process under its control.
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.
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:None
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.
161934 pid %d is stopped.
Description:HA-NFS fault monitor has detected that the specified process has been stopped with a signal.
Solution:No action. 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:HA Storage Plus 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:None. This is only for information.
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.
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.
167108 Starting Oracle server.
Description:Informational message. Oracle server is being started by HA-Oracle.
Solution:None
167253 Server stopped successfully.
Description:Informational message. Oracle server successfully stopped.
Solution:None
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:HA Storage Plus 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:None.
169082 start_dependency: Exeeded %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.
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:HA Storage Plus 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 reosurce 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.
173201 Removing node %s from device service %s
Description:Informational message from scdidadm.
Solution:No user action required.
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 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 non-existent 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.
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 encounterd. /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 setting of the Failover_mode system property, the action script is not restarting the application.
Solution:This is an informational message, no user action is needed.
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 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.
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.
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.
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 specifes 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.
185089 CCR: Updating table %s failed to startup on node %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.
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 action 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 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 action is required. This is an informational message only.
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.
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 proccessing 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 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 nd 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 action 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.
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.
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 occured. 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 respecify 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.
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 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.
- © 2010, Oracle Corporation and/or its affiliates