SMB events
The following table lists the events that are created for the SMB component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| ctdb_down | STATE_CHANGE FAILED |
ERROR | FTDC upload | Message: The CTDB process is not running. |
| Description: The CTDB process is not running. | ||||
| Cause: N/A | ||||
| User Action: Perform the troubleshooting. | ||||
| ctdb_recovered | STATE_CHANGE HEALTHY |
INFO | no | Message: The CTDB recovery is finished. |
| Description: CTDB completed the database recovery. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ctdb_recovery | STATE_CHANGE DEGRADED |
WARNING | no | Message: The CTDB recovery is detected. |
| Description: CTDB is performing a database recovery. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ctdb_state_down | STATE_CHANGE FAILED |
ERROR | FTDC upload | Message: The CTDB state is {0}. |
| Description: The CTDB state is unhealthy. | ||||
| Cause: N/A | ||||
| User Action: Perform the troubleshooting. | ||||
| ctdb_state_up | STATE_CHANGE HEALTHY |
INFO | no | Message: The CTDB state is healthy. |
| Description: The CTDB state is healthy. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ctdb_up | STATE_CHANGE HEALTHY |
INFO | no | Message: The CTDB process is now running. |
| Description: The CTDB process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ctdb_version_match | STATE_CHANGE_EXTERNAL HEALTHY |
INFO | no | Message: CTDB passed the version check. |
| Description: The CTDB service successfully passed the version check. | ||||
| Cause: The CTDB service successfully passed the version check on a node and can join the running cluster. The node is given. | ||||
| User Action: N/A | ||||
| ctdb_version_mismatch | STATE_CHANGE_EXTERNAL FAILED |
ERROR | FTDC upload | Message: Cannot start CTDB version {0} as {1} is already running in the cluster. |
| Description: CTDB cannot start on a node as it detected that on other CES nodes a CTDB cluster is running at a different version. This prevents the SMB service to get healthy. | ||||
| Cause: CTDB cannot start on a node as it detected a conflicting version that is running in the cluster. The name of the failing node, the starting CTDB version, and the conflicting version that is running in the cluster are provided. | ||||
| User Action: Get all gpfs-smb packages to the same version. | ||||
| ctdb_warn | INFO | WARNING | no | Message: The CTDB monitoring returned an unknown result. |
| Description: The CTDB check returned an unknown result. | ||||
| Cause: N/A | ||||
| User Action: Perform the troubleshooting. | ||||
| smb_exported_fs_chk | STATE_CHANGE_EXTERNAL HEALTHY |
INFO | no | Message: The Cluster State Manager (CSM) cleared the
smb_exported_fs_down event. |
| Description: Declared SMB exported file systems are either available again on this node or not available on any node. | ||||
Cause: The CSM cleared an smb_exported_fs_down event on this node to
display the self-detected state of this node. |
||||
| User Action: N/A | ||||
| smb_exported_fs_down | STATE_CHANGE_EXTERNAL FAILED |
ERROR | no | Message: One or more declared SMB exported file systems are not available on this node. |
| Description: One or more declared SMB exported file systems are not available on this node. Other nodes might have those file systems available. | ||||
| Cause: One or more declared SMB exported file systems are not available on this node. | ||||
| User Action: Check the SMB export-related local and remote file system states. | ||||
| smb_exports_clear_state | STATE_CHANGE HEALTHY |
INFO | no | Message: Clear local SMB export down state temporarily. |
| Description: Clear local SMB export down state temporarily because a message as 'all nodes have the same problem' was received. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| smb_exports_down | STATE_CHANGE DEGRADED |
WARNING | no | Message: One or more declared file systems for SMB exports are not available. |
| Description: One or more declared file systems for SMB exports are not available. | ||||
| Cause: One or more declared file systems for SMB exports are not available. | ||||
| User Action: Check local and remote file system states. | ||||
| smb_exports_up | STATE_CHANGE HEALTHY |
INFO | no | Message: All declared file systems for SMB exports are available. |
| Description: All declared file systems for SMB exports are available. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| smb_restart | INFO | WARNING | no | Message: The SMB service failed. Trying to recover. |
| Description: Attempt to start the SMBD process. | ||||
| Cause: The SMBD process was not running. | ||||
| User Action: N/A | ||||
| smb_sensors_active | TIP | INFO | no | Message: The SMB perfmon sensor {0} is active. |
| Description: The SMB perfmon sensors are active. This event's monitor is running only once an hour. | ||||
| Cause: The SMB perfmon sensors' period attribute is greater than 0. | ||||
| User Action: N/A | ||||
| smb_sensors_inactive | TIP | TIP | no | Message: The following SMB perfmon sensor {0} is inactive. |
| Description: The SMB perfmon sensors are inactive. This event's monitor is running only once an hour. | ||||
| Cause: The SMB perfmon sensors' period attribute is 0. | ||||
| User Action: Set the period attribute of the SMB sensors greater than 0. Run the mmperfmon config update SensorName.period=N command, where 'SensorName' is one of the SMB sensors' name and 'N' is a natural number, that is greater than 0. Consider that this TIP monitor is running only once per hour and might take up to 1 hour to detect the changes in the configuration. | ||||
| smb_sensors_not_configured | TIP | TIP | no | Message: The SMB perfmon sensor {0} is not configured. |
| Description: The SMB perfmon sensor does not exist in the mmperfmon config show command. | ||||
| Cause: The SMB perfmon sensor is not configured in the sensors configuration file. | ||||
| User Action: Include the sensors into the perfmon configuration by using the mmperfmon config add --sensors /opt/IBM/zimon/defaults/ZIMonSensors_smb.cfg command. For more information on the configuration file, see the mmperfmon command section in the Command Reference Guide. | ||||
| smbd_down | STATE_CHANGE FAILED |
ERROR | FTDC upload | Message: SMBD process is not running. |
| Description: The SMBD process is not running. | ||||
| Cause: N/A | ||||
| User Action: Perform the troubleshooting. | ||||
| smbd_up | STATE_CHANGE HEALTHY |
INFO | no | Message: SMBD process is now running. |
| Description: The SMBD process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| smbd_warn | INFO | WARNING | no | Message: The SMBD process monitoring returned an unknown result. |
| Description: The SMBD process monitoring returned an unknown result. | ||||
| Cause: N/A | ||||
| User Action: Perform troubleshooting. | ||||
| smbport_down | STATE_CHANGE FAILED |
ERROR | no | Message: SMB port {0} is not active. |
| Description: SMBD is not listening on a TCP protocol port. | ||||
| Cause: N/A | ||||
| User Action: Perform troubleshooting. | ||||
| smbport_up | STATE_CHANGE HEALTHY |
INFO | no | Message: SMB port {0} is now active. |
| Description: An SMB port was activated. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| smbport_warn | INFO | WARNING | no | Message: The SMB port monitoring {0} returned an unknown result. |
| Description: An internal error occurred while monitoring the SMB TCP protocol ports. | ||||
| Cause: N/A | ||||
| User Action: Perform troubleshooting. | ||||
| start_smb_service | INFO | INFO | no | Message: SMB service was started. |
| Description: Information about an SMB service start. | ||||
| Cause: The SMB service was started by using the mmces service start smb command. | ||||
| User Action: N/A | ||||
| stop_smb_service | INFO | INFO | no | Message: SMB service was stopped. |
| Description: Information about an SMB service stop. | ||||
| Cause: The SMB service was stopped by using the mmces service stop smb command. | ||||
| User Action: N/A |