Keystone events
The following table lists the events that are created for the Keystone component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| ks_failed | STATE_CHANGE | ERROR | FTDC upload | Message: The keystone (HTTPd) process should be {0}, but is {1}. |
| Description: The keystone (HTTPd) process is in an unexpected mode. | ||||
| Cause: If the object authentication is local, AD or LDAP, then the process failed. If the object authentication is none or user-defined, then the process is expected to be stopped, but was running. | ||||
| User Action: Ensure that the process is in the expected state. | ||||
| ks_ok | STATE_CHANGE | INFO | no | Message: The keystone (HTTPd) process as expected, state is {0}. |
| Description: The keystone (HTTPd) process is in the expected state. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ks_restart | INFO | WARNING | no | Message: The {0} service failed. Trying to recover. |
| Description: A service was not in the expected state. | ||||
| Cause: A service might have stopped unexpectedly. | ||||
| User Action: N/A | ||||
| ks_url_exfail | STATE_CHANGE | WARNING | no | Message: Keystone request failed by using {0}. |
| Description: A request to an external keystone URL failed. | ||||
| Cause: An HTTP request to an external keystone server failed. | ||||
| User Action: Check that HTTPd or keystone is running on the expected server, and is accessible with the defined ports. | ||||
| ks_url_failed | STATE_CHANGE | ERROR | no | Message: Keystone request failed by using {0}. |
| Description: A keystone URL request failed. | ||||
| Cause: An HTTP request to keystone failed. | ||||
| User Action: Check whether the HTTPd or keystone is running on the expected server, and is accessible with the defined ports. | ||||
| ks_url_ok | STATE_CHANGE | INFO | no | Message: Keystone request is successful by using {0}. |
| Description: A keystone URL request was successful. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ks_url_warn | INFO | WARNING | no | Message: Keystone request {0} returned an unknown result. |
| Description: A keystone URL request returned an unknown result. | ||||
| Cause: A simple HTTP request to keystone returned an unexpected error. | ||||
| User Action: Check whether HTTPd or keystone is running on the expected server, and is accessible with the defined ports. | ||||
| ks_warn | INFO | WARNING | no | Message: The keystone (HTTPd) process monitoring returned an unknown result. |
| Description: The keystone (HTTPd) monitoring returned an unknown result. | ||||
| Cause: A status query for HTTPd returned an unexpected error. | ||||
| User Action: Check service script and settings of HTTPd. | ||||
| ldap_reachable | STATE_CHANGE | INFO | no | Message: The external LDAP server {0} is up. |
| Description: The external LDAP server is operational. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ldap_unreachable | STATE_CHANGE | ERROR | no | Message: The external LDAP server {0} is unresponsive. |
| Description: The external LDAP server is unresponsive. | ||||
| Cause: The local node is unable to connect to the LDAP server. | ||||
| User Action: Verify network connection and check whether that LDAP server is operational. | ||||
| postgresql_failed | STATE_CHANGE | ERROR | FTDC upload | Message: The 'postgresql-obj' process should be {0}, but is {1}. |
| Description: The 'postgresql-obj' process is in an unexpected mode. | ||||
| Cause: The database backend for object authentication is supposed to run on a single node when either database is not running on the designated node or it is running on a different node. | ||||
| User Action: Check that the 'postgresql-obj' process is running on the expected server. | ||||
| postgresql_ok | STATE_CHANGE | INFO | no | Message: The 'postgresql-obj' process as expected, state is {0}. |
| Description: The 'postgresql-obj' process is in the expected mode. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| postgresql_warn | INFO | WARNING | no | Message: The 'postgresql-obj' process monitoring returned an unknown result. |
| Description: The 'postgresql-obj' process monitoring returned an unknown result. | ||||
| Cause: A status query for 'postgresql-obj' returned an unexpected error. | ||||
| User Action: Check PostgresSQL database engine. |