Sun Cluster Error Messages Guide for Solaris OS

Message IDs 100000–199999

This section contains message IDs 100000–199999.

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.

100293 dl_bind: kstr_msg failed %d error

Description:

Could not bind to the private interconnect.

Solution:

Reboot of the node might fix the problem.

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.

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.

101461 INTERNAL ERROR in J2EE probe calling scds_fm_tcp_connect()

Description:

The data service could not connect to the J2EE engine port.

Solution:

Informational message. No user action is needed.

102218 couldn't initialize ORB, possibly because machine is booted innon-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.

102779 %s has been removed from %s.\nMake sure that all HA IP addresses hosted on %s are moved.

Description:

We do not allow removig of an adapter from an IPMP group. The correct way to DR an adapter is to use if_mpadm(1M). Therefore we notify the user of the potential error.

Solution:

This message is informational; no user action is needed if the DR was done properly (using if_mpadm).

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

104005 restart_resource_group - Resource Group restart failed rc<%s>

Description:

As the result of the Broker RDBMS failing or restarting a Resource Group restart was initiated to effectively restart the Broker Queue Manager, however this has failed.

Solution:

Examine the other syslog messages occurring at the same time on the same node to see if the cause of the problem can be identified. If required turn on debug for the resource. Please refer to the data service documentation to determine how to do this

104035 Failed to start sap processes with command %s.

Description:

Failed to start up SAP with the specified command.

Solution:

SAP Central Instance 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 Central Instance failed to start on any other node, disable the SAP Central Instance 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.

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.

105337 WARNING: thr_getspecific %d

Description:

The rgmd has encountered a failed call to thr_getspecific(3T). The error message indicates the reason for the failure. This error is non-fatal.

Solution:

If the error message is not self-explanatory, contact your authorized Sun service provider for assistance in diagnosing the problem.

105450 Validation failed. ASE directory %s does not exist.

Description:

The Adaptive Server Environment directory does not exist. TheSYBASE_ASE environment variable may be incorrectly set or theinstallation may be incorrect.

Solution:

Check the SYBASE_ASE environment variable value and verify the Sybaseinstallation.

105569 clexecd: Can allocate execit_msg. Exiting. 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.

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.

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.

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.

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.

111527 Method <%s> on resource <%s>: unknown command.

Description:

An internal logic error in the rgmd has prevented it from successfully executing a resource method.

Solution:

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

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.

111797 sigaction: %s

Description:

The rpc.pmfd server was not able to set its signal handler. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.

Solution:

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

111804 validate: Host $Hostname is not found in /etc/hosts but it is required

Description:

The hostname $Hostname is not in the etc hosts file.

Solution:

Set the variable Host in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.

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.

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.

113551 INITFED Error: Startup of ${SERVER} failed.

Description:

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

Solution:

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

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.

113712 start_sap_j2ee - The SAP J2EE instances (%s) is started manually.

Description:

The agent has detected that the defined SAP J2EE instancies has been started manually.

Solution:

No user action is needed.

113792 Failed to retrieve the extension property %s: %s

Description:

The data service could not retrieve the extension property.

Solution:

No user action needed.

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.

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.

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

115256 file specified in USER_ENV %s doesn't exist

Description:

'User_env' property was set when configuring the resource. File specified in 'User_env' property does not exist or is not readable. File should be specified with fully qualified path.

Solution:

Specify existing file with fully qualified file name when creating resource. If resource is already created, please update resource property 'User_env'.

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.

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.

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.

117770 Hostname %s is already plumbed.

Description:

An attempt was made to create a Network resource with the specified hostname, while the hostname was already plumbed on a cluster node.

Solution:

Specify a unique hostname on the cluster. It should be a valid hostname in /etc/inet/hosts file, should be on a subnet which is available on the cluster and this hostname should not be in use on any cluster node.

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.

118261 Successfully stopped the service %s.

Description:

Specified data service stopped successfully.

Solution:

None. This is only an informational message.

119069 Waiting for WebSphere MQ Broker Queue Manager

Description:

The WebSphere Broker is dependent on the WebSphere MQ Broker Queue manager, which is not available. So the WebSphere Broker will wait until it is available before it is started, or until Start_timeout for the resource occurs.

Solution:

No user action is needed.

119120 clconf: Key length is more than max supported length in clconf_ccr read

Description:

In reading configuration data through CCR, found the key length is more than max supported length.

Solution:

Check the CCR configuraton information.

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.

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.

120972 IPMP Failure.

Description:

The IPMP group hosting the LogicalHostname has failed.

Solution:

The LogicalHostname resource would be failed over to a different node. If that fails, check the system logs for other messages. Also, correct the networking problem on the node so that the IPMP group in question is healthy again.

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.

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.

121872 Validate - Samba bin directory %s does not exist

Description:

The Samba bin directory does not exist.

Solution:

Check the correct pathname for the Samba bin directory was entered when registering the Samba resource and that the directory exists.

122160 Unable to write to file %s: %s.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

122188 IPMP logical interface configuration operation failed with <%d>.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

122638 lockd is not runing. Will retry in 2 seconds

Description:

HA-NFS started lockd, but lockd could not start.

Solution:

This is an informative message. HA-NFS will attempt to restart lockd.

122801 check_mysql - Couldn't retrieve defined databases for %s

Description:

The fault monitor can't retrieve all defined databases for the specified instance.

Solution:

Either was MySQL already down or the fault monitor user doesn't have the right permission. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges. Check also the MySQL logfiles for any other errors.

122807 INITPMF Error: Startup of ${SERVER} failed.

Description:

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

Solution:

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.

123167 in libsecurity for program %s (%lu); could not negotiate uid on any transport in NETPATH

Description:

The specified server was not able to start because it could not establish a rpc connection for the network specified, because it couldn't find any transport. 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.

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.

123524 The quorum configuration task succeeded on node ${nodename}

Description:

Quorum disk was configured and the cluster was initialized on the last of the 2 nodes to join the cluster.

Solution:

None.

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:

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.

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

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.

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 may not be defined in RTR file. Use the default value of -1.

Solution:

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

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

125049 Fault monitor cannot access view sys.v$archive_dest view. Please ensure the fault monitor user is granted select permission to this view

Description:

The HA-Oracle fault monitor was unable to select from the v$archive_dest view. It requires select access to this view so that it can monitor the status of archive log destinations.

Solution:

Grant the fault monitor user select access to the view. As a dba user, run the following SQL: grant select on v_$archive_dest to <fault_monitor_username>;

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.

125356 Failed to connect to %s:%d: %s.

Description:

The data service fault monitor probe was trying to connect to the host and port specified and failed. There may be a prior message in syslog with further information.

Solution:

Make sure that the port configuration for the data service matches the port configuration for the underlying application.

126077 All WebSphere MQ UserNameServer processes stopped

Description:

All WebSphere MQ UserNameServer processes have been successfully stopped.

Solution:

No user action is needed.

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

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.

127411 Error in reading /etc/mnttab: getmntent() returns <%d>

Description:

Failed to read /etc/mnttab.

Solution:

Check with system administrator and make sure /etc/mnttab is properly defined.

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.

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.

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.

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.

131492 pxvfs::mount(): global mounts are not enabled (need to run "clconfig -g" first)

Description:

A global mount command is attempted before the node has initialized the global file system name space. Typically this caused by trying to perform a global mount while the system is booted in single user mode.

Solution:

If the system is not at run level 2 or 3, change to run level 2 or 3 using the init(1M) command. Otherwise, check message logs for errors during boot.

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.

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.

133342 The N1 Grid Service Provisioning System database is unavailable

Description:

The Database or the master server is unavailble.

Solution:

None. The cluster will restart or failover the master server.

134020 get_resource_dependencies - WebSphere MQ Broker RDBMS resource %s already set

Description:

The WebSphere Broker is dependent on a WebSphere MQ Broker Queue Manager, however more than one WebSphere MQ Broker Queue Manager has been defined in the resource's extension property - resource_dependencies.

Solution:

Ensure that only one WebSphere MQ Broker Queue Manager is defined for the resource's extension property - resource_dependencies.

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.

134417 Global service <%s> of path <%s> is in maintainance.

Description:

Service is not supported by HA replica.

Solution:

Resume the service by using scswitch(1m).

134923 INITRGM Error: rpc.fed is not running.

Description:

The initrgm init script was unable to verify that the rpc.fed is running and available. This error will prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.

Solution:

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

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.

136852 in libsecurity for program %s (%lu); could not negotiate uid on any loopback transport in /net/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.

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:

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

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.

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.

138285 Unable to open <%s>

Description:

The clapi_mod in the syseventd failed to open the specified door, so it will be unable to deliver events to that service.

Solution:

139283 SCDPMD Error: Can't start ${SERVER}.

Description:

An attempt to start the scdpmd failed.

Solution:

139415 could not kill swa_rpcd

Description:

swa_rpcd could not be stopped

Solution:

Verify configuration.

139773 clexecd: Error %d from strdup

Description:

clexecd program has encountered a failed strdup(3C) system call. The error message indicates the error number for the failure.

Solution:

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.

140225 The request to relocate resource %s completed successfully.

Description:

The resource named was relocated to a different node.

Solution:

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

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.

142779 Unable to open failfast device

Description:

A server (rpc.pmfd or rpc.fed) was not able to establish a link to the failfast device, which ensures that the host aborts if the server dies. 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 already 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.

144109 RGM isn't restarting resource group <%s> or resource <%s> on node <%d> 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 scrgadm(1M) and scstat(1M) to determine the resources on which the specified resource depends that are not online, and bring them online.

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.

145270 Cannot determine if the server is secure: assuming non-secure.

Description:

While parsing the Netscape configuration file to determine if the Netscape server is running under secure or non-secure mode an error occured. This error results in the Data Service assuming a non-secure Netscape server, and will probe the server as such.

Solution:

Check the Netscape configuration file to make sure that it exists and that it contains information about whether the server is running as a secure server or not.

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.

146238 CMM: Halting to prevent split brain with node %ld.

Description:

Due to a connection failure with the specified node, the CMM is failing this node to prevent split brain partial connectivity.

Solution:

Any interconnect failure should be resolved, and/or the failed node rebooted.

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.

146961 Signal %d terminated the child process.

Description:

An unexpected signal caused the termination of the program that checks the availability of name service.

Solution:

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

147230 Invalid resource settings.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

147394 scf_entry_add_value failed: %s

Description:

An API call failed.

Solution:

147516 sigprocmask: %s

Description:

The rpc.pmfd server was not able to set its signal mask. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.

Solution:

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

148393 Unable to create thread. Exiting.\n

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.

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.

148526 fatal: Cannot get local nodename

Description:

An internal error has occurred. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution:

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

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.

149124 ERROR: probe_mysql Option -F not set

Description:

The -F option is missing for probe_mysql command.

Solution:

Add the -F option for probe_mysql command.

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.

150105 This list element in System property %s has an invalid IP address (hostname): %s.

Description:

The system property that was named does not have a valid hostname or dotted-decimal IP address string.

Solution:

Change the value of the property to use a valid hostname or dotted-decimal IP address string.

150171 :Function: validate - Zone name not set in %s

Description:

The variable Zonename does not contain a value.

Solution:

Review the /opt/SUNWsczone/sczsh/util/sczsh_config 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.

150628 sigaddset: %s

Description:

The rpc.pmfd server was not able to add a signal to a signal set. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.

Solution:

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

150719 INITRGM Error: Startup of ${SERVER} failed.

Description:

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

Solution:

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.

151356 the setting of Failover_mode for resource %s doesn't allow the scha_control operation. The number of restarts within the past Retry_interval (%d seconds) would exceed Retry_count (%d)

Description:

The rgmd is enforcing the RESTART_ONLY value for the Failover_mode system property. A request to restart a resource is denied because the resource has already been restarted Retry_count times within the past Retry_interval seconds

Solution:

No action required. If desired, use scrgadm(1M) to change the Failover_mode setting.

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.

152043 stop_sge_commd failed

Description:

The command '${SGE_ROOT}/bin/<arch>/sgecommdcntl -k' failed to stop the sge_commd process.

Solution:

Run the 'ps -ef | grep sge_commd' command to verify the process is really running. Try running '${SGE_ROOT}/bin/<arch>/sgecommdcntl -k' manually. Ensure sge_commd is not busy.

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

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.

153025 Failed to unplumb %s from %s.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

154317 launch_validate: fe_method_full_name() failed for resource <%s>, resource group <%s>, method <%s>

Description:

Due to an internal error, the rgmd 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.

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 scrgadm(1M) -pvv 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.

156178 Encountered an error while starting device services.

Description:

An error was detected by the HAStoragePlus resource's start method. This error was encountered during attempts to start a device service on a given node. Startup of the device services occur when the HAStoragePlus resource is brought online on a node the first time or after the resource is switched/failed over to another node. It is highly likely that a DCS function call returned an error.

Solution:

Examine the GlobalDevicePaths and FilesystemMountpoint extension properties for any invalid specifications. Examine the status of DCS. Contact your authorized Sun service provider for assistance in diagnosing the problem.

156527 Unable to execute <%s>: <%s>.

Description:

Sun Cluster was unable to execute a command.

Solution:

The problem could be caused by: 1) No more process table entries for a fork() 2) No available memory For the above two causes, the only option is to reboot the node. The problem might also be caused by: 3) The command that could not execute is not correctly installed For the above cause, the command might have the wrong path or file permissions. Correctly install the command.

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.

156889 Specified global device path %s is invalid.

Description:

HA Storage Plus found that the specified path is not a global device.

Solution:

Usually, this means that a typo has been made when filling the GlobalDevicePaths property -or- that the underlying device corresponding to the mount point is not a device group name.

156966 Validate - smbconf %s does not exist

Description:

The smb.conf file does not exist.

Solution:

Check the correct pathname for the Samba smb.conf file was entered when registering the Samba resource and that the smb.conf file exists.

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.

157577 Enabling failfast on HW RAID devices

Description:

This is informational message.

Solution:

None

157736 Unable to queue event %lld

Description:

The cl_apid was unable to queue the incoming sysevent specified.

Solution:

158471 Share command %s did not complete successfully.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

158530 CMM: Halting because this node is severely short of resident physical memory; availrmem = %ld pages, tune.t_minarmem = %ld pages.

Description:

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

Solution:

There may be other related messages that may indicate the cause for the node having reached the low memory state. Resolve the problem and reboot the node. If unable to resolve the problem, contact your authorized Sun service provider to determine whether a workaround or patch is available

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.

159059 IP address (hostname) %s from %s at entry %d in list property %s does not belong to any network resource used by resource %s.

Description:

The hostname or dotted-decimal IP address string in the message does not resolve to an IP address equal to any resolved IP address from the named resource's Network_resources_used property. Any explicitly named hostname or dotted-decimal IP address string in the named list property must resolve to an IP address equal to a resolved IP address from Network_resources_used.

Solution:

Either modify the hostname or dotted-decimal IP address string from the entry in the named property or modify Network_resources_used so that the entry resolves to an IP address equal to a resolved IP address from Network_resources_used.

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.

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

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 syetem is low on memory. If problem persists, please stop and start the fault monitor.

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 may be possible to switch the device group to this node with the scswitch command. If no other node was available, then the device group will not have been started. The scswitch command may be used to retry the attempt to start the device group. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group has failed. The desired action may be retried.

161643 Failed to add the sci%d adapter

Description:

The Sun Cluster Topology Manager (TM) has failed to add the SCI adapter.

Solution:

Make sure that the SCI adapter is installed correctly on the system or contact your authorized Sun service provider for assistance.

161683 %s/%s/install/startserver does not have executepermissions set.

Description:

The Sybase Adaptive Server is started by execution of the"startserver" file. The file's current permissions prevent itsexecution. The full path name of the "startserver" file is specified as a part of this error message. This file is locatedin the $SYBASE/$ASE/install directory

Solution:

Verify the permissions of the "startserver" file and ensure thatit 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.

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

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 scswitch command. If no other node was available, then the device group will not have been started. The scswitch command may be used 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.

165512 reservation error(%s) - my_map_to_did_device() error in other_node_status()

Description:

The device fencing program has suffered an internal error.

Solution:

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.

165731 Backup server successfully started.

Description:

The Sybase backup server has been successfully started by Sun ClusterHA 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.

166362 clexecd: Got back %d from I_RECVFD. Looks like parent is dead.

Description:

Parent process in the clexecd program is dead.

Solution:

If the node is shutting down, ignore the message. If not, the node on which this message is seen, will shutdown to prevent to prevent data corruption. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

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 using scrgadm(1M).

166590 NULL value returned for the extension property <%s>.

Description:

The extension property <%s> is set to NULL in the RTR File.

Solution:

Serious error, the RTR file is corrupted. Reload the package for HA-NetBackup SUNWscnb. If problem persists contact the Sun Cluster HA developer.

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

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.

168383 Service not started

Description:

There was a problem detected in the initial startup of the service.

Solution:

Attempt to start the service by hand to see if there are any apparent problems with the application. Correct these problems and attempt to start the data service again.

168387 ERROR: stop_sap_j2ee Option -S not set

Description:

The -S option is missing for the stop_command.

Solution:

Add -S option to the stop-command.

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.

168917 %s: Not able to get the private network address.

Description:

The daemon is unable to get private net address. Cluster is configured incorrectly on the machine where message is logged.

Solution:

Need a user action for this message.

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.

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.

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.

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.

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:

171565 WebSphere MQ Broker Queue Manager not available

Description:

The WebSphere Broker is dependent on a WebSphere MQ Broker Queue Manager, however the WebSphere MQ Broker Queue Manager is currently not available.

Solution:

No user action is needed. The fault monitor detects that the WebSphere MQ Broker Queue Manager is not available and will stop the WebSphere MQ Broker. After the WebSphere MQ Broker Queue Manager is available again, the fault monitor will restart the WebSphere MQ Broker.

171786 listener %s is not running. Attempting restart.

Description:

Listen monitor has detected failure of listener. Monitor will attempt to restart the listener.

Solution:

None

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.

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.

173313 Unable to restart NFS daemons.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

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:

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.

174352 INITPMF Error: Can't stop ${SERVER} outside of run control environment.Explanation The initpmf init script was run manually (not automatically by init(1M)) This is not supported by Sun Cluster. This message informs that the "initpmf stop" command was not successful. Not action has been done.

Solution:

No action required.

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, please save a copy of the /var/adm/messages files on all nodes, the output of an scstat -g command, and the output of a scrgadm -pvv command. Report the problem to your authorized Sun service provider.

175370 svc_restore_priority: Could not restore original scheduling parameters: %s

Description:

The server was not able to restore the original scheduling mode. The system error message is shown. An error message is output to syslog.

Solution:

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

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.

176074 INITPNM Can't start pnmd

Description:

The pnm startup script was not able to run pnmd.

Solution:

There should be other error messages related to pmf.

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.

176860 Error: Unable to update scha_control timestamp file <%s> for resource <%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.

176861 check_broker - sc3inq %s CURDEPTH(%s)

Description:

The WebSphere Broker fault monitor checks to see if the message flow was successful, by inquiring on the current queue depth for the output queue within the simple message flow.

Solution:

No user action is needed. The fault monitor displays the current queue depth until it successfully checks that the simple message flow has worked.

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.

177252 reservation warning(%s) - MHIOCGRP_INRESV error 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.

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.

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

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.

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

183799 clconf: CSR not initialized

Description:

While executing task in clconf and modifying the state of proxy, found component CSR not initialized.

Solution:

Check the CSR component in the configuration file.

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.

184139 scvxvmlg warning - found no match for %s, removing it

Description:

The program responsible for maintaining the VxVM device namespace has discovered inconsistencies between the VxVM device namespace on this node and the VxVM configuration information stored in the cluster device configuration system. If configuration changes were made recently, then this message should reflect one of the configuration changes. If no changes were made recently or if this message does not correctly reflect a change that has been made, the VxVM device namespace on this node may be in an inconsistent state. VxVM volumes may be inaccessible from this node.

Solution:

If this message correctly reflects a configuration change to VxVM diskgroups then no action is required. If the change this message reflects is not correct, then the information stored in the device configuration system for each VxVM diskgroup should be examined for correctness. If the information in the device configuration system is accurate, then executing '/usr/cluster/lib/dcs/scvxvmlg' on this node should restore the device namespace. If the information stored in the device configuration system is not accurate, it must be updated by executing '/usr/cluster/bin/scconf -c -D name=diskgroup_name' for each VxVM diskgroup with inconsistent information.

184448 scnetapp fatal error - Cannot lookup %s

Description:

The program responsible for retrieving NetApp 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:

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:

185713 Unable to start lockd.

Description:

HA-NFS was not able to start lockd.

Solution:

This is an informative message. HA-NFS will try and restart lockd.

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.

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

Description:

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

Solution:

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

185974 Default Oracle paramter file %s does not exist

Description:

Oracle Parameter file has not been specified. Default parameter file indicated in the message does not exist.

Solution:

Please make sure that parameter file exists at the location indicated in message or specify 'Parameter_file' property for the resource.

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.

186488 INITPMF Error: ${SERVER} is running but not accessible.

Description:

The initpmf init script was unable to verify the availability of the rpc.pmfd server, even though it successfuly started. This error may prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.

Solution:

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 may have failed to start on this node. If the device group was started on another node, it may be moved to this node with the scswitch command. If the device group was not started, it may be started with the scswitch command. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group may have failed. If so, the desired action may be retried.

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.

186810 ERROR: resource %s state change to %s on node %s is INVALID because we are not running at a high enough version. Aborting node.

Description:

The rgmd on this node is running at a lower version than the rgmd on the specified node.

Solution:

Run scversions -c to commit your latest upgrade. 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.

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.

187120 MQSeriesIntegrator2%s exists without an IPC semaphore entry

Description:

The WebSphere Broker fault monitor checks to see if MQSeriesIntegrator2BrokerResourceTableLockSempahore or MQSeriesIntegrator2RetainedPubsTableLockSemaphore exists within /var/mqsi/locks and that their respective semaphore id exists.

Solution:

No user action is needed. If either MQSeriesIntegrator2%s file exists without an IPC semaphore entry, then the MQSeriesIntegrator2%s file is deleted. This prevents (a) Execution Group termination on startup with BIP2123 and (b) bipbroker termination on startup with BIP2088.

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.

187679 NULL hostname passed to validate local host function.

Description:

Need explanation of this message!

Solution:

Need a user action for this message.

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:

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.

190918 Failed to start orbixd.

Description:

The orbix daemon couldnt not be started.

Solution:

Check if orbix daemon could be started manuallyas the Broadvision user.If it can be started but couldntbe started under HA then,save a copy of the /var/adm/messages files on all nodes. Save a copy of the orbixd log files which are located in /var/run/cluster/bv/ and contact your authorized Sun service provider.

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.

191270 IP address (hostname) string %s in property %s, entry %d does not resolve to an IP address that belongs to one of the resources named in property %s.

Description:

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

Solution:

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

191409 scvxvmlg warning - chown(%s) failed

Description:

The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. If configuration changes were recently made to VxVM diskgroups or volumes, this node may be unaware of those changes. Recently created volumes may be unaccessible from this node.

Solution:

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

191492 CCR: CCR unable to read root file system.

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.

191506 ERROR: enabled resource <%s> in resource group <%s> depends on disabled resource <%s>

Description:

An enabled resource was found to depend on a disabled resource. 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.

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.

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 may have failed to start on this node. If the device group was started on another node, it may be moved to this node with the scswitch command. If the device group was not started, it may be started with the scswitch command. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group may have failed. If so, the desired action may be retried.

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.

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.

194179 Failed to stop the service %s.

Description:

Specified data service failed to stop.

Solution:

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

194481 svc_rpc_pmf: INITPMF Error: ${SERVER} is being stopped.

Description:

The start method of the SMF service svc:/system/cluster/rpc_pmf:default failed to start the pmf properly, so it is being killed. One possible reason for the failure might be an inability to create the rpc file in /var/run/scrpc. The svc:/system/cluster/rpc_pmf:default service will go into maintenance mode.

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.

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.

194810 clcomm: thread_create failed for resource_thread

Description:

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

Solution:

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

194934 ping_interval %d

Description:

The ping_interval value used by scdpmd.

Solution:

No action required.

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.

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.

196538 validate_options - Fatal: SGE_ROOT %s not a directory

Description:

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

Solution:

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

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.

196779 Service failed and the fault monitor is not running on this node. Restarting service.

Description:

The process monitoring facility tried to send a message to the fault monitor noting that the data service application died. It was unable to do so.

Solution:

Since some part (daemon) of the application has failed, it would be restarted. If fault monitor is not yet started, wait for it to be started by Sun Cluster framework. If fault monitor has been disabled, enable it using scswitch.

197306 Skipping file system check of %s.

Description:

The specified mount point will not be checked because it was told to do so by specifying the FilesystemCheckCommand extension property as empty.

Solution:

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

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 scrgadm command to respecify the hostnames for this logical host resource.

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

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. You may consider increasing the Monitor_Start_timeout property. Try switching the resource group to another node using scswitch (1M).

198542 No network resources found for resource.

Description:

No network resources were found for the resource.

Solution:

Declare network resources used by the resource explicitly using the property Network_resources_used. For the resource name and resource group name, check the syslog tag.

198851 fatal: Got error <%d> trying to read CCR when disabling resource <%s>; aborting node

Description:

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

Solution:

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

199467 clcomm::ObjectHandler::_unreferenced called

Description:

This operation should never be executed.

Solution:

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

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.