Authentication events
The following table lists the events that are created for the AUTH component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| ad_smb_nfs_ready | STATE_CHANGE HEALTHY |
INFO | no | Message: SMB and NFS monitoring has started. |
| Description: AD authentication for NFS is configured, and SMB and NFS monitoring has started. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ad_smb_not_yet_ready | STATE_CHANGE | WARNING | no | Message: AD authentication is configured, but the SMB monitoring is not yet ready. |
| Description: AD authentication for NFS is configured, but SMB monitoring is not yet ready. | ||||
| Cause: SMB monitoring has not started yet, but NFS is ready to process requests. | ||||
| User Action: Check as to why the SMB or CTDB is not yet running. This problem might be caused by a temporary issue. | ||||
| ads_cfg_entry_warn | INFO | WARNING | no | Message: {0} returned unknown result for item {1} query. |
| Description: The external DNS server monitoring returned an unknown result. | ||||
| Cause: An internal error occurred while querying the external DNS server. | ||||
| User Action: Perform troubleshooting to resolve the error. | ||||
| ads_down | STATE_CHANGE | ERROR | FTDC upload | Message: The external ADS server is unresponsive. |
| Description: The external ADS server is unresponsive. | ||||
| Cause: The local node is unable to connect to any Active Directory Service (ADS) server. | ||||
| User Action: Verify the network connection and check whether the ADS server is operational. | ||||
| ads_failed | STATE_CHANGE FAILED |
ERROR | FTDC upload | Message: The local winbindd service is unresponsive. |
| Description: The local winbindd service is unresponsive. | ||||
| Cause: The local winbindd service, which is needed for ADS, is not responding to ping requests. | ||||
| User Action: Restart the winbindd service. If the service restart is not successful, then perform the winbindd troubleshooting. | ||||
| dns_krb_tcp_dc_msdcs_down | STATE_CHANGE DEGRAGED |
INFO | no | Message: The external ADS server is up. |
| Description: The external ADS server is operational. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ads_warn | INFO | WARNING | no | Message: The external ADS server monitoring returned an unknown result. |
| Description: The external ADS server monitoring returned an unknown result. | ||||
| Cause: An internal error occurred while monitoring the external ADS server. | ||||
| User Action: Perform troubleshooting to resolve the error. | ||||
| dns_found | ADD_ENTITY | INFO | no | Message: The nameserver {0} was found. |
| Description: A nameserver was found. | ||||
| Cause: A nameserver was found. | ||||
| User Action: N/A | ||||
| dns_krb_tcp_dc_msdcs_down | STATE_CHANGE | WARNING | no | Message: {0} has no {1} declared. |
Description: The required SRV item_kerberos._tcp.dc._msdcs.<Realm>
is not declared in the DNS. |
||||
| Cause: The AD server might not be fully usable. | ||||
| User Action: Add the missing settings to the DNS. | ||||
| dns_krb_tcp_dc_msdcs_up | STATE_CHANGE HEALTHY |
INFO | no | Message: {0} has {1} declared. |
Description: A required SRV item_kerberos._tcp.dc._msdcs.<Realm>
is declared in the DNS. |
||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| dns_krb_tcp_down | STATE_CHANGE DEGRADED |
WARNING | no | Message: {0} has no {1} declared. |
Description: The required SRV item _kerberos._tcp.<Realm> is not
declared in the DNS. |
||||
| Cause: The AD server might not be fully usable. | ||||
| User Action: Add the missing settings to the DNS. | ||||
| dns_krb_tcp_up | STATE_CHANGE HEALTHY |
WARNING | no | Message: {0} has no {1} declared. |
Description: A required SRV item _kerberos._tcp.<Realm> is
declared inthe DNS. |
||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| dns_krb_tcp_dc_msdcs_up | STATE_CHANGE | INFO | no | Message: {0} has {1} declared. |
Description: A required SRV item _kerberos._tcp.<Realm> is
declared in the DNS. |
||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| dns_ldap_tcp_dc_msdcs_down | STATE_CHANGE | WARNING | no | Message: {0} has no {1} declared. |
Description: The required SRV item_ldap._tcp.dc._msdcs.<Realm> is
not declared in the DNS. |
||||
| Cause: The ADS might not be fully usable. | ||||
| User Action: Add the missing settings to the DNS. | ||||
| dns_ldap_tcp_dc_msdcs_up | STATE_CHANGE | INFO | no | Message: {0} has {1} declared. |
Description: A required SRV item_ldap._tcp.dc._msdcs.<Realm> is
declared in the DNS. |
||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| dns_ldap_tcp_down | STATE_CHANGE DEGRAGED |
WARNING | no | Message: {0} has no {1} declared. |
Description: The required SRV item _ldap._tcp.<Realm> is not
declared in the DNS. |
||||
| Cause: The AD server might not be fully usable. | ||||
| User Action: Add the missing settings to the DNS. | ||||
| dns_ldap_tcp_up | STATE_CHANGE HEALTHY |
INFO | no | Message: {0} has {1} declared. |
Description: A required SRV item _ldap._tcp.<Realm> is declared in
the DNS. |
||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| dns_query_fail | STATE_CHANGE DEGRAGED |
WARNING | no | Message: The {0} query failed {1}. |
| Description: A nameserver did not provide the expected AD-related SRV items. | ||||
| Cause: A nameserver query for AD-specific SRV items failed. | ||||
| User Action: Check the nameserver configuration for the missing AD-specific settings. | ||||
| dns_query_ok | STATE_CHANGE HEALTHY |
INFO | no | Message: The {0} query is successful. |
| Description: A nameserver query for AD-specific settings is successful. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| dns_query_proto_fail | TIP | WARNING | no | Message: The {0} query failed for UDP and TCP. |
| Description: A nameserver did not react on a query protocol. | ||||
| Cause: A nameserver query for UDP and TCP check failed. | ||||
| User Action: Check the nameserver configuration for allowed protocols, port, and firewall settings. | ||||
| dns_query_proto_ok | TIP | INFO | no | Message: The {0} query succeeded with UDP and TCP protocols. |
| Description: A nameserver can be queried with UDP and TCP protocols. | ||||
| Cause: A nameserver can be queried with UDP and TCP protocols. | ||||
| User Action: N/A | ||||
| dns_vanished | DEL_ENTITY | INFO | no | Message: The nameserver {0} has vanished. |
| Description: A declared nameserver is not detected anymore. | ||||
| Cause: A nameserver is not detected anymore, which could be a valid situation. | ||||
| User Action: Check the configuration, which could be a valid situation. | ||||
| ldap_down | STATE_CHANGE DEGRAGED |
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 the network connection and check whether the LDAP server is operational. | ||||
| ldap_up | STATE_CHANGE HEALTHY |
INFO | no | Message: The external LDAP server {0} is up. |
| Description: The external LDAP server is operational. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| nis_down | STATE_CHANGE DEGRAGED |
ERROR | no | Message: The external NIS server {0} is unresponsive. |
| Description: The external NIS server is unresponsive. | ||||
| Cause: The local node is unable to connect to any Network Information Service (NIS) server. | ||||
| User Action: Verify the network connection and check whether the NIS server is operational. | ||||
| nis_failed | STATE_CHANGE FAILED |
ERROR | no | Message: ypbind daemon is unresponsive. |
| Description: ypbind daemon is unresponsive. | ||||
| Cause: The local ypbind daemon does not respond. | ||||
| User Action: Restart ypbind daemon. If the restart is not successful, then perform ypbind troubleshooting. | ||||
| nis_up | STATE_CHANGE HEALTHY |
INFO | no | Message: The external NIS server {0} is up. |
| Description: The external NIS server is operational. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| nis_warn | INFO | WARNING | no | Message: The external NIS monitoring returned unknown result. |
| Description: The external NIS server monitoring returned an unknown result. | ||||
| Cause: An internal error occurred while monitoring external NIS server. | ||||
| User Action: Perform troubleshooting to resolve the error. | ||||
| sssd_down | STATE_CHANGE FAILED |
ERROR | no | Message: The SSSD process is not running. |
| Description: The SSSD process is not running. | ||||
| Cause: The SSSD authentication service is not running. | ||||
| User Action: Perform troubleshooting to resolve the issue. | ||||
| sssd_restart | INFO | INFO | no | Message: The SSSD process is not running. Trying to start the SSSD process. |
| Description: Attempt to start the SSSD authentication process. | ||||
| Cause: The SSSD process is not running. | ||||
| User Action: N/A | ||||
| sssd_up | STATE_CHANGE HEALTHY |
INFO | no | Message: The SSSD process is now running. |
| Description: The SSSD authentication process is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| sssd_warn | INFO | WARNING | no | Message: The SSSD process monitoring returned unknown result. |
| Description: The SSSD authentication process monitoring returned an unknown result. | ||||
| Cause: An internal error occurred while monitoring SSSD. | ||||
| User Action: Perform troubleshooting to resolve the error. | ||||
| wnbd_down | STATE_CHANGE F |
ERROR | no | Message: The WINBINDD process is not running. |
| Description: The WINBINDD authentication process is not running. | ||||
| Cause: The WINBINDD authentication service is not running. | ||||
| User Action: Verify configuration and Active Directory (AD) connection. | ||||
| wnbd_restart | INFO | INFO | no | Message: WINBINDD process was not running. Trying to start the WINBINDD process. |
| Description: Attempt to start the WINBINDD authentication process. | ||||
| Cause: The WINBINDD process was not running. | ||||
| User Action: N/A | ||||
| wnbd_up | STATE_CHANGE HEALTHY |
INFO | no | Message: The WINBINDD process is now running. |
| Description: The WINBINDD authentication service is operational. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| wnbd_warn | INFO | WARNING | no | Message: The WINBINDD process monitoring returned unknown result. |
| Description: The WINBINDD process monitoring returned an unknown result. | ||||
| Cause: An internal error occurred while monitoring the WINBINDD process. | ||||
| User Action: Perform troubleshooting to resolve the error. | ||||
| yp_down | STATE_CHANGE FAILED |
ERROR | no | Message: The YPBIND process is not running. |
| Description: The YPBIND process is not running. | ||||
| Cause: The YPBIND authentication service is not running. | ||||
| User Action: Perform troubleshooting to resolve the issue. | ||||
| yp_restart | INFO | INFO | no | Message: The YPBIND process was not running. Trying to start the YPBIND process. |
| Description: Attempt to start the YPBIND process. | ||||
| Cause: The YPBIND process was not running. | ||||
| User Action: N/A | ||||
| yp_up | STATE_CHANGE HEALTHY |
INFO | no | Message: The YPBIND process is now running. |
| Description: The YPBIND process is operational. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| yp_warn | INFO | WARNING | no | Message: The YPBIND process monitoring returned unknown result. |
| Description: The YPBIND process monitoring returned an unknown result. | ||||
| Cause: An internal error occurred while monitoring the YPBIND process. | ||||
| User Action: Perform troubleshooting to resolve the error. |