Sun Cluster 3.1 Data Services 10/03 Release Notes

Previous: Sun Cluster 3.1 Data Services 10/03 Release Notes

Appendix A New Error Messages

This appendix lists error message explanations not included in the Sun Cluster 3.1 10/03 Error Messages Guide. These error messages might be seen on the console or in syslog(3) files while running Sun Cluster software. For most error messages, there is an explanation and a suggested solution. Each message includes the following information:

Message ID

The message ID is an internally-generated ID that uniquely identifies the message.
Description

The description is an expanded explanation of the error that was encountered including any background information that might aid you in determining what caused the error.
Solution

The solution is the suggested action or steps that you should take to recover from any problems caused by the error.

This appendix contains the following sections.

Message IDs 100000–199999

101122 Validate - Couldn't retrieve MySQL version number

Description:

Internal error when retrieving MySQL version.

Solution:

Make sure that supported MySQL version is being used.

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

Description:

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

Solution:

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

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

Description:

The hostname $Hostname is not in the etc hosts file

Solution:

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

119069 Waiting for WebSphere MQ Broker Queue Manager

Description:

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

Solution:

None.

121872 Validate - Samba bin directory %s does not exist

Description:

The Samba bin directory does not exist.

Solution:

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

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

Description:

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

Solution:

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

126077 All WebSphere MQ UserNameServer processes stopped

Description:

All WebSphere MQ UserNameServer processes have been successfully stopped.

Solution:

None.

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

Description:

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

Solution:

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

139415 could not kill swa_rpcd

Description:

swa_rpcd could not be stopped

Solution:

Verify configuration.

149124 ERROR: probe_mysql Option -F not set

Description:

The -F option is missing for probe_mysql command.

Solution:

Add the -F option for probe_mysql command.

156966 Validate - smbconf %s does not exist

Description:

The smb.conf file does not exist.

Solution:

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

171565 WebSphere MQ Broker Queue Manager not available

Description:

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

Solution:

None, the fault monitor detects that the WebSphere MQ Broker Queue Manager is not available and will stop the WebSphere MQ Broker. After the WebSphere MQ Broker Queue Manager is available again, the fault monitor will restart the WebSphere MQ Broker.

176861 check_broker - sc3inq %s CURDEPTH(%s)

Description:

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

Solution:

None, the fault monitor displays the current queue depth until it successfully checks that the simple message flow has worked.

187120 MQSeriesIntegrator2%s exists without an IPC semaphore entry

Description:

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

Solution:

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

Message IDs 200000–299999

207873 Validate - User ID root is not a member of group mqbrkrs

Description:

The WebSphere Broker resource requires that root mqbrkrs is a member of group mqbrkrs.

Solution:

Ensure that root is a member of group mqbrkrs.

211869 validate: Basepath is not set but it is required

Description:

The parameter Basepath is not set in the parameter file

Solution:

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

220824 stop SAA failed rc<>

Description:

Failed to stop SAA.

Solution:

Verify if SAA has not been stopped manually outside the cluster.

230326 start_uns - Waiting for WebSphere MQ UserNameServer Queue Manager

Description:

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

Solution:

None.

251620 Validate - RUN_MODE has to be server

Description:

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

Solution:

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

252585 ERROR: stop_mysql Option -U not set

Description:

The -U option is missing for stop_mysql command.

Solution:

Add the -U option for stop_mysql command.

261236 Validate - my.cnf %s does not exist

Description:

The my.cnf configuration doesn't exist in the defined database directory.

Solution:

Make sure that my.cnf is placed in the defined database directory.

262281 Validate - User %s does not exist

Description:

The WebSphere Broker userid does not exist.

Solution:

Ensure the correct WebSphere Broker userid has been setup and was correctly entered when registering the WebSphere Broker resource.

266602 ERROR: stop_mysql Option -G not set

Description:

The -G option is missing for stop_mysql command.

Solution:

Add the -G option for stop_mysql command.

267361 check_cmg - Database connect to %s failed

Description:

While probing the Oracle E-Business Suite concurrent manager, a test to connect to the database failed.

Solution:

None, if two successive failures occur the concurrent manager resource will be restarted.

270645 Resource Group %s will be restarted

Description:

The WebSphere Broker resource has determined that the WebSphere MQ Broker RDBMS has either failed or has been restarted.

Solution:

None, as the Resource Group will be restarted.

274229 validate_options: $COMMANDNAME Option -N not set

Description:

The option -N of the Apache Tomcat agent command $COMMANDNAME is not set, $COMMANDNAME is either start_sctomcat, stop_sctomcat or probe_sctomcat.

Solution:

Look at previous error messages in the syslog.

280505 Validate - Application user <%s> does not exist

Description:

The Oracle E-Business Suite applications userid was not found in /etc/passwd.

Solution:

Ensure that a local applications userid is defined on all nodes within the cluster.

291362 Validate - nmbd %s non-existent executable

Description:

The Samba executable nmbd either doesn't exist or is not executable.

Solution:

Check the correct pathname for the Samba (s)bin directory was entered when registering the resource and that the program exists and is executable.

291522 Validate - smbd %s non-existent executable

Description:

The Samba executable smbd either doesn't exist or is not executable.

Solution:

Check the correct pathname for the Samba (s)bin directory was entered when registering the resource and that the program exists and is executable.

297493 Validate - Applications directory %s does not exist

Description:

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

Solution:

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

298625 check_winbind - User <%s> can't be retrieved by the nameservice

Description:

The Windows NT userid used by winbind could not be retrieved through the name service.

Solution:

Check that the correct userid was entered when registering the Winbind resource and that the userid exists within the Windows NT domain.

298744 validate: $Variable is not set in the parameterfile $Filename but it is required

Description:

The variable $Variable is not set in the parameter file $Filename.

Solution:

Set the variable in the file $Filename to a valid contents.

Message IDs 300000–399999

300278 Validate - CON_LIMIT=%s is incorrect, default CON_LIMIT=70 is being used

Description:

The value specified for CON_LIMIT is invalid.

Solution:

Either accept the default value of CON_LIMIT=70 or change the value of CON_LIMIT to be less than or equal to 100 when registering the resource.

300598 Validate - Winbind configuration directory %s does not exist

Description:

The Winbind configuration directory does not exist.

Solution:

Check that the correct Winbind configuration directory was entered when registering the Winbind resource and that the directory exists.

300956 stopped SAA rc<>

Description:

SAA stopped with result code <

Solution:

None ... normal message when SAA gets stopped.

303009 validate: EnvScript $Filename does not exist but it is required

Description:

The environment script $Filename is set in the parameter file but does not exist.

Solution:

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

306944 Validate - Only SUNWfiles or SUNWbinfiles are supported

Description:

The DHCP resource requires that that the /etc/inet/dhcpsvc.conf file has RESOURCE=SUNWfiles or SUNWbinfiles.

Solution:

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

310640 runmqtrm - %s

Description:

The following output was generated from the runmqtrm command.

Solution:

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

311639 check_dhcp - Active interface has changed from %s to %s

Description:

The DHCP resource's fault monitor has detected that the active interface has changed.

Solution:

None, the fault monitor will restart the DHCP server.

316019 WebSphere MQ Channel Initiator %s started

Description:

The WebSphere MQ Channel Initiator has been started.

Solution:

None.

319873 ERROR: stop_mysql Option -R not set

Description:

The -R option is missing for stop_mysql command.

Solution:

Add the -R option for stop_mysql command.

327437 runmqchi - %s

Description:

The following output was generated from the runmqchi command.

Solution:

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

333890 ERROR: stop_mysql Option -D not set

Description:

The -D option is missing for stop_mysql command.

Solution:

Add the -D option for stop_mysql command.

335316 ERROR: start_mysql Option -H not set

Description:

The -H option is missing for start_mysql command.

Solution:

Add the -H option for start_mysql command.

336128 start_winbind - Could not start winbind

Description:

The Winbind resource could not start winbind.

Solution:

339206 validate: An invalid option entered or

Description:

There is an invalid variable set the parameter file mentioned in option -N to a of the start, stop and probe command or the first character of a

Solution:

Fix the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents

340441 Unexpected - test_rdbms_pid<%s>

Description:

The fault monitor found an unexpected error with testing the RDBMS.

Solution:

341702 could not start swa_rpcd, aborting

Description:

swa_rpcd could not be started.

Solution:

Check configuration of SAA.

357988 set_status - rc<%s> type<%s>

Description:

If the call to scha_resource_setstatus returns an error, the resource's fault probe sets the appropriate return code from scha_resource_setstatus call.

Solution:

Examine the other syslog messages occurring at the same time on the same node, to see if the cause of the problem can be identified

382114 start_dhcp - DHCP batch job failed rc<%s>

Description:

Whenever the DHCP server has switched over to another node, the DHCP network table is updated via a batch job running pntadm commands. This message is produced if the submission of that batch job fails.

Solution:

Please refer to the pntadm(1M) man page.

382661 WebSphere MQ Broker Queue Manager available

Description:

The WebSphere MQ Broker is dependent on the WebSphere MQ Broker Queue Manager. This message simple informs that the WebSphere MQ Broker Queue Manager is available.

Solution:

None.

398643 Validate - nmblookup %s non-existent executable

Description:

The Samba resource tries to validate that the nmblookup program exists and is executable.

Solution:

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

Message IDs 400000–499999

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

Description:

The bit mode value for MODE is invalid.

Solution:

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

404259 ERROR: probe_mysql Option -H not set

Description:

The -H option is missing for probe_mysql command.

Solution:

Add the -H option for probe_mysql command.

404388 Failed to retrieve ip number for host %s

Description:

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

Solution:

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

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

Description:

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

Solution:

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

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

Description:

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

Solution:

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

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

Description:

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

Solution:

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

410272 Validate - ORACLE_HOME directory %s does not exist

Description:

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

Solution:

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

419384 stop dced failed rc<>

Description:

Stop of dce subcomponent failed.

Solution:

Verify configuration.

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

Description:

The parameter ReturnString is not set in the parameter file

Solution:

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

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

Description:

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

Solution:

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

430357 endmqm - %s

Description:

The following output was generated from the endmqm command.

Solution:

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

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

Description:

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

Solution:

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

438199 Validate - Samba configuration directory %s does not exist

Description:

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

Solution:

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

450308 check_broker - Main Queue Manager processes not found

Description:

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

Solution:

None, the WebSphere MQ Broker will be restarted.

454449 ERROR: stop_mysql Option -L not set

Description:

The -L option is missing for stop_mysql command.

Solution:

Add the -L option for stop_mysql command.

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

Description:

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

Solution:

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

459848 WebSphere MQ Broker RDBMS available

Description:

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

Solution:

None.

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

Description:

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

Solution:

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

469892 ERROR: start_mysql Option -B not set

Description:

The -B option is missing for start_mysql command.

Solution:

Add the -B option for start_mysql command.

474576 check_dhcp - The DHCP has died

Description:

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

Solution:

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

476023 Validate - DHCP is not enabled (DAEMON_ENABLED)

Description:

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

Solution:

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

479015 Validate - DHCP directory %s does not exist

Description:

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

Solution:

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

496553 Validate - DHCP config file %s does not exist

Description:

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

Solution:

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

497093 WebSphere MQ Check Broker failed - see reason above

Description:

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

Solution:

Examine the other syslog messages occurring at the same time on the same node, to see if the cause of the problem can be identified

Message IDs 500000–599999

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

Description:

The fault monitor 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.

524300 get_server_ip - pntadm failed rc<%s>

Description:

The DHCP resource gets the server ip from the DHCP network table using the pntadm command, however this command has failed.

Solution:

Please refer to the pntadm(1M) man page.

527700 stop_chi - WebSphere MQ Channel Initiator %s stopped

Description:

The WebSphere MQ Channel Initiator has been stopped.

Solution:

None.

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

Description:

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

Solution:

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

538835 ERROR: probe_mysql Option -B not set

Description:

The -B option is missing for probe_mysql command.

Solution:

Add the -B option for probe_mysql command.

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

Description:

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

Solution:

558184 Validate - MySQL logdirectory for mysqld does not exist

Description:

The defined (-L option) logdirectory doesn't exist.

Solution:

Make sure that the defined logdirectory exists.

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:

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

574421 MQSeriesIntegrator2%s file deleted

Description:

Solution:

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 fault monitor user doesn't have the right permission to flush tables. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges.

589025 ERROR: stop_mysql Option -F not set

Description:

The -F option is missing for stop_mysql command.

Solution:

Add the -F option for stop_mysql command.

589689 get_resource_dependencies - Only one WebSphere MQ Broker RDBMS resource dependency can be set

Description:

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

Solution:

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

592738 Validate - smbclient %s non-existent executable

Description:

The Samba resource tries to validate that the smbclient exists and is executable.

Solution:

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

595448 Validate - mysqld %s non-existent executable

Description:

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

Solution:

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

598483 Waiting for WebSphere MQ Broker RDBMS

Description:

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

Solution:

None.

Message IDs 600000–699999

600398 validate - file $FILENAME does not exist

Description:

The parameter file of option -N of the start, stop or probe command does not exist.

Solution:

Correct the filename and reregister the data service.

600552 validate: User is not set but it is required

Description:

The parameter User is not set in the parameter file

Solution:

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

601312 Validate - Winbind bin directory %s does not exist

Description:

The Winbind resource could not validate that winbind bin directory exists.

Solution:

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

603913 last probe failed, Tomcat considered as unavailable

Description:

The last sanity check was unsuccessful, may be out of sessions

Solution:

None required, it is recommended to observe Tomcats number of configured sessions

604642 Validate - winbind is not defined in %s in the passwd section

Description:

The Winbind resource could not validate that winbind is defined within the password section of /etc/nsswitch.conf.

Solution:

Ensure that winbind is defined within the password section of /etc/nsswitch.conf.

608780 get_resource_dependencies - Resource_dependencies does not have a Queue Manager resource

Description:

The WebSphere Broker is dependent on the WebSphere MQ Broker Queue Manager resource, which is not available. So the WebSphere Broker will terminate.

Solution:

Ensure that the WebSphere MQ Broker Queue Manager resource is defined within resource_dependencies when registering the WebSphere MQ Broker resource.

611103 get_resource_dependencies - Only one WebSphere MQ Broker Queue Manager resource dependency can be set

Description:

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

Solution:

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

616858 WebSphere MQ Broker will be restarted

Description:

The WebSphere MQ Broker fault monitor has detected a condition that requires that the WebSphere MQ Broker is to be restarted.

Solution:

None, the WebSphere MQ Broker will be restarted.

620125 WebSphere MQ Broker bipservice %s failed

Description:

The WebSphere MQ Broker fault monitor has detected that the WebSphere MQ Broker bipservice process has failed.

Solution:

None, the WebSphere MQ Broker will be restarted.

620477 mqsistop - %s

Description:

The following output was generated from the mqsistop command.

Solution:

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

622367 start_dhcp - %s %s failed

Description:

The DHCP resource has tried to start the DHCP server using in.dhcpd, however this has failed.

Solution:

The DHCP server will be restarted. 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.

623488 Validate - winbind is not defined in %s in the group section

Description:

The Winbind resource could not validate that winbind is defined within the group section of /etc/nsswitch.conf.

Solution:

Ensure that winbind is defined within the group section of /etc/nsswitch.conf.

632788 Validate - User root is not a member of group mqbrkrs

Description:

The WebSphere Broker resource requires that root mqbrkrs is a member of group mqbrkrs.

Solution:

Ensure that root is a member of group mqbrkrs.

635839 first probe was unsuccessful, try again in 5 seconds

Description:

The first sanity check was unsuccessful, may be out of sessions

Solution:

None required, it is recommended to observe Tomcats number of configured sessions

643722 ERROR: start_mysql Option -U not set

Description:

The -U option is missing for start_mysql command.

Solution:

Add the -U option for start_mysql command.

644941 Probe failed, HTTP GET Response Code for %s is %d.

Description:

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

Solution:

This message is informational; no user action is needed.

647559 Validate - Couldn't retrieve Samba version number

Description:

The Samba resource tries to validate that an acceptable version of Samba is being deployed, however it was unable to retrieve the Samba version number.

Solution:

Check that Samba has been installed correctly

652173 start_samba - Could not start Samba server %s nmb

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.

657739 ERROR: start_mysql Option -G not set

Description:

The -G option is missing for start_mysql command.

Solution:

Add the -G option for start_mysql command.

667613 start_mysql - myisamchk found errors in some index in %s, perform manual repairs

Description:

mysiamchk found errors in MyISAM based tables.

Solution:

Consult MySQL documentation when repairing MyISAM tables.

668840 Validate - Couldn't retrieve faultmonitor-user <%s> from the nameservice

Description:

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

Solution:

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

672337 runmqlsr - %s

Description:

The following output was generated from the runmqlsr command.

Solution:

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

693424 Waiting for WebSphere MQ UserNameServer Queue Manager

Description:

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

Solution:

None.

693579 stop_mysql - Failed to flush MySql logfiles for %s

Description:

mysqladmin command failed to flush MySQL logfiles.

Solution:

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

Message IDs 700000–799999

700425 WebSphere MQ Broker RDBMS not available

Description:

The WebSphere MQ Broker is dependent on a WebSphere MQ Broker RDBMS, which is currently not available.

Solution:

None, the fault monitor detects that the WebSphere MQ Broker RDBMS is not available and will restart the Resource Group.

708719 check_mysql - mysqld server <%s> not working, failed to connect to MySQL

Description:

The fault monitor can't connect to the specified MySQL instance.

Solution:

This is an error message from MySQL fault monitor, no user action is needed.

711010 ERROR: start_mysql Option -R not set

Description:

The -R option is missing for start_mysql command.

Solution:

Add the -R option for start_mysql command.

712665 ERROR: probe_mysql Option -U not set

Description:

The -U option is missing for probe_mysql command.

Solution:

Add the -U option for probe_mysql command.

717827 error in configuration of SAA

Description:

Could not start SAA because of SAA configuration problems.

Solution:

Correct configuration of SAA, try manual start, and stop, re-enable in cluster.

722025 Function: stop_mysql - Sql-command SLAVE STOP returned error (%s)

Description:

Couldn't stop slave instance.

Solution:

Examine the returned Sql-status message and consult MySQL documentation.

725027 ERROR: start_mysql Option -D not set

Description:

The -D option is missing for start_mysql command.

Solution:

Add the -D option for start_mysql command.

725933 start_samba - Could not start Samba server %s smb daemon

Description:

The Samba resource could not start the Samba server smbd 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.

726682 ERROR: probe_mysql Option -G not set

Description:

The -G option is missing for probe_mysql command.

Solution:

Add the -G option for probe_mysql command.

728840 get_resource_dependencies - Resource_dependencies does not have a RDBMS resource

Description:

The WebSphere MQ Broker is dependent on the WebSphere MQ Broker RDBMS resource, which is not available. So the WebSphere MQ Broker will terminate.

Solution:

Ensure that the WebSphere MQ Broker RDBMS resource is defined within resource_dependencies when registering the WebSphere MQ Broker resource.

731228 validate_options: $COMMANDNAME Option -G not set

Description:

The option -G of the Apache Tomcat agent command $COMMANDNAME is not set, $COMMANDNAME is either start_sctomcat, stop_sctomcat or probe_sctomcat.

Solution:

Look at previous error messages in the syslog.

739997 endmqcsv - %s"

Description:

The following output was generated from the endmqcsv command.

Solution:

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

741561 Unexpected - test_qmgr_pid<%s>

Description:

The WebSphere MQ Broker is dependent on the WebSphere MQ Broker Queue Manager, however an unexpected error was found while checking the WebSphere MQ Broker Queue Manager.

Solution:

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

742807 Ignoring command execution `<command>`

Description:

HA-Oracle reads the file specified in USER_ENV property and exports the variables declared in the file. Syntax for declaring the variables is : VARIABLE=VALUE If a command execution is attempted using `<command>`, the VARIABLE is ignored.

Solution:

Please check the environment file and correct the syntax errors by removing any entry containing a back-quote (`) from it.

747268 strmqcsv - %s

Description:

The following output was generated from the strmqcsv command.

Solution:

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

751205 Validate - WebSphere MQ Broker file systems not defined

Description:

The WebSphere MQ Broker file systems (/opt/mqsi and /var/mqsi) are not defined.

Solution:

Ensure that the WebSphere MQ Broker file systems are defined correctly.

771151 WebSphere MQ Queue Manager available

Description:

The WebSphere MQ Broker is dependent on the WebSphere MQ Broker Queue Manager. This message simple informs that the WebSphere MQ Broker Queue Manager is available.

Solution:

None.

778674 start_mysql - Could not start mysql server for %s

Description:

GDS couldn't start this instance of MySQL.

Solution:

Look at previous error messages.

779953 ERROR: probe_mysql Option -R not set

Description:

The -R option is missing for probe_mysql command.

Solution:

Add the -R option for probe_mysql command.

782497 Ignoring command execution $(command)

Description:

Solution:

Please check the environment file and correct the syntax errors by removing any entry containing a $(command) construct from it.

784499 validate_options: $COMMANDNAME Option -R not set

Description:

The option -R of the Apache Tomcat agent command $COMMANDNAME is not set, $COMMANDNAME is either start_sctomcat, stop_sctomcat or probe_sctomcat.

Solution:

Look at previous error messages in the syslog.

787938 stopped dce rc<>

Description:

Informational message stop of dced.

Solution:

None

789392 Validate - MySQL basedirectory %s does not exist

Description:

The defined basedirectory (-B option) doesn't exist.

Solution:

Make sure that defined basedirectory exists.

792848 ended host rename

Description:

Housekeeping has been performed after a successful failover.

Solution:

None

793970 ERROR: probe_mysql Option -D not set

Description:

The -D option is missing for probe_mysql command.

Solution:

Add the -D option for probe_mysql command.

795360 Validate - User ID %s does not exist

Description:

The WebSphere MQ UserNameServer resource could not validate that the UserNameServer userid exists.

Solution:

Ensure that the UserNameServer userid has been correctly entered when registering the WebSphere MQ UserNameServer resource and that the userid really exists.

796592 Monitor stopped due to setup error or custom action.

Description:

Fault monitor detected an error in the setup or an error specified in the custom action file for which the specified action was to stop the fault monitor. While the fault monitor remains offline, no other errors will be detected or acted upon.

Solution:

Please correct the condition which lead to the error. The information about this error would be logged together with this message.

Message IDs 800000–899999

806128 Ignoring PATH set in environment file %s

Description:

HA-Oracle reads the file specified in USER_ENV property and exports the variables declared in the file. If PATH variable is attempted to be set in the USER_ENV file, it gets ignored.

Solution:

Please check the environment file and remove any PATH variable setting from it.

815147 Validate - Faultmonitor-resource <%s> does not exist

Description:

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

Solution:

Check that the Samba instance's smb.conf file has the fault monitor resource scmondir defined. Please refer to the data service documentation to determine how to do this.

821789 Validate - User %s is not a member of group mqbrkrs

Description:

The WebSphere MQ Broker userid is not a member of the group mqbrkrs.

Solution:

Ensure that the WebSphere MQ Broker userid is a member of the group mqbrkrs.

826556 Validate - Group mqbrkrs does not exist

Description:

The WebSphere MQ Broker resource failed to validate that the group mqbrkrs exists.

Solution:

Ensure that the group mqbrkrs exists.

834841 Validate - myisamchk %s non-existent or non-executable

Description:

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

Solution:

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

835739 validate: Host is not set but it is required

Description:

The parameter Host is not set in the parameter file

Solution:

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

836825 validate: TestCmd is not set but it is required

Description:

The parameter TestCmd is not set in the parameter file

Solution:

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

838688 validate: Startwait is not set but it is required

Description:

The parameter Startwait is not set in the parameter file

Solution:

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

844160 ERROR: stop_mysql Option -H not set

Description:

The -H option is missing for stop_mysql command.

Solution:

Add the -H option for stop_mysql command.

845276 WebSphere MQ Broker Queue Manager has been restarted

Description:

The WebSphere MQ Broker fault monitor has detected that the WebSphere MQ Broker Queue Manager has been restarted.

Solution:

None. The WebSphere MQ Broker will be restarted.

845586 ERROR: start_mysql Option -L not set

Description:

The -L option is missing for start_mysql command.

Solution:

Add the -L option for start_mysql command.

857002 Validate - Secure mode invalid in %s

Description:

The secure mode value for MODE is invalid.

Solution:

Ensure that the secure mode value for MODE equals Y or N when registering the resource.

865963 stop_mysql - Pid is not running, let GDS stop MySQL for %s

Description:

The saved Pid didn't exist in process list.

Solution:

MySQL was already down.

871438 Validate - User ID %s is not a member of group mqbrkrs

Description:

The WebSphere MQ UserNameServer userid is not a member of the group mqbrkrs.

Solution:

Ensure that the WebSphere MQ UserNameServer userid is a member of the group mqbrkrs.

884759 All WebSphere MQ Broker processes stopped

Description:

The WebSphere MQ Broker has been successfully stopped.

Solution:

None.

895418 stop_mysql - Failed to stop MySQL through mysqladmin for %s, send TERM signal to process

Description:

mysqladmin command failed to stop MySQL instance.

Solution:

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

897653 Validate - Samba sbin directory %s does not exist

Description:

The Samba resource could not validate that Samba sbin directory exists.

Solution:

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

898957 Validate - De-activating %s, by removing it

Description:

The DHCP resource validates that /etc/rc3.d/S34dhcp is not active and achieves this by deleting/etc/rc3.d/S34dhcp.

Solution:

None, /etc/rc3.d/S34dhcp will be deleted.

899940 check_mysql - Couldn't drop table %s from database %s (%s)

Description:

The fault monitor can't drop specified table from the test database.

Solution:

Message IDs 900000–999999

900198 validate: Port is not set but it is required

Description:

The parameter Port is not set in the parameter file

Solution:

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

914529 ERROR: probe_mysql Option -L not set

Description:

The -L option is missing for probe_mysql command.

Solution:

Add the -L option for probe_mysql command.

916067 validate: Directory $Directoryname does not exist but it is required

Description:

The directory with the name $Directoryname does not exist

Solution:

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

924002 check_samba - Samba server <%s> not working, failed to connect to samba-resource <%s>

Description:

The Samba resource's fault monitor checks that the Samba server is working by using the smbclient program. However this test failed to connect to the Samba server.

Solution:

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

924059 Validate - MySQL database directory %s does not exist

Description:

The defined database directory (-D option) doesn't exist.

Solution:

Make sure that defined database directory exists.

930535 Ignoring string with misplaced quotes in the entry for %s

Description:

HA-Oracle reads the file specified in USER_ENV property and exports the variables declared in the file. Syntax for declaring the variables is : VARIABLE=VALUE VALUE may be a single-quoted or double-quoted string. The string itself may not contain any quotes.

Solution:

Please check the environment file and correct the syntax errors.

932026 WebSphere MQ Broker RDBMS has been restarted

Description:

The WebSphere MQ Broker fault monitor has detected that the WebSphere MQ Broker RDBMS has been restarted.

Solution:

None. The resource group will be restarted.

935470 validate: EnvScript not set but it is required

Description:

The parameter EnvScript is not set in the parameter file

Solution:

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

939576 WebSphere MQ bipservice UserNameServer failed

Description:

The WebSphere MQ UserNameServer fault monitor has detected that the WebSphere MQ UserNameServer bipservice process has failed.

Solution:

None, the WebSphere MQ UserNameServer will be restarted.

942855 check_mysql - Couldn't do show tables for defined database %s (%s)

Description:

The fault monitor can't issue show tables for the specified database.

Solution:

944096 Validate - This version of MySQL <%s> is not supported with this dataservice

Description:

An unsupported MySQL version is being used.

Solution:

Make sure that supported MySQL version is being used.

947882 WebSphere MQ Queue Manager not available - will try later

Description:

Some WebSphere MQ processes are start dependent on the WebSphere MQ Queue Manger, however the WebSphere MQ Queue Manager is not available.

Solution:

None. The resource will try again and gets restarted.

957505 Validate - WebSphere MQ Broker /var/mqsi/locks is not a symbolic link

Description:

The WebSphere MQ Broker failed to validate that /var/mqsi/locks is a symbolic link.

Solution:

Ensure that /var/mqsi/locks is a symbolic link. Please refer to the data service documentation to determine how to do this.

978736 ERROR: stop_mysql Option -B not set

Description:

The -B option is missing for stop_mysql command.

Solution:

Add the -B option for stop_mysql command.

980162 ERROR: start_mysql Option -F not set

Description:

The -F option is missing for start_mysql command.

Solution:

Add the -F option for start_mysql command.

983530 can not find alliance_init in ~ALL_ADM for instance $INST_NAME

Description:

Configuration error in configuration file.

Solution:

Verify and correct SAA configuration file.

986150 check_mysql - Sql-command %s returned error (%s)

Description:

The fault monitor can't execute the specified SQL command.

Solution:

992415 Validate - Couldn't retrieve MySQL-user <%s> from the nameservice

Description:

Couldn't retrieve the defined user from name service.

Solution:

Make sure that the right user is defined or the user exists. Use getent passwd 'username' to verify that defined user exist.

995331 start_broker - Waiting for WebSphere MQ Broker Queue Manager

Description:

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

Solution:

None.

996303 Validate - winbindd %s non-existent executable

Description:

The Winbind resource failed to validate that the winbindd program exists and is executable.

Solution:

Check that the correct bin directory for the winbindd program was entered when registering the winbind resource. Please refer to the data service documentation to determine how to do this.

Previous: Sun Cluster 3.1 Data Services 10/03 Release Notes