Sun Cluster Error Messages Guide for Solaris OS

Message IDs 500000–599999

This section contains message IDs 500000–599999.

501495 Validation failed. The RAC framework resource %s that is specified in the RESOURCE_DEPENDENCIES property is not in any of the resource groups specified by the resource group property RG_AFFINITIES.

Description:

The resource being created or modified should be dependent upon the rac_framework resource in the RAC framework resource group.

Solution:

If not already created, create the scalable resource group containing RAC framework resource and its associated resources. Specify this resource's dependency on the RAC framework by updating the RESOURCE_DEPENDENCIES property, and ensure that the RAC framework resource group is a part of the strong positive affinity (++) list specified in the RG_AFFINITIES property value for the resource group containing the proxy resource.

501628 Function: check_sczbt - runlevel did not run successfully (return code %s) in the non-global zone %s, try again in 5 seconds

Description:

The runlevel command did not run successfully in the configured non-global zone. The state is checked again in 5 seconds.

Solution:

None.

501632 Incorrect syntax in the environment file %s. Ignoring %s

Description:

HA-Oracle reads the fle specified in USER_ENV property and exports the variables declared in the file. Syntax for declaring the variables is : VARIABLE=VALUE Lines starting with " VARIABLE is expected to be a valid Korn shell variable that starts with alphabet or "_" and contains alphanumerics and "_".

Solution:

Please check the environment file and correct the syntax errors. Do not use export statement in environment file.

501733 scvxvmlg fatal error - _cladm() failed

Description:

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

Solution:

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

501763 recv_request: t_alloc: %s

Description:

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

Solution:

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

501981 Valid connection attempted from %s: %s

Description:

The cl_apid received a valid client connection attempt from the specified IP address.

Solution:

No action required. If you do not wish to allow access to the client with this IP address, modify the allow_hosts or deny_hosts as required.

502022 fatal: joiners_read_ccr: exiting early because of unexpected exception

Description:

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

Solution:

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

502258 fatal: Resource group <%s> create failed with error <%s>; aborting node

Description:

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

Solution:

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

502326 UNRECOVERABLE ERROR: Reading mount point from %s failed with error code %s

Description:

Reading mount point from ${QL_LU_CONTINUE} failed with error code ${retval}

Solution:

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

502438 IPMP group %s has status %s.

Description:

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

Solution:

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

502943 SCSLM <%s> is not a regular file

Description:

Should never occur.

Solution:

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

503686 CMM: Node %d has version %d higher than the local version %d

Description:

The configuration information shows that the node supports a higher version than the currently running software can support. This happens when old software is loaded onto a machine.

Solution:

Upgrade the software on this node to support the version shown in the configuration information.

503803 scha_resource_get() failed for MDS Resource %s : %s

Description:

A call to scha_resource_get() failed.

Solution:

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

503817 No PDT Dispatcher thread.

Description:

The system has run out of resources that is required to create a thread. The system could not create the connection processing thread for scalable services.

Solution:

If cluster networking is required, add more resources (most probably, memory) and reboot.

503911 The action to be taken as determined by scds_fm_action is failover. However the application is not being failed over because %s. The application is left as-is. Probe quitting ...

Description:

Based on the restart history, the fault monitor decided for application failover. However the application is not being failed over because of the specified reason. The probe is quitting because it does not have any application to monitor.

Solution:

The application or the monitor is not working properly. Correct the problem and restart the application and/or its monitor.

504363 ERROR: process_resource: resource <%s> is pending_update but no UPDATE method is registered

Description:

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

Solution:

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

504559 FED XDR Buffer Shortfall while encoding return arguments API num = %d, will retry.

Description:

A non-fatal error occurred while rpc.fed was marshalling arguments for a remote procedure call. The operation will be re-tried with a larger buffer.

Solution:

No user action is required. If the message recurs frequently, contact your authorized Sun service provider to determine whether a workaround or patch is available.

505040 Failed to allocate memory.

Description:

HA Storage Plus ran out of resources.

Solution:

Usually, this means that the system has exhausted its resources. Check if the swap file is big enough to run Sun Cluster.

505101 Found another active instance of clexecd. Exiting daemon_process.

Description:

An active instance of clexecd program is already running on the node.

Solution:

This would usually happen if the operator tries to start the clexecd program by hand on a node which is booted in cluster mode. If thats not the case, contact your authorized Sun service provider to determine whether a workaround or patch is available.

505840 SCSLM <%s> zone <%s> missing project.cpu-shares

Description:

Should never occur.

Solution:

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

506381 Custom action file %s contains errors.

Description:

The custom action file that is specified contains errors which need to be corrected before it can be processed completely.

Solution:

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

506673 Error in scha_res_get of retry cnt prop,res:%s, Err: %s

Description:

Cannot read the resource retry count in sc delegated restarter

Solution:

Take action depending on the error and contact sun vendor for more help.

507193 Queued event %lld

Description:

The cl_apid successfully queued the incoming sysevent.

Solution:

This message is informational only. No action is required.

507263 Telemetry data service stop method completed sucessfully

Description:

The telemetry data service stopped successfully.

Solution:

This message is informational; no user action needed.

507882 J2EE engine probe returned http code 503. Temp. not available.

Description:

The data service received http code 503, which indicates that the service is temporarily not availble.

Solution:

Informational message. No user action is needed.

508003 check_pgs: The test database %s is not in the database catalog

Description:

The database to monitor does not exist in the database catalog.

Solution:

Fix the parameter file to contain the right database name in the SCDB variable, or prepare the database.

508391 Error: failed to load catalog %s

Description:

The cl_apid was unable to load the xml catalog for the dtds. No validation will be performed on CRNP xml messages.

Solution:

No action is required. If you want to diagnose the problem, examine other syslog messages occurring at about the same time to see if the problem can be identified. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

508671 mmap: %s

Description:

The rpc.pmfd server was not able to allocate shared memory for a semaphore, possibly due to low memory, and the system error is shown. The server does not perform the action requested by the client, and pmfadm returns error. An error message is also output to syslog.

Solution:

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

509069 CMM: Halting because this node has no configuration info about node %ld which is currently configured in the cluster and running.

Description:

The local node has no configuration information about the specified node. This indicates a misconfiguration problem in the cluster. The /etc/cluster/ccr/infrastructure table on this node may be out of date with respect to the other nodes in the cluster.

Solution:

Correct the misconfiguration problem or update the infrastructure table if out of date, and reboot the nodes. To update the table, boot the node in non-cluster (-x) mode, restore the table from the other nodes in the cluster or backup, and boot the node back in cluster mode.

509136 Probe failed.

Description:

Fault monitor was unable to perform complete health check of the service.

Solution:

1) Fault monitor would take appropiate action (by restarting or failing over the service.). 2) Data service could be under load, try increasing the values for Probe_timeout and Thororugh_probe_interval properties. 3) If this problem continues to occur, look at other messages in syslog to determine the root cause of the problem. If all else fails reboot node.

510280 check_mysql - MySQL slave instance %s is not connected to master %s with MySql error (%s)

Description:

The faultmonitor has detected that the MySQL slave instance is not connected to the specified master.

Solution:

Check MySQL logfiles to determine why the slave has been disconnected to the master.

510369 sema_wait parent: %s

Description:

The rpc.pmfd server was not able to act on a semaphore. The message contains the system error. The server does not perform the action requested by the client, and an error message is output to syslog.

Solution:

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

510372 Error: /var/run is not mounted; cannot start cl_eventd.

Description:

The cl_event init script found that /var/run is not mounted. Because cl_eventd requires /var/run for sysevent reception, cl_eventd will not be started. This error may prevent the event subsystem from working correctly.

Solution:

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

510585 Found (%d) did devices and (%d) ctd devices in dg (%s)

Description:

The method queried for and found DID and ctd devices.

Solution:

No user action is required.

510646 SCSLM <%s> pool_create error <%s>

Description:

Should never occur.

Solution:

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

511177 clcomm: solaris xdoor door_info failed

Description:

A door_info operation failed. Refer to the "door_info" man page for more information.

Solution:

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

511749 rgm_launch_method: failed to get method <%s> timeout value from resource <%s>

Description:

Due to an internal error, the rgmd daemon was unable to obtain the method timeout for the indicated resource. This is considered a method failure. Depending on which method was being invoked and the Failover_mode setting on the resource, this might cause the resource group to fail over or move to an error state.

Solution:

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

512422 WARNING: unknown msg (type %d) was picked up by a lkcm_act, returning LKCM_NOOP

Description:

Warning for unknown message picked up during udlm state update.

Solution:

None.

512691 <%s> using fake user name for setproject

Description:

Should never occur.

Solution:

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

512980 Internal Error: ORACLE_OWNER not set even after successful validation. Shutdown may not be successful in cleaning up all resources.

Description:

An internal error occurred while attempting to save the name of the owner of the Oracle installation in a local file for use during shutdown of Oracle.

Solution:

After next shutdown of the resource, check to verify if the shutdown completed successfully by cleaning up all the resources. If the problem persists, report it to your Sun support representative.

513986 Waiting for the first partition nodes to come online

Description:

During a dual-partition upgrade in a live upgrade scenario, the node is waiting for all the nodes of the first partition to come online in the new boot environment.

Solution:

This is a informational message. If the user sees that any of the nodes of the first partition has panicked or hung, then he should abort the upgrade and do a normal upgrade after doing the recovery steps.

514047 select: %s

Description:

The cl_apid received the specified error from select(3C). No action was taken by the daemon.

Solution:

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

514078 Validate - The keyword INTERFACES have to be set in %s when -T is being used

Description:

If USE_CGTP=TRUE was set within /opt/SUNWscdhc/util/dhcp_config then the INTERFACES within /etc/inet/dhcpsvc.conf needs to be set.

Solution:

If USE_CGTP=TRUE is required, then ensure that the INTERFACES variable is set within /etc/inet/dhcpsvc.conf. If USE_CGTP=TRUE is required, then ensure that the INTERFACES variable is set within /etc/inet/dhcpsvc.conf. Refer to dhcpsvc.conf(4) man page for further information on INTERFACES.

514234 Error probing devicegroup (%s)

Description:

An error occurred during a probe of the disk set or disk group.

Solution:

Verify the status of the disk set or disk group. Contact your authorized Sun service provider for further assistance in diagnosing the problem.

514383 ping_timeout %d

Description:

The ping_timeout value used by scdpmd.

Solution:

No action required.

514574 Upgrade has completed on all the nodes that have joined the cluster

Description:

Cluster upgrade has completed on all the nodes that have joined the cluster. Software upgrade might not be complete on any nodes that have not rejoined the cluster.

Solution:

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

514630 The entry in vfstab for mount point '%s' has too few fields.

Description:

The entry in vfstab for the specified mount point has fewer fields than are defined for a single vfstab entry.

Solution:

Add the missing fields from the entry in vfstab for the mount point and repeat the operation.

514688 Invalid port number %s in the %s property.

Description:

The specified system property does not have a valid port number.

Solution:

Using clresource, specify the positive, valid port number.

514731 Failed to kill listener process for %s

Description:

Failed to kill listener processes.

Solution:

None

515159 method <%s> completed successfully for resource <%s>, resource group <%s>, node <%s>, time used: %d%% of timeout <%d seconds>

Description:

RGM invoked a callback method for the named resource, as a result of a cluster reconfiguration, scha_control GIVEOVER, or clresourcegroup switch. The method completed successfully.

Solution:

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

515411 CMM: Registered key on and acquired quorum device %d (gdevname %s).

Description:

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

Solution:

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

516089 Oracle commands inaccessible. Forcing shutdown of Oracle by killing Oracle processes and removing any shared memory.

Description:

The resource shutdown will attempt to clean up any Oracle processes or shared memory segments. A graceful shutdown could not be attempted as Oracle commands are inaccessible, possibly due to the commands residing on a failover, global, or NAS file system on which the database resource's dependency has not been set.

Solution:

This message is informational. You must ensure that the resource comes online correctly on an alternate cluster node or on the same node after the Oracle commands become accessible again. If possible and supported, set the dependency of the database resource on the file system resource.

516515 Function: validate_options: %s Option %s not set

Description:

The start, stop or probe command requires an option which is not set.

Solution:

Fix the start, stop or probe command in the SUNW.gds resource.

516650 "pmfadm -s": Error signaling <%s>: %s

Description:

An error occured while rpc.pmfd attempted to send a signal to one of the processes of the given tag. The reason for the failure is also given. The signal was sent as a result of a 'pmfadm -s' command.

Solution:

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

516722 WARNING !!! Devicegroup %s does not have any volumes.

Description:

The devicegroup does not have any volumes.

Solution:

Make sure to create volumes in the devicegroup, before starting the resource.

517009 lkcm_act: invalid handle was passed %s %d

Description:

Handle for communcation with udlmctl is invalid.

Solution:

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

517036 connection from outside the cluster - rejected.

Description:

There was a connection from an IP address which does not belong to the cluster. This is not allowed so the PNM daemon rejected the connection.

Solution:

This message is informational; no user action is needed. However, it would be a good idea to see who is trying to talk to the PNM daemon and why?

517343 clexecd: Error %d from pipe

Description:

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

Solution:

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

517363 clconf: Unrecognized property type

Description:

Found the unrecognized property type in the configuration file.

Solution:

Check the configuration file.

518018 CMM: Node being aborted from the cluster.

Description:

This node is being excluded from the cluster.

Solution:

Node should be rebooted if required. Resolve the problem according to other messages preceding this message.

518158 Probe for resource sctelemetry successful

Description:

Telemetry data service probe method completed successfully.

Solution:

This message is informational; no user action needed.

518291 Warning: Failed to check if scalable service group %s exists: %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.

518378 The file system type is not specified in vfstab for mount point : %s.

Description:

The 'file system type' field in the vfstab entry for the specified mount point does not specify the type of file system.

Solution:

Add the type of file system to the 'file system type' field in the vfstab entry for the specified mount point and repeat the operation.

518383 Received notice that IPMP group %s has repaired.

Description:

The named IPMP group is now functional.

Solution:

No user action is required. This is an informational message.

518710 Validate - WebSphere MQ file systems not defined

Description:

The required WebSphere MQ file systems, /opt/mqm and /var/mqm are not defined.

Solution:

Ensure that /opt/mqm and /var/mqm are defined.

518966 SCSLM getzoneidbyname error <%s>

Description:

Should never occur.

Solution:

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

519262 Validation failed. SYBASE monitor server startup file RUN_%s not found SYBASE=%s.

Description:

Monitor server was specified in the extension property Monitor_Server_Name. However, monitor server startup file was not found. Monitor server startup file is expected to be: $SYBASE/$SYBASE_ASE/install/RUN_<Monitor_Server_Name>

Solution:

Check the monitor server name specified in the Monitor_Server_Name property. Verify that SYBASE and SYBASE_ASE environment variables are set property in the Environment_file. Verify that RUN_<Monitor_Server_Name> file exists.

519406 %s: Couldn't fork to execute method %s

Description:

Have problems in starting a communication with the SMF repository

Solution:

Depending on the error, check the SMF man page.Contact SUN vendor for help.

519641 sckrb5 not running.

Description:

HA-KDC's stop method was called but the service was not running.

Solution:

This is for informational purposes only, no action is required.

520231 Unable to set the number of threads for the FED RPC threadpool.

Description:

The rpc.fed server was unable to set the number of threads for the RPC threadpool. This happens while the server is starting up.

Solution:

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

520373 Internal error: %s.

Description:

Self explanatory.

Solution:

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

520437 SCSLM <%s> pool_value_get_int64 error <%s>

Description:

Should never occur.

Solution:

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

521185 pthread_cond_wait: %s

Description:

The sc_zonesd daemon received an unexpected error from pthread_cond_wait. This error should not impact the sc_zonesd's operations.

Solution:

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

521319 Waiting for the FED to stop

Description:

The FED service is being stopped.

Solution:

Please wait. No action is required. This is an informational message.

521393 Backup server stopped.

Description:

The backup server was stopped by Sun Cluster HA for Sybase.

Solution:

This is an information message, no user action is needed. may

521560 Resource %s named in one of the resource dependencies properties does not exist.

Description:

The resource dependencies property (one of strong/weak/restart/offline-restart) contains an invalid resource. This is an internal error and should not occur.

Solution:

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

521671 uri <%s> probe failed

Description:

The probing of the url set in the monitor_uri_list extension property failed. The agent probe will take action.

Solution:

None. The agent probe will take action. However, the cause of the failure should be investigated further. Examine the log file and syslog messages for additional information.

521918 Validation failed. Connect string is NULL.

Description:

The 'Connect_String' extension property used for fault monitoring is null. This has the format "username/password".

Solution:

Check for syslog messages from other system modules. Check the resource configuration and the value of the 'Connect_string' property.

522480 RGM state machine returned error %d

Description:

An error has occurred on this node while attempting to execute the rgmd state machine.

Solution:

522710 Failed to parse xml: invalid reg_type [%s]

Description:

The cl_apid was unable to parse an xml message because of an invalid registration type.

Solution:

No action needed.

522779 IP address (hostname) string %s in property %s, entry %d could not be resolved to an IP address.

Description:

The IP address (hostname) string within the named property in the message did not resolve to a real IP address.

Solution:

Change the IP address (hostname) string within the entry in the property to one that does resolve to a real IP address. Make sure the syntax of the entry is correct.

523346 Failed to retrieve extension properties.

Description:

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

Solution:

Serious error. The RTR file may be corrupted. Reload the package for HA-HADB MA. If problem persists save a copy of the /var/adm/messages files on all nodes and contact the Sun Cluster HA developer.

523531 Listener probe timed out two times consecutively.

Description:

Listener monitor has timed out in two successive attempts to probe the listener.

Solution:

None

523643 INTERNAL ERROR: %s

Description:

An internal error has occurred.

Solution:

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

524232 %s: Unable to register.

Description:

This program could not register the RPC service.

Solution:

Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.

524368 Kerberos database %s is missing, exiting.

Description:

The /var/krb5/principal database is missing or of zero length.

Solution:

Verify that the principal database has been properly configured and that the /etc/krb5/krb5.conf and /etc/krb5/kdc.conf files have been specified correctly.

525152 Sigsend failed to send sig to contract %d: %s

Description:

Could not send the signal to the specified contract

Solution:

Man pages for sigsend will give more info about it.Contact SUN vendor for more help.

525197 No network address resources in resource group.

Description:

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

Solution:

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

525628 CMM: Cluster has reached quorum.

Description:

Enough nodes are operational to obtain a majority quorum; the cluster is now moving into operational state.

Solution:

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

526056 Resource <%s> of Resource Group <%s> failed pingpong check on node <%s>. The resource group will not be mastered by that node.

Description:

A scha_control(1HA,3HA) call has failed because no healthy new master could be found for the resource group. A given node is considered unhealthy for a given resource if that same resource has recently initiated a failover off of that node by a previous scha_control call. In this context, "recently" means within the past Pingpong_interval seconds, where Pingpong_interval is a user-configurable property of the resource group. The default value of Pingpong_interval is 3600 seconds. This check is performed to avoid the situation where a resource group repeatedly "ping-pongs" or moves back and forth between two or more nodes, which might occur if some external problem prevents the resource group from running successfuly on *any* node.

Solution:

A properly-implemented resource monitor, upon encountering the failure of a scha_control call, should sleep for awhile and restart its probes. If the resource remains unhealthy, the problem that caused the scha_control call to fail (such as pingpong check described above) will eventually resolve, permitting a later scha_control request to succeed. Therefore, no user action is required. If the system administrator wishes to permit failovers to be attempted even at the risk of ping-pong behavior, the Pingpong_interval property of the resource group should be set to a smaller value.

526324 scnetapp fatal error - clconf_lib_init() error

Description:

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

Solution:

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

526340 Resource %s does not have the property DB_PROBE_PORT defined

Description:

The property DB_PROBE_PORT is a mandatory property of the data service. Should never occur.

Solution:

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

526492 Service object [%s, %s, %d] removed from group '%s'

Description:

A specific service known by its unique name SAP (service access point), the three-tuple, has been deleted in the designated group.

Solution:

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

526671 Failed to initialize the DSDL.

Description:

HA Storage Plus was not able to connect to the DSDL.

Solution:

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

526876 check_pgs: The test database manipulation failed for database %s, user %s and table %s

Description:

The monitoring action on the specified table failed.

Solution:

None

526963 Checking UFS quota for %s

Description:

The UFS mount point specified by %s, which has quotas enabled, is being checked using /usr/sbin/quotacheck.

Solution:

This is an informational message. No action is necessary.

527073 Could not set uid to '%d': %s

Description:

The program failed to change the user ID to the specified value. The reason for the failure is also specified in the above message.

Solution:

Please verify that the specified user ID is valid. For Oracle, the specified user ID is obtained from the owner of the file $ORACLE_HOME/bin/oracle.

527153 find_our_mds_rs() call failed.

Description:

The resource that represents the metadata server of the specified file system could not be found.

Solution:

Examine more specific error messages about not finding this resource to determine why the resource was not found.

527795 clexecd: setrlimit returned %d

Description:

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

Solution:

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

528020 CCR: Remove table %s failed.

Description:

The CCR failed to remove the indicated table.

Solution:

The failure can happen due to many reasons, for some of which no user action is required because the CCR client in that case will handle the failure. The cases for which user action is required depends on other messages from CCR on the node, and include: If it failed because the cluster lost quorum, reboot the cluster. If the root file system is full on the node, then free up some space by removing unnecessary files. If the root disk on the afflicted node has failed, then it needs to be replaced. If the cluster repository is corrupted as indicated by other CCR messages, then boot the offending node(s) in -x mode to restore the cluster repository from backup. The cluster repository is located at /etc/cluster/ccr/.

528499 scsblconfig not configured correctly.

Description:

The specified file has not been configured correctly, or it does not have all the required settings.

Solution:

Please verify that required variables (according to the installation instructions for this data service) are correctly configured in this file. Try to manually source this file in korn shell (". scsblconfig"), and verify if the required variables are getting set correctly.

528701 Failed to create repository object %s

Description:

Error in creating various handles to interact with the SMF repository.

Solution:

Check the SMF manpage to know more about the error.Also make sure the basic SMF functionalities are working fine.Contact SUN vendor for more help.

529096 Function: validate - %s is not executable

Description:

The Zone SMF Probe Script is not executable.

Solution:

Review the /opt/SUNWsczone/sczsmf/util/sczsmf_config configuration file and make sure you have specified the correct SERVICE_PROBE.

529191 clexecd: Sending fd to workerd returned %d. Exiting.

Description:

There was some error in setting up interprocess communication in the clexecd program.

Solution:

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

529407 resource group %s state on node %s change to %s

Description:

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

Solution:

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

529502 UNRECOVERABLE ERROR: /etc/cluster/ccr/infrastructure file is corrupted

Description:

/etc/cluster/ccr/infrastructure file is corrupted.

Solution:

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

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

Description:

Failfast failed to reboot zone, because the door to the zoneadmd daemon could not be opened. Failfast will halt the zone as a result.

Solution:

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

530064 reservation error(%s) - do_enfailfast() error for disk %s

Description:

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

Solution:

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

530492 fatal: ucmm_initialize() failed

Description:

The daemon indicated in the message tag (rgmd or ucmmd) was unable to initialize its interface to the low-level cluster membership monitor. This is a fatal error, and causes the node to be halted or rebooted to avoid data corruption. The daemon produces a core file before exiting.

Solution:

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

530603 Warning: Scalable service group for resource %s has already been created.

Description:

It was not expected that the scalable services group for the named resource existed.

Solution:

Rebooting all nodes of the cluster will cause the scalable services group to be deleted.

530628 Could not allocate memory in get_method

Description:

Could not allocate memory

Solution:

Check the availabilty of the memory.Contact SUN vendor for more help.

530828 Failed to disconnect from host %s and port %d.

Description:

The data service fault monitor probe was trying to disconnect from the specified host/port and failed. The problem may be due to an overloaded system or other problems. If such failure is repeated, Sun Cluster will attempt to correct the situation by either doing a restart or a failover of the data service.

Solution:

If this problem is due to an overloaded system, you may consider increasing the Probe_timeout property.

530938 Starting NFS daemon %s.

Description:

The specified NFS daemon is being started by the HA-NFS implementation.

Solution:

This is an informational message. No action is needed.

530977 Error in scha_rg_get of rg:%s, Err: %s

Description:

Cannot get the requesting rg

Solution:

Depending on the error take action and the deatils are provided in the man page scha_rg_get(3HA)

531148 fatal: thr_create stack allocation failure: %s (UNIX error %d)

Description:

The rgmd daemon was unable to create a thread stack, most likely because the system has run out of swap space. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution:

Rebooting the node has probably cured the problem. If the problem recurs, you might need to increase swap space by configuring additional swap devices. See swap(1M) for more information.

531989 Prog <%s> step <%s>: authorization error: %s.

Description:

An attempted program execution failed, apparently due to a security violation; this error should not occur. The last portion of the message describes the error. This failure is considered a program failure.

Solution:

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

532118 All the SUNW.HAStoragePlus resources that this resource depends on are not online on the local node. Skipping the checks for the existence and permissions of the start/stop/probe commands.

Description:

The HAStoragePlus resources that this resource depends on are online on another node. Validation checks will be done on that other node.

Solution:

This message is informational; no user action is needed.

532454 file specified in USER_ENV parameter %s does not exist

Description:

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

Solution:

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

532654 The -c or -u flag must be specified for the %s method.

Description:

The arguments passed to the function unexpected omitted the given flags.

Solution:

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

532740 Failed to parse the Nodelist property

Description:

A LogicalHostname resource could not be initialized because of failure to parse the resource group's Nodelist property.

Solution:

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

532774 Function: validate - %s state is %s

Description:

The referenced zone is not in the state installed, ready or running.

Solution:

Make sure that the referenced zone name is configured properly. Check if you have done a zlogin -C. Make sure that the name in the appropriate config file is correct.

532854 Probe for J2EE engine timed out in scds_fm_tcp_disconnect().

Description:

The data service timed out while disconnecting the socket.

Solution:

Informational message. No user action is needed.

532973 clcomm: User Error: Loading duplicate TypeId: %s.

Description:

The system records type identifiers for multiple kinds of type data. The system checks for type identifiers when loading type information. This message identifies that a type is being reloaded most likely as a consequence of reloading an existing module.

Solution:

Reboot the node and do not load any Sun Cluster modules manually.

532980 clcomm: Pathend %p: deferred task not allowed in state %d

Description:

The system maintains state information about a path. A deferred task is not allowed in this state.

Solution:

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

533359 pmf_monitor_suspend: Error opening procfs control file <%s> for tag <%s>: %s

Description:

The rpc.pmfd server was not able to resume the monitoring of a process because the rpc.pmfd server was not able to open a procfs control file. If the system error is 'Device busy', the procfs control file is being used by another command (like truss, pstack, dbx...) and the monitoring of this process remains suspended. If this is not the case, the monitoring of this process has been aborted and can not be resumed.

Solution:

If the system error is 'Device busy', stop the command which is using the procfs control file and issue the monitoring resume command again. Otherwise investigate if the machine is running out of memory. If this is not the case, save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

533824 Function: validate - %s invalid boot option [%s]

Description:

The specified boot option is not allowed.

Solution:

Consult the manpage of zoneadm which boot options are allowed and specify one of them.

533854 reservation notice(%s) - MHIOCGRP_PREEMPTANDABORT success during retry attempt: %d

Description:

Informational message from reserve on ioctl success during retry.

Solution:

No user action required.

533895 Error getting ucmm state.

Description:

The state of the UCMM could not be determined.

Solution:

Verify the status of the SUNW.rac_framework resource and either the SUNW.rac_svm resource or the SUNW.rac_cvm resource. Contact your authorized Sun service provider for further assistance in diagnosing the problem.

533912 Warning! Sun Cluster resource cannot be brought online on this node because the corresponding Solaris SMF services may be online. Please disable the Solaris SMF services using the following command: 'svcadm disable %s'

Description:

The Solaris SMF service indicated above could not be disabled as required by Sun Cluster to make the service capable of restart/failover.

Solution:

Try to manually disable the SMF service specified by the error message using the 'svcadm disable' command and retry the operation.

534408 "%s" restarting too often ... sleeping %d seconds.

Description:

The tag shown, run by rpc.pmfd server, is restarting and exiting too often. This means more than once a minute. This can happen if the application is restarting, then immediately exiting for some reason, then the action is executed and returns OK (0), which causes the server to restart the application. When this happens, the rpc.pmfd server waits for up to 1 min before it restarts the application. An error message is output to syslog.

Solution:

Examine the state of the application, try to figure out why the application doesn't stay up, and yet the action returns OK.

534415 stop_pgs: Stop PostgreSQL process %s with kill -9

Description:

The previous stop attempts for PostgreSQL failed. The server is now killed with kill -9.

Solution:

None

534499 Failed to take the resource out of PMF control.

Description:

Sun Cluster was unable to remove the resource out of PMF control. This may cause the service to keep restarting on an unhealthy node.

Solution:

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

534592 %s is not a local or a global mount point in /etc/mnttab.

Description:

Self explanatory.

Solution:

This is a warning message. If the file system that is associated with the specified mount point is not available, copy the /var/adm/messages and contact an authorized Sun service provider.

534644 Failed to start SAP processes with %s.

Description:

The data service failed to start the SAP processes.

Solution:

Check the script and execute manually.

534755 Shutdown - can't access pidfile %s of process %s

Description:

The file ${pidfile} was not found. ${pidfile} is the second argument to the 'Shutdown' function. 'Shutdown' is called within the stop scripts of sge_qmaster-rs and sge_schedd-rs resources.

Solution:

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

535044 Creation of resource <%s> failed because none of the nodes on which VALIDATE would have run are currently up

Description:

In order to create a resource whose type has a registered VALIDATE method, the rgmd must be able to run VALIDATE on at least one node. However, all of the candidate nodes are down. "Candidate nodes" are either members of the resource group's Nodelist or members of the resource type's Installed_nodes list, depending on the setting of the resource's Init_nodes property.

Solution:

Boot one of the resource group's potential masters and retry the resource creation operation.

535181 Host %s is not valid.

Description:

Validation method has failed to validate the ip addresses.

Solution:

Invalid hostnames/ip addresses have been specified while creating resource. Recreate the resource with valid hostnames. Check the syslog message for the specific information.

535809 malloc failed for ipaddr string

Description:

Call to malloc failed. The "malloc" man page describes possible reasons.

Solution:

Install more memory, increase swap space or reduce peak memory consumption.

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

Description:

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

Solution:

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

536048 libsecurity, door_call: %s

Description:

A door_call failed with the specified reason, causing a Sun Cluster daemon to be terminated, and the node to be rebooted or halted.

Solution:

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

536091 Failed to retrieve the cluster handle while querying for property %s: %s.

Description:

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

Solution:

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

536458 Failed to register CMM version key %s, version %d in the CCR infrastructure table

Description:

The CMM failed to register the CMM version in the CCR. The result of this failure will be to continue using the old CMM version during the next reconfiguration.

Solution:

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

536550 check_dhcp - Dhcpclient didn't retrieve any IP-number

Description:

The dhcpclient could not retrieve any IP number.

Solution:

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

536867 scvxvmlg error - dcs_get_service_parameters() failed, returned %d

Description:

Solution:

537175 CMM: Node %s (nodeid: %ld, incarnation

Description:

The cluster can communicate with the specified node. A node becomes reachable before it is declared up and having joined the cluster.

Solution:

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

537352 reservation error(%s) - do_scsi3_preemptandabort() error for disk %s

Description:

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

Solution:

537367 Failed build path to status message file.

Description:

The path to the status message file could not be built. This is an internal error.

Solution:

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

537380 Invalid option -%c for the validate method.

Description:

Invalid option is passed to validate call back method.

Solution:

This is an internal error. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

537498 Invalid value was returned for resource property %s for %s.

Description:

The value returned for the named property was not valid.

Solution:

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

537607 Not found clexecd on node %d for %d seconds. Retrying...

Description:

Could not find clexecd to execute the program on a node. Indicated retry times.

Solution:

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

538177 in libsecurity contacting program %s (%lu); uname sys call failed: %s

Description:

A client was not able to make an rpc connection to the specified server because the host name could not be obtained. The system error message is shown. An error message is output to syslog.

Solution:

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

538570 sema_post parent: %s

Description:

Solution:

539760 Error parsing URL: %s. Will shutdown the WLS using sigkill

Description:

There is an error in parsing the URL needed to do a smooth shutdown. The WLS stop method however will go ahead and kill the WLS process.

Solution:

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

540274 got unexpected exception %s

Description:

An inter-node communication failed with an unknown exception.

Solution:

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

540279 scha_cluster_get failed for (%s) with %d

Description:

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

Solution:

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

540705 The DB probe script %s Timed out while executing

Description:

probing of the URL's set in the Server_url or the Monitor_uri_list failed. Before taking any action the WLS probe would make sure the DB is up. The Database probe script set in the extension property db_probe_script timed out while executing. The probe will not take any action till the DB is UP and the DB probe succeeds.

Solution:

Make sure the DB probe (set in db_probe_script) succeeds. Once the DB is started the WLS probe will take action on the failed WLS instance.

541145 No active replicas where detected for the global service %s.

Description:

The DCS did not find any information on the specified global service.

Solution:

Check the global service configuration.

541180 Sun udlmlib library called with unknown option: '%c'

Description:

Unknown option used while starting up Oracle unix dlm.

Solution:

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

541206 Couldn't read deleted directory: error (%d)

Description:

The file system is unable to create temporary copies of deleted files.

Solution:

Mount the affected file system as a local file system, and ensure that there is no file system entry with name "._" at the root level of that file system. Alternatively, run fsck on the device to ensure that the file system is not corrupt.

541277 PMF did not restart tag <%s>, cmd_path="%s"

Description:

The process with the given tag failed to stay up and exceeded the allowed number of retry attempts (given by the 'pmfadm -n' option) and the action (given by the 'pmfadm -a' option) was initiated by rpc.pmfd. The action failed (i.e., returned non-zero), and rpc.pmfd will delete this tag from its tag list and discontinue retry attempts. For more information, see pmfadm(1M).

Solution:

This message is informational; no user action is needed.

541415 SCSLM malloc error <%s>

Description:

Should never occur.

Solution:

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

541445 Unable to compose %s path.

Description:

Unable to construct the path to the indicated file.

Solution:

Check system log messages to determine the underlying problem.

541818 Service group '%s' created

Description:

The service group by that name is now known by the scalable services framework.

Solution:

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

543720 Desired Primaries is %d. It should be 1.

Description:

Invalid value for Desired Primaries property.

Solution:

Invalid value is set for Desired Primaries property. The value should be 1. Reset the property value by using clresourcegroup.

544030 The entry in mnttab for mount point '%s' has too many fields.

Description:

The entry in mnttab for the specified mount point has more fields than are defined for a single mnttab entry.

Solution:

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

544097 Unable toallocate memory in sc delegated resource mgmt

Description:

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

Solution:

Check the system memory usage

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

Description:

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

Solution:

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

544185 A resource restart attempt on resource %s in resource group %s on node %s with Failover_mode=RESTART_ONLY has been blocked because the number of restarts within the past Retry_interval (%d seconds) would exceed Retry_count (%d)

Description:

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

Solution:

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

544380 Failed to retrieve the resource type handle: %s.

Description:

An API operation on the resource type has failed.

Solution:

For the resource type name, check the syslog tag. For more details, check the syslog messages from other components. If the error persists, reboot the node.

544497 Auto_recovery_command is not set.

Description:

Auto recovery was performed and the database was reinitialized by running the hadbm clear command. However the extension property auto_recovery_command was not set so no further recovery was attempted.

Solution:

HADB is up with a fresh database. Session stores will need to be recreated. In the future the auto_recovery_command extension property can be set to a command that can do this whenever autorecovery is performed.

544592 PCSENTRY: %s

Description:

The rpc.pmfd server was not able to monitor a process, and the system error is shown. An error message is output to syslog.

Solution:

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

544600 Reading from server timed out: server %s port %d

Description:

While reading the response from a request sent to the server the probe timeout ran out.

Solution:

Check that the server is functioning correctly and if the resources probe timeout is set too low.

544775 libpnm system error: %s

Description:

A system error has occured in libpnm. This could be because of the resources on the system being very low. eg: low memory.

Solution:

The user of libpnm should handle these errors. However, if the message is out of memory - increase the swap space, install more memory or reduce peak memory consumption. Otherwise the error is unrecovarable, and the node needs to be rebooted. write error - check the "write" man page for possible errors. read error - check the "read" man page for possible errors. socket failed - check the "socket" man page for possible errors. TCP_ANONPRIVBIND failed - check the "setsockopt" man page for possible errors. gethostbyname failed for %s - make sure entries in /etc/hosts, /etc/nsswitch.conf and /etc/netconfig are correct to get information about this host. bind failed - check the "bind" man page for possible errors. SIOCGLIFFLAGS failed - check the "ioctl" man page for possible errors. SIOCSLIFFLAGS failed - check the "ioctl" man page for possible errors. SIOCSLIFADDR failed - check the "ioctl" man page for possible errors. open failed - check the "open" man page for possible errors. SIOCLIFADDIF failed - check the "ioctl" man page for possible errors. SIOCLIFREMOVEIF failed - check the "ioctl" man page for possible errors. SIOCSLIFNETMASK failed - check the "ioctl" man page for possible errors. SIOCGLIFNUM failed - check the "ioctl" man page for possible errors. SIOCGLIFCONF failed - check the "ioctl" man page for possible errors. SIOCGLIFGROUPNAME failed - check the "ioctl" man page for possible errors. wrong address family - check the "ioctl" man page for possible errors. Cannot open libscconf - check that /usr/cluster/lib/libscconf.so.1 is properly installed. Cannot access libscconf function - check that /usr/cluster/lib/libscconf.so.1 is properly installed. Cannot access cluster configuration - check that you are in cluster mode. Failed to retrieve nodeid for %s. - Make sure that the name given is a valid node name.

544904 %s: exec failed for method %s: %s

Description:

Cannot execute the specified method of the service fmri

Solution:

The exec call has errored out not being able to execute.Test and see if the method is able to be executed without sc_delegated_restarter.

546018 Class <%s> SubClass <%s> Vendor <%s> Pub <%s>

Description:

The cl_eventd is posting an event locally with the specified attributes.

Solution:

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

546051 Error stopping the FED

Description:

The FED service fails to stop.

Solution:

Please reboot the node,

546524 dl_info ack bad len %d

Description:

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

Solution:

Reboot of the node might fix the problem.

546856 CCR: Could not find the CCR transaction manager.

Description:

The CCR data server could not find the CCR transaction manager in the cluster.

Solution:

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

547145 Initialization error. Fault Monitor username is NULL

Description:

Internal error. Environment variable SYBASE_MONITOR_USER not set before invoking fault monitor.

Solution:

Report this problem to your authorized Sun service provider.

547301 reservation error(%s) error. Unknown internal error returned from clconf_do_execution().

Description:

The device fencing program has suffered an internal error.

Solution:

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

547307 Initialization failed. Invalid command line %s

Description:

This method is expected to be called the the resource group manager. This method was not called with expected command line arguments.

Solution:

This is an internal error. Save the contents of /var/adm/messages from all the nodes and contact your Sun service representative.

547532 "pmfadm -s": Can not stop <%s>: Monitoring is not resumed on pid %d

Description:

The command 'pmfadm -s' can not be executed on the given tag because the monitoring is suspended on the indicated pid.

Solution:

Resume the monitoring on the indicated pid with the 'pmfctl -R' command.

548162 Error (%s) when reading standard property <%s>.

Description:

This is an internal error. Program failed to read a standard property of the resource.

Solution:

If the problem persists, save the contents of /var/adm/messages and contact your Sun service representative.

548237 Validation failed. Connect string contains 'sa' password.

Description:

The 'Connect_String' extension property used for fault monitoring uses 'sa' as the account password combination. This is a security risk, because the extension properties are accessible by everyone.

Solution:

Check the resource configuration and the value of the 'Connect_string'. property. Ensure that a dedicated account (with minimal privileges) is created for fault monitoring purposes.

548260 The ucmmd daemon will not be started due to errors in previous reconfiguration.

Description:

Error was detected during previous reconfiguration of the RAC framework component. Error is indicated in the message. As a result of error, the ucmmd daemon was stopped and node was rebooted. On node reboot, the ucmmd daemon was not started on the node to allow investigation of the problem. RAC framework is not running on this node. Oracle parallel server/ Real Application Clusters database instances will not be able to start on this node.

Solution:

Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Resolve the problem that resulted in reconfiguration error. Reboot the node to start RAC framework on the node. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters. If problem persists, contact your Sun service representative.

548445 Failed to refresh %s after property update.

Description:

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

Solution:

Run the command 'svcadm refresh <fmri>' to refresh the service instance. Then run the command 'svcs -x <service>' to verify that the service is online. If the problem persists, contact your Sun Support representative for further assistance.

548691 Delegating giveover request to resource group %s, due to a +++ affinity of resource group %s (possibly transitively).

Description:

A resource from a resource group which declares a strong positive affinity with failover delegation (+++ affinity) attempted a giveover request via the scha_control command. Accordingly, the giveover request was forwarded to the delegate resource group.

Solution:

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

548977 Function: clear_zone - Killing processes with fuser -cs 15 on the file system %s

Description:

The non-global zones shutdown command did not complete in time or zoneadm halt was not able to bring the non-global zone into state "installed". A fuser -cs 15 is submitted against each of the zones file systems. The reported processes will be send a SIGTERM.

Solution:

None.

549190 Text server successfully started.

Description:

The Sybase text server has been successfully started by Sun Cluster HA for Sybase.

Solution:

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

549765 Preparing to start service %s.

Description:

Sun Cluster is preparing to start the specified application

Solution:

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

549875 check_mysql - Couldn't get SHOW SLAVE STATUS for instance %s (%s)

Description:

The faultmonitor can't retrieve the MySQL slave status for the specified instance.

Solution:

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

550112 %s: Warning: The force option is being used to unmount %s

Description:

An attempt to unmount a global filesystem using umount(2) was unsuccessful. The system will retry to unmount the global filesystem using umount2(2) with the force option (MS_FORCE).

Solution:

None.

550126 Validate - The tftp testfile (%s) don't exist in directory (%s) or has filesize of zero bytes

Description:

The file specified in TFTPTESTFILE= within /opt/SUNWscdhc/util/dhcp_config doesn't exist or has a zero length witihin /etc/inet/inetd.conf.

Solution:

If TFTPTESTFILE= is required, then ensure file specified is correct.

550770 The resource "%s" cannot be added while the UCMMD is running.

Description:

An attempt was made to add a resource to the RAC framework resource group while the UCMM is running.

Solution:

Bring the RAC framework resource group to an unmanaged state, reboot the cluster, and repeat the attempt to add a resource.

551094 reservation warning(%s) - Unable to open device %s, will retry in %d seconds

Description:

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

Solution:

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

551285 %s not mounted, exiting

Description:

The /usr/lib/krb5 path is not accessible.

Solution:

Check this path and determine if /usr needs to be mounted.

551654 Port (%d) determined from Monitor_Uri_List is invalid

Description:

The indicated port is not valid.

Solution:

Correct the port specified in Monitor_Uri_List.

551893 Function: val_parfile - File %s does not exist

Description:

The parameter file does not exist in the parameter file directory.

Solution:

Restore the parameter file or re-register the resource.

552067 Waiting for Kerberos daemons to startup.

Description:

Waiting for both the krb5kdc and kadmind daemons to start successfully under PMF.

Solution:

This is for informational purposes only, no action is required.

552278 All WebSphere MQ Broker processes stopped

Description:

The WebSphere MQ Broker has been successfully stopped.

Solution:

No user action is needed.

553048 Cannot determine the nodeid

Description:

Internal error.

Solution:

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

553443 clq_netapp: quorum open error: Failed to create door_call_thread --- quorum device %s will be unavailable.

Description:

An internal error occurred when creating a thread to communicate with the NetApp NAS quorum device. The device will not be available.

Solution:

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

553590 User id %d not found in file %s.

Description:

The program failed to locate a valid entry in /etc/passwd for the specified user ID.

Solution:

Please verify that the specified user ID is valid. For Oracle, the specified user ID is obtained from the owner of the file $ORACLE_HOME/bin/oracle. Also ensure that both the Oracle user and dba group are declared locally in the /etc/passwd and /etc/group files.

555317 Could not restart telemetry data service

Description:

The Telemetry data service could not be restarted.

Solution:

This message is informational; no user action needed.

555780 Failed to clear active contract template: %s

Description:

Not able to clear the active contract template.

Solution:

Check the contract manpage to know more about the error.Also make sure the basic contract functionalities are working fine.Contact SUN vendor for more help.

555844 Cannot send reply: invalid socket

Description:

The cl_apid experienced an internal error.

Solution:

556039 Validation failed. ORACLE_HOME/bin/srvctl not found ORACLE_HOME=%s

Description:

The SUNW.scalable_rac_server_proxy agent could not find the srvctl binary in the indicated ORACLE_HOME/bin directory.

Solution:

Check whether the $ORACLE_HOME/bin directory is accessible, and if so, whether the srvctl binary exists. If the problem persists, contact your Sun support representative for further assistance.

556113 Resource dependency on SAP enqueue server does not match the affinity setting on SAP enqueue server resource group.

Description:

Both the dependency on a SAP enqueue server resource and the affinity on a SAP enqueue server resource group are set. However, the resource groups specified in the affinity property does not correspond to the resource group that the SAP enqueue server resource (specified in the resource dependency) belongs to.

Solution:

Specify a SAP enqueue server resource group in the affinity property. Make sure that SAP enqueue server resource group contains the SAP enqueue server resource that is specified in the resource dependency property.

556466 clexecd: dup2 of stdout returned with errno %d while exec'ing (%s). Exiting.

Description:

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

Solution:

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

556694 Nodes %u and %u have incompatible versions and will not communicate properly.

Description:

This is an informational message from the cluster version manager and may help diagnose which systems have incompatible versions with eachother during a rolling upgrade. This error may also be due to attempting to boot a cluster node in 64-bit address mode when other nodes are booted in 32-bit address mode, or vice versa.

Solution:

This message is informational; no user action is needed. However, one or more nodes may shut down in order to preserve system integrity. Verify that any recent software installations completed without errors and that the installed packages or patches are compatible with the software installed on the other cluster nodes.

556800 Validation failed. Resource Group %s containing the Proxy Resource %s should have a strong positive affinity on the Resource Group %s containing an offline restart dependee resource %s.

Description:

One or more resources that you are specifying as an offline restart dependee of the proxy resource does not belong to a resource group on which the resource group containing the proxy resource has a strong positive affinity.

Solution:

Modify the resource group containing the proxy resource to have a strong positive affinity on the dependee resource's resource group.

556945 No permission for owner to execute %s.

Description:

The specified path does not have the correct permissions as expected by a program.

Solution:

Set the permissions for the file so that it is readable and executable by the owner.

557585 No filesystem mounted on %s.

Description:

There is no filesystem mounted on the mount point.

Solution:

None. This is a debug message.

558184 Validate - MySQL logdirectory for mysqld does not exist

Description:

The defined (-L option) log directory does not exist.

Solution:

Make sure that the defined log directory exists.

558306 Error deleting PidLog <%s> (%s) for iPlanet service with config file <%s>.

Description:

The data service was not able to delete the specified PidLog file.

Solution:

Delete the PidLog file manually and start the the resource group.

558350 Validation failed. Connect string is incomplete.

Description:

The 'Connect_String' extension property used for fault monitoring has been incorrectly specified. This has the format "username/password".

Solution:

Check the resource configuration and the value of the 'Connect_String' property. Ensure that there are no spaces in the 'Connect_String' specification.

558742 Resource group %s is online on more than one node.

Description:

The named resource group should be online on only one node, but it is actually online on more than one node.

Solution:

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

558763 Failed to start the WebLogic server configuredin resource %s

Description:

The WebLogic Server configured in the resource could not be started by the agent.

Solution:

Try to start the Weblogic Server manually and check if it can be started manually. Make sure the logical host is UP before starting the WLS manually. If it fails to start manually then check your configuration and make sure it can be started manually before it can be started by the agent. Make sure the extension properties are correct. Make sure the port is not already in use.

558769 Failed to get UCMM state; can not continue IO probing !

Description:

The state of the UCMM could not be retrieved by the probe. This is an internal error.

Solution:

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

559206 Either extension property <stop_signal> is not defined, or an error occurred while retrieving this property; using the default value of SIGTERM.

Description:

Property stop_signal might not be defined in RTR file. The process continues with the default value of SIGTERM.

Solution:

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

559516 SCSLM <%s> ret %d

Description:

Should never occur.

Solution:

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

559857 Starting liveCache with command %s failed. Return code is %d.

Description:

Starting liveCache failed.

Solution:

Check SAP liveCache log files and also look for syslog error messages on the same node for potential errors.

560047 Unix DLM version (%d) and SUN Unix DLM library version (%d): compatible.

Description:

The Unix DLM is compatible with the installed version of libudlm.

Solution:

None.

560241 Error: Can't run RGEVACUATE script outside of run control environment.

Description:

The stoprgm init script was run manually (not automatically by init(1M)). This is not supported by Sun Cluster software. The "stoprgm" command was not successful. No action was performed.

Solution:

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

560630 SCSLM <%s> zone <%s> no groups

Description:

Should never occur.

Solution:

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

560781 Tag %s: could not allocate history.

Description:

The rpc.pmfd server was not able to allocate memory for the history of the tag shown. Monitoring of he process associated with the tag is stopped and pmfadm returns an error. This problem can occur if the machine has low memory.

Solution:

560808 Derby data service start method timed out

Description:

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

Solution:

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

561162 Failed to remove sci%d adapter

Description:

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

Solution:

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

561299 Error: ${SERVER} is already running.

Description:

The initfed init script found the rpc.fed already running. It will not start it again.

Solution:

No action required.

561862 PNM daemon config error: %s

Description:

A configuration error has occured in the PNM daemon. This could be because of wrong configuration/format etc.

Solution:

If the message is: IPMP group %s not found - either an IPMP group name has been changed or all the adapters in the IPMP group have been unplumbed. There would have been an earlier NOTICE which said that a particular IPMP group has been removed. The pnmd has to be restarted. Send a KILL (9) signal to the PNM daemon. Because pnmd is under PMF control, it will be restarted automatically. If the problem persists, restart the node with clnode evacuate and shutdown. IPMP group %s already exists - the user of libpnm is trying to auto-create an IPMP group with a groupname that is already being used. Typically, this should not happen so contact your authorized Sun service provider to determine whether a workaround or patch or suggestion is available. Make a note of all the IPMP group names on your cluster. wrong format for /etc/hostname.%s - the format of /etc/hostname.<adp> file is wrong. Either it has the keyword group but no group name following it or the file has multiple lines. Correct the format of the file after going through the IPMP Admin Guide. The pnmd has to be restarted. Send a KILL (9) signal to the PNM daemon. Because pnmd is under PMF control, it will be restarted automatically. If the problem persists, restart the node by using clnode evacuate and shutdown. We do not support multi-line /etc/hostname.adp file in auto-create since it becomes difficult to figure out which IP address the user wanted to use as the non-failover IP address. All adps in %s do not have similar instances (IPv4/IPv6) plumbed - An IPMP group is supposed to be homogenous. If any adp in an IPMP group has a certain instance (IPv4 or IPv6) then all the adps in that IPMP group must have that particular instance plumbed in order to facilitate failover. Please see the Solaris IPMP docs for more details. %s is blank - this means that the /etc/hostname.<adp> file is blank. We do not support auto-create for blank v4 hostname files - since this will mean that 0.0.0.0 will be plumbed on the v4 address.

561896 Failed to create thread for probing. %s

Description:

The thread that is used for the I/O probe could not be created.

Solution:

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

562040 Update_drv failed to re-read did.conf file for

Description:

Update_drv command was NOT able to make did driver re-read did.conf.

Solution:

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

562200 Application failed to stay up.

Description:

The probe for the SUNW.Event data service found that the cl_apid application failed to stay up.

Solution:

562397 Failfast: %s.

Description:

A failfast client has encountered a deferred panic timeout and is going to panic the node or zone. This might happen if a critical userland process, as identified by the message, dies unexpectedly.

Solution:

Check for core files of the process after rebooting the node or zone and report these files to your authorized Sun service provider.

562700 unable to arm failfast.

Description:

Internal error.

Solution:

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

563025 XDR FE Buffer Shortfall while encoding arguments API num = %d, will retry

Description:

A non-fatal error occurred while rpc.fed was marshalling arguments for a remote procedure call. The operation will be re-tried with a larger buffer.

Solution:

No user action is required. If the message recurs frequently, contact your authorized Sun service provider to determine whether a workaround or patch is available.

563343 resource type %s updated.

Description:

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

Solution:

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

563800 Failed to get all IPMP groups (request failed with %d).

Description:

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

Solution:

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

563847 INTERNAL ERROR: POSTNET_STOP method is not registered for resource <%s>

Description:

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

Solution:

563976 Unable to get socket flags: %s.

Description:

Failed to get status flags for the socket used in communicating with the application.

Solution:

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

564643 Fault monitor detected error %s: %ld %s Action=%s : %s

Description:

Fault monitor has detected an error. Error detected by fault monitor and action taken by fault monitor is indicated in message. This message also indicates whether the action taken is default or user-defined (custom).

Solution:

None

564810 Function: validate - Zone %s has brand type %s. No SMF available, sczsmf does not work for the configured Zone.

Description:

The sczsmf component does not work with zones of brand type other than "native", since they have no SMF feature implemented.

Solution:

Don't configure the sczsmf component for a zone of brand type other than "native". Use the sczsh component instead.

564883 The Data base probe %s also failed. Will restart or failover the WLS only if the DB is UP

Description:

probing of the URL's set in the Server_url or the Monitor_uri_list failed. Before taking any action the WLS probe would make sure the DB is up (if a db_probe_script extension property is set). But, the DB probe also failed. The probe will not take any action till the DB is UP and the DB probe succeeds.

Solution:

Start the Data Base and make sure the DB probe (the script set in the db_probe_script) returns 0 for success. Once the DB is started the WLS probe will take action on the failed WLS instance.

565198 did subpath %s created for instance %d.

Description:

Informational message from scdidadm.

Solution:

No user action required.

565220 Derby start method failed for unknown reason

Description:

The derby data service could not start for an unknown reason.

Solution:

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

565362 Transport heart beat timeout is changed to %s.

Description:

The global transport heart beat timeout is changed.

Solution:

None. This is only for information.

565368 Could not dlopen (%s)

Description:

An error occurred during an attempt to open the library.

Solution:

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

565438 svc_run returned

Description:

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

Solution:

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

565591 Failed to add CMM version key %s, version %d to the CCR infrastructure table

Description:

The CMM failed to register the CMM version in the CCR. The result of this failure will be to continue using the old CMM version during the next reconfiguration.

Solution:

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

565943 %s group name is not found in the netiflist property for node %s. Current netiflist value is %s.

Description:

Netiflist property value does not have an IPMP group name specified for the node.

Solution:

Update the netiflist property to include the IPMP group name for the given node. Then, retry the resource group update operation.

565978 Home dir is not set for user %s.

Description:

Home directory for the specified user is not set in the system.

Solution:

Check and make sure the home directory is set up correctly for the specified user.

566781 ORACLE_HOME %s does not exist

Description:

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

Solution:

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

567338 Error in scha_rg_open of rg:%s, Err: %s

Description:

Cannot open the resource group

Solution:

Take action depending on the error depending on the error code

567374 Failed to stop %s.

Description:

Sun Cluster failed to stop the application.

Solution:

Use process monitor facility (pmfadm (1M)) with -L option to retrieve all the tags that are running on the server. Identify the tag name for the application in this resource. This can be easily identified as the tag ends in the string ".svc" and contains the resource group name and the resource name. Then use pmfadm (1M) with -s option to stop the application. This problem may occur when the cluster is under load and Sun Cluster cannot stop the application within the timeout period specified. You may consider increasing the Stop_timeout property. If the error still persists, then reboot the node.

567783 %s - %s

Description:

The first %s refers to the calling program, whereas the second %s represents the output produced by that program. Typically, these messages are produced by programs such as strmqm, endmqm rumqtrm etc.

Solution:

No user action is required if the command was successful. Otherwise, examine the other syslog messages occurring at the same time on the same node to see if the cause of the problem can be identified.

567819 clcomm: Fixed size resource_pool short server threads: pool %d for client %d total %d

Description:

The system can create a fixed number of server threads dedicated for a specific purpose. The system expects to be able to create this fixed number of threads. The system could fail under certain scenarios without the specified number of threads. The server node creates these server threads when another node joins the cluster. The system cannot create a thread when there is inadequate memory.

Solution:

There are two possible solutions. Install more memory. Alternatively, reduce memory usage. Application memory usage could be a factor, if the error occurs when a node joins an operational cluster and not during cluster startup.

568314 Failed to remove node %d from scalable service group %s: %s.

Description:

A call to the underlying scalable networking code failed.

Solution:

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

568392 check_dhcp - Dhcpclient test timed out exeeded %s seconds

Description:

The dhcpclient has exceeded it's timeout allowance.

Solution:

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

568789 libsecurity, door_call: Fatal, could not allocate space for return arguments, Client is out of memory.

Description:

The client (libpmf/libfe/libscha) has run out of memory and the door call could not complete.

Solution:

Check for swap space and/or memory usage of the client process. Try rebooting the node and/or check the client process configuration. Save the /var/adm/messages files on each node. Contact your authorized Sun service provider for assistance.

569010 Can't open %s

Description:

Cannot open the file provided the extended resource property

Solution:

Chack for the permision and path validity of the file

569552 %s: Create failed for netpath "circuit_v".

Description:

This program could not create the RPC server handle.

Solution:

Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.

569559 Start of %s completed successfully.

Description:

The resource successfully started the application.

Solution:

This message is informational; no user action is needed.

569889 Function: validate - Zonebrand for zone %s is configured as native, but the zone is configured as brand type %s.

Description:

Zonebrand is set to "native". But the Zone is configured as a different brand type (i.e. lx) according to zonecfg info.

Solution:

Review the components configuration file and make sure the variable Zonebrand defines the actual zone brand type for the Zone.

570204 Resource group %s rebalanced successfully

Description:

The named resource group was successfully brought online on the cluster node.

Solution:

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

570394 reservation warning(%s) - USCSI_RESET failed for device %s, returned %d, will retry in %d seconds

Description:

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

Solution:

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

570525 Stopping startup script initiated by agent.

Description:

The agent is attempting to stop a previous instance startup instruction that was issued to it.

Solution:

None required. Informational message.

570811 Filer "%s" not configured within SunCluster

Description:

The NAS device is not configured with Sun Cluster. Before the ScalMountPoint resource can be brought online, the NAS device must be configured by using the scnas command.

Solution:

Use the scnas command to configure the NAS device with Sun Cluster.

571642 ucm_callback for cmmreturn generated exception %d

Description:

ucmm callback for step cmmreturn failed.

Solution:

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

571734 Validation failed. ORACLE_SID is not set

Description:

ORACLE_SID property for the resource is not set. HA-Oracle will not be able to manage Oracle server if ORACLE_SID is incorrect.

Solution:

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

571825 Stopping listener %s.

Description:

Informational message. HA-Oracle will be stopping Oracle listener.

Solution:

None

571838 Failed to get information for filer "%s"

Description:

The call to scnas_get_one_filer() failed. This call is supposed to return information regarding the given filer. Possible reasons for the failure might be that the filer is not configured yet.

Solution:

Check that the NAS device is ready to work with Sun Cluster.

572181 SCSLM <%s> pool_to_elem error <%s>

Description:

Should never occur.

Solution:

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

572398 HA: primary RM died during boot, no secondary available, must reboot.

Description:

Primary and secondaries for Replica Manger service are all dead, remaining nodes which are booting cannot rebuild RM state and must reboot immediatly, even if they were able to form a valid partition from the quorum point of view.

Solution:

No action required

572885 Pathprefix %s for resource group %s is not readable: %s.

Description:

A HA-NFS method attempted to access the specified Pathprefix but was unable to do so. The reason for the failure is also logged.

Solution:

This could happen if the filesystem on which the Pathprefix directory resides is not available. Use the HAStorage resource in the resource group to make sure that HA-NFS methods have access to the file system at the time when they are launched. Check to see if the pathname is correct and correct it if not so. HA-NFS would attempt to recover from this situation by failing over to some other node.

572955 host %s: client is null

Description:

The rgm is not able to obtain an rpc client handle to connect to the rpc.fed server on the named host. An error message is output to syslog.

Solution:

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

574542 clexecd: fork1 returned %d. Exiting.

Description:

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

Solution:

If the error number is 12 (ENOMEM), install more memory, increase swap space, or reduce peak memory consumption. If error number is something else, contact your authorized Sun service provider to determine whether a workaround or patch is available.

574675 nodeid of ctxp is bad : %d

Description:

nodeid in the context pointer is bad.

Solution:

None. udlm takes appropriate action.

574906 start_samba - Could not start Samba server %s %s daemon

Description:

The Samba resource could not start the Samba server nmbd process.

Solution:

The Samba resource will be restarted, however examine the other syslog messages occurring at the same time on the same node, to see if the cause of the problem can be identified.

575351 Can't retrieve binding entries from node %d for GIF node %d

Description:

Failed to maintain client affinity for some sticky services running on the named server node. Connections from existing clients for those services might go to a different server node as a result.

Solution:

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

575545 fatal: rgm_chg_freeze: INTERNAL ERROR: invalid value of rgl_is_frozen <%d> for resource group <%s>

Description:

The in-memory state of the rgmd has been corrupted due to an internal error. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution:

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

575905 Failed to stop DNS using the custom stop command; trying SIGKILL now.

Description:

The stop command failed to stop the application.

Solution:

Refer to your data services documentation for configuring the stop command. If problem persists, contact your Sun service provider to determine whether a workaround or patch is available.

576169 Validate callback completed successfully.

Description:

The validate callback was successful.

Solution:

No user action is required.

576196 clcomm: error loading kernel module: %d

Description:

The loading of the cl_comm module failed.

Solution:

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

576621 Command %s does not have execute permission set.

Description:

The specified pathname, which was passed to a libdsdev routine such as scds_timerun or scds_pmf_start, refers to a file that does not have execute permission set. This could be the result of 1) mis-configuring the name of a START or MONITOR_START method or other property, 2) a programming error made by the resource type developer, or 3) a problem with the specified pathname in the file system itself.

Solution:

Ensure that the pathname refers to a regular, executable file.

576769 Start command %s failed with error %s.

Description:

The execution of the command for starting the data service failed.

Solution:

No user action needed.

577088 Waiting for WLS to startup

Description:

This is just a informational message that the WLS is still starting up.

Solution:

None

577130 Failed to retrieve network configuration: %s.

Description:

Attempt to get network configuration failed. The precise error strings is included with the message.

Solution:

Check to make sure that the /etc/netconfig file on the system is not corrupted and it has entries for tcp and udp. Additionally, make sure that the system has enough resources (particularly memory). HA-NFS would attempt to recover from this failure by failing over to another node, by crashing the current node, if this error occurs during STOP or POSTNET_STOP method execution.

577140 clcomm: Exception during unmarshal_receive

Description:

The server encountered an exception while unmarshalling the arguments for a remote invocation. The system prints the exception causing this error.

Solution:

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

577241 %s: Warning: The force option was needed to unmount %s

Description:

The scshutdown command broadcasts a warning message of an impending cluster shutdown and provides a grace period for users to desist usage of filesystems. Subsequently, if scshutdown cannot unmount a global filesystem because of continued activity, scshutdown uses the force option for unmount, regardless of user activity.

Solution:

None.

577688 SCSLM fe_run wrong args <%s>

Description:

Should never occur.

Solution:

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

578055 stop_mysql - Failed to flush MySQL tables for %s

Description:

mysqladmin command failed to flush MySQL tables.

Solution:

Either was MySQL already down or the faultmonitor user does not have the right permission to flush tables. The defined faultmonitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges.

578979 SCSLM zone <%s> bind to pool.sys_id %llu, which is not pool_default (pool.sys_id %llu)

Description:

Non-global Zone configuration error. A non-global zone used to run resource groups under SLM control must use pool pool_default, (zonecfg) and dynamically (poolbind).

Solution:

Set zone pool to pool_default in zonecfg and set zone binding to pool_default (poolbind) before launching a resource group under SLM control in this zone.

579190 INTERNAL ERROR: resource group <%s> state <%s> node <%s> contains resource <%s> in state <%s>

Description:

The rgmd has discovered that the indicated resource group's state information appears to be incorrect. This may prevent any administrative actions from being performed on the resource group.

Solution:

579208 Global service %s associated with path %s is found to be in maintenance state.

Description:

Self explanatory.

Solution:

Check the global service configuration.

579367 Update_drv failed to re-read did.conf file

Description:

Update_drv command was NOT able to make did driver re-read did.conf file after 1 retry. Will use devfsadm command instead.

Solution:

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

579575 Will not start database. Waiting for %s (HADB node %d) to start resource.

Description:

The specified Sun Cluster node must be running the HADB resource before the database can be started.

Solution:

Bring the HADB resource online on the specified Sun Cluster node.

579818 No entry for file-system %s found in /etc/vfstab.

Description:

The entry for the specified shared QFS file system is missing from the /etc/vfstab file.

Solution:

Add a valid entry for this file system to /etc/vfstab and repeat the operation.

579987 Error binding '%s' in the name server. Exiting.

Description:

clexecd program was unable to start because of some problems in the low-level clustering software.

Solution:

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

580015 WebSphere MQ Trigger Monitor %s started

Description:

The specified WebSphere MQ Trigger Monitor has been started.

Solution:

None required. Informational message.

580105 MQSeriesIntegrator2%s file deleted

Description:

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

Solution:

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

580416 Cannot restart monitor: Monitor is not enabled.

Description:

An update operation on the resource would have been restarted the fault monitor. But, the monitor is currently disabled for the resource.

Solution:

This is informational message. Check whether the monitor is disabled for the resource. If not, consider it as an internal error and contact your authorised Sun service provider.

580750 Auto_recovery_command should be a regular file: %s

Description:

The Auto_recovery_command extension property needs to be a regular file.

Solution:

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

580802 Either extension property <network_aware> is not defined, or an error occured while retrieving this property; using the default value of TRUE.

Description:

Property Network_aware might not be defined in RTR file. Use the default value of true.

Solution:

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

580948 fatal: can't be run in a non-global zone.

Description:

The cl_apid can't be executed from a non-global zone.

Solution:

Run cl_apid only from the global zone.

581117 Cleanup with command %s.

Description:

Cleanup the SAPDB database instance before starting up the instance in case the database crashed and was in a bad state with the command which is listed.

Solution:

Informational message. No action is needed.

581180 launch_validate: call to rpc.fed failed for resource <%s>, method <%s>

Description:

The rgmd failed in an attempt to execute a VALIDATE method, due to a failure to communicate with the rpc.fed daemon. If the rpc.fed process died, this might lead to a subsequent reboot of the node. Otherwise, this will cause the failure of a creation or update operation on a resource or resource group.

Solution:

Examine other syslog messages occurring at about the same time to see if the problem can be identified. 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.

581376 clcomm: solaris xdoor: too much reply data

Description:

The reply from a user level server will not fit in the available space.

Solution:

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

581413 Daemon %s is not running.

Description:

HA-NFS fault monitor checks the health of statd, lockd, mountd and nfsd daemons on the node. It detected that one these are not currently running.

Solution:

No action. The monitor would restart these.

581586 Failfast timeout - unit "%s" of zone "%s" (zone ID %d) %s

Description:

The specified failfast unit has timed out, and is going to panic the zone.

Solution:

There might be other related messages on this node that can help diagnose the problem. Resolve the problem and reboot the zone if the zone panic is unexpected.

581898 Application failed to stay up. Start method Failure.

Description:

The Application failed to stay start up.

Solution:

Look in /var/adm/messages for the cause of failure. Try to start the Weblogic Server manually and check if it can be started manually. Make sure the logical host is UP before starting the DAS manually. If it fails to start manually then check your configuration and make sure it can be started manually before it can be started by the agent. Make sure the extension properties are correct. Make sure the port is not already in use. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

581902 (%s) invalid timeout '%d'

Description:

Invalid timeout value for a method.

Solution:

Make sure udlm.conf file has correct timeouts for methods.

582353 Adaptive server shutdown with wait failed. STOP_FILE %s.

Description:

The Sybase adaptive server failed to shutdown with the wait option using the file specified in the STOP_FILE property.

Solution:

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

582418 Validation failed. SYBASE ASE startserver file not found SYBASE=%s.

Description:

The Sybase Adaptive server is started by execution of the "startserver" file. This file is missing. The SYBASE directory is specified as a part of this error message.

Solution:

Verify the Sybase installation including the existence and proper permissions of the "startserver" file in the $SYBASE/$SYBASE_ASE/install directory.

582651 tag %s: does not belong to caller

Description:

The user sent a suspend/resume command to the rpc.fed server for a tag that was started by a different user. An error message is output to syslog.

Solution:

Check the tag name.

582789 Function: check_sczbt - %s runlevel [%s] not online, runlevel is %s, try again in 5 seconds

Description:

The runlevel is not equal to the configured LXrunlevel. The state is checked again in 5 seconds.

Solution:

None.

583147 scf_service_create failed: %s

Description:

An API call failed.

Solution:

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

583224 Rebooting this node because daemon %s is not running.

Description:

The rpcbind daemon on this node is not running.

Solution:

No action. Fault monitor would reboot the node. Also see message id 804791.

583542 clcomm: Pathend: would abort node because %s for %u ms

Description:

The system would have aborted the node for the specified reason if the check for send thread running was enabled.

Solution:

No user action is required.

583970 Failed to shutdown liveCache immediately with command %s.

Description:

Stopping SAP liveCache with the specified command failed to complete.

Solution:

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

584022 zoneadm call failed for zone %s: %d

Description:

The attempted zoneadm call failed. The zone will stay up, but the rgmd will not attempt to start services on the zone.

Solution:

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

584207 Stopping %s.

Description:

Sun Cluster is stopping the specified application.

Solution:

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

584386 PENDING_OFFLINE: bad resource state <%s> (%d) for resource <%s>

Description:

The rgmd state machine has discovered a resource in an unexpected state on the local node. This should not occur and may indicate an internal logic error in the rgmd.

Solution:

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

584425 Validation failed. CRS_HOME/bin/crs_start not found CRS_HOME=%s

Description:

The SUNW.scalable_rac_server_proxy agent could not find the crs_start binary in the indicated $CRS_HOME/bin/ directory.

Solution:

Check whether the $CRS_HOME/bin/ directory is accessible, and if so, whether the crs_start binary exists. If the problem persists, contact your Sun support representative for further assistance.

585295 Validate - getservbyname file does not exist or is not executable at %s/getservbyname

Description:

The file 'getservbyname' can not be found, or is not executable.

Solution:

Confirm the file '${SGE_ROOT}/utilbin/<arch>/getservbyname' both exists in that location, and is executable.

585726 pthread_cond_init: %s

Description:

The cl_apid was unable to initialize a synchronization object, so it was not able to start-up. The error message is specified.

Solution:

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

585843 open64 while retrieving template info: %s

Description:

The rpc.pmfd was unable to open a file in the /system/contract/process/ directory. Consequently, the rpc.pmfd was unable to launch the requested 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.

586052 Derby data service Stop method timed out

Description:

The derby data service could not stop before the configured timeout elapsed.

Solution:

This message is informational; no user action needed.

586294 Thread creation error: %s

Description:

Internal error.

Solution:

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

586298 clcomm: unknown type of signals message %d

Description:

The system has received a signals message of unknown type.

Solution:

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

586689 Cannot access the %s command <%s> : <%s>

Description:

The command input to the agent builder is not accessible and executable. This may be due to the program not existing or the permissions not being set properly.

Solution:

Make sure the program in the command exists, is in the proper directory, and has read and execute permissions set appropriately.

586807 Telemetry data service monitor check method succeeded

Description:

The monitor program of the telemetry data service reported success.

Solution:

This message is informational; no user action needed.

587554 Function: validate - Syntax errors in %s

Description:

The parameter file is not a valid shell script.

Solution:

Correct the parameter file. It must pass ksh -n <file name>.

587573 cm_getstate failed with error %d

Description:

Unable to get the cluster state.

Solution:

Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.

588055 Failed to retrieve information for SAP xserver user %s.

Description:

The SAP xserver user is not found on the system.

Solution:

Make sure the user is available on the system.

589035 Error in the mnttab entry for mount point '%s'.

Description:

An error occurred while the mnttab entry for the specified mount point was being read.

Solution:

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

589373 scha_control RESOURCE_RESTART failed with error code: %s

Description:

Fault monitor had detected problems in Oracle listener. Attempt to switchover resource to another node failed. Error returned by API call scha_control is indicated in the message. If problem persists, fault monitor will make another attempt to restart the listener.

Solution:

Check Oracle listener setup. Please make sure that Listener_name specified in the resource property is configured in listener.ora file. Check 'Host' property of listener in listener.ora file. Examine log file and syslog messages for additional information.

589594 scha_control: warning, RESOURCE_IS_RESTARTED call on resource <%s> will not increment the resource_restart count because the resource does not have a Retry_interval property

Description:

A resource monitor (or some other program) is attempting to notify the RGM that the indicated resource has been restarted, by calling scha_control(1ha),(3ha) with the RESOURCE_IS_RESTARTED option. This request will trigger restart dependencies, but will not increment the retry_count for the resource, because the resource type does not declare the Retry_interval property for its resources. To enable the NUM_RESOURCE_RESTARTS query, the resource type registration (RTR) file must declare the Retry_interval property.

Solution:

Contact the author of the data service (or of whatever program is attempting to call scha_control) and report the warning.

589805 Fault monitor probe response times are back below 50%% of probe timeout. The timeout will be reduced to it's configured value

Description:

The resource's probe timeout had been previously increased by 10% because of slow response, but the time taken for the last fault monitor probe to complete, and the avarege probe time, are both now less than 50% of the timeout. The probe timeout will therefore be reduced to it's configured value.

Solution:

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

589817 clcomm: nil_sendstream::send

Description:

The system attempted to use a "send" operation for a local invocation. Local invocations do not use a "send" operation.

Solution:

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

590147 Resource%s has reached the max retries of its services and will be failingover now

Description:

The number of restarts of services under the resource has reached the max. So the resource will be failing over

Solution:

No action neede.Just a notice meesage

590454 TCPTR: Machine with MAC address %s is using cluster private IP address %s on a network reachable from me. Path timeouts are likely.

Description:

The transport at the local node detected an arp cache entry that showed the specified MAC address for the above IP address. The IP address is in use at this cluster on the private network. However, the MAC address is a foreign MAC address. A possible cause is that this machine received an ARP request from another machine that does not belong to this cluster, but hosts the same IP address using the above MAC address on a network accessible from this machine. The transport has temporarily corrected the problem by flushing the offending arp cache entry. However, unless corrective steps are taken, TCP/IP communication over the relevant subnet of the private interconnect might break down, thus causing path downs.

Solution:

Make sure that no machine outside this cluster hosts this IP address on a network reachable from this cluster. If there are other sunclusters sharing a public network with this cluster, make sure that their private network adapters are not miscabled to the public network. By default all sunclusters use the same set of IP addresses on their private networks.

590700 ALERT_LOG_FILE %s doesn't exist

Description:

File specified in resource property 'Alert_log_file' does no exist. HA-Oracle requires correct Alert Log file for fault monitoring.

Solution:

Check 'Alert_log_file' property of the resource. Specify correct Oracle Alert Log file when creating resource. If resource is already created, please update resource property Alert_log_file'.

591719 Invalid error return (%d) from device group probe

Description:

An unexpected error occurred in the probe of a disk set or disk group.

Solution:

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

592233 setrlimit(RLIMIT_NOFILE): %s

Description:

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

Solution:

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

592276 (%s) not owner of diskgroup (%s)

Description:

This node is not the owner of the disk set or disk group.

Solution:

Determine whether the SUNW.rac_framework resource is online. To obtain this information, run 'scstat -b'. Determine whether the node is in the node list of the disk set or disk group. To retrieve the node list of the disk set or disk group, run scstat -D or cldevicegroup show.

592285 clexecd: getrlimit returned %d

Description:

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

Solution:

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

592305 Failed to retrieve the resource property %s on node %s: %s.

Description:

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

Solution:

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

592352 SCSLM <%s> error pmin > pmax

Description:

Should never occur.

Solution:

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

592378 Resource %s is not online anywhere.

Description:

The named resource is not online on any cluster node.

Solution:

None. This is an informational message.

592920 sigemptyset: %s

Description:

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

Solution:

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

593143 Incorrect numberof volumes!

Description:

The number of volumes that a call to libvxvmsc.so returned differs from the number that an earlier call returned.

Solution:

Check the status of the disk set or disk group. Contact your authorized Sun service provider for further assistance in diagnosing the problem.

593330 Resource type name is null.

Description:

This is an internal error. While attempting to retrieve the resource information, null value was retrieved for the resource type name.

Solution:

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

593712 ORACLE_SID extension property must match the ORACLE_SID environment variable setting for Oracle.

Description:

The value of the ORACLE_SID extension property should be a valid value, that is identical to the value of the ORACLE_SID environment variable set before starting up the Oracle database.

Solution:

In order to bring the resource online, set the value of the ORACLE_SID extension property of the Sun Cluster resource to the value for that Oracle instance using appropriate Sun Cluster commands and retry bringing the resource online.

593855 Custom monitor actions found in %s. These will override the default actions.

Description:

This message indicates that a custom monitor action file has been configured. The entries in this file will determine the actual action that is taken for the specified errors. In case any error is specified in both, the custom and the default action files, the action specified in the custom action file will be chosen.

Solution:

None.

594348 About to umount %s.

Description:

HAStoragePlus will umount the underlying device corresponding to the mount point that is specified in /etc/mnttab.

Solution:

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

594396 Thread creation failed for node %d.

Description:

The cl_eventd failed to create a thread. This error may cause the daemon to operate in a mode of reduced functionality.

Solution:

595077 Error in hasp_check. Validation failed.

Description:

Internal error occured in hasp_check.

Solution:

Check the errors logged in the syslog messages by hasp_check. Please verify existance of /usr/cluster/bin/hasp_check binary. Please report this problem.

595101 t_sndudata in send_reply: %s

Description:

Call to t_sndudata() failed. The "t_sndudata" man page describes possible error codes. udlm will try to resend the message. abort.

Solution:

None.

595448 Validate - mysqld %s non-existent executable

Description:

The mysqld command don't exist or is not executable.

Solution:

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

595686 %s is %d for %s. It should be 1.

Description:

The named property has an unexpected value.

Solution:

Change the value of the property to be 1.

595774 cm_getclustmbyname failed

Description:

Unable to get the cluster name.

Solution:

Save the contents of /var/adm/messages from all nodes and contact your Sun service representative for assistance in diagnosing and correcting the problem.

595926 Stopping Adaptive server with nowait option.

Description:

The Sun Cluster HA for Sybase will retry the shutdown using the nowait option.

Solution:

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

596001 The fault monitor will not be restarted

Description:

Fault Monitor will not be restarted when resource is configured to indicate Database role transition.

Solution:

None required. Informational message.

596447 Unix DLM is asking for a reconfiguration to recover from a communication error.

Description:

A reconfiguration has been requested by udlm.

Solution:

None.

596604 clcomm: solookup on routing socket failed with error = %d

Description:

The system prepares IP communications across the private interconnect. A lookup operation on the routing socket failed.

Solution:

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

596938 Could not restart the derby data service

Description:

The Derby data service could be restarted.

Solution:

For more detailed error message, check the syslog messages. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

597239 The weight portion of %s at position %d in property %s is not a valid weight. The weight should be an integer between %d and %d.

Description:

The weight noted does not have a valid value. The position index, which starts at 0 for the first element in the list, indicates which element in the property list was invalid.

Solution:

Give the weight a valid value.

597381 setrlimit before exec: %s

Description:

rpc.pmfd was unable to set the number of file descriptors before executing a process.

Solution:

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

598087 PCWSTOP: %s

Description:

The rpc.pmfd server was not able to monitor a process, and the system error is shown. An error message is output to syslog.

Solution:

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

598115 Ignoring invalid expression <%s> in custom action file.

Description:

This is an informational message indicating that an entry with an invalid expression was found in the custom action file and will be ignored.

Solution:

Remove the invalid entry from the custom action file or correct it to be a valid regular expression.

598540 clcomm: solaris xdoor: completed invo: door_return returned, errno = %d

Description:

An unusual but harmless event occurred. System operations continue unaffected.

Solution:

No user action is required.

598554 launch_validate_method: getlocalhostname() failed for resource <%s>, resource group <%s>, method <%s>

Description:

The rgmd daemon was unable to obtain the name of the local host, causing a VALIDATE method invocation to fail. This in turn will cause the failure of a creation or update operation on a resource or resource group.

Solution:

598979 tag %s: already suspended

Description:

The user sent a suspend command to the rpc.fed server for a tag that is already suspended. An error message is output to syslog.

Solution:

Check the tag name.

599371 Failed to stop the WebLogic server smoothly.Will try killing the process using sigkill

Description:

The Smooth shutdown of the WLS failed. The WLS stop method however will go ahead and kill the WLS process.

Solution:

Check the WLS logs for more details. Check the /var/adm/messages and the syslogs for more details to fix the problem.

599430 Failed to retrieve the resource property %s: %s.

Description:

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

Solution:

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