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.