Keystone events
The following table lists the events that are created for the Keystone component.
| Event | EventType | Severity | Message | Description | Cause | User action |
|---|---|---|---|---|---|---|
| ks_failed | STATE_CHANGE | ERROR | The status of the keystone (httpd) process must be {0} but it is {1} now. | The keystone (httpd) process is not in the expected state. | If the object authentication is local, AD, orLDAP, then the process is failed unexpectedly. If the object authentication is none or userdefined, then the process is expected to be stopped, but it was running. | Make sure that the process is in the expected state. |
| ks_ok | STATE_CHANGE | INFO | The status of the keystone (httpd) is {0} as expected. | The keystone (httpd) process is in the expected state. | If the object authentication is local, AD, orLDAP, process is running. If the object authentication is none or userdefined, then the process is stopped as expected. | N/A |
| ks_restart | INFO | WARNING | The {0} service is failed. Trying to recover. | The {0} service failed. Trying to recover. | A service was not in the expected state. | None, recovery is automatic. |
| ks_url_exfail | STATE_CHANGE | WARNING | Keystone request failed using {0}. | A request to an external keystone URL failed. | A HTTP request to an external keystone server failed. | Check that httpd / keystone is running on the expected server, and is accessible with the defined ports. |
| ks_url_failed | STATE_CHANGE | ERROR | The {0} request to keystone is failed. | A keystone URL request failed. | An HTTP request to keystone failed. | Check that httpd / keystone is running on the expected server and is accessible with the defined ports. |
| ks_url_ok | STATE_CHANGE | INFO | The {0} request to keystone is successful. | A keystone URL request was successful. | A HTTP request to keystone returned successfully. | N/A |
| ks_url_warn | INFO | WARNING | Keystone request on {0} returned unknown result. | A keystone URL request returned an unknown result. | A simple HTTP request to keystone returned with an unexpected error. | Check that httpd / keystone is running on the expected server and is accessible with the defined ports. |
| ks_warn | INFO | WARNING | Keystone (httpd) process monitoring returned unknown result. | The keystone (httpd) monitoring returned an unknown result. | A status query for httpd returned an unexpected error. | Check service script and settings of httpd. |
| postgresql_failed | STATE_CHANGE | ERROR | The status of the postgresql-obj process must be {0} but it is {1} now. | The postgresql-obj process is in an unexpected mode. | The database backend for object authentication is supposed to run on a single node. Either the database is not running on the designated node or it is running on a different node. | Check that postgresql-obj is running on the expected server. |
| postgresql_ok | STATE_CHANGE | INFO | The status of the postgresql-obj process is {0} as expected. | The postgresql-obj process is in the expected mode. | The database backend for object authentication is supposed to run on the right node while being stopped on other nodes. | N/A |
| postgresql_warn | INFO | WARNING | The status of the postgresql-obj process monitoring returned unknown result. |
The postgresql-obj process monitoring returned an unknown result. | A status query for postgresql-obj returned with an unexpected error. | Check postgres database engine. |
| ldap_reachable | STATE_CHANGE | INFO | External LDAP server {0} is up. | The external LDAP server is operational. | The external LDAP server is operational. | N/A |
| ldap_unreachable | STATE_CHANGE | ERROR | External LDAP server {0} is unresponsive. | The external LDAP server is unresponsive. | The local node is unable to connect to the LDAP server. | Verify network connection and check if that LDAP server is operational. |