Object events
The following table lists the events that are created for the Object component.
Important:
- CES Swift Object protocol feature is not supported from IBM Storage Scale 5.2.0 onwards.
- IBM Storage Scale 5.1.8 is the last release that has CES Swift Object protocol.
- IBM Storage Scale 5.2.0 will tolerate the update of a CES
node from IBM Storage Scale 5.1.8.
- Tolerate means:
- The CES node will be updated to 5.2.0.
- Swift Object support will not be updated as part of the 5.2.0 update.
- You may continue to use the version of Swift Object protocol that was provided in IBM Storage Scale 5.1.8 on the CES 5.2.0 node.
- IBM will provide usage and known defect support for the version of Swift Object that was provided in IBM Storage Scale 5.1.8 until you migrate to a supported object solution that IBM Storage Scale provides.
- Tolerate means:
- Please contact IBM for further details and migration planning.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| account-auditor_failed | STATE_CHANGE | ERROR | no | Message: The account-auditor process should be {0}, but is {1}. |
| Description: The account-auditor process is not running. | ||||
| Cause: The account-auditor process is not running. | ||||
| User Action: Check the status of openstack-swift-account-auditor process. | ||||
| account-auditor_ok | STATE_CHANGE | INFO | no | Message: The state of the account-auditor process, as expected, is {0}. |
| Description: The account-auditor process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| account-auditor_warn | INFO | WARNING | no | Message: The account-auditor process monitoring returned an unknown result. |
| Description: The account-auditor check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-account-auditor returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| account-reaper_failed | STATE_CHANGE | ERROR | no | Message: The account-reaper process should be {0}, but is {1}. |
| Description: The account-reaper process is not running. | ||||
| Cause: The account-reaper process is not running. | ||||
| User Action: Check the status of openstack-swift-account-reaper process. | ||||
| account-reaper_ok | STATE_CHANGE | INFO | no | Message: The state of account-reaper process, as expected, is {0}. |
| Description: The account-reaper process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| account-reaper_warn | INFO | WARNING | no | Message: The account-reaper process monitoring returned an unknown result. |
| Description: The account-reaper check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-account-reaper returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| account-replicator_failed | STATE_CHANGE | ERROR | no | Message: The account-replicator process should be {0}, but is {1}. |
| Description: The account-replicator process is not running. | ||||
| Cause: The account-replicator process is not running. | ||||
| User Action: Check the status of openstack-swift-account-replicator process. | ||||
| account-replicator_ok | STATE_CHANGE | INFO | no | Message: The state of account-replicator process, as expected, is {0}. |
| Description: The account-replicator process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| account-replicator_warn | INFO | WARNING | no | Message: The account-replicator process monitoring returned an unknown result. |
| Description: The account-replicator check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-account-replicator returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| account-server_failed | STATE_CHANGE | ERROR | no | Message: The account process should be {0}, but is {1}. |
| Description: The account-server process is not running. | ||||
| Cause: The account-server process is not running. | ||||
| User Action: Check the status of openstack-swift-account process. | ||||
| account-server_ok | STATE_CHANGE | INFO | no | Message: The state of account process, as expected, is {0}. |
| Description: The account-server process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| account-server_warn | INFO | WARNING | no | Message: The account process monitoring returned an unknown result. |
| Description: The account-server check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-account returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| account_access_down | STATE_CHANGE | ERROR | no | Message: No access to account service ip {0} and port {1}. Check the firewall. |
| Description: The access check of the account service port failed. | ||||
| Cause: The port is probably blocked by a firewall rule. | ||||
| User Action: Check whether the account service is running and the firewall rules. | ||||
| account_access_up | STATE_CHANGE | INFO | no | Message: Access to account service ip {0} and port {1} is OK. |
| Description: The access check of the account service port was successful. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| account_access_warn | INFO | WARNING | no | Message: Account service access check ip {0} and port {1} failed. Check for validity. |
| Description: The access check of the account service port returned an unknown result. | ||||
| Cause: The account service port access cannot be determined due to a problem. | ||||
| User Action: Find potential issues for this kind of failure in the logs. | ||||
| container-auditor_failed | STATE_CHANGE | ERROR | no | Message: The container-auditor process should be {0}, but is {1}. |
| Description: The container-auditor process is not running. | ||||
| Cause: The container-auditor process is not running. | ||||
| User Action: Check the status of openstack-swift-container-auditor process. | ||||
| container-auditor_ok | STATE_CHANGE | INFO | no | Message: The state of container-auditor process, as expected, is {0}. |
| Description: The container-auditor process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| container-auditor_warn | INFO | WARNING | no | Message: The container-auditor process monitoring returned an unknown result. |
| Description: The container-auditor check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-container-auditor returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| container-replicator_failed | STATE_CHANGE | ERROR | no | Message: The container-replicator process should be {0}, but is {1}. |
| Description: The container-replicator process is not running. | ||||
| Cause: The container-replicator process is not running. | ||||
| User Action: Check the status of openstack-swift-container-replicator process. | ||||
| container-replicator_ok | STATE_CHANGE | INFO | no | Message: The state of container-replicator process, as expected, is {0}. |
| Description: The container-replicator process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| container-replicator_warn | INFO | WARNING | no | Message: The container-replicator process monitoring returned an unknown result. |
| Description: The container-replicator check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-container-replicator returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| container-server_failed | STATE_CHANGE | ERROR | no | Message: The container process should be {0}, but is {1}. |
| Description: The container-server process is not running. | ||||
| Cause: The container-server process is not running. | ||||
| User Action: Check the status of openstack-swift-container process. | ||||
| container-server_ok | STATE_CHANGE | INFO | no | Message: The state of container process, as expected, is {0}. |
| Description: The container-server process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| container-server_warn | INFO | WARNING | no | Message: The container process monitoring returned an unknown result. |
| Description: The container-server check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-container returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| container-updater_failed | STATE_CHANGE | ERROR | no | Message: The container-updater process should be {0}, but is {1}. |
| Description: The container-updater process is not running. | ||||
| Cause: The container-updater process is not running. | ||||
| User Action: Check the status of openstack-swift-container-updater process. | ||||
| container-updater_ok | STATE_CHANGE | INFO | no | Message: The state of container-updater process, as expected, is {0}. |
| Description: The container-updater process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| container-updater_warn | INFO | WARNING | no | Message: The container-updater process monitoring returned an unknown result. |
| Description: The container-updater check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-container-updater returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| container_access_down | STATE_CHANGE | ERROR | no | Message: No access to container service ip {0} and port {1}. Check the firewall. |
| Description: The access check to the container service port failed. | ||||
| Cause: The port is probably blocked by a firewall rule. | ||||
| User Action: Check whether the file system daemon is running and the firewall rules. | ||||
| container_access_up | STATE_CHANGE | INFO | no | Message: Access to container service ip {0} and port {1} is OK. |
| Description: The access check to the container service port was successful. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| container_access_warn | INFO | WARNING | no | Message: Container service access check ip {0} and port {1} failed. Check for validity. |
| Description: The access check to the container service port returned an unknown result. | ||||
| Cause: The container service port access cannot be determined due to a problem. | ||||
| User Action: Find potential issues for this kind of failure in the logs. | ||||
| disable_Address_database_node | INFO_EXTERNAL | INFO | no | Message: Disable the Address Database node. |
| Description: Event to signal that the database flag was removed from this node. | ||||
| Cause: A CES IP with a singleton or database flag, which is linked to it, was either removed from or moved to this node. | ||||
| User Action: N/A | ||||
| disable_Address_singleton_node | INFO_EXTERNAL | INFO | no | Message: Disable the Address Singleton node. |
| Description: Event to signal that the singleton flag was removed from this node. | ||||
| Cause: A CES IP with a singleton or database flag, which is linked to it, was either removed from or moved to this node. | ||||
| User Action: N/A | ||||
| enable_Address_database_node | INFO_EXTERNAL | INFO | no | Message: Enable the Address Database node. |
| Description: Event to signal that the database flag was moved to this node. | ||||
| Cause: A CES IP with a singleton or database flag, which is linked to it, was either removed from or moved to this node. | ||||
| User Action: N/A | ||||
| enable_Address_singleton_node | INFO_EXTERNAL | INFO | no | Message: Enable the Address Singleton node. |
| Description: Event to signal that the singleton flag was moved to this node. | ||||
| Cause: A CES IP with a singleton or database flag, which is linked to it, was either removed from or moved to this node. | ||||
| User Action: N/A | ||||
| ibmobjectizer_failed | STATE_CHANGE | ERROR | no | Message: The ibmobjectizer process should be {0}, but is {1}. |
| Description: The ibmobjectizer process is in the expected state. | ||||
| Cause: The ibmobjectizer process is expected to be running only on the singleton node. | ||||
| User Action: Check the status of ibmobjectizer process and object singleton flag. | ||||
| ibmobjectizer_ok | STATE_CHANGE | INFO | no | Message: The state of ibmobjectizer process, as expected, is {0}. |
| Description: The ibmobjectizer process is not in the expected to be running only on the singleton node.. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ibmobjectizer_warn | INFO | WARNING | no | Message: The ibmobjectizer process monitoring returned an unknown result. |
| Description: The ibmobjectizer check returned an unknown result. | ||||
| Cause: A status query for ibmobjectizer returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| memcached_failed | STATE_CHANGE | ERROR | no | Message: The memcached process should be {0}, but is {1}. |
| Description: The memcached process is not running. | ||||
| Cause: The memcached process is not running. | ||||
| User Action: Check the status of memcached process. | ||||
| memcached_ok | STATE_CHANGE | INFO | no | Message: The state of memcached process, as expected, is {0}. |
| Description: The memcached process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| memcached_warn | INFO | WARNING | no | Message: The memcached process monitoring returned an unknown result. |
| Description: The memcached check returned an unknown result. | ||||
| Cause: A status query for memcached returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| obj_restart | INFO | WARNING | no | Message: The {0} service failed. Trying to recover. |
| Description: An object service was not in the expected state. | ||||
| Cause: An object service might have stopped unexpectedly. | ||||
| User Action: N/A | ||||
| object-expirer_failed | STATE_CHANGE | ERROR | no | Message: The object-expirer process should be {0}, but is {1}. |
| Description: The object-expirer process is not in the expected state. | ||||
| Cause: The object-expirer process is expected to be running only on the singleton node. | ||||
| User Action: Check the status of openstack-swift-object-expirer process and object singleton flag. | ||||
| object-expirer_ok | STATE_CHANGE | INFO | no | Message: The state of object-expirer process, as expected, is {0}. |
| Description: The object-expirer process is in the expected state. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| object-expirer_warn | INFO | WARNING | no | Message: The object-expirer process monitoring returned an unknown result. |
| Description: The object-expirer check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-object-expirer returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| object-replicator_failed | STATE_CHANGE | ERROR | no | Message: The object-replicator process should be {0}, but is {1}. |
| Description: The object-replicator process is not running. | ||||
| Cause: The object-replicator process is not running. | ||||
| User Action: Check the status of openstack-swift-object-replicator process. | ||||
| object-replicator_ok | STATE_CHANGE | INFO | no | Message: The state of object-replicator process, as expected, is {0}. |
| Description: The object-replicator process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| object-replicator_warn | INFO | WARNING | no | Message: The object-replicator process monitoring returned an unknown result. |
| Description: The object-replicator check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-object-replicator returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| object-server_failed | STATE_CHANGE | ERROR | no | Message: The object process should be {0}, but is {1}. |
| Description: The object-server process is not running. | ||||
| Cause: The object-server process is not running. | ||||
| User Action: Check the status of openstack-swift-object process. | ||||
| object-server_ok | STATE_CHANGE | INFO | no | Message: The state of object process, as expected, is {0}. |
| Description: The object-server process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| object-server_warn | INFO | WARNING | no | Message: The object process monitoring returned an unknown result. |
| Description: The object-server check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-object-server returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| object-updater_failed | STATE_CHANGE | ERROR | no | Message: The object-updater process should be {0}, but is {1}. |
| Description: The object-updater process is not in the expected state. | ||||
| Cause: The object-updater process is expected to be running only on the singleton node. | ||||
| User Action: Check the status of openstack-swift-object-updater process and object singleton flag. | ||||
| object-updater_ok | STATE_CHANGE | INFO | no | Message: The state of object-updater process, as expected, is {0}. |
| Description: The object-updater process is expected to be running only on the singleton node. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| object-updater_warn | INFO | WARNING | no | Message: The object-updater process monitoring returned an unknown result. |
| Description: The object-updater check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-object-updater returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| object_access_down | STATE_CHANGE | ERROR | no | Message: No access to object store ip {0} and port {1}. Check the firewall. |
| Description: The access check to the object service port failed. | ||||
| Cause: The port is probably blocked by a firewall rule. | ||||
| User Action: Check whether the object service is running and the firewall rules. | ||||
| object_access_up | STATE_CHANGE | INFO | no | Message: Access to object store ip {0} and port {1} is OK. |
| Description: The access check to the object service port was successful. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| object_access_warn | INFO | WARNING | no | Message: Object store access check ip {0} and port {1} failed. |
| Description: The access check to the object service port returned an unknown result. | ||||
| Cause: The object service port access cannot be determined due to a problem. | ||||
| User Action: Find potential issues for this kind of failure in the logs. | ||||
| object_quarantined | INFO_EXTERNAL | WARNING | no | Message: The object "{0}", container "{1}", account "{2}" is quarantined. Path of quarantined object: "{3}". |
| Description: The object, which was being accessed, is quarantined. | ||||
| Cause: Mismatch in data and metadata is found. | ||||
| User Action: N/A | ||||
| object_sof_access_down | STATE_CHANGE | ERROR | no | Message: No access to unified object store ip {0} and port {1}. Check the firewall. |
| Description: The access check to the unified object service port failed. | ||||
| Cause: The port is probably blocked by a firewall rule. | ||||
| User Action: Check whether the unified object service is running and the firewall rules. | ||||
| object_sof_access_up | STATE_CHANGE | INFO | no | Message: Access to unified object store ip {0} and port {1} is OK. |
| Description: The access check to the unified object service port was successful. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| object_sof_access_warn | INFO | WARNING | no | Message: Unified object store access check ip {0} and port {1} failed. Check for validity. |
| Description: The access check to the object unified access service port returned an unknown result. | ||||
| Cause: The unified object service port access cannot be determined due to a problem. | ||||
| User Action: Find potential issues for this kind of failure in the logs. | ||||
| openstack-object-sof_failed | STATE_CHANGE | ERROR | no | Message: The object-sof process should be {0}, but is {1}. |
| Description: The swift-on-file process is not in the expected state. | ||||
| Cause: If the swift-on-file process is expected to be running, then the capability is enabled, and stopped when disabled. | ||||
| User Action: Check the status of openstack-swift-object-sof process and capabilities flag in spectrum-scale-object.conf. | ||||
| openstack-object-sof_ok | STATE_CHANGE | INFO | no | Message: The state of object-sof process, as expected, is {0}. |
| Description: The swift-on-file process is in the expected state. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| openstack-object-sof_warn | INFO | INFO | no | Message: The object-sof process monitoring returned an unknown result. |
| Description: The openstack-swift-object-sof check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-object-sof returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| openstack-swift-object-auditor_failed | STATE_CHANGE | ERROR | no | Message: The object-auditor process should be {0}, but is {1}. |
| Description: The object-auditor process is not in the expected state. | ||||
| Cause: The openstack-swift-object-auditor process is expected to be running only on the singleton node and when the capability multi-region is enabled. It needs to be stopped in other cases. | ||||
| User Action: Check the status of openstack-swift-object-auditor process and capabilities flag in spectrum-scale-object.conf. | ||||
| openstack-swift-object-auditor_ok | STATE_CHANGE | INFO | no | Message: The state of object-auditor process, as expected, is {0}. |
| Description: The object-auditor process is in the expected state. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| openstack-swift-object-auditor_warn | INFO | INFO | no | Message: The object-auditor process monitoring returned an unknown result. |
| Description: The openstack-swift-object-auditor check returned an unknown result. | ||||
| Cause: A status query for openstack-swift-object-auditor returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| postIpChange_info_o | INFO_EXTERNAL | INFO | no | Message: IP addresses are modified {0}. |
| Description: CES IP addresses are moved and activated. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| proxy-httpd-server_failed | STATE_CHANGE | ERROR | no | Message: The proxy process should be {0}, but is {1}. |
| Description: The proxy-server process is not running. | ||||
| Cause: The proxy-server process is not running. | ||||
| User Action: Check the status of openstack-swift-proxy process. | ||||
| proxy-httpd-server_ok | STATE_CHANGE | INFO | no | Message: The state of proxy process, as expected, is {0}. |
| Description: The proxy-server process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| proxy-httpd-server_warn | INFO | WARNING | no | Message: The proxy process monitoring returned an unknown result. |
| Description: The monitoring process returned an unknown result. | ||||
| Cause: A status query for HTTPd, which runs the proxy server, returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| proxy-server_failed | STATE_CHANGE | ERROR | FTDC upload | Message: The proxy process should be {0}, but is {1}. |
| Description: The proxy-server process is not running. | ||||
| Cause: The proxy-server process is not running. | ||||
| User Action: Check the status of openstack-swift-proxy process. | ||||
| proxy-server_ok | STATE_CHANGE | INFO | no | Message: The state of proxy process, as expected, is {0}. |
| Description: The proxy-server process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| proxy-server_warn | INFO | WARNING | no | Message: The proxy process monitoring returned an unknown result. |
| Description: The proxy-server process monitoring returned an unknown result. | ||||
| Cause: A status query for openstack-swift-proxy-server returned an unexpected error. | ||||
| User Action: Check the service script and settings. | ||||
| proxy_access_down | STATE_CHANGE | ERROR | no | Message: No access to proxy service ip {0} and port {1}. Check the firewall. |
| Description: The access check to the proxy service port failed. | ||||
| Cause: The port is probably blocked by a firewall rule. | ||||
| User Action: Check whether the proxy service is running and the firewall rules. | ||||
| proxy_access_up | STATE_CHANGE | INFO | no | Message: Access to proxy service ip {0}, port {1} is OK. |
| Description: The access check of the proxy service port was successful. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| proxy_access_warn | INFO | WARNING | no | Message: Proxy service access check ip {0} and port {1} failed. Check for validity. |
| Description: The access check of the proxy service port returned an unknown result. | ||||
| Cause: The proxy service port access cannot be determined due to a problem. | ||||
| User Action: Find potential issues for this kind of failure in the logs. | ||||
| ring_checksum_failed | STATE_CHANGE | ERROR | FTDC upload | Message: Checksum of ring file {0} does not match the one in CCR. |
| Description: Files for object rings were modified unexpectedly. | ||||
| Cause: Checksum of ring file did not match the stored value. | ||||
| User Action: Check the ring files. | ||||
| ring_checksum_ok | STATE_CHANGE | INFO | no | Message: Checksum of ring file {0} is OK. |
| Description: Files for object rings were checked successfully. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ring_checksum_warn | INFO | WARNING | no | Message: Issue while checking checksum of ring file is {0}. |
| Description: Checksum generation process failed. | ||||
| Cause: The ring_checksum check returned an unknown result. | ||||
| User Action: Check whether the ring files and md5sum are executable. | ||||
| start_obj_service | INFO_EXTERNAL | INFO | no | Message: OBJ service was started. |
| Description: Information about an OBJ service start. | ||||
| Cause: The OBJECT service was started by using the mmces service start obj command. | ||||
| User Action: N/A | ||||
| stop_obj_service | INFO_EXTERNAL | INFO | no | Message: OBJ service was stopped. |
| Description: Information about an OBJ service stop. | ||||
| Cause: The OBJECT service was stopped by using the mmces service stop obj command. | ||||
| User Action: N/A |