Sun Cluster Error Messages Guide for Solaris OS

Message IDs 400000–499999


400592 UNIX DLM is asking for a reconfiguration to recover from a communication error. This message is acceptable during a reconfiguration already in progress.

Description:

The cluster will reconfigure.

Solution:

None.


401115 t_rcvudata (recv_request) failed

Description:

Call to t_rcvudata() failed. The "t_rcvudata" man page describes possible error codes. ucmmd will exit and the node will abort.

Solution:

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


401252 Validation failed. Resource property FAILOVER_MODE must be NONE

Description:

The resource being created or modified must have a value of NONE for its FAILOVER_MODE property.

Solution:

Specify NONE for the FAILOVER_MODE property.


401400 Successfully stopped the application

Description:

The STOP method successfully stopped the resource.

Solution:

This message is informational; no user action is needed.


401400 Successfully stopped the application

Description:

This message is to inform the administrator that the application was topped successfully.

Solution:

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


401573 INTERNAL ERROR: START method not registered for resource <%s>

Description:

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

Solution:

Since this problem might indicate an internal logic error in the rgmd, 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.


402289 t_bind: %s

Description:

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

Solution:

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


402484 NULL command string passed.

Description:

A NULL value was specified for the command argument.

Solution:

Specify a non-NULL value for the command string.


402992 Failfast: Destroying failfast unit %s while armed.

Description:

The specified failfast unit was destroyed while it was still armed.

Solution:

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


403257 Failed to start Backup server.

Description:

Sun Cluster HA for Sybase failed to start the backup server. Other syslog messages and the log file will provide additional information on possible reasons for the failure.

Solution:

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


404190 Validate - 32|64-bit mode invalid in %s

Description:

The bit mode value for MODE is invalid.

Solution:

Ensure that the bit mode value for MODE equals 32 or 64 when registering the resource.


404259 ERROR: probe_mysql Option -H not set

Description:

The -H option is missing for probe_mysql command.

Solution:

Add the -H option for probe_mysql command.


404309 in libsecurity cred flavor is not AUTH_SYS

Description:

A server (rpc.pmfd, rpc.fed or rgmd) refused an rpc connection from a client because because the authorization is not of UNIX type. An error message is output to syslog.

Solution:

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


404388 Failed to retrieve ip number for host %s

Description:

The DHCP resource tries to get the hostname ip address based on the cluster node id but failed.

Solution:

Check that the correct NETWORK parameter was used when registering the DHCP resource and that the correct cluster node id was used.


404866 method_full_name: malloc failed

Description:

The rgmd server was not able to create the full name of the method, while trying to connect to the rpc.fed server, probably 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.


404924 validate: there are syntactical errors in the parameterfile $Filename

Description:

The parameter file $Filename of option -N of the start, stop or probe command is not a valid ksh script.

Solution:

Correct the file until ksh -n filename exits with 0.


405030 Hosts in the startup order are not up.The Probe will start the processes on %s

Description:

The resource group containing the specified hostwill be online but the BV processes will not be started because the hosts in the startup order(backend hosts) are not up.The Probe will wait for these hosts to startup before starting the processes on the specified host.

Solution:

If the Resource Groups which contain the Backend resources arenot online then bring them online.If they are online then probablythe BV processes are in the process of coming up and so no need totake any action,the probe will take the appropriate action.


405201 Validation failed. Resource group property NODELIST must contain only 1 node

Description:

The resource being created or modified must belong to a group that can have only one node name in it's NODELIST property.

Solution:

Specify just one node in the NODELIST property.


405508 clcomm: Adapter %s has been deleted

Description:

A network adapter has been removed.

Solution:

No action required.


405519 check_samba - Couldn't retrieve faultmonitor-user <%s> from the nameservice

Description:

The Samba resource could not validate that the fault monitor userid exists.

Solution:

Check that the correct fault monitor userid was used when registering the Samba resource and that the userid really exists.


405552 Unable to contact fault monitor, 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.


405649 validate: User $Username does not exist but it is required

Description:

The user with the name $Username does not exist or was not returned by the name service.

Solution:

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


405989 %s can't plumb %s

Description:

This means that the Logical IP address could not be plumbed on an adapter belonging to the named IPMP group.

Solution:

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


406042 Communication module initialization error

Description:

Internal error.

Solution:

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


406610 st_ff_arm failed: %s

Description:

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

Solution:

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


406635 fatal: joiners_run_boot_methods: exiting early because of unexpected exception

Description:

The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.

Solution:

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


407784 socket: %s

Description:

The cl_apid experienced an error while constructing a socket. This error may prohibit event delivery to CRNP clients.

Solution:

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


408164 Invalid value for property %s.

Description:

The cl_apid encountered an invalid property value. If it is trying to start, it will terminate. If it is trying to reload the properties, it will use the old properties instead.

Solution:

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


408214 Failed to create scalable service group %s: %s.

Description:

A call to the underlying scalable networking code failed.

Solution:

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


408282 clcomm: RT or TS classes not configured

Description:

The system requires either real time or time sharing thread scheduling classes for use in user processes. Neither class is available.

Solution:

Configure Solaris to support either real time or time sharing or both thread scheduling classes for user processes.


408672 Removing file %s.

Description:

HA-NetBackup removes NetBackup startup and shutdown scripts from /etc/rc2.d and /etc/rc0.d to prevent automatic startup and shutdown of NetBackup.

Solution:

None. This is only an informational message.


408742 svc_setschedprio: Could not save current scheduling parameters: %s

Description:

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

Solution:

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


409267 Error opening procfs control file (for parent process) <%s> for tag <%s>: %

Description:

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

Solution:

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


409443 fatal: unexpected exception in rgm_init_pres_state

Description:

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

Solution:

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


409693 Aborting startup: failover of NFS resource groups may be in progress.

Description:

Startup of an NFS resource was aborted because a failure was detected by another resource group, which would be in the process of failover.

Solution:

Attempt to start the NFS resource after the failover is completed. It may be necessary to start the resource on another node if current node is not healthy.


410176 Failed to register callback for IPMP group %s with tag %s and callback command %s (request failed with %d).

Description:

An unexpected error occurred while trying to communicate with the network monitoring daemon (pnmd).

Solution:

Make sure the network monitoring daemon (pnmd) is running.


410272 Validate - ORACLE_HOME directory %s does not exist

Description:

The Oracle E-Business Suite ORACLE_HOME directory does not exist.

Solution:

Check that the correct pathname was entered for the Oracle Home directory when registering the resource and that the directory exists.


410860 lkcm_act: cm_reconfigure failed: %s

Description:

ucmm reconfiguration failed. This could also point to a problem with the interconnect components.

Solution:

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


411227 Failed to stop the process with: %s. Retry with SIGKILL.

Description:

Process monitor facility is failed to stop the data service. It is reattempting to stop the data service.

Solution:

This is informational message. Check the Stop_timeout and adjust it, if it is not appropriate value.


411369 Not found clexecd on node %d for %d seconds. Giving up!

Description:

Could not find clexecd to execute the program on a node. Indicated giving up after retries.

Solution:

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


412106 Internal Error. Unable to get fault monitor name

Description:

This is an internal error. Could not determine fault monitor program name.

Solution:

Please report this problem.


412106 Internal Error. Unable to get fault monitor name

Description:

This is an internal error. Could not determine fault monitor program name.

Solution:

Please report this problem.


412366 setsid failed: %s

Description:

Failed to run the "setsid" command. The "setsid" man page describes possible error codes.

Solution:

None. ucmmd will exit.


412533 clcomm: validate_policy: invalid relationship moderate %d low %d pool %d

Description:

The system checks the proposed flow control policy parameters at system startup and when processing a change request. The moderate server thread level cannot be less than the low server thread level.

Solution:

No user action required.


412558 inet addr %s length %d = %s

Description:

Information about hosts.

Solution:

None.


413513 INTERNAL ERROR Failfast: ff_impl_shouldnt_happen.

Description:

An internal error has occurred in the failfast software.

Solution:

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


413569 CCR: Invalid CCR table : %s.

Description:

CCR could not find a valid version of the indicated table on the nodes in the cluster.

Solution:

There may be other related messages on the nodes where the failure occurred. They may help diagnose the problem. If the indicated table is unreadable due to disk failure, the root disk on that node needs to be replaced. If the table file is corrupted or missing, boot the cluster in -x mode to restore the indicated table from backup. The CCR tables are located at /etc/cluster/ccr/.


414135 INITRGM Error: ${SERVER} is already running.

Description:

The initrgm init script found the rgmd already running. It will not start it again.

Solution:

No action required.


414680 fatal: register_president: Don't have reference to myself

Description:

The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.

Solution:

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


415842 fatal: scswitch_onoff: invalid opcode <%d>

Description:

While attempting to execute an operator-requested enable or disable of a resource, the rgmd has encountered an internal error. This error should not occur. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution:

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


416483 Failed to retrieve the resource information.

Description:

A Sun Cluster data service is unable to retrieve the resource information. Low memory or API call failure might be the reasons.

Solution:

In case of low memory, the problem will probably cured by rebooting. If the problem 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.


416904 Orbixd Probe failed

Description:

Just an informational message that the orbix daemon probe failed.

Solution:

No action needed.The probe will take appropriate message.


417144 Must be root to start %s

Description:

The program or daemon has been started by someone not in superuser mode.

Solution:

Login as root and run the program. If it is a daemon, it may be incorrectly installed. Reinstall cluster packages or contact your service provider.


417629 Database or gateway down.

Description:

This indicates that the Siebel database or Siebel gateway is unavailable for the Siebel server.

Solution:

Please determine the reason for Siebel database or Siebel gateway failure, and ensure that they are both running. If the Siebel server resource is not offline, it should get started by the fault monitor.


417903 clexecd: waitpid returned %d. clexecd program has encountered a failed waitpid(2) system call. The error message indicates the error number for the failure.

Solution:

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


418772 Unable to post event %lld: %s: Retrying..

Description:

The cl_eventd was unable to post an event to the sysevent queue locally, but will retry.

Solution:

No action required yet.


419220 %s restore operation failed.

Description:

In the process of creating a shared address resource the system was attempting to reconfigure the ip addresses on the system. The specified operation failed.

Solution:

Use ifconfig command to make sure that all the ip addresses are present. If not, remove the shared address resource and run scrgadm command to recreate it. If problem persists, reboot.


419291 Unable to connect to Siebel gateway.

Description:

Siebel gateway may be unreachable.

Solution:

Please verify that the Siebel gateway resource is up.


419301 The probe command <%s> timed out

Description:

Timeout occurred when executing the probe command provided by user under the hatimerun(1M) utility.

Solution:

This problem may occur when the cluster is under load. You may consider increasing the Probe_timeout property.


419384 stop dced failed rc<>

Description:

Stop of dce subcomponent failed.

Solution:

Verify configuration.


419529 INTERNAL ERROR CMM: Failure registering callbacks.

Description:

An instance of the userland CMM encountered an internal initialization error.

Solution:

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


419733 Database is already stopped.

Description:

The database does not need to be stopped.

Solution:

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


419972 clcomm: Adapter %s is faulted

Description:

A network adapter has encountered a fault.

Solution:

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


420591 BV Config Error:IMs configured on both physical and private interconnect.

Description:

The Interaction Managers are configured on both the physical hostas well as the Private host.This is not supported.The InteractionManagers should be configured on only on one,either the physicalnode or the cluster private node.

Solution:

Reconfigure the Broadvision servers with IMs only on either physicalnode or on cluster private IP.Refer to the HA-BV installation and configuration guide.


420763 Switchover (%s) error (%d) after failure to become secondary

Description:

The file system specified in the message could not be hosted on the node the message came from.

Solution:

Check /var/adm/messages to make sure there were no device errors. If not, contact your authorized Sun service provider to determine whether a workaround or patch is available.


421944 Could not load transport %s, paths configured with this transport will not come up.

Description:

Topology Manager could not load the specified transport module. Paths configured with this transport will not come up.

Solution:

Check if the transport modules exist with right permissions in the right directories.


422033 HA: exception %s (major=%d) from stop_receiving_ckpt().

Description:

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

Solution:

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


422190 Failed to reboot node: %s.

Description:

HA-NFS fault monitor was attempting to reboot the node, because rpcbind daemon was unresponsive. However, the attempt to reboot the node itself did not succeed.

Solution:

Fault monitor would exit once it encounters this error. However, process monitoring facility would restart it (if enough resources are available on the system). If rpcbind remains unresponsive, the fault monitor (restarted by PMF) would again attempt to reboot the node. If this problem persists, reboot the node. Also see message id 804791.


422214 CMM: Votecount changed from %d to %d for quorum device %ld (%s).

Description:

The votecount for the specified quorum device has been changed as indicated.

Solution:

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


422541 Failed to register with PDTserver

Description:

This means that we have lost communication with PDT server. Scalable services will not work any more. Probably, the nodes which are configured to be the primaries and secondaries for the PDT server are down.

Solution:

Need to restart any of the nodes which are configured be the primary or secondary for the PDT server.


423538 WARNING: UDLM_PROCEED was picked up by a lkcm_act, returning LKCM_NOOP

Description:

An internal warning during udlm state update.

Solution:

None.


423928 Error reading line %d from stopstate file: %s.

Description:

There was an error reading from the stopstate file at the specified line.

Solution:

Examine other syslog messages occurring around the same time on the same node, to see if the source of the problem can be identified. Check to see if their is a problem with the stopstate file.


423958 resource group %s state change to unmanaged.

Description:

This is a notification from the rgmd that a resource group's state has changed. This may be used by system monitoring tools.

Solution:

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


424061 Validation failed. ORACLE_HOME %s does not exist

Description:

Directory specified as ORACLE_HOME does not exist. ORACLE_HOME property is specified when creating Oracle_server and Oracle_listener resources.

Solution:

Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.


424061 Validation failed. ORACLE_HOME %s does not exist

Description:

Directory specified as ORACLE_HOME does not exist. ORACLE_HOME property is specified when creating Oracle_server and Oracle_listener resources.

Solution:

Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.


424095 scvxvmlg fatal error - %s does not exist

Description:

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

Solution:

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


424309 clapi_mod: Class<%s>

Description:

The clapi_mod in the syseventd received the specified event.

Solution:

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


424774 Resource group <%s> requires operator attention due to STOP failure

Description:

This is a notification from the rgmd that a resource group has had a STOP method failure or timeout on one of its resources. The resource group is in ERROR_STOP_FAILED state. This may cause another operation such as scswitch(1M), scrgadm(1M), or scha_control(1HA,3HA) to fail with a SCHA_ERR_STOPFAILED error.

Solution:

Refer to the procedure for clearing the ERROR_STOP_FAILED condition on a resource group in the Sun Cluster Administration Guide.


424783 pmf_monitor_suspend: PCRUN: %s

Description:

The rpc.pmfd server was not able to suspend the monitoring of a process and the monitoring of the process has been aborted. The message contains the system error.

Solution:

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


424816 Unable to set automatic MT mode.

Description:

The rpc.pmfd server was not able to set the multi-threaded operation mode. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.

Solution:

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


424834 Failed to connect to %s port %d for secure resource %s.

Description:

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

Solution:

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


425053 CCR: Can't access table %s while updating it on node %s errno = %d.

Description:

The indicated error occurred while updating the the indicated table on the indicated node. The errno value indicates the nature of the problem. errno values are defined in the file /usr/include/sys/errno.h. An errno value of 28 (ENOSPC) indicates that the root file system on the node is full. Other values of errno can be returned when the root disk has failed (EIO) or some of the CCR tables have been deleted outside the control of the cluster software (ENOENT).

Solution:

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


425328 validate: Return String is not set but it is required

Description:

The parameter ReturnString is not set in the parameter file

Solution:

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


425366 check_cmg - FUNDRUN = %s, FNDMAX = %s

Description:

While probing the Oracle E-Business Suite concurrent manager, the actual percentage of processes running is below the user defined acceptable limit set by CON_LIMIT when the resource was registered.

Solution:

Determine why the number of actual processes for the concurrent manager is below the limit set by CON_LIMIT. The concurrent manager resource will be restarted.


425551 getnetconfigent (open_cmd_port) failed

Description:

Call to getnetconfigent failed and ucmmd could not get network information. ucmmd will exit and the node will abort.

Solution:

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


426221 CMM: Reservation key changed from %s to %s for node %s (id = %d).

Description:

The reservation key for the specified node was changed. This can only happen due to the CCR infrastructure being changed by hand, which is not a supported operation. The system can not continue, and the node will panic.

Solution:

Boot the node in non-cluster (-x) mode, recover a good copy of the file /etc/cluster/ccr/infrastructure from one of the cluster nodes or from backup, and then boot this node back in cluster mode. If all nodes in the cluster exhibit this problem, then boot them all in non-cluster mode, make sure that the infrastructure files are the same on all of them, and boot them back in cluster mode. The problem should not happen again.


426570 Property %s can be changed only while UNIX Distributed Lock Manager is not running on the node.

Description:

This property can be changed only while UNIX Distributed Lock Manager (UDLM) is not running on the node. The UDLM on all the nodes must use identical value of this property for proper functioning of the UDLM.

Solution:

Change the RAC framework resource group to unmanaged state. Reboot all the nodes that can run RAC framework and modify the property.


426678 rgmd died

Description:

An inter-node communication failed because the rgmd died on another node. To avoid data corruption, the failfast mechanism will cause that node to halt or reboot.

Solution:

No action is required. The cluster will reconfigure automatically. Examine syslog output on the rebooted node to determine the cause of node death. The syslog output might indicate further remedial actions.


429203 Exceeded Monitor_retry_count: Fault monitor for resource %s failed to stay up.

Description:

Resource fault monitor failed to start after Monitor_retry_count number of attempts. The resource will not be monitored.

Solution:

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


429663 Node %s not in list of configured nodes

Description:

The specified scalable service could not be started on this node because the node is not in the list of configured nodes for this particluar service.

Solution:

If the specified service needs to be started on this node, use scrgadm to add the node to the list of configured nodes for this service and then restart the service.


429819 Monitor_retry_interval is not set.

Description:

The resource property Monitor_retry_interval is not set. This property specifies the time interval between two restarts of the fault monitor.

Solution:

Check whether this property is set. Otherwise, set it using scrgadm(1M).


429907 clexecd: waitpid returned %d. Returning %d to clexecd.

Description:

clexecd program has encountered a failed waitpid(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.


430357 endmqm - %s

Description:

The following output was generated from the endmqm command.

Solution:

None, if the command was successful, otherwise examine the other syslog messages occurring at the same time on the same node, to see if the cause of the problem can be identified.


430445 Monitor initialization error. Incorrect arguments

Description:

Error occurred in monitor initialization. Arguments passed to the monitor by callback methods were incorrect.

Solution:

This is an internal error. Disable the monitor and report the problem.


432144 %d entries found in property %s. For a secure %s instance %s should have one or two entries.

Description:

Since a secure Server instance can listen on only one or two ports, the specified property should have either one or two entries. A different number of entries was found.

Solution:

Change the number of entries to be either one or two.


432166 Partially successful probe of %s port %d for non-secure resource %s. (%s)

Description:

The probe was only partially successful because of the reason given.

Solution:

If the problem persists the fault monitor will correct it by doing a restart or failover. For more error description, look at the syslog messages.


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

Description:

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

Solution:

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


432473 reservation fatal error(%s) - joining_node not specified

Description:

The device fencing program has suffered an internal error.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available. Copies of /var/adm/messages from all nodes should be provided for diagnosis. It may be possible to retry the failed operation, depending on the nature of the error. If the message specifies the 'node_join' transition, then this node may be unable to access shared devices. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access shared devices. In either case, it may be possible to reacquire access to shared devices by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on all cluster nodes. If the failure occurred during the 'make_primary' transition, then a device group has failed to start on this node. If another node was available to host the device group, then it should have been started on that node. If desired, it 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.


432987 Failed to retrieve nodeid.

Description:

Data service is failed to retrieve the host information.

Solution:

If the logical host and shared address entries are specified in the /etc/inet/hosts file, check these entries are correct. If this is not the reason then check the health of the name server. For more error information, check the syslog messages.


433438 Setup error. SUPPORT_FILE %s does not exist

Description:

This is an internal error. Support file is used by HA-Oracle to determine the fault monitor information.

Solution:

Please report this problem.


433481 reservation fatal error(%s) - did_get_num_paths() error in is_scsi3_disk(), returned %d

Description:

The device fencing program has suffered an internal error.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available. Copies of /var/adm/messages from all nodes should be provided for diagnosis. It may be possible to retry the failed operation, depending on the nature of the error. If the message specifies the 'node_join' transition, then this node may be unable to access shared devices. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access shared devices. In either case, it may be possible to reacquire access to shared devices by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on all cluster nodes. If the failure occurred during the 'make_primary' transition, then a device group has failed to start on this node. If another node was available to host the device group, then it should have been started on that node. If desired, it 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.


433501 fatal: priocntl: %s (UNIX error %d)

Description:

The daemon indicated in the message tag (rgmd or ucmmd) has encountered a failed system call to priocntl(2). The error message indicates the reason for the failure. The daemon will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution:

If the error message is not self-explanatory, save a copy of the /var/adm/messages files on all nodes, and of the core file generated by the daemon. Contact your authorized Sun service provider for assistance in diagnosing the problem.


433895 INTERNAL ERROR: Invalid resource property tunable flag <%d> for property <%s>; aborting node

Description:

An internal error occurred in the rgmd while checking whether a resource property could be modified. The rgmd will produce a core file and will force the node to halt or reboot.

Solution:

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


434480 CCR: CCR data server not found.

Description:

The CCR data server could not be found in the local name server.

Solution:

Reboot the node. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.


435521 Warning: node %d does not have a weight assigned to it for property %s, but node %d is in the %s for resource %s. A weight of %d will be used for node %d.

Description:

The named node does not have a weight assigned to it, but it is a potential master of the resource.

Solution:

No user action is required if the default weight is acceptable. Otherwise, use scrgadm(1M) to set the Load_balancing_weights property to include the node that does not have an explicit weight set for it.


436659 Failed to start the adaptive server.

Description:

Sun Cluster HA for Sybase failed to start sybase server. Other syslog messages and the log file will provide additional information on possible reasons for the failure.

Solution:

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


436871 liveCache is already online.

Description:

liveCache was started up outside of Sun Cluster when Sun Cluster tries to start it up. In this case, Sun Cluster will just put the already started up liveCache under Sun Cluster's control.

Solution:

Informative message, no action is needed.


437100 Validation failed. Invalid command line parameter %s %s

Description:

Unable to process parameters passed to the call back method. This is an internal error.

Solution:

Please report this problem.


437236 dl_bind: DLPI error %u

Description:

DLPI protocol error. We cannot bind to the physical device. We are trying to open a fast path to the private transport adapters.

Solution:

Reboot of the node might fix the problem.


437834 stat of share path %s failed.

Description:

HA-NFS fault monitor reports a probe failure on a specified file system.

Solution:

Make sure the specified path exists.


437837 get_resource_dependencies - WebSphere MQ Broker Queue Manager resource %s already set

Description:

The WebSphere MQ Broker resource checks to see if the correct resource dependencies exists, however it appears that there already is a WebSphere MQ Broker Queue manager defined in resource_dependencies when registering the WebSphere MQ Broker resource.

Solution:

Check the resource_dependencies entry when you registered the WebSphere MQ Broker resource.


437975 The property %s cannot be updated because it affects the scalable resource %s.

Description:

The property named is not allowed to be changed after the resource has been created.

Solution:

If the property must be changed, then the resource should be removed and re-added with the new value of the property.


438175 HA: exception %s (major=%d) from start_receiving_ckpt().

Description:

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

Solution:

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


438199 Validate - Samba configuration directory %s does not exist

Description:

The Samba resource could not validate that the Samba configuration directory exists.

Solution:

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


438420 Interface %s is plumbed but is not suitable for global networking.

Description:

The specified adapter may be either point to point adapter or loopback adapter which is not suitable for global networking.

Solution:

Reconfigure the appropriate IPMP group to exclude this adapter.


438454 request addr > max \"%s\"

Description:

Error from udlm on an address request. Udlm exits and the nodes aborts and panics.

Solution:

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


438700 Some ip addresses might still be on loopback.

Description:

Some of the ip addresses managed by the specified SharedAddress resource were not removed from the loopback interface.

Solution:

Use the ifconfig command to make sure that the ip addresses being managed by the SharedAddress implementation are present either on the loopback interface or on a physical adapter. If they are present on both, use ifconfig to delete them from the loopback interface. Then use scswitch to move the resource group containing the SharedAddresses to another node to make sure that the resource group can be switched over successfully.


438866 sysinfo in getlocalhostname failed

Description:

sysinfo call did not succeed. The "sysinfo" man page describes possible error codes.

Solution:

This is an internal error. Please report this problem.


439099 HA: hxdoor %d.%d does not exist on secondary

Description:

An HA framework hxdoor is missing.

Solution:

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


440290 Archive log destination %s has error condition '%s'. Fault monitor transactions will be disabled until the error condition is cleared

Description:

The HA-Oracle fault monitor has detected an error condition with the reported archive log destnation. To avoid timing out waiting for a log switch (and causing a database restart), the fault monitor will temporarily disable it's test transactions until the error condition is cleared.

Solution:

Investigate and fix the cause of the error, and restart log archiving.


440406 Cannot check online status. Server processes are running.

Description:

HA-Oracle could not check online status of Oracle server. Oracle server processes are running but Oracle server may or may not be online yet.

Solution:

Examine 'Connetc_string' property of the resource. Make sure that user id and password specified in connect string are correct and permissions are granted to user for connecting to the server.


440530 Started the fault monitor.

Description:

The fault monitor for this data service was started successfully.

Solution:

No action needed.


440792 Warning: some resources in resource group <%s> failed to start

Description:

The indicated resource group was pending online. One or more resources' START methods failed to execute successfully. Because the resources' Failover_mode is set to NONE, the resource group is moving to the ONLINE_FAULTED state rather than failing over to another node.

Solution:

This is a warning message, no user action is needed. The operator may choose to issue an scswitch(1M) command to try switching the affected resource group to another node or to try restarting it on the same node.


441826 "pmfadm -a" Action failed for <%s>

Description:

The given tag has exceeded the allowed number of retry attempts (given by the 'pmfadm -n' option) and the action (given by the 'pmfadm -a' option) was initiated by rpc.pmfd. The action failed (i.e., returned non-zero), and rpc.pmfd will delete this tag from its tag list and discontinue retry attempts.

Solution:

This message is informational; no user action is needed.


442053 clcomm: Invalid path_manager client_type (%d)

Description:

The system attempted to add a client of unknown type to the set of path manager clients.

Solution:

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


442281 reservation error(%s) - did_get_path() error in other_node_status()

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.


442767 Failed to stop SAP processes under PMF with SIGKILL.

Description:

Failed to stop SAP processes with Process Monitor Facility(PMF) with signal.

Solution:

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


443271 clcomm: Pathend: Aborting node because %s for %u ms

Description:

The pathend aborted the node for the specified reason.

Solution:

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


443479 CMM: Quorum device %ld with gdevname %s has %d configured path - Ignoring mis-configured quorum device.

Description:

The specified number of configured paths to the specified quorum device is less than two, which is the minimum allowed. This quorum device will be ignored.

Solution:

Reconfigure the quorum device appropriately.


443746 resource %s state on node %s change to %s

Description:

This is a notification from the rgmd that a resource's state has changed. This may be used by system monitoring tools.

Solution:

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


444001 %s: Call failed, return code=%d

Description:

A client was not able to make an rpc connection to a server (rpc.pmfd, rpc.fed or rgmd) to execute the action shown, and was not able to read the rpc error. The rpc error number 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.


444078 Cleaning up IPC facilities.

Description:

Sun Cluster is cleaning up the IPC facilities used by the application.

Solution:

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


444144 clcomm: Cannot change increment

Description:

An attempt was made to change the flow control policy parameter that specifies the thread increment level. The flow control system uses this parameter to set the number of threads that are acted upon at one time. This value currently cannot be changed.

Solution:

No user action required.


446068 CMM: Node %s (nodeid = %ld) is down.

Description:

The specified node has gone down in that communication with it has been lost.

Solution:

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


446249 Method <%s> on resource <%s>: authorization error.

Description:

An attempted method execution failed, apparently due to a security violation; this error should not occur. This failure is considered a method failure. Depending on which method was being invoked and the Failover_mode setting on the resource, this might cause the resource group to fail over or move to an error state.

Solution:

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


447417 call get_dpm_global with an invalid argument

Description:

Internal error.

Solution:

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


447465 call set_dpm_global with an invalid argument

Description:

Internal error.

Solution:

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


447578 Duplicated installed nodename when Resource Type <%s> is added.

Description:

User has defined duplicated installed node name when creating resource type.

Solution:

Recheck the installed nodename list and make sure there is no nodename duplication.


447846 Invalid registration operation

Description:

The cl_apid experienced an internal error that prevented proper registration of a CRNP client.

Solution:

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


447872 fatal: Unable to reserve %d MBytes of swap space; exiting

Description:

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

Solution:

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


448703 clcomm: validate_policy: high too small. high %d low %d nodes %d pool %d

Description:

The system checks the proposed flow control policy parameters at system startup and when processing a change request. The high server thread level must be large enough to grant the low number of threads to all of the nodes identified in the message for a fixed size resource pool.

Solution:

No user action required.


448844 clcomm: inbound_invo::done: state is 0x%x

Description:

The internal state describing the server side of a remote invocation is invalid when the invocation completes server side processing.

Solution:

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


448898 %s.nodes entry in the configuration file must be between 1 and %d.

Description:

Illegal value for a node number. Perhaps the system is not booted as part of the cluster.

Solution:

Make sure the node is booted as part of a cluster.


449159 clconf: No valid quorum_vote field for node %u

Description:

Found the quorum vote field being incorrect while converting the quorum configuration information into quorum table.

Solution:

Check the quorum configuration information.


449286 Starting %s timed out with command %s.

Description:

An attempt to start the application by the command that is listed was timed out.

Solution:

Ensure the command that is listed in the message can be executed successfully outside Sun Cluster.


449288 setgid: %s

Description:

The rpc.pmfd server was not able to set the group id of a process. The message contains the system error. The server does not perform the action requested by the client, and an error message is output to syslog.

Solution:

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


449336 setsid: %s

Description:

The rpc.pmfd or rpc.fed server was not able to set the session id, and the system error is shown. An error message is output to syslog.

Solution:

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


449344 setuid: %s

Description:

The rpc.pmfd server was not able to set the user id of a process. The message contains the system error. The server does not perform the action requested by the client, and an error message is output to syslog.

Solution:

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


449661 No permission for owner to write %s.

Description:

The owner of the file does not have write permission on it.

Solution:

Set the permissions on the file so the owner can write it.


449907 scvxvmlg error - mknod(%s) failed

Description:

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

Solution:

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


450171 CL_EVENTLOG Error: /var/run is not mounted; cannot start cl_eventlogd.

Description:

The cl_eventlog init script found that /var/run is not mounted. Because cl_eventlogd requires /var/run for sysevent reception, cl_eventlogd will not be started.

Solution:

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


450173 Error accessing policy

Description:

This message appears when the customer is initializing or changing a scalable services load balancer, by starting or updating a service. The Load_Balancing_Policy is missing.

Solution:

Add a Load_Balancing_Policy parameter when creating the resource group.


450308 check_broker - Main Queue Manager processes not found

Description:

The WebSphere MQ Broker checks to see if the main WebSphere MQ processes are available before it performs a simple message flow test. If these processes are not present, the WebSphere MQ Broker fault monitor requests a restart of the broker, as the WebSphere MQ Broker is probably restarting. Furthermore this helps to avoid AMQ8041 messages when the WebSphere MQ Broker is restarting.

Solution:

None, the WebSphere MQ Broker will be restarted.


450412 Unable to determine resource group status.

Description:

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

Solution:

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


450780 Error: Unable to create scha_control timestamp file <%s> for resource <%s>

Description:

The rgmd has failed in an attempt to create a file used for the anti-"pingpong" feature. This may prevent the anti-pingpong feature from working, which may permit a resource group to fail over repeatedly between two or more nodes. The failure to create the file might indicate a more serious problem on the node.

Solution:

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


451115 ucmmd is already running.

Description:

This is informational message.

Solution:

None.


451315 Error retrieving the extension property %s: %s.

Description:

An error occurred reading the indicated extension property.

Solution:

Check syslog messages for errors logged from other system modules. If error persists, please report the problem.


451640 tag %s: stat of command file %s failed

Description:

The rpc.fed server checked the command path indicated by the tag, and this check failed, possibly because the path is incorrect. An error message is output to syslog.

Solution:

Check the path of the command.


451699 No reference to remote node %d, not forwarding event %lld

Description:

The cl_eventd cannot forward the specified event to the specified node because it has no reference to the remote node.

Solution:

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


451793 Class<%s> SubClass<%s> Pid<%d> Pub<%s> Seq<%lld> Len<%d>

Description:

The cl_eventd received the specified event.

Solution:

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


452150 Failed to start the fault monitor.

Description:

Process monitor facility has failed to start the fault monitor.

Solution:

Check whether the system is low in memory or the process table is full and correct these probelms. If the error persists, use scswitch to switch the resource group to another node.


452202 clcomm: sdoor_sendstream::send

Description:

This operation should never occur.

Solution:

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


452205 Failed to form the %s command.

Description:

The method searches the commands input to the Agent Builder for the occurence of specific Builder defined variables, e.g. $hostnames, and replaces them with appropriate value. This action failed.

Solution:

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


452279 CMM: Retry of initialization for quorum device %s was successful.

Description:

This node was fenced off from the quorum device while it was booting, so the initial attempt to access the device returned EACCES. When the access was retried, it was successful.

Solution:

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


452552 Extension property <%s> has a value of <%s>

Description:

The property is set to the indicated value.

Solution:

This message is informational; no user action is needed.


452604 CMM: Registered key on and acquired quorum device %ld (gdevname %s).

Description:

When this node was booting up, it had found only non-cluster member keys on the specified device. After joining the cluster and having its CCR recovered, this node has been able to register its keys on this device and is its owner.

Solution:

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


452716 dl_info: kstr_msg failed %d error

Description:

Could not get a DLPI info_req message to the private interconnect.

Solution:

Reboot of the node might fix the problem.


453919 Pathprefix is not set for resource group %s.

Description:

Resource Group property Pathprefix is not set.

Solution:

Use scrgadm to set the Pathprefix property on the resource group.


453919 Pathprefix is not set for resource group %s.

Description:

Resource Group property Pathprefix is not set.

Solution:

Use scrgadm to set the Pathprefix property on the resource group.


454247 Error: Unable to create directory <%s> for scha_control timestamp file

Description:

The rgmd is unable to access the directory used for the anti-"pingpong" feature, and cannot create the directory (which should already exist). This may prevent the anti-pingpong feature from working, which may permit a resource group to fail over repeatedly between two or more nodes. The failure to access or create the directory might indicate a more serious problem on the node.

Solution:

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


454449 ERROR: stop_mysql Option -L not set

Description:

The -L option is missing for stop_mysql command.

Solution:

Add the -L option for stop_mysql command.


454607 INTERNAL ERROR: Invalid resource extension property type <%d> on resource <%s>; aborting node

Description:

An attempted creation or update of a resource has failed because of invalid resource type data. This may indicate CCR data corruption or an internal logic error in the rgmd. The rgmd will produce a core file and will force the node to halt or reboot.

Solution:

Use scrgadm(1M) -pvv to examine resource properties. If the resource or resource type properties appear to be corrupted, the CCR might have to be rebuilt. If values appear correct, this may indicate an internal error in the rgmd. 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.


454930 Scheduling class %s not configured

Description:

An attempt to change the thread scheduling class failed, because the scheduling class was not configured.

Solution:

Configure the system to support the desired thread scheduling class.


456015 Validate - mysqladmin %s non-existent or non-executable

Description:

The mysqladmin command doesn't exist or is not executable.

Solution:

Make sure that MySQL is installed correctly or right base directory is defined.


456853 %s can't DOWN

Description:

This means that the Logical IP address could not be set to DOWN.

Solution:

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


457114 fatal: death_ff->arm failed

Description:

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

Solution:

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


457121 Failed to retrieve the host information for %s: %s.

Description:

The data service failed to retrieve the host information.

Solution:

If the logical hostname and shared address entries are specified in the /etc/inet/hosts file, check that the entries are correct. Verify the settings in the /etc/nsswitch.conf file include "files" for host lookup. If these are correct, check the health of the name server. For more error information, check the syslog messages.


458091 CMM: Reconfiguration delaying for %d seconds to allow larger partitions to win race for quorum devices.

Description:

In the case of potential split brain scenarios, the CMM allows larger partitions to win the race to acquire quorum devices by forcing the smaller partitions to sleep for a time period proportional to the number of nodes not in that partition.

Solution:

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


458373 fatal: cannot create thread to notify President of state changes

Description:

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

Solution:

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


458530 Method <%s> on resource <%s>: program file is not executable.

Description:

A method pathname points to a file that is not executable. This may have been caused by incorrect installation of the resource type.

Solution:

Identify registered resource type methods using scrgadm(1M) -pvv. Check the permissions on the resource type methods. Reinstall the resource type if necessary, following resource type documentation.


458880 event lacking correct names

Description:

The cl_apid event cache was unable to store an event because of the specified reason.

Solution:

No action required.


458988 libcdb: scha_cluster_open failed with %d

Description:

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

Solution:

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


459220 pthread_rwlock_unlock err %d line %d\n

Description:

Internal error.

Solution:

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


459220 pthread_rwlock_unlock err %d line %d\n

Description:

Internal error.

Solution:

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


459848 WebSphere MQ Broker RDBMS available

Description:

The WebSphere MQ Broker is dependent on the WebSphere MQ Broker DBMS. This message simple informs that the WebSphere MQ Broker RDBMS is available.

Solution:

None.


460027 Resource <%s> of Resource Group <%s> failed sanity check on node <%s>\n

Description:

Message logged for failed scha_control sanity check methods on specific node.

Solution:

No user action required.


460452 %s access error: %s Continuing with the scdpmd defaults values

Description:

No scdpmd config file (/etc/cluster/scdpm/scdpmd.conf) has been found. The scdpmd deamon uses default values.

Solution:

No action required.


460520 scvxvmlg fatal error - dcs_get_service_names_of_class(%s) failed, returned %d

Description:

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

Solution:

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


461872 check_cmg - Actual (%s) FND processes running is below limit (%s)

Description:

While probing the Oracle E-Business Suite concurrent manager, the actual percentage of processes running is below the user defined acceptable limit set by CON_LIMIT when the resource was registered.

Solution:

Determine why the number of actual processes for the concurrent manager is below the limit set by CON_LIMIT. The concurrent manager resource will be restarted.


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

Description:

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

Solution:

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


462632 HA: repl_mgr: exception invalid_repl_prov_state %d

Description:

The system did not perform this operation on the primary object.

Solution:

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


463953 %s failed to complete

Description:

The command failed.

Solution:

Check the syslog and /var/adm/messages for more details.


464588 Failed to retreive the resource group property %s: %s.

Description:

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

Solution:

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


465065 Error accessing group

Description:

This message appears when the customer is initializing or changing a scalable services load balancer, by starting or updating a service. The specified resource group is invalid.

Solution:

Check the resource group name specified and make sure that a valid value is used.


466896 Could not create file %s: %s.

Description:

Failed to create file.

Solution:

Check whether the permissions are valid. This might be the result of a lack of system resources. Check whether the system is low in memory and take appropriate action.


468199 The %s file of the Oracle UNIX Distributed Lock Manager not found or is not executable.

Description:

Unable to locale the lock manager binary. This file is installed as a part of Oracle Unix Distributed Lock Manager (UDLM). The Oracle OPS/RAC will not be able to run on this node if the UDLM is not available.

Solution:

Make sure Oracle UDLM package is properly installed on this node.


468477 Failed to retrieve the property %s: %s.

Description:

API operation has failed in retrieving the cluster property.

Solution:

For property name, check the syslog message. For more details about API call failure, check the syslog messages from other components.


468477 Failed to retrieve the property %s: %s.

Description:

An internal error occurred in the rgmd while checking a cluster property.

Solution:

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


468732 Too many modules configured for autopush.

Description:

The system attempted to configure a clustering STREAMS module for autopush but too many modules were already configured.

Solution:

Check in your /etc/iu.ap file if too many modules have been configured to be autopushed on a network adapter. Reduce the number of modules. Use autopush(1m) command to remove some modules from the autopush configuration.


469417 Failfast: timeout - unit \"%s\"%s.

Description:

A failfast client has encountered a timeout and is going to panic the node.

Solution:

There may be other related messages on this node which may help diagnose the problem. Resolve the problem and reboot the node if node panic is unexpected.


469817 Specified resource group does not exist: %s.

Description:

The name of a specified resource group is invalid. Such a resource group does not exist.

Solution:

This probably is the result of specifying an incorrect resource group name in an dependency, or an extension property of a resource, or resource group. Please repeat the steps which led to this error using an existing resource group name.


469892 ERROR: start_mysql Option -B not set

Description:

The -B option is missing for start_mysql command.

Solution:

Add the -B option for start_mysql command.


471186 going down on signal %d\n

Description:

scdpmd has received a signal and is goind down.

Solution:

No action required.


471241 Probing SAP Message Server times out with command %s.

Description:

Checking SAP message server with utility lgtst times out. This may happen under heavy system load.

Solution:

You might consider increasing the Probe_timeout property. Try switching the resource group to another node using scswitch (1M).


471788 Unable to resolve hostname %s

Description:

The cl_apid could not resolve the specified hostname. If this error occurs at start-up of the daemon, it may prevent the daemon from starting. Otherwise, it will prevent the daemon from delivering an event to a CRNP client.

Solution:

If the error occurred at start-up, verify the integrity of the resource properties specifying the IP address on which the CRNP server should listen. Otherwise, no action is required.


472185 Failed to retrieve the resource group property %s for %s: %s.

Description:

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

Solution:

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


473021 in libsecurity uname sys call failed: %s

Description:

A client was not able to make an rpc connection to a server (rpc.pmfd, rpc.fed or rgmd) because the host name could not be obtained. The system error message is shown. An error message is output to syslog.

Solution:

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


473141 Resource is disabled, stopping database.

Description:

The HADB database will be stopped because the resource is being disabled.

Solution:

This is an informational message, no user action is needed.491533: DB_password_file should be a regular file: %s

Description:

The DB_password_file extension property needs to be a regular file.

Solution:

Give appropriate file name to the extension property. Make sure that the path name does not point to a directory or any other file type. Moreover, the DB_password_file could be a link to a file also.580750: Auto_recovery_command should be a regular file: %s

Description:

The Auto_recovery_command extension property needs to be a regular file.

Solution:

Give appropriate file name to the extension property. Make sure that the path name does not point to a directory or any other file type. Moreover, the Auto_recovery_command could be a link to a file also.


473460 Method <%s> on resource <%s>: authorization error: %s.

Description:

An attempted method execution failed, apparently due to a security violation; this error should not occur. The last portion of the message describes the error. This failure is considered a method failure. Depending on which method was being invoked and the Failover_mode setting on the resource, this might cause the resource group to fail over or move to an error state.

Solution:

Correct the problem identified in the error message. If necessary, examine other syslog messages occurring at about the same time to see if the problem can be diagnosed. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing the problem.


473653 Failed to retrieve the resource type handle for %s while querying for property %s: %s.

Description:

Access to the object named failed. The reason for the failure is given in the message.

Solution:

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


474256 Validations of all specified global device services complete.

Description:

All device services specified directly or indirectly via the GlobalDevicePath and FilesystemMountPoint extension properties respectively are found to be correct. Other Sun Cluster components like DCS, DSDL, RGM are found to be in order. Specified file system mount point entries are found to be correct.

Solution:

None.


474576 check_dhcp - The DHCP has died

Description:

The DHCP resource's fault monitor has found that the DHCP process has died.

Solution:

None, the DHCP resource's fault monitor will request a restart of the DHCP server.


474690 clexecd: Error %d from send_fd

Description:

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

Solution:

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


475398 Out of memory (memory allocation failed):%s.%s

Description:

There is not enough swap space on the system.

Solution:

Add more swap space. See swap(1M) for more details.


475611 Fault monitor probe response time exceeded extended timeout (%d secs). The database should be checked for hangs or locking problems, or the probe timeout should be increased accordingly

Description:

The time taken for the last fault monitor probe to complete was greater than the probe timeout, which had been increased by 10% because of previous slow response.

Solution:

The database should be investigated for the cause of the slow response and the problem fixed, or the resource's probe timeout value increased accordingly.


476023 Validate - DHCP is not enabled (DAEMON_ENABLED)

Description:

The DHCP resource requires that that the /etc/inet/dhcpsvc.conf file has DAEMON_ENABLED=TRUE.

Solution:

Ensure that /etc/inet/dhcpsvc.conf has DAEMON_ENABLED=TRUE by configuring DHCP appropriately, i.e. as defined within the Sun Cluster 3.0 Data Service for DHCP.


476157 Failed to get the pmf_status. Error: %s.

Description:

A method could not obtain the status of the service from PMF. The specific cause for the failure may be logged with the message.

Solution:

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


477296 Validation failed. SYBASE ASE STOP_FILE %s not found.

Description:

File specified in the STOP_FILE extension property was not found. Or the file specified is not an ordinary file.

Solution:

Please check that file specified in the STOP_FILE extension property exists on all the nodes.


477378 Failed to restart the service.

Description:

Restart attempt of the dataservice is failed.

Solution:

Check the sylog messages that are occurred just before this message to check whether there is any internal error. In case of internal error, contact your Sun service provider. Otherwise, any of the following situations may have happened. 1) Check the Start_timeout and Stop_timeout values and adjust them if they are not appropriate. 2) This might be the result of lack of the system resources. Check whether the system is low in memory or the process table is full and take appropriate action.


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

Solution:

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


478523 Could not mount '%s' because there was an error (%d) in opening the directory.

Description:

While mounting a Cluster file system, the directory on which the mount is to take place could not be opened.

Solution:

Fix the reported error and retry. The most likely problem is that the directory does not exist - in that case, create it with the appropriate permissions and retry.


479015 Validate - DHCP directory %s does not exist

Description:

The DHCP resource could not validate that the DHCP directory defined in the /etc/inet/dhcpsvc.conf file for the PATH variable exists.

Solution:

Ensure that /etc/inet/dhcpsvc.conf has the correct entry for the PATH variable by configuring DHCP appropriately, i.e. as defined within the Sun Cluster 3.0 Data Service for DHCP.


479105 Can not get service status for global service <%s> of path <%s>

Description:

Can not get status for the global service. This is a servere problem.

Solution:

Contact your authorized Sun service provider to determine what is the cause of the problem.


479184 Failed to signal cl_apid.

Description:

The update method for the SUNW.Event service was unable to notify the cl_apid following changes to property values.

Solution:

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


479213 Monitor server terminated.

Description:

Graceful shutdown did not succeed. Monitor server processes were killed in STOP method. It is likely that adaptive server terminated prior to shutdown of monitor server.

Solution:

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


479442 in libsecurity could not allocate memory

Description:

A server (rpc.pmfd, rpc.fed or rgmd) was not able to start, or a client was not able to make an rpc connection to the server, probably due to low memory. An error message is output to syslog.

Solution:

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


480354 Error on line %ld: %s

Description:

Indicates the line number on which the error was detected. The error message follows the line number.

Solution:

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


482531 IPMP group %s has unknown status %d. Skipping this IPMP group.

Description:

The status of the IPMP group is not among the set of statuses that is known.

Solution:

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


482901 Can't allocate binding element

Description:

Client affinity state on the node has become incomplete due to unexpected memory shortage. New connections from some clients that have existing connections with this node might go to a different node as a result.

Solution:

If client affinity is a requirement for some of the sticky services, say due to data integrity reasons, these services must be brought offline on the node, or the node itself should be restarted.


483160 Failed to connect to socket: %s.

Description:

While determing the health of the resource, process monitor facility has failed to communicate with the resource fault monitor.

Solution:

Any of the following situations might have occurred. 1) Check whether the fault monitor is running, if not wait for the fault monitor to start. 2) Check whether the fault monitor is disabled, if it is then user can enable the fault monitor, otherwise ignore it. 3) In all other situations, consider it as an internal error. Save /var/adm/messages file and contact your authorized Sun service provider. For more error description check the syslog messages.


483528 NULL value returned for resource name.

Description:

A null value was returned for resource name.

Solution:

Check the resource name.


483858 Must set at least one of Port_List or Monitor_Uri_List.

Description:

When creating the resource a Port_List or Monitor_Uri_List must be specified.

Solution:

Run the resource creation again specifying either a Port_List or Monitor_Uri_List.


484084 INTERNAL ERROR: non-existent resource <%s> appears in dependency list of resource <%s>

Description:

While attempting to execute an operator-requested enable of a resource, the rgmd has found a non-existent resource to be listed in the Resource_dependencies or Resource_dependencies_weak property of the indicated resource. This suggests corruption of the RGM's internal data but is not fatal.

Solution:

Use scrgadm(1M) -pvv to examine resource group properties. If the values appear corrupted, the CCR might have to be rebuilt. If values appear correct, this may indicate an internal error in the rgmd. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.


484513 Failed to retrieve the probe command with error <%d>. Will continue to do the simple probe.

Description:

The fault monitor failed to retrieve the probe command from the cluster configuration. It will continue using the simple probe to monitor the application.

Solution:

No action required.


485464 clcomm: Failed to allocate simple xdoor server %d

Description:

The system could not allocate a simple xdoor server. This can happen when the xdoor number is already in use. This message is only possible on debug systems.

Solution:

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


485680 reservation warning(%s) - Unable to lookup local_only flag for device %s.

Description:

The device fencing program was unable to determine if the specified device is marked as local_only. This device will be treated as a non- local_only device and nodes not within the cluster will be fenced from it.

Solution:

If the device in question is marked marked as local_only and is being used as the boot device or the mirror of a boot device for a node, then that node may be unable to access this device and hence, unable to boot. Contact your authorized Sun service provider to determine whether a workaround or patch is available.


485759 transition '%s' failed for cluster '%s'

Description:

The mentioned state transition failed for the cluster. udlmctl will exit.

Solution:

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


485942 (%s) sigprocmask failed: %s (UNIX errno %d)

Description:

Call to sigprocmask() failed. The "sigprocmask" man page describes possible error codes. udlmctl will exit.

Solution:

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


486301 Confdir_list %s is not defined via macro CONFDIR_LIST in script %s/%s/db/sap/lccluster.

Description:

Confdir_list path which is listed in the message is not defined in the script 'lccluster' which is listed in the message.

Solution:

Make sure the path for Confdir_list is defined in the script lccluster using parameter 'CONFDIR_LIST'. The value should be defined inside the double quotes, and it is the same as what is defined for extension property 'Confdir_list'.


486841 SIOCGLIFCONF: %s

Description:

The ioctl command with this option failed in the cl_apid. This error may prevent the cl_apid from starting up.

Solution:

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


487022 The networking components for scalable resource %s have been configured successfully for method %s.

Description:

The calls to the underlying scalable networking code succeeded.

Solution:

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


487418 libsecurity: create of rpc handle to program %s (%lu) failed, will not retry

Description:

A client of the specified server was not able to initiate an rpc connection, after multiple retries. The maximum time allowed for connecting has been exceeded, or the types of rpc errors encountered indicate that there is no point in retrying. An accompanying error message shows the rpc error data. The pmfadm or scha command exits with error. The program number is shown. To find out what program corresponds to this number, use the rpcinfo command. An error message is output to syslog.

Solution:

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


487484 lkcm_reg: lib initialization failed

Description:

udlm could not register with cmm because lib initialization failed.

Solution:

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


487574 Failed to alloc memory

Description:

A scha_control call failed because the system has run out of swap space. The system is likely to halt or reboot if swap space continues to be depleted.

Solution:

Investigate the cause of swap space depletion and correct the problem, if possible.


487778 RGM isn't failing resource group <%s> off of node <%d>, because there are no other current or potential masters

Description:

A scha_control(1HA,3HA) GIVEOVER attempt failed because no candidate node was healthy enough to host the resource group, and the resource group was not currently mastered by any other node.

Solution:

Examine other syslog messages on all cluster members that occurred about the same time as this message, to see why other candidate nodes were not helathy enough to master the resource group. Repair the condition that is preventing any potential master from hosting the resource group.


487827 CCR: Waiting for repository synchronization to finish.

Description:

This node is waiting to finish the synchronization of its repository with other nodes in the cluster before it can join the cluster membership.

Solution:

This is an informational message, generally no user action is needed. If all the nodes in the cluster are hanging at this message for a long time, look for other messages. The possible cause is the cluster hasn't obtained quorum, or there is CCR metadata missing or invalid. If the cluster is hanging due to missing or invalid metadata, the ccr metadata needs to be recovered from backup.


488276 in libsecurity write of file %s failed: %s

Description:

The rpc.pmfd, rpc.fed or rgmd 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.


488980 HTTP GET Response Code for probe of %s is %d. Failover will be in progress

Description:

The status code of the response to a HTTP GET probe that indicates the HTTP server has failed. It will be restarted or failed over.

Solution:

This message is informational; no user action is needed.


488988 Unable to open libxml2.so.

Description:

The SUNW.Event validate method was unable to find the libxml2.so library on the system. The Event service will not be started.

Solution:

Install the libxml2.so library.


489069 Extension property <Failover_enabled> is not defined, using the default value of TRUE.

Description:

Property failover_enabled is not be defined in RTR file. A value of TRUE is being used as default.

Solution:

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


489438 clcomm: Path %s being drained

Description:

A communication link is being removed with another node. The interconnect may have failed or the remote node may be down.

Solution:

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


489644 Could not look up host because host was NULL.

Description:

Can't look up the hostname locally in hostfile. The specified host name is invalid.

Solution:

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


489903 setproject: %s; attempting to continue the process with the system default project.

Description:

Either the given project name was invalid, or the caller of setproject() was not a valid user of the given project. The process was launched with project "default" instead of the specified project.

Solution:

Use the projects(1) command to check if the project name is valid and the caller is a valid user of the given project.


489913 The state of the path to device: %s has changed to OK

Description:

A device is seen as OK.

Solution:

No action required.


491081 resource %s removed.

Description:

This is a notification from the rgmd that the operator has deleted a resource. This may be used by system monitoring tools.

Solution:

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


491579 clcomm: validate_policy: fixed size pool low %d must match moderate %d

Description:

The system checks the proposed flow control policy parameters at system startup and when processing a change request. The low and moderate server thread levels must be the same for fixed size resource pools.

Solution:

No user action required.


491694 Could not %s any ip addresses.

Description:

The specified action was not successful for all ip addresses managed by the LogicalHostname resource.

Solution:

Check the logs for any error messages from pnm. This could be result from the lack of system resources, such as low on memory. Reboot the node if the problem persists.


491738 Local node failed to do affinity switchover to global service <%s> of path <%s>: %s

Description:

When prenet_start method of SUNW.HAStorage attempted an affinity switch, it failed.

Solution:

The affinity switchover may have failed due to an equivalent switchover having been in progress at the time. The service may indeed have successfully come online later during boot. Use the scstat (1M) -g command to verify service availability and scstat(1M) -D to identify primary server. If the service state does not reflect expected configuration, retry the affinity switchover via scswitch(1M).


492603 launch_fed_prog: fe_method_full_name() failed for program <%s>

Description:

The ucmmd was unable to assemble the full method pathname for the fed program to be launched. This is considered a launch_fed_prog failure.

Solution:

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


492781 Retrying to retrieve the resource information: %s.

Description:

An update to cluster configuration occurred while resource properties were being retrieved

Solution:

This is only an informational message.


492953 ORACLE_HOME/bin/lsnrctl not found ORACLE_HOME=%s

Description:

Oracle listener binaries not found under ORACLE_HOME. ORACLE_HOME specified for the resource is indicated in the message. HA-Oracle will not be able to manage Oracle listener if ORACLE_HOME is incorrect.

Solution:

Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.


493657 Unable to get status for IPMP group %s.

Description:

The specified IPMP group is not in functional state. Logical host resource can't be started without a functional IPMP group.

Solution:

LogicalHostname resource will not be brought online on this node. Check the messages(pnmd errors) that encountered just before this message for any IPMP or adapter problem. Correct the problem and rerun the scrgadm.


494534 clcomm: per node IP config %s%d:%d (%d): %d.%d.%d.%d failed with %d

Description:

The system failed to configure IP communications across the private interconnect of this device and IP address, resulting in the error identified in the message. This happened during initialization. Someone has used the "lo0:1" device before the system could configure it.

Solution:

If you used "lo0:1", please use another device. Otherwise, Contact your authorized Sun service provider to determine whether a workaround or patch is available.


494563 "pmfctl -S": Error suspending pid %d for tag <%s>: %d

Description:

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

Solution:

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


494913 pmfd: unknown action (0x%x)

Description:

An internal error has occurred in the rpc.pmfd server. This should not happen.

Solution:

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


495284 dl_attach: DLPI error %u

Description:

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

Solution:

Reboot of the node might fix the problem.


495386 INTERNAL ERROR: %s.

Description:

An internal error has occurred.

Solution:

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


495386 INTERNAL ERROR: %s.

Description:

An internal error has occurred.

Solution:

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


495529 Prog <%s> failed to execute step <%s> - <%s>

Description:

ucmmd failed to execute a step.

Solution:

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


495710 Stopping oracle server using shutdown immediate

Description:

Informational message. Oracle server will be stopped using 'shutdown immediate' command.

Solution:

None


496553 Validate - DHCP config file %s does not exist

Description:

The DHCP resource could not validate that /etc/inet/dhcpsvc.conf exists.

Solution:

Ensure that /etc/inet/dhcpsvc.conf exists.


496746 reservation error(%s) - USCSI_RESET failed for device %s, returned%d

Description:

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

Solution:

This may be indicative of a hardware problem, which should be resolved as soon as possible. Once the problem has been resolved, the following actions may be necessary: If the message specifies the 'node_join' transition, then this node may be unable to access the specified device. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access the device. In either case, access can be reacquired by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on all cluster nodes. If the failure occurred during the 'make_primary' transition, then a device group 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.


496884 Despite the warnings, the validation of the hostname list succeeded.

Description:

While validating the hostname list, non fatal errors have been found.

Solution:

This is informational message. It is suggested to correct the errors if applicable. For the error information, check the syslog messages that have been encountered before this message.


496991 BV Config Error:IMs not configured on either the physical or the private interconnect.

Description:

The Interaction Managers are not configured on either the physical node or on the cluster private node.

Solution:

Reconfigure the Interaction Managers on a physical host or ona cluster private IP.Refer to the HA-BV installation andconfiguration giude.


497093 WebSphere MQ Check Broker failed - see reason above

Description:

The WebSphere MQ Broker fault monitor has detected a problem, this message is provided simple to highlight that fact.

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


497795 gethostbyname() timed out.

Description:

The name service could be unavailable.

Solution:

If the cluster is under load or too much network trafiic, increase the timeout value of monitor_check method using scrgadm command. Otherwise, check if name servcie is configured correctly. Try some commands to query name serves, such as ping and nslookup, and correct the problem. If the error still persists, then reboot the node.


498582 Attempt to load %s failed: %s.

Description:

A shared address resource was in the process of being created. In order to prepare this node to handle scalable services, the specified kernel module was attempted to be loaded into the system, but failed.

Solution:

This might be the result from the lack of system resources. Check whether the system is low in memory and take appropriate action (e.g., by killing hung processes). For specific information check the syslog message. After more resources are available on the system , attempt to create shared address resource. If problem persists, reboot.


498711 Could not initialize the ORB. Exiting.

Description:

clexecd program was unable to initialize its interface to the low-level clustering software.

Solution:

This might occur because the operator has attempted to start clexecd program on a node that is booted in non-cluster mode. If the node is in non-cluster mode, boot it into cluster mode. If the node is already in cluster mode, contact your authorized Sun service provider to determine whether a workaround or patch is available.


498909 accept: %s

Description:

The cl_apid received the specified error from accept(3SOCKET). The attempted connection was ignored.

Solution:

No action required. If the problem persists, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.


499486 Unable to set socket flags: %s.

Description:

Failed to set the non-blocking flag for the socket used in communicating with the application.

Solution:

This is an internal error, no user action is required. Also contact your authorized Sun service provider.


499756 CMM: Node %s: joined cluster.

Description:

The specified node has joined the cluster.

Solution:

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


499775 resource group %s added.

Description:

This is a notification from the rgmd that a new resource group has been added. This may be used by system monitoring tools.

Solution:

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


499940 Attempted client registration would exceed the maximum clients allowed: %d

Description:

The cl_apid refused a CRNP client registration request because it would have exceeded the maximum number of clients allowed to register.

Solution:

If you wish to provide access to the CRNP service for more clients, modify the max_clients parameter on the SUNW.Event resource.