Authentication error events

This topic describes how to verify and resolve Authentication errors.

Following is a list of possible events that may cause a node to go into a failed state and possible solutions for each of the issues. To determine what state a component is in, issue the mmces command.

SSD/YPBIND process not running (sssd_down)

Cause

The SSSD or the YPBIND process is not running.

Determination

To learn the authentication current state, run the following command:

mmces state show auth

To check the active events for authentication, run the following command:

mmces events active auth

To check the current authentication state, run the following command:

mmces state show auth

To check the current authentication configuration, run the following command:

mmuserauth service list

To check the current authentication configuration across the cluster, run the following command:

mmuserauth service check -N cesNodes --server-reachability

Solution

Rectify the configuration by running the following command:

mmuserauth service check -N cesNodes --rectify

Note: Server reachability cannot be rectified by using the --rectify flag.

Winbind process not running (wnbd_down)

Cause

The Winbind process is not running.

Determination

Run the same command as recommended in the section above, SSD/YPBIND process not running (sssd_down).

Solution

Follow the steps in the previous section, SSD/YPBIND process not running (sssd_down). Then, run the following command:

mmces service stop smb -N <Node on which the problem exists>

mmces service start smb -N <Node on which the problem existed>