Object events
The following table lists the events that are created for the Object component.
| Event | EventType | Severity | Message | Description | Cause | User Action |
|---|---|---|---|---|---|---|
| account-auditor_failed | STATE_CHANGE | ERROR | The status of the account-auditor process must be {0} but it is {1} now. | The account-auditor process is not in the expected state. | The account-auditor process is expected to be running on the singleton node only. | Check the status of openstack-swift-account-auditor process and object singleton flag. |
| account-auditor_ok | STATE_CHANGE | INFO | The account-auditor process status is {0} as expected. | The account-auditor process is in the expected state. | The account-auditor process is expected to be running on the singleton node only. | N/A |
| account-auditor_warn | INFO | WARNING | The account-auditor process monitoring returned unknown result. | The account-auditor process monitoring service returned an unknown result. | A status query for openstack-swift-account-auditor process returned with an unexpected error. | Check service script and settings. |
| account-reaper_failed | STATE_CHANGE | ERROR | The status of the account-reaper process must be {0} but it is {1} now. | The account-reaper process is not running. | The account-reaper process is not running. | Check the status of openstack-swift- account-reaper process. |
| account-reaper_ok | STATE_CHANGE | INFO | The status of the account-reaper process is {0} as expected. | The account-reaper process is running. | The account-reaper process is running. | N/A |
| account-reaper_warn | INFO | WARNING | The account-reaper process monitoring service returned an unknown result. | The account-reaper process monitoring service returned an unknown result. |
A status query for openstack-swift-account-reaper returned with an unexpected error. | Check service script and settings. |
| account-replicator_failed | STATE_CHANGE | ERROR | The status of the account-replicator process must be {0} but it is {1} now. | The account-replicator process is not running. | The account-replicator process is not running. | Check the status of openstack-swift-account-replicator process. |
| account-replicator_ok | STATE_CHANGE | INFO | The status of the account-replicator process is {0} as expected. | The account-replicator process is running. | The account-replicator process is running. | N/A |
| account-replicator_warn | INFO | WARNING | The account-replicator process monitoring service returned an unknown result. | The account-replicator check returned an unknown result. | A status query for openstack-swift-account-replicator returned with an unexpected error. | Check the service script and settings. |
| account-server_failed | STATE_CHANGE | ERROR | The status of the account-server process must be {0} but it is {1} now. | The account-server process is not running. | The account-server process is not running. | Check the status of openstack-swift-account process. |
| account-server_ok | STATE_CHANGE | INFO | The status of the account process is {0} as expected. | The account-server process is running. | The account-server process is running. | N/A |
| account-server_warn | INFO | WARNING | The account-server process monitoring service returned unknown result. | The account-server check returned unknown result. | A status query for openstack-swift-account returned with an unexpected error. | Check the service script and existing configuration. |
| container-auditor_failed | STATE_CHANGE | ERROR | The status of the container-auditor process must be {0} but it is {1} now. | The container-auditor process is not in the expected state. | The container-auditor process is expected to be running on the singleton node only. | Check the status of openstack-swift-container-auditor process and object singleton flag. |
| container-auditor_ok | STATE_CHANGE | INFO | The status of the container-auditor process is {0} as expected. | The container-auditor process is in the expected state. | The container-auditor process is running on the singleton node only as expected. | N/A |
| container-auditor_warn | INFO | WARNING | The container-auditor process monitoring service returned unknown result. | The container-auditor monitoring service returned an unknown result. |
A status query for openstack-swift-container-auditor returned with an unexpected error. | Check service script and settings. |
| container-replicator_failed | STATE_CHANGE | ERROR | The status of the container-replicator process must be {0} but it is {1} now. | The container-replicator process is not running. | The container-replicator process is not running. | Check the status of openstack-swift-container-replicator process. |
| container-replicator_ok | STATE_CHANGE | INFO | The status of the container-replicator process is {0} as expected. | The container-replicator process is running. | The container-replicator process is running. | N/A |
| container-replicator_warn | INFO | WARNING | The status of the container-replicator process monitoring service returned unknown result. | The container-replicator check returned an unknown result. | A status query for openstack-swift-container-replicator returned with an unexpected error. | Check service script and settings. |
| container-server_failed | STATE_CHANGE | ERROR | The status of the container-server process must be {0} but it is {1} now. | The container-server process is not running. | The container-server process is not running. | Check the status of openstack-swift-container process. |
| container-server_ok | STATE_CHANGE | INFO | The status of the container-server is {0} as expected. | The container-server process is running. | The container-server process is running. | N/A |
| container-server_warn | INFO | WARNING | The container-server process monitoring service returned unknown result. | The container-server check returned an unknown result. | A status query for openstack-swift-container returned with an unexpected error. | Check the service script and settings. |
| container-updater_failed | STATE_CHANGE | ERROR | The status of the container-updater process must be {0} but it is {1} now. | The container-updater process is not in the expected state. | The container-updater process is expected to be running on the singleton node only. | Check the status of openstack-swift-container-updater process and object singleton flag. |
| container-updater_ok | STATE_CHANGE | INFO | The status of the container-updater process is {0} as expected. |
The container-updater process is in the expected state. | The container-updater process is expected to be running on the singleton node only. | N/A |
| container-updater_warn | INFO | WARNING | The container-updater process monitoring service returned unknown result. | The container-updater check returned an unknown result. | A status query for openstack-swift-container-updater returned with an unexpected error. | Check the service script and settings. |
| disable_Address_database _node | INFO | INFO | An address database node is disabled. | Database flag is removed from this node. | A CES IP with a database flag linked to it is either removed from this node or moved to this node. |
N/A |
| disable_Address_singleton _node | INFO | INFO | An address singleton node is disabled. | Singleton flag is removed from this node. | A CES IP with a singleton flag linked to it is either removed from this node or moved from/to this node. | N/A |
| enable_Address_database _node | INFO | INFO | An address database node is enabled. | The database flag is moved to this node. | A CES IP with a database flag linked to it is either removed from this node or moved from/to this node. | N/A |
| enable_Address_singleton _node | INFO | INFO | An address singleton node is enabled. | The singleton flag is moved to this node. |
A CES IP with a singleton flag linked to it is either removed from this node or moved from/to this node. |
N/A |
| ibmobjectizer_failed | STATE_CHANGE | ERROR | The status of the ibmobjectizer process must be {0} but it is {1} now. | The ibmobjectizer process is not in the expected state. | The ibmobjectizer process is expected to be running on the singleton node only. | Check the status of the ibmobjectizer process and object singleton flag. |
| ibmobjectizer_ok | STATE_CHANGE | INFO | The status of the ibmobjectizer process is {0} as expected. | The ibmobjectizer process is in the expected state. | The ibmobjectizer process is expected to be running on the singleton node only. | N/A |
| ibmobjectizer_warn | INFO | WARNING | The ibmobjectizer process monitoring service returned unknown result | The ibmobjectizer check returned an unknown result. | A status query for ibmobjectizer returned with an unexpected error. | Check the service script and settings. |
| memcached_failed | STATE_CHANGE | ERROR | The status of the memcached process must be {0} but it is {1} now. | The memcached process is not running. | The memcached process is not running. | Check the status of memcached process. |
| memcached_ok | STATE_CHANGE | INFO | The status of the memcached process is {0} as expected. | The memcached process is running. | The memcached process is running. | N/A |
| memcached_warn | INFO | WARNING | The memcached process monitoring service returned unknown result. | The memcached check returned an unknown result. | A status query for memcached returned with an unexpected error. | Check the service script and settings. |
| obj_restart | INFO | WARNING | The {0} service is failed. Trying to recover. | An object service was not in the expected state. | An object service might have stopped unexpectedly. | None, recovery is automatic. |
| object-expirer_failed | STATE_CHANGE | ERROR | The status of the object-expirer process must be {0} but it is {1} now. | The object-expirer process is not in the expected state. | The object-expirer process is expected to be running on the singleton node only. | Check the status of openstack-swift-object-expirer process and object singleton flag. |
| object-expirer_ok | STATE_CHANGE | INFO | The status of the object-expirer process is {0} as expected. | The object-expirer process is in the expected state. | The object-expirer process is expected to be running on the singleton node only. | N/A |
| object-expirer_warn | INFO | WARNING | The object-expirer process monitoring service returned unknown result. | The object-expirer check returned an unknown result. | A status query for openstack-swift-object-expirer returned with an unexpected error. | Check the service script and settings. |
| object-replicator_failed | STATE_CHANGE | ERROR | The status of the object-replicator process must be {0} but it is {1} now. | The object-replicator process is not running. | The object-replicator process is not running. | Check the status of openstack-swift-object-replicator process. |
| object-replicator_ok | STATE_CHANGE | INFO | The status of the object-replicator process is {0} as expected. | The object-replicator process is running. | The object-replicator process is running. | N/A |
| object-replicator_warn | INFO | WARNING | The object-replicator process monitoring service returned unknown result. | The object-replicator check returned an unknown result. | A status query for openstack-swift-object-replicator returned with an unexpected error. | Check the service script and settings. |
| object-server_failed | STATE_CHANGE | ERROR | The status of the object-server process must be {0} but it is {1} now. | The object-server process is not running. | The object-server process is not running. | Check the status of the openstack-swift-object process. |
| object-server_ok | STATE_CHANGE | INFO | The status of the object-server process is {0} as expected. | The object-server process is running. | The object-server process is running. | N/A |
| object-server_warn | INFO | WARNING | The object-server process monitoring service returned unknown result. | The object-server check returned an unknown result. | A status query for openstack-swift-object-server returned with an unexpected error. | Check the service script and settings. |
| object-updater_failed | STATE_CHANGE | ERROR | The status of the object-updater process must be {0} but it is {1} now. | The object-updater process is not in the expected state. | The object-updater process is expected to be running on the singleton node only. | Check the status of the openstack-swift-object-updater process and object singleton flag. |
| object-updater_ok | STATE_CHANGE | INFO | The status of the object-updater process is {0} as expected. | The object-updater process is in the expected state. | The object-updater process is expected to be running on the singleton node only. | N/A |
| object-updater_warn | INFO | WARNING | The object-updater process monitoring returned unknown result. | The object-updater check returned an unknown result. | A status query for openstack-swift-object- updater returned with an unexpected error. | Check the service script and settings. |
| openstack-object-sof_failed | STATE_CHANGE | ERROR | The status of the object-sof process must be {0} but is {1}. | The swift-on-file process is not in the expected state. | The swift-on-file process is expected to be running then the capability is enabled and stopped when disabled. | Check the status of the openstack-swift-object-sof process and capabilities flag in spectrum-scale -object.conf. |
| openstack-object-sof_ok | STATE_CHANGE | INFO | The status of the object-sof process is {0} as expected. | The swift-on-file process is in the expected state. | The swift-on-file process is expected to be running then the capability is enabled and stopped when disabled. | N/A |
| openstack-object-sof_warn | INFO | INFO | The object-sof process monitoring returned unknown result. | The openstack-swift-object-sof check returned an unknown result. | A status query for openstack-swift-object-sof returned with an unexpected error. | Check the service script and settings. |
| postIpChange_info_o | INFO | INFO | The following IP addresses are modified: {0} | CES IP addresses have been moved and activated. | N/A | |
| proxy-server_failed | STATE_CHANGE | ERROR | The status of the proxy process must be {0} but it is {1} now. | The proxy-server process is not running. | The proxy-server process is not running. | Check the status of the openstack-swift-proxy process. |
| proxy-server_ok | STATE_CHANGE | INFO | The status of the proxy process is {0} as expected. | The proxy-server process is running. | The proxy-server process is running. | N/A |
| proxy-server_warn | INFO | WARNING | The proxy-server process monitoring returned unknown result. | The proxy-server process monitoring returned an unknown result. | A status query for openstack-swift-proxy-server returned with an unexpected error. | Check the service script and settings. |
| ring_checksum_failed | STATE_CHANGE | ERROR | Checksum of the ring file {0} does not match the one in CCR. | Files for object rings have been modified unexpectedly. | Checksum of file did not match the stored value. | Check the ring files. |
| ring_checksum_ok | STATE_CHANGE | INFO | Checksum of the ring file {0} is OK. | Files for object rings were successfully checked. | Checksum of file found unchanged. | N/A |
| ring_checksum_warn | INFO | WARNING | Issue while checking checksum of the ring file {0}. | Checksum generation process failed. | The ring_checksum check returned an unknown result. | Check the ring files and the md5sum executable. |
| proxy-httpd-server_failed | STATE_CHANGE | ERROR | Proxy process should be {0} but is {1}. | The proxy-server process is not running. | The proxy-server process is not running. | Check status of openstack-swift-proxy process. |
| proxy-httpd-server_ok | INFO | INFO | Proxy process as expected, state is {0}. | The proxy-server process is running. | The proxy-server process is running. | N/A |
| proxy_access_up | STATE_CHANGE | INFO | Access to proxy service ip {0} port {1} ok. | The access check of the proxy service port was successful. | N/A | |
| proxy_access_down | STATE_CHANGE | ERROR | No access to proxy service ip {0} port {1}. Check firewall. | The access check of the proxy service port failed. | The port is probably blocked by a firewall rule. | Check if the proxy service is running, and the firewall rules. |
| proxy_access_warn | STATE_CHANGE | WARNING | Proxy service access check ip {0} port {1} failed. Check for validity. | The access check of the proxy service port returned an unknown result. | The proxy service port access could not be determined due to a problem. | Find potential issues for this kind of failure in the logs. |
| account_access_up | STATE_CHANGE | INFO | Access to account service ip {0} port {1} ok. | The access check of the account service port was successful. | N/A | |
| account_access_down | STATE_CHANGE | ERROR | No access to account service ip {0} port {1}. Check firewall. | The access check of the account service port failed. | The port is probably blocked by a firewall rule | Check if the account service is running and the firewall rules |
| account_access_warn | INFO | WARNING | Account service access check ip {0} port {1} failed. Check for validity. | The access check of the account service port returned an unknown result. | The account service port access could not be determined due to a problem. | Find potential issues for this kind of failure in the logs. |
| container_access_up | STATE_CHANGE | INFO | Access to container service ip {0} port {1} ok. | The access check of the container service port was successful. | N/A | |
| container_access_down | STATE_CHANGE | ERROR | No access to container service ip {0} port {1}. Check firewall. | The access check of the container service port failed. | The port is probably blocked by a firewall rule. | Check if the filesystem daemon is running, and the firewall rules. |
| container_access_warn | INFO | WARNING | Container service access check ip {0} port {1} failed. Check for validity. | The access check of the container service port returned an unknown result. | The container service port access could not be determined due to a problem. | Find potential issues for this kind of failure in the logs. |
| object_access_up | STATE_CHANGE | INFO | Access to object store ip {0} port {1} ok. | The access check of the object service port was successful. | N/A | |
| object_access_down | STATE_CHANGE | ERROR | No access to object store ip {0} port {1}. Check firewall. | The access check of the object service port failed. | The port is probably blocked by a firewall rule. | Check if the object service is running, and the firewall rules. |
| object_access_warn | INFO | WARNING | Object store access check ip {0} port {1} failed. | The access check of the object service port returned an unknown result. | The object service port access could not be determined due to a problem. | Find potential issues for this kind of failure in the logs. |
| object_sof_access_up | STATE_CHANGE | INFO | Access to unified object store ip {0} port {1} ok. | The access check of the unified object service port was successful. | N/A | |
| object_sof_access_down | STATE_CHANGE | ERROR | No access to unified object store ip {0} port {1}. Check firewall. | The access check of the unified object service port failed. | The port is probably blocked by a firewall rule. | Check if thunified object service is running, and the firewall rules. |
| object_sof_access_warn | INFO | WARNING | Unified object store access check ip {0} port {1} failed. Check for validity. | The access check of the unified object access service port returned an unknown result. | The unified object service port access could not be determined due to a problem. | Find potential issues for this kind of failure in the logs. |
| stop_obj_service | INFO_EXTERNAL | INFO | OBJ service was stopped. | Information about an OBJ service stop. | The OBJECT service was stopped (e.g. using the mmces service stop obj command). | N/A |
| start_obj_service | INFO_EXTERNAL | INFO | OBJ service was started. | information about a OBJ service start. | The OBJECT service was started (e.g. using the mmces service start obj command). | N/A |
| object_quarantined | INFO_EXTERNAL | WARNING | The object \"{0}\", container \"{1}\", account \"{2}\" has been quarantined. Path of quarantined object: \"{3}\. | The object which was being accessed is quarantined. | Mismatch in data or metadata. | |
| openstack-swift-object-auditor_failed | STATE_CHANGE | ERROR | Object-auditor process should be {0} but is {1}. | The object-auditor process is not in the expected state. | The openstack-swift-object-auditor process is expected to be running on the singleton node only, and when the capability multi-region is enabled. It needs to be stopped in other cases | Check status of openstack-swift-object-auditor process and capabilities flag in spectrum-scale-object.conf |
| openstack-swift-object-auditor_ok | STATE_CHANGE | INFO | Object-auditor process as expected, state is {0}}. | The object-auditor process is in the expected state. | The openstack-swift-object-auditor process is expected to be running on the singleton node only, and when the capability multi-region is enabled. It needs to be stopped in other cases. | N/A |
| openstack-swift-object-auditor_warn | INFO | INFO | Object-auditor process monitoring returned unknown result. | The openstack-swift-object-auditor check returned an unknown result. | A status query for openstack-swift-object-auditor returned with an unexpected error. | Check service script and settings. |