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:

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 $(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.