Sun Cluster Error Messages Guide for Solaris OS

Message IDs 400000–499999

This section contains message IDs 400000–499999.


400164 SCSLM <%s> pool_put_property <%s> error <%s>

Description:

Should never occur.

Solution:

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


400225 Function: validate: Return code for failed connections %s is not numeric

Description:

The value for the NOCONRET variable contains a non numeric character.

Solution:

Fix the NOCONRET variable in the parameter file.


400579 in libsecurity for program %s (%lu); could not register on any transport in /etc/netconfig

Description:

A server (rpc.pmfd, rpc.fed or rgmd) was not able to register with rpcbind and not able to create the "cache" files for any transport. An error message is output to syslog.

Solution:

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


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

Description:

The cluster will reconfigure.

Solution:

None.


400904 fatal: getzoneid() failed. Unable to verify privilege.

Description:

The cl_apid was unable to query the zoneid and hence exited prematurely.

Solution:

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


401115 t_rcvudata (recv_request) failed

Description:

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

Solution:

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


401190 Monitor check for derby data service successful.

Description:

The data service successfully checked that node.

Solution:

This message is informational; no user action is needed.


401400 Successfully stopped the application

Description:

The STOP method successfully stopped the resource.

Solution:

This message is informational; no user action is needed.


402190 Validate - %s bin directory %s does not exist

Description:

The Samba bin directory does not exist.

Solution:

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


402289 t_bind: %s

Description:

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

Solution:

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


402359 dl_attach: DL_ERROR_ACK access error

Description:

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

Solution:

Reboot of the node might fix the problem


402484 NULL command string passed.

Description:

A NULL value was specified for the command argument.

Solution:

Specify a non-NULL value for the command string.


402992 Failfast: Destroying failfast unit %s while armed.

Description:

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

Solution:

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


403257 Failed to start Backup server.

Description:

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

Solution:

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


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

Description:

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

Solution:

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


403701 Shutdown request successfully issued to RAC instance.

Description:

The agent successfully issued a shutdown request to the Oracle RAC instance.

Solution:

None required. Informational message.


403891 Error in scha_res_get of extn prop,res:%s, Err: %s

Description:

Cannot read the extension property

Solution:

Take action dependng on the error.Can contact your SUN vendor for updates or patches if any


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.


404500 Probe failed in the prenet start method. ucmm is aborting

Description:

The disk set or disk group failed its availability check because the UCMM is aborting.

Solution:

This is behavior valid for a node that is aborting. If the node is not aborting, determine whether the SUNW.rac_framework resource and either the SUNW.rac_svm resource or the SUNW.rac_cvm resource are online. Contact your authorized Sun service provider for further assistance in diagnosing the problem.


404866 method_full_name: malloc failed

Description:

The rgmd server was not able to create the full name of the method, while trying to connect to the rpc.fed server. This problem can occur if the machine has low memory. An error message is output to syslog.

Solution:

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


404924 validate: there are syntactical errors in the parameterfile %s

Description:

The parameterfile did not pass ksh -n filename.

Solution:

fix the parameter file until it passe ksh -n.


405019 ERROR: Option %s unknown

Description:

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

Solution:

Please report this problem.


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

Description:

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

Solution:

Specify just one node in the NODELIST property.


405588 ERROR: Option %s passed to a script of the telemetry data service is unknown

Description:

An unknown option was given to a program or script of the telemetry data service. This should never occur.

Solution:

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


405649 validate: User %s does not exist but it is required

Description:

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

Solution:

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


405790 gethostname() call failed : %s

Description:

A call to gethostname() failed.

Solution:

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


405989 %s can't plumb %s.

Description:

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

Solution:

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


406042 Communication module initialization error

Description:

Internal error.

Solution:

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


406321 INTERNAL ERROR CMM: Cannot resolve type registry object in local name server.

Description:

This is an internal error during node initialization, and the system can not continue.

Solution:

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


406429 Waiting for %s service to be moved into disabled/maintenance state.

Description:

The specified SMF service is being moved to disabled/maintenance state.

Solution:

This is an informational message. No action is needed.


406610 st_ff_arm failed: %s

Description:

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

Solution:

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


406635 fatal: joiners_run_boot_methods: exiting early because of unexpected exception

Description:

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

Solution:

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


407357 in libsecurity strong UNIX authorization failed

Description:

A cluster daemon refused an RPC connection from a client because it failed UNIX authentication. This might happen if a caller program is required to run as superuser or as a specific user ID, and fails to do so; or if the caller is attempting to access a Sun Cluster daemon from a remote host, in a case where only local node access is permitted.

Solution:

Examine other syslog messages occurring at about the same time to see if the problem can be identified. Check that the clustering software is properly installed, and that no unauthorized user processes are running on the cluster. If these checks cannot explain the error, contact your authorized Sun service provider to determine whether a workaround or patch is available.


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.


407789 in libsecurity for program %s ;unable to get zone name

Description:

While starting up on a system running version 10 or above of the Solaris operating environment, the indicated Sun Cluster daemon was unable to determine the name of the zone in which it is being executed.

Solution:

This message might indicate an internal error or misconfiguration of Sun Cluster software. If Sun Cluster sofware appears to be correctly installed and configured, contact your authorized Sun service provider to determine whether a workaround or patch is available.


407851 Probe for J2EE engine timed out in scds_fm_tcp_read().

Description:

The data service timed out while reading J2EE probe reply.

Solution:

Informational message. No user action is needed.


407913 Error getting handle tolibvxvm_get_volinfo

Description:

An error occurred when the library routine was called.

Solution:

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


408164 Invalid value for property %s.

Description:

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

Solution:

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


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

Description:

A call to the underlying scalable networking code failed.

Solution:

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


408254 check_dhcp - tftp transfer test generated an error code of (%s)

Description:

The tftp transfer exited with a non-zero return code.

Solution:

None required. Informational message, an immediate failover is being requested.


408282 clcomm: RT or TS classes not configured

Description:

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

Solution:

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


408621 INTERNAL ERROR: stopping_iter_deps_list: invalid dependency type <%d>

Description:

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

Solution:

Since this problem might indicate an internal logic error in the rgmd, save a copy of the /var/adm/messages files on all nodes, and the output of clresourcetype show -v, clresourcegroup show -v +, and clresourcegroup status +. Report the problem to your authorized Sun service provider.


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

Description:

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

Solution:

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


409230 ct_event_read: %s

Description:

The rpc.pmfd was unable to read the next contract event. It will retry.

Solution:

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


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

Description:

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

Solution:

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


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

Description:

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

Solution:

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


409938 Failed to get state of SMF service %s

Description:

There was a failure in attempting to determine the state of the SMF service.

Solution:

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


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

Description:

An unexpected error occurred while trying to communicate with the network monitoring daemon (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.


410358 scslm_stop: FE_SLM_ERROR %d

Description:

Resource group is under SC SLM control and an SLM error occurred. Check fed SLM errors for more details.

Solution:

Move RG_SLM_type to manual and restart the resource group.


410860 lkcm_act: cm_reconfigure failed: %s

Description:

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

Solution:

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


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

Description:

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

Solution:

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


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

Description:

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

Solution:

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


411471 Error while initializing XDR stream

Description:

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

Solution:

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


412106 Internal Error. Unable to get fault monitor name

Description:

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

Solution:

Please report this problem.


412366 setsid failed: %s

Description:

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

Solution:

None. ucmmd will exit.


412530 Error: could not start the Derby server because the directory path specified in the resource property DB_path is not valid.

Description:

The Derby server could not be started because the path specified in DB_path is not valid.

Solution:

Use a valid directory path as the value of the DB_path property.


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

Description:

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

Solution:

No user action required.


412717 scvxvmlg error - getminor called with a bad filename: %s

Description:

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

Solution:

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


413513 INTERNAL ERROR Failfast: ff_impl_shouldnt_happen.

Description:

An internal error has occurred in the failfast software.

Solution:

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


413569 CCR: Invalid CCR table : %s.

Description:

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


413925 in libsecurity ; unable to create door : %s

Description:

A Sun Cluster daemon was unable to create a door for communication with its clients. A following syslog message provides the name of the daemon that failed. This might cause the node to be rebooted or halted.

Solution:

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


414007 CMM: Placing reservation on quorum device %s failed.

Description:

An error was encountered while trying to place a reservation on the specified quorum device, hence this node can not take ownership of this quorum device.

Solution:

There may be other related messages on this and other nodes connected to this quorum device that may indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.


414281 %s affinity property for %s resource group is set. Retry_count cannot be greater than 0.

Description:

The specified affinity has been set for the specified resource group. That means the SAP enqueue server is running with the replica server. Hence the retry_count for SAP enqueue server resource must not restart locally. Therefore, the Retry_count must be set to zero.

Solution:

Set the value for Retry_count to zero for the SAP enqueue server resource.


414431 Unable to create server thread for immediate failfast of zone %s with zone ID %d

Description:

A server thread that is needed for failfasting a zone could not be created. This might be due to lack of memory.

Solution:

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


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

Description:

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

Solution:

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


414705 RGM unblocked, encountered an exception

Description:

The RGM returned from the blocking invocation with an exception. The process that hosts the server object might have terminated. As a result of this, RGM might try to bring the resources online that need global file systems data. The data might not be available yet, which might result in failure to start the resource groups.

Solution:

Save a copy of /var/adm/messages, /var/cluster/logs/ql_server_debug.log and /var/cluster/logs/install/ql_upgrade_debug.log on all the nodes. Report the problem to your authorized Sun service provider.


415110 Error: pmfadm could not start fault monitor, tag "%s" error="%s"

Description:

The PMF could not start the CRS framework monitor.

Solution:

Check for other errors on the system and correct them before restarting the CRS framework resource. If you cannot resolve this problem, contact your Sun service representative for assistance.


415591 SCSLM fstat <%s> error <%s>

Description:

Should never occur.

Solution:

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


415619 srm_function - The user %s does not belongs to project %s

Description:

The specified user does not belong to the project defined by Resource_project_name or Rg_project_name.

Solution:

Add the user to the defined project in /etc/project.


415736 Failed to retrieve failback value.

Description:

Unable to retrieve the failback property value.

Solution:

Check the resource group configuration in which this resource is configured. If the problem persists, contact your authorized Sun service provider with copies of /var/adm/messages files on all nodes.


415842 fatal: scswitch_onoff: invalid opcode <%d>

Description:

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

Solution:

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


416483 Failed to retrieve the resource information.

Description:

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

Solution:

In case of low memory, the problem will probably cured by rebooting. If the problem recurs, you might need to increase swap space by configuring additional swap devices. Otherwise, if it is API call failure, check the syslog messages from other components.


416930 fatal: %s: internal error: bad state <%d> for resource group <%s>

Description:

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

Solution:

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


417144 Must be root to start %s

Description:

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

Solution:

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


417232 scvxvmlg warning - %s does not link to %s, changing it

Description:

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

Solution:

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


417629 Database or gateway down.

Description:

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

Solution:

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


417740 Unregistered syscall. %s(%d)

Description:

An event which was not registered for, has been received. This can happen if the monitored process is simultaneously being controlled by another process, most notably, by a proc tool.

Solution:

This is informational. No action is needed.


417903 clexecd: waitpid returned %d.

Description:

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

Solution:

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


418511 XDR Error while decoding return arguments.

Description:

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

Solution:

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


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

Description:

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

Solution:

No action required yet.


418787 Dependency on %s or %s not defined

Description:

A ScalDeviceGroup resource is defined without the required dependency on a resource of type SUNW.rac_svm or of type SUNW.rac_svm.

Solution:

Modify the ScalDeviceGroup resource to depend on a resource either of type SUNW.rac_svm or of type SUNW.rac_cvm.


418869 clq_scsi3: Error %d from MHIOCGRP_INRESV --- failed to read reservations from quorum device %s.

Description:

An error was encountered while trying to read reservations on the specified quorum device.

Solution:

There may be other related messages on this and other nodes connected to this quorum device that may indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.


419061 getlocalhostname() failed; unable to execute zoneadm reboot for zone %s

Description:

The rgmd daemon was unable to obtain the name of the local host, causing a zoneadm reboot invocation to fail. The zone will stay up, but the rgmd will not attempt to start services on it.

Solution:

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


419291 Unable to connect to Siebel gateway.

Description:

Siebel gateway may be unreachable.

Solution:

Please verify that the Siebel gateway resource is up.


419301 The probe command <%s> timed out

Description:

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

Solution:

This problem might occur when the cluster is under load. Consider increasing the Probe_timeout property.


419529 INTERNAL ERROR CMM: Failure registering callbacks.

Description:

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

Solution:

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


419733 Database is already stopped.

Description:

The database does not need to be stopped.

Solution:

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


419972 clcomm: Adapter %s is faulted

Description:

A network adapter has encountered a fault.

Solution:

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


420338 Validate - RUN_MODE has to be server

Description:

The DHCP resource requires that that the /etc/inet/dhcpsvc.conf file has RUN_MODE=SERVER.

Solution:

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


420573 Error sending signal to contract <%d>: %s

Description:

The rpc.pmfd was not able to send the requested signal to the specified contract id.

Solution:

If the message is isolated, it was probably a transient error. If you were running pmfadm(1M) directly, retry the requested action. If there are many instances of the message, there is a problem with the contract file system. Search for other syslog error messages on the same node. Save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.


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

Description:

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

Solution:

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


420823 XDR Error while encoding return arguments.

Description:

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

Solution:

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


421576 Validation failed. PARAMETER_FILE: %s does not exist.

Description:

The file that the extension property parameter_file specifies does not exist.

Solution:

Check that the extension property parameter_file specifies the correct file name. If the file name is correct, check that the file system where the file resides is accessible. If the file system is accessible, check that the file exists on all nodes where the resource can be brought online. If the file exists on all nodes, check that the access permissions of the file are correct. If the problem persists, contact your Sun support representative for further assistance.


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

Description:

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

Solution:

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


421967 Cannot stat() home directory: %s

Description:

Home directory of the SAP admin user could not be checked.

Solution:

Ensure that the directory is accessible from all relevant cluster nodes.


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

Description:

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

Solution:

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


422190 Failed to reboot node: %s.

Description:

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

Solution:

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


422302 scnetapp fatal error - Unexpected filer type(%s) in table %s

Description:

The program responsible for retrieving NetApp NAS configuration information from the CCR has suffered an internal error. Continued errors of this type may lead to a compromise in data integrity.

Solution:

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


422541 Failed to register with PDTserver

Description:

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

Solution:

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


422561 SCSLM zone <%s> rg_name <%s> not found

Description:

Should never occur.

Solution:

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


422570 Probing thread failed to wait on Condition variable : %s

Description:

The thread that was created to perform a probe failed.

Solution:

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


422594 Error: The resource property RESOURCE_DEPENDENCIES must contain the "%s" resource.

Description:

An attempt was made to create or update a CRS framework resource without specifying a dependency on the RAC framework resource.

Solution:

Repeat the attempt to create or update the CRS framework resource, specifying the required dependency on the RAC framework resource.


423137 A resource restart attempt on resource %s in resource group %s has been blocked because the number of restarts within the past Retry_interval (%d seconds) would exceed Retry_count (%d)

Description:

A request to restart a resource is denied because the resource has already been restarted Retry_count times within the past Retry_interval seconds

Solution:

No action required. If desired, use clresourcegroup to change the Failover_mode setting.


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

Description:

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

Solution:

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


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

Description:

An internal warning during udlm state update.

Solution:

None.


423704 Validate - DHCP config file %s does not exist

Description:

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

Solution:

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


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

Description:

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

Solution:

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


423958 resource group %s state change to unmanaged.

Description:

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

Solution:

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


424061 Validation failed. ORACLE_HOME %s does not exist

Description:

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

Solution:

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


424083 Validation failed. Specified DB_NAME %s not registered with CRS

Description:

Creation of a resource of type SUNW.scalable_rac_server_proxy failed because the specified DB_NAME %s is not recognized by CRS as a valid RAC database.

Solution:

Verify using CRS interfaces whether the specified DB_NAME is valid or not. If the problem persists, contact your Sun support representative for further assistance.


424683 SCSLM file <%s> is empty

Description:

Should never occur.

Solution:

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


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

Description:

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

Solution:

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


424783 pmf_monitor_suspend: PCRUN: %s

Description:

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

Solution:

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


424816 Unable to set automatic MT mode.

Description:

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

Solution:

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


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.


425044 Unable to attach zone %s to door server; programs in this zone will not be able to post sysevents

Description:

A non-global zone booted on this node, but the clustering software was unable to configure it properly. Programs in this zone will not be able to post system events. System events are used for keeping an audit trail of cluster behavior.

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.


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.


425256 Started SAP processes successfully w/o PMF.

Description:

The data service started the processes w/o PMF.

Solution:

Informational message. No user action is needed.


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

Description:

-2 The Return string is not set in the parameter file.

Solution:

-2 Specify the ReturnString in the parameter file.


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

Description:

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

Solution:

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


425551 getnetconfigent (open_cmd_port) failed

Description:

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

Solution:

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


425618 Failed to send ICMP packet: %s

Description:

There was a problem in sending an ICMP packet over a raw socket.

Solution:

If the error message string thats logged in this message does not offer any hint as to what the problem could be, contact your authorized Sun service provider.


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

Description:

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

Solution:

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


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

Description:

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

Solution:

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


426613 Error: unable to bring Resource Group <%s> ONLINE, because one or more Resource Groups with a strong negative affinity for it are in an error state.

Description:

The rgmd is unable to bring the specified resource group online on the specified node because one or more resource groups related to it by strong affinities are in an error state.

Solution:

Find the errored resource groups(s) by using clresourcegroup status, and clear their error states by using clresourcegroup clear. If desired, use clresourcegroup to change the resource group affinities.


426721 Diskgroup (%s) could not be found!

Description:

The disk set or disk group that is being validated was not found.

Solution:

Determine whether the disk set or disk group was removed. Contact your authorized Sun service provider for assistance in diagnosing the problem.


426827 reservation error(%s) - Unable to gain access to device '%s', errno %d

Description:

The device fencing program has encountered errors while trying to access a device.

Solution:

Another cluster node has fenced this node from the specified device, preventing this node from accessing that device. Access should have been reacquired when this node joined the cluster, but this must have experienced problems. If the message specifies the 'node_join' transition, this node will be unable to access the specified device. If the failure occurred during the 'make_primary' transition, then this will be unable to access the specified device and a device group that contains the specified device might have failed to start on this node. An attempt can be made to acquire access to the device by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on this node. If a device group failed to start on this node, the cldevicegroup command can be used to start the device group on this node if access can be reacquired. If the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.


428011 pnmd has requested an immediate failover of all scalable resources dependent on IPMP group %s

Description:

All network interfaces in the IPMP group have failed. All of these failures were detected by the hardware drivers for the network interfaces, and not by in.mpathd probes. In such a situation pnmd requests all scalable resources to fail over to another node without any delay.

Solution:

No user action is needed. This is an informational message that indicates that the scalable resources will be failed over to another node immediately.


428036 Function: validate - %s state is %

Description:

The SMF service state is not installed or ready.

Solution:

If the SMF service is required to be managed by the Sun Cluster the SMF satte must be either installed or ready.


428115 Failed to open SAM-FS volume file %s: %s.

Description:

HA Storage Plus was not able to open the specified volume that is part of the SAM-FS file system.

Solution:

Check the SAM-FS file system configuration. If the problem persists, contact your authorized Sun service provider.


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.


429549 reservation warning(%s) - MHIOCGRP_REGISTERANDIGNOREKEY error(%d) will retry in %d seconds

Description:

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

Solution:

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


429663 Node %s not in list of configured nodes

Description:

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

Solution:

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


429962 Successfully unmounted %s.

Description:

HA Storage Plus successfully mounted the specified file system.

Solution:

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


430034 Monitor for resource %s successfully stopped.

Description:

The monitor for HA-KDC has been stopped.

Solution:

This is for informational purposes, no action is required.


430296 Starting Proxy monitor. pmf tag %s

Description:

The agent is attempting to startup the Monitor of a resource of type SUNW.scalable_rac_server_proxy.

Solution:

None required. Informational message.


430445 Monitor initialization error. Incorrect arguments

Description:

Error occured 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.


431650 User %s does not exist

Description:

The User list operation failed for broker_user.

Solution:

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


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 name on this node.

Description:

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

Solution:

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


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

Description:

The device fencing program has suffered an internal error.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available. Copies of /var/adm/messages from all nodes should be provided for diagnosis. It may be possible to retry the failed operation, depending on the nature of the error. If the message specifies the 'node_join' transition, then this node may be unable to access shared devices. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access shared devices. In either case, it may be possible to reacquire access to shared devices by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on all cluster nodes. If the failure occurred during the 'make_primary' transition, then a device group has failed to start on this node. If another node was available to host the device group, then it should have been started on that node. If desired, it might be possible to switch the device group to this node by using the cldevicegroup command. If no other node was available, then the device group will not have been started. You can use the cldevicegroup command to retry the attempt to start the device group. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group has failed. The desired action may be retried.


432951 %s is not a directory.

Description:

The path listed in the message is not a directory.

Solution:

Specify a directory path for the extension property.


432987 Failed to retrieve nodeid.

Description:

Data service is failed to retrieve the host information.

Solution:

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


433041 The Diskgroup (%s) is not imported on this node.

Description:

The VxVM disk group has not been imported.

Solution:

Ensure that the SUNW.rac_framework resource and the SUNW.rac_cvm resource are online.


433438 Setup error. SUPPORT_FILE %s does not exist

Description:

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

Solution:

Please report this problem.


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

Description:

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

Solution:

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


433689 CVM version is not compatible

Description:

The version of the library libvxvmsc.so is incompatible with this version of Sun Cluster.

Solution:

Install a compatible version of the library libvxvmsc.so.


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

Description:

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

Solution:

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


434480 CCR: CCR data server not found.

Description:

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

Solution:

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


434733 All WebSphere MQ non-attached IPC shared memory segments removed

Description:

All the WebSphere MQ shared memory segments that were not being used have been removed.

Solution:

None required. Informational message.


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 clresourcegroup set -p Load_balancing_weights=<value> <RG_NAME> to set the Load_balancing_weights property to include the node that does not have an explicit weight set for it.


435929 Validation failed. Resource group property RG_AFFINITIES should specify affinities only on SCALABLE resource groups.

Description:

The resource group should have affinities only on resource groups that are of type SCALABLE.

Solution:

Ensure that only resource groups of type SCALABLE are specified in the RG_AFFINITIES property of the Resource Group that is to contain the Proxy Resource.


435944 Error: could not start the Derby server, check whether the port specified in the resource property DB_port is already used.

Description:

The Derby server could not be started probably because the port specified in DB_port is already used.

Solution:

Check the resource property DB_port of the Derby data service and try to use another port number.


436659 Failed to start the adaptive server.

Description:

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

Solution:

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


436871 liveCache is already online.

Description:

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

Solution:

Informative message, no action is needed.


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

Description:

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

Solution:

Please report this problem.


437350 File system associated with mount point %s is to be locally mounted. Local file systems cannot be specified with scalable service resources.

Description:

HA Storage Plus detected an inconsistency in its configuration: the resource group has been specified as scalable, hence local file systems cannot be specified in the FilesystemMountPoints extension property.

Solution:

Correct either the resource group type or remove the local file system from the FilesystemMountPoints extension property.


437834 stat of share path %s failed: %s.

Description:

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

Solution:

Make sure the specified path exists.


437850 in libsecurity for program %s (%lu); svc_reg failed for transport %s. Remote clients won't be able to connect

Description:

A server (rpc.pmfd, rpc.fed or rgmd) was not able to register with rpcbind. The server should still be able to receive requests from clients using the "cache" files under /var/run/scrpc/ but remote clients won't be able to connect. An error message is output to syslog.

Solution:

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


437950 Global service %s associated with path %s is found to be unavailable: %s.

Description:

The DCS reported that the specified global service was unavailable.

Solution:

Check the device links (SCSI, Fiberchannel, etc.) cables.


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.


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.


438700 Some ip addresses might still be on loopback.

Description:

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

Solution:

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


438866 sysinfo in getlocalhostname failed

Description:

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

Solution:

This is an internal error. Please report this problem.


439933 monitor_check: call to rpc.fed failed for resource <%s>, resource group <%s>, node <%s>, method <%s>

Description:

A scha_control(1HA,3HA) GIVEOVER attempt failed, due to a failure of the rgmd to communicate with the rpc.fed daemon. If the rpc.fed process died, this might lead to a subsequent reboot of the node. Otherwise, this will prevent a resource group on the local node from failing over to an alternate primary node

Solution:

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


440289 validate: The N1 Grid Service Provisioning System local distributor agent start command does not exist, its not a valid local distributor installation

Description:

The Basepath is set to a false value.

Solution:

Set the Basepath to the right directory


440406 Cannot check online status. Server processes are running.

Description:

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

Solution:

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


440477 Validate - This version of samba <%s> is not supported with this dataservice

Description:

The Samba resource check to see that an appropriate version of Samba is being deployed. Versions below v2.2.2 will generate this message.

Solution:

Ensure that the Samba version is equal to or above v2.2.2


440530 Started the fault monitor.

Description:

The fault monitor for this data service was started successfully.

Solution:

No action needed.


441874 Ignoring %s set in environment file %s

Description:

HA-Oracle methods read the file specified by the USER_ENV property and set the environment variables declared in this file. If an entry in the file specified by the USER_ENV property tries to set a critical environment variable, that entry is ignored.

Solution:

Check USER_ENV and remove any entries which attempt to set the environment variable specified in the error message.


442053 clcomm: Invalid path_manager client_type (%d)

Description:

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

Solution:

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


442581 request addr > max "%s"

Description:

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

Solution:

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


442767 Failed to stop SAP processes under PMF with SIGKILL.

Description:

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

Solution:

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


442846 in libsecurity for program %s ; creat of file %s failed: %s

Description:

A Sun Cluster daemon was unable to create a door descriptor for communication with its clients. A following syslog message provides the name of the daemon that failed. This might cause the node to be rebooted or halted.

Solution:

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


442862 scha_cluster_open() failed: %s

Description:

A call to scha_cluster_open() failed.

Solution:

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


443010 WARNING !!! Current node is hosting the MDS Resource %s, file-system %s has been left in mounted-state...

Description:

An attempt to unmount a shared QFS file system failed because the current node is hosting the metadata server resource for the file system. The attempt to unmount the file system occurred because the ScalMountPoint resource was going offline on the current node.

Solution:

Manually switch over the metadata resource to another suitable node and unmount the shared QFS file system.


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

Description:

The pathend aborted the node for the specified reason.

Solution:

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


443542 repl_check fatal error - could not load DID repl list

Description:

An error was encountered while checking for replicated device groups.

Solution:

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


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

Description:

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

Solution:

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


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

Description:

A client was not able to make an RPC or door connection to a server (rpc.pmfd, rpc.fed or rgmd) to execute the action shown. The error number is shown.

Solution:

Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.


444078 Cleaning up IPC facilities.

Description:

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

Solution:

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


444144 clcomm: Cannot change increment

Description:

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

Solution:

No user action required.


444161 dl_attach: DLPI error %u

Description:

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

Solution:

Reboot of the node might fix the problem.


444334 Test-file %s is a symlink !! Not expected to be symlink.

Description:

The test file for performing I/O operations is a symbolic link. The replacement of the test file by a symbolic link might be caused by malicious activity in your system.

Solution:

Delete the symbolic link and restart the ScalMountPoint resource.


444479 Unable to allocate memory in sc delegated service_mgmt

Description:

Problem in creating memory space during service management of SMF delegated restarter

Solution:

Check the system memory usage


445216 stop_trm - WebSphere MQ Trigger Monitor %s stopped

Description:

The specified WebSphere MQ Trigger Monitor has been stopped.

Solution:

None required. Informational message.


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

Description:

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

Solution:

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


446650 SCSLM cannot modify pset <%s%s> to min=%u,max=%u

Description:

Requested number of cpus cannot be set for this resource group on this node.

Solution:

Switch the resource group on a node with enough cpus or lower RG_SLM_CPU_SHARES andor RG_SLM_PSET_MIN properties values or move RG_SLM_type to manual and restart the resource group.


446764 SCSLM lseek <%s> off is 0

Description:

Should never occur.

Solution:

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


446827 fatal: cannot create thread to notify President of status changes

Description:

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

Solution:

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


446967 Stopping Proxy monitor using pmfadm tag %s

Description:

The agent is attempting to stop the Monitor of a resource of type SUNW.scalable_rac_server_proxy.

Solution:

None required. Informational message.


447268 Proxy Daemon failed to start.

Description:

The Monitor of the SUNW.scalable_rac_server_proxy resource failed to startup.

Solution:

Try disabling the resource on the failed node. This will lead to a STOP_FAILED condition for that RAC instance resource. Try enabling the resource again. If the problem persists, contact your Sun support representative for further assistance.


447417 call get_dpm_global with an invalid argument

Description:

Internal error.

Solution:

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


447451 Not attempting to start resource group <%s> on node <%s> because this resource group has already failed to start on this node %d or more times in the past %d seconds

Description:

The rgmd is preventing "ping-pong" failover of the resource group, i.e., repeated failover of the resource group between two or more nodes.

Solution:

The time interval in seconds that is mentioned in the message can be adjusted by using clresourcegroup to set the Pingpong_interval property of the resource group.


447465 call set_dpm_global with an invalid argument

Description:

Internal error.

Solution:

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


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

Description:

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

Solution:

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


447846 Invalid registration operation

Description:

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

Solution:

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


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

Description:

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

Solution:

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


448079 Dataguard_role is IN_TRANSITION. Switchover may be in progress. Instance will not be started.

Description:

The administrator has set the 'dataguard_role' resource property to indicate that role switchover operation is in progress outside Sun Cluster control. This resource will not be started.

Solution:

If this property is incorrectly set, please set the correct value of 'dataguard_role' and restart the resource.


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

Description:

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

Solution:

No user action required.


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

Description:

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

Solution:

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


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

Description:

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

Solution:

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


449159 clconf: No valid quorum_vote field for node %u

Description:

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

Solution:

Check the quorum configuration information.


449288 setgid: %s

Description:

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

Solution:

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


449336 setsid: %s

Description:

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

Solution:

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


449344 setuid: %s

Description:

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

Solution:

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


449661 No permission for owner to write %s.

Description:

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

Solution:

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


449819 scvxvmlg fatal error - %s does not exist

Description:

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

Solution:

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


450032 SCSLM <%s> pool_resource_destroy error <%s>

Description:

Should never occur.

Solution:

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


450412 Unable to determine resource group status.

Description:

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

Solution:

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


450579 door_call: %s; will retry

Description:

The door_call failed with the specified reason.

Solution:

No action necessary.


451010 INTERNAL ERROR: stopping_iter_deps_list: meth type <%d>

Description:

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

Solution:

Since this problem might indicate an internal logic error in the rgmd, save a copy of the /var/adm/messages files on all nodes, and the output of clresourcetype show -v, clresourcegroup show -v +, and clresourcegroup status +. Report the problem to your authorized Sun service provider.


451115 ucmmd is already running.

Description:

This is informational message.

Solution:

None.


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

Description:

An error occured reading the indicated extension property.

Solution:

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


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

Description:

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

Solution:

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


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

Description:

The cl_eventd received the specified event.

Solution:

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


452202 clcomm: sdoor_sendstream::send

Description:

This operation should never occur.

Solution:

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


452205 Failed to form the %s command.

Description:

The method searches the commands input to the Agent Builder for the 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, report this problem.


452302 Validation failed. Resource property RESOURCE_DEPENDENCIES should contain at least the RAC framework resource of type SUNW.rac_framework or SUNW.rac_framework:*

Description:

The resource being created or modified must be dependent upon at least the rac_framework resource

Solution:

Amend the RESOURCE_DEPENDENCIES property to inlude the rac_framework resource


452356 CMM: Quorum device %d has been changed from %s to %s.

Description:

The name of the specified quorum device has been changed as indicated. This can happen if while this node was down, the previous quorum device was removed from the cluster, and a new one was added (and assigned the same id as the old one) to the cluster.

Solution:

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


452366 The resource '%s' is at resourcetype version '%d' that does not support zones.

Description:

The specific resource is at resourcetype version where there is no zones support.

Solution:

Upgrade the resource to latest resourcetype version which has zones support.


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

Description:

The property is set to the indicated value.

Solution:

This message is informational; no user action is needed.


452747 Reaping tcp_rio_client %p [%x]

Description:

The replyio subsystem starts deferred processing of a tcp_rio_client object.

Solution:

This message is for diagnostic purposes only; no action required.


453064 Error: ${PROCESS} is not started.

Description:

the rgmd depends on a server which is not started. The specified server probably failed to start. This error will prevent the rgmd from starting, which will prevent this node from participating as a full member of the cluster.

Solution:

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


453193 Failure in sending signal to cl_apid.

Description:

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

Solution:

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


453919 Pathprefix is not set for resource group %s.

Description:

Resource Group property Pathprefix is not set.

Solution:

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


454214 Resource %s is associated with scalable resource group %s. AffinityOn set to TRUE will be ignored.

Description:

Self explanatory.

Solution:

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


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

Description:

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

Solution:

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


454584 Error: more than one rpc.pmfd is running; will retry

Description:

The rpc.pmfd is probably in the process of forking a process to monitor. The script will retry.

Solution:

This is an informational message only: No user action is necessary.


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

Description:

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

Solution:

Use clresource show -v and clresourcetype show -v to examine resource properties. If the resource or resource type properties appear to be corrupted, the CCR might have to be rebuilt. If values appear correct, this may indicate an internal error in the rgmd. 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 don't exist or is not executable.

Solution:

Make sure that MySQL is installed correctly or right basedirectory is defined.


456036 File system checking is disabled for global file system %s.

Description:

The FilesystemCheckCommand has been specified as '/bin/true'. This means that no file system check will be performed on the specified file system. This is not advised.

Solution:

This is an informational message, no user action is needed. However, it is recommended to make HA Storage Plus check the file system upon switchover or failover, in order to avoid possible file system inconsistencies.


456853 %s can't DOWN.

Description:

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

Solution:

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


457114 fatal: death_ff->arm failed

Description:

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

Solution:

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


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

Description:

The data service failed to retrieve the host information.

Solution:

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


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 daemon was unable to create a thread upon starting up. This is a fatal error. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution:

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


458880 event lacking correct names

Description:

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

Solution:

No action required.


459216 Error determining the resource name

Description:

The program could not determine the resource name.

Solution:

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


459485 Error: could not start the Derby server because of an internal error.

Description:

The Derby command server could not be started because of an internal error.

Solution:

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


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

Description:

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

Solution:

No action required.


461673 Function: validate: Directory %s does not exist, an existing directory is required

Description:

The directory mentioned in the parameter file for the PGROOT or PGDATA variable does not exist.

Solution:

Fix the parameter file and provide an existing directoy for the variable PGROOT or PGDATA.


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

Description:

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

Solution:

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


461944 ORACLE_SID is set to a default value. Assign a

Description:

The value of the ORACLE_SID extension property should be valid and not the default value of " ".

Solution:

The default value is used to facilitate the creation of certain resource and resource group configurations. If the instance needs to be brought online, change the ORACLE_SID extension property value to the valid value for that instance using the appropriate Sun Cluster commands and retry bringing the resource online.


462032 ct_tmpl_set_informative: %s

Description:

The rpc.pmfd was unable to configure a process template in which to launch the requested service. Consequently, the rpc.pmfd was unable to launch the process under its control.

Solution:

If the message is isolated, it was probably a transient error. If you were running pmfadm(1M) directly, retry the requested action. If there are many instances of the message, there is a problem with the contract file system. Search for other syslog error messages on the same node. Save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.


462048 Telemetry data service start method timed out

Description:

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

Solution:

This message is informational; no user action needed.


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

Description:

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

Solution:

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


462253 fattach: %s

Description:

fattach failed for the specified reason. The specified program will be terminated.

Solution:

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


462632 HA: repl_mgr: exception invalid_repl_prov_state %d

Description:

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

Solution:

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


463171 Probe for derby data service successful

Description:

Derby data service probe method completed successfully.

Solution:

This message is informational; no user action needed.


463828 Failed to start Kerberos daemons.

Description:

The krb5kdc and kadmind daemons had failed to come up.

Solution:

Check the syslog messages for further information on specific configuration issues of Kerberos.


463953 %s failed to complete

Description:

The command failed.

Solution:

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


464111 validate: Directory %s does not exist

Description:

The specified directory does not exist

Solution:

Set the directory name to the right directory.


464484 Function: validate: Port %s is not numeric

Description:

In the parameter file, there is a non numeric character in the value for the PGPORT variable.

Solution:

Fix the PGPORT variable in the parameter file.


464869 Command %s failed with exit status <%d>.

Description:

Failure in executing the command.

Solution:

Check the syslog message for the command description. Check whether the system is low in memory or the process table is full and take appropriate action. Make sure that the executable exists.


465295 Command %s failed to complete - unable to catch signal: %d, HA-SAP will continue to start SAP.

Description:

Command exited abnormally as process was not able to catch a particular signal.

Solution:

Contact your authorized SAP service provider.


466153 getipnodebyname() timed out.

Description:

A call to getipnodebyname(3SOCKET) timed out.

Solution:

Check the settings in /etc/nsswitch.conf and make sure that the name resolver is not having problems on the system.


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.


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.


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

Description:

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

Solution:

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


471587 Resource <%s> is restarting too often on <%s>. Sleeping for <%d> seconds.

Description:

A misconfiguration in the application and/or its monitor probe, or an administrative action is causing continuous restart requests to be sent to the RGM. Hence RGM is blocking the requests for some time, so that too many restarts are prevented.

Solution:

Check accompanying syslog messages being issued from the application or the fault monitor of the data service to diagnose any misconfiguration issues.


471757 %s : %s

Description:

Self explanatory.

Solution:

Check the syslog messages and try to resolve the problem. If the problem persists, contact your authorized Sun service provider.


471788 Unable to resolve hostname %s

Description:

The cl_apid could not resolve the specified hostname. If this error occurs at 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.


472060 CMM: Halting because realtime callout processing is not working on this node. current_time %lld last_update_time %lld

Description:

This node is being aborted from the cluster as the CMM's realtime callout monitor thread did not run for more than the maximum allowed period. This is caused by heavy interrupt processing load or a blocked interrupt.

Solution:

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


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

Description:

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

Solution:

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


472312 Stop - can't determine Qmaster pid file - %s/qmaster.pid does not exist.

Description:

The file '${qmaster_spool_dir}/qmaster.pid' was not found. '${qmaster_spool_dir}/qmaster.pid' is the second argument to the 'Shutdown' function. 'Shutdown' is called within the stop script of the sge_qmaster-rs resource.

Solution:

Confirm the file 'qmaster.pid' exists. Said file should be found in the respective spool directory of the daemon in question.


472444 Stop - can't determine sge_schedd pid file - %s/schedd/schedd.pid does not exist.

Description:

The file '${qmaster_spool_dir}/schedd.pid' was not found. '${qmaster_spool_dir}/schedd.pid' is the second argument to the 'Shutdown' function. 'Shutdown' is called within the stop script of the sge_schedd-rs resource.

Solution:

Confirm the file 'schedd.pid' exists. Said file should be found in the respective spool directory of the daemon in question.


472501 Failed to disable resource: %s.

Description:

An attempt to disable the specified resource on this node failed.

Solution:

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


472748 Error: /usr/ucb/ps is not installed!

Description:

HA-Oracle attempted to determine if tnslsnr was running with the command /usr/ucb/ps. The /usr/ucb/ps command does not exist or is not executable.

Solution:

Please check that /usr/ucb/ps exists and has correct permissions. If /usr/ucb/ps does not exist, install the package SUNWscpu. Alternatively, shorten the listener name or path to tnslnsr so that the length of the tnslsnr command is less than 80 characters.


473021 in libsecurity uname sys call failed: %s

Description:

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

Solution:

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


473141 Resource is disabled, stopping database.

Description:

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

Solution:

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


473257 scf_transaction_create failed: %s

Description:

An API call failed.

Solution:

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


473361 Removing Device service %s

Description:

Informational message from scdidadm.

Solution:

No user action required.


473571 Mismatch between the resource group %s node list preference and the global device %s node list preference detected.

Description:

HA Storage Plus detected that the RGM node list preference and the DCS device service node list preference do not match. This is not allowed because AffinityOn is set to True.

Solution:

Correct either the RGM node list preference -or- the DCS node list preference (by using the scconf command).


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

Description:

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

Solution:

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


474256 Validations of all specified global device services complete.

Description:

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

Solution:

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


474413 Validate - sge_schedd file does not exist or is not executable at %s/sge_schedd

Description:

The file sge_schedd can not be found, or is not executable.

Solution:

Confirm the file '${SGE_ROOT}/bin/<arch>/sge_schedd' both exists at that location, and is executable.


474690 clexecd: Error %d from send_fd

Description:

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

Solution:

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


475251 Error: Sun Cluster software does not support transitioning from run level 3 to levels S (single-user), 1, or 2; halting

Description:

A transition which is not allowed by Sun Cluster software has been requested. Sun Cluster software does not permit transition from run level 3 to run level 1, 2 or S. The node is halted.

Solution:

Reboot the node.


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

Description:

There is not enough swap space on the system.

Solution:

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


475562 Successfully stopped the Node Agent %s and the server instances.

Description:

This is an informational message indicating that the Node Agent and all its Application Server instances are stopped.

Solution:

None.


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

Description:

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

Solution:

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


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

Description:

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

Solution:

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


476649 Could not lookup %s scheduling class info: %s

Description:

The server was not able to determine the scheduling mode info, and the system error is shown. An error message is output to syslog.

Solution:

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


476979 scds_pmf_stop() timed out.

Description:

Shutdown through PMF timed out.

Solution:

No user action needed.


477116 IP Address %s is already plumbed.

Description:

An IP address corresponding to a hostname in this resource is already plumbed on the system. You can not create a LogicalHostname or a SharedAddress resource with hostnames that map to that IP address.

Solution:

Unplumb the IP address or remove the hostname corresponding to that IP address from the list of hostnames in the SUNW.LogicalHostname or SUNW.SharedAddress resource.


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.

Description:

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

Solution:

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


478328 Failed to retrieve property %s of storage %s : %s

Description:

An error occurred while a property of the resource was being retrieved.

Solution:

Ensure that the property is defined for the resource. If the property is defined, investigate possible RGM or DSDL errors. Contact your authorized Sun service provider for assistance in diagnosing the problem.


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

Description:

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

Solution:

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


478877 scvxvmlg error - mkdirp(%s) failed

Description:

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

Solution:

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


479184 Error determining the zonename.

Description:

The cl_boot_check service could not determine the zonename.

Solution:

This message might indicate an internal error. Contact your authorized Sun service provider to determine whether a workaround or patch is available.


479213 Monitor server terminated.

Description:

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

Solution:

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


479308 There should be at least one Network Resource in this resource group

Description:

Since DAS resource is a Failover Resource, the Failover IP address that DAS uses must be created in this Resource Group.

Solution:

Create the Failover IP address resource in this Resource Group.


479331 Error in res %s execution Stop

Description:

Not able to process the resource to stop all the services.Previous messages to this should give the reason.

Solution:

If it fails after couple of retries, contact SUN vendor for more help


479442 in libsecurity could not allocate memory

Description:

A server (rpc.pmfd, rpc.fed or rgmd) was not able to start, or a client was not able to make an rpc connection to the server. This problem can occur of the machine has low memory. An error message is output to syslog.

Solution:

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


479591 File %s is not configured, exiting.

Description:

The specified file has not been configured.

Solution:

Look at the file's man page to determine how to properly configure the file.


480354 Error on line %ld: %s

Description:

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

Solution:

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


481187 Validate - smbconf %s does not exist

Description:

The smb.conf file does not exist.

Solution:

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


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

Description:

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

Solution:

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


482231 Failed to stop fault monitor, %s.

Description:

Error in stopping the fault monitor.

Solution:

No user action needed.


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

Description:

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

Solution:

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


482901 Can't allocate binding element

Description:

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

Solution:

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


483409 Validate - User mqm does not exist

Description:

The userid mqm does not exist.

Solution:

The userid mqm must exist within /etc/passwd.


483446 Fault-monitor successfully stopped.

Description:

The fault monitor of this ScalMountPoint resource was stopped successfully. This message is an informational message.

Solution:

No user action is required.


483858 Must set at least one of Port_List or Monitor_Uri_List.

Description:

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

Solution:

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


484189 Failed to disable %s service

Description:

The Solaris service management facility failed to disable the service instance that the fault management resource identifier (FMRI) in the /var/adm/messages specifies.

Solution:

Run the command 'svcadm disable <fmri>' to disable the service instance. Then run the command 'svccfg -s <fmri>' to enable you to modify the configuration of the service instance interactively. Use the subcommand 'addpg startd framework' to add the startd and framework property group and the subcommand 'setprop startd/duration = astring: transient' to set the duration to transient. After modfiying the configuration of the service instance, run the command 'svcadm enable <fmri>' to enable the service instance. Then run the command 'svcs -x <service>' command to verify that the service is online. If the problem persists, contact your Sun Support representative for further assistance.


484248 SCSLM pools facility is disabled

Description:

Should never occur.

Solution:

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


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.


484726 Resource %s named in one of the resource dependencies properties is not a SharedAddress resource.

Description:

The dependee resource is not a SharedAddress resource.

Solution:

Specify at least one SharedAddresses resource as a dependee.


485462 Error: duplicate method <%s> launched on resource <%s> in resource group <%s> on node <%s>

Description:

Due to an internal error, the rgmd state machine has attempted to launch two different methods on the same resource on the same node, simultaneously. The rgmd will reject the second attempt and treat it as a method failure.

Solution:

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


485464 clcomm: Failed to allocate simple xdoor server %d

Description:

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

Solution:

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


485631 Checking of Master Configuration file failed.

Description:

The master configuration file /etc/opt/SUNWsamfs/mcf for the specified file system contains incorrect entries. A misconfiguration is one possible cause of incorrect entries in this file.

Solution:

Correct the entries in the master configuration file and repeat the operation.


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.


485941 Function: check_sczsh - %s does not exist or is not executable in zone %s - early End

Description:

The command specified for variable ServiceProbeCommand within the /opt/SUNWsczone/sczsh/util/sczsh_config configuration file is not executable or does not exist in the specified zone.

Solution:

Make sure that the command specified for variable ServiceProbeCommand within the /opt/SUNWsczone/sczsh/util/sczsh_config configuration file is existing and executable for user root in the specified zone. If you do not want to re-register the resource, make sure the variable ServiceProbeCommand is properly set within the ${PARAMETERDIR}/sczsh_${RS} parameterfile.


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.


486057 J2EE probe didn't return expected message: %s

Description:

The data service received an unexpected reply from the J2EE engine.

Solution:

Informational message. No user action is needed.


486201 Disabling of %s under smf(5), failed. Admin intervention may be required.

Description:

The initialization script was not able to disable krb5kdc or kadmind under SMF.

Solution:

Check the state of krb5kdc or kadmind using "svcs -x".


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

Description:

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

Solution:

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


486484 Error: The Oracle CRS shutdown script "%s" is missing.

Description:

The Oracle CRS shutdown script could not be located.

Solution:

Ensure that Oracle CRS is correctly installed.


486841 SIOCGLIFCONF: %s

Description:

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

Solution:

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


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

Description:

The calls to the underlying scalable networking code succeeded.

Solution:

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


487148 Could not find a mapping for %s in %s or %s. It is recommended that a mapping for %s be added to %s.

Description:

No mapping was found in the local hosts or ipnodes file for the specified ip address.

Solution:

Applications might use hostnames instead of ip addresses. It is recommended to have a mapping in the hosts and/or ipnodes file. Add an entry in the hosts and/or ipnodes file for the specified ip address.


487270 Sun Java Systems Application Server <%s> is already running on this node outside of Sun Cluster. The start of <%s> from Sun Cluster will be aborted.

Description:

It is detected that DAS is already running on this node outside of Sun Cluster. The start of DAS from Sun Cluster will be aborted.

Solution:

No user action is needed.


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

Description:

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

Solution:

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


487484 lkcm_reg: lib initialization failed

Description:

udlm could not register with cmm because lib initialization failed.

Solution:

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


487516 Failed to obtain SAM-FS constituent volumes for %s.

Description:

HA Storage Plus was not able to determine the volumes that are part of this SAM-FS special device.

Solution:

Check the SAM-FS file system configuration. If the problem persists, contact your authorized Sun service provider.


487574 Failed to alloc memory

Description:

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

Solution:

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


487827 CCR: Waiting for repository synchronization to finish.

Description:

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

Solution:

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


488313 Could not start Proxy Daemon.

Description:

The agent failed to startup the Monitor of a resource of type SUNW.scalable_rac_server_proxy.

Solution:

Contact your Sun support representative for further assistance.


488595 Cluster Configuration Repository transformation completed successfully

Description:

Cluster Configuration Repository transformation completed successfully.

Solution:

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


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

Description:

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

Solution:

This message is informational; no user action is needed.


488988 Unable to open libxml2.so.

Description:

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

Solution:

Install the libxml2.so library.


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

Description:

Property failover_enabled is not 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 might have failed or the remote node might be down.

Solution:

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


489465 Severe XDR Error, Cannot recover.

Description:

An internal error has occurred in the inter-process communication between rgmd and another clustering process. Other related error messages might precede or follow this one in the syslog output.

Solution:

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


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.


490249 Stopping SAP Central Service.

Description:

This message indicates that the data service is stoping the SCS.

Solution:

No user action needed.


490268 Failfast : Failed to reboot zone %s (zone ID %d) as door upcall to 'zoneadmd' door failed with error code %d. Failfast will halt the zone now.

Description:

Failfast failed to reboot zone, because door upcall to zoneadmd daemon failed. Failfast will halt the zone as a result.

Solution:

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


490360 zoneadm call for zone %s failed

Description:

The attempted zoneadm call failed to exit properly. The zone may or may not have actually rebooted.

Solution:

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


490977 dl_bind ack bad len %d

Description:

Sanity check. The message length in the acknowledgment to the bind request is different from what was expected. We are trying to open a fast path to the private transport adapters.

Solution:

Reboot of the node might fix the problem.


491081 resource %s removed.

Description:

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

Solution:

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


491533 DB_password_file should be a regular file: %s

Description:

The DB_password_file extension property needs to be a regular file.

Solution:

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


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

Description:

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

Solution:

No user action required.


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

Description:

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

Solution:

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


492781 Retrying to retrieve the resource information: %s.

Description:

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

Solution:

This is only an informational message.


492922 Validate callback failed.

Description:

The validate callback failed.

Solution:

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


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

Description:

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

Solution:

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


493130 Could not copy %s to %s

Description:

HA-Oracle copies the Oracle shared library used by the fault monitor to a local file system. Without this local copy of the Oracle shared library, the HA-Oracle installation is vulnerable because failures may not be detected when the shared library under <ORACLE_HOME>/lib or <ORACLE_HOME>/lib32 (32-bit installation) is unavailable.

Solution:

Verify that the specified Oracle shared library under <ORACLE_HOME>/lib or <ORACLE_HOME>/lib32 (32-bit installation) is readable and that the local directory/file as specified in the error message is writable. There should be sufficient disk space in the local file system to copy the shared library. You may manually copy the shared library by using 'cp -p <source> <destination>' as 'root' (replace the source and destination by the appropriate pathnames as indicated in the error message).


493261 Could not remove node %s from device service %s, error = %d

Description:

Failed to remove the indicated node from a device service because of the indicated error.

Solution:

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


493641 Failed to open file %s.

Description:

The master configuration file under /etc/opt/SUNWsamfs for the specified shared QFS file system could not be opened.

Solution:

Determine whether the file exists. If the file exists, ensure that the file-access permissions are correct. If the file does not exist, ensure that the specified file system is correctly configured with Sun Cluster.


493657 Unable to get status for IPMP group %s.

Description:

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

Solution:

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


494475 Function: val_in_global - Not in the global zone

Description:

A start, stop or probe command was used from the local zone.

Solution:

Use the start, stop and probe commands from th eglobal zone only.


494478 resource %s in resource group %s has requested %s on %s.

Description:

The RGM has recieved a request for the specified scha_control(1HA) or scha_control(3HA) operation.

Solution:

No user action required.


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

Description:

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

Solution:

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


494913 pmfd: unknown action (0x%x)

Description:

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

Solution:

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


495386 INTERNAL ERROR: %s.

Description:

An internal error has occurred.

Solution:

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


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

Description:

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


496555 couldn't query zonename

Description:

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

Solution:

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


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

Description:

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

Solution:

This may be indicative of a hardware problem, which should be resolved as soon as possible. Once the problem has been resolved, the following actions may be necessary: If the message specifies the 'node_join' transition, then this node may be unable to access the specified device. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access the device. In either case, access can be reacquired by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on all cluster nodes. If the failure occurred during the 'make_primary' transition, then a device group might have failed to start on this node. If the device group was started on another node, move it to this node by using the cldevicegroup command. If the device group was not started, you can start it by using the cldevicegroup command. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group might have failed. If so, the desired action may be retried.


496814 restart_dependency - Dependent resource to resource %s has been restarted, restart this resource %s

Description:

-4 a restart of the dependant resource has been noticed, it might be necessary to restart the resource depending on

Solution:

-4 check the validity of the service. there might be a dependancy problem, a sub resource has benn restarted, and functionality might have been impaired


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

Description:

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

Solution:

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


497867 open64 pbundle: %s

Description:

The rpc.pmfd was unable to open a file in the /system/contract/process/ directory. Consequently, the rpc.pmfd was unable to receive contract events. The rpc.pmfd will exit, causing a node panic.

Solution:

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


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.


499715 Error in scha_resourcegroup_get

Description:

Error in reading the resource group

Solution:

Check if the RGM functionalities are working fine and if the resource group is present. Contact SUN vendor for more help.


499756 CMM: Node %s: joined cluster.

Description:

The specified node has joined the cluster.

Solution:

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


499775 resource group %s added.

Description:

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

Solution:

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


499796 reservation notice(%s) - MHIOCENABLEFAILFAST success during retry attempt: %d

Description:

Informational message from reserve on ioctl success during retry.

Solution:

No user action required.


499903 Error %d running quotacheck for %s

Description:

The /usr/sbin/quotacheck command failed for $mountp.

Solution:

The system administrator should run the /usr/sbin/quotacheck command manually. If that succeeds, also run /usr/sbin/quotaon. If the quotacheck attempt fails, stop any applications that are using the file system and attempt the quotacheck command again.


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

Description:

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

Solution:

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