Red Hat Linux Interview Series 36

[Chetan_Tiwary_]

Q.) Given a script that suddenly consumes 100% CPU, how do you trace the issue to the line of code causing it?

Q.) Ansible Task - Create a playbook that ensures /etc/ssh/sshd_config has "PermitRootLogin no" and restarts SSH only if it changed.

Bonus Q.) How do you handle rolling patching across 500 Linux servers using Ansible ensuring only 10 reboot at a time?

Q.) Users cannot log in via ssh using LDAP or SSSD after a reboot whereas local users can login - investigate. 

Level L2 and above

I'll be posting a series of Linux-related questions covering various skill levels. Feel free to share your insights and expertise. Your contributions will benefit learners at all stages, from those in current roles to those preparing for Linux interviews.

[Trevor]

Q.) Users cannot log in via ssh using LDAP or SSSD after a reboot whereas local users can login - investigate. 

Could it be that both of these services, LDAP and SSSD, were not enabled to
automatically start when the Linux system boots?  Well, the first (and easiest)
thing I'm going to do is to look at the status of these services:

$ sudo  systemctl  status  slapd

$ sudo  systemctl  status  sssd

If I see that both services are not running, I'm simply going to configure
them to auto start (enable) when the system boots, and manually start
them while configuring this:

$  sudo  systemctl  enable  --now  slapd

$  sudo  systemctl  enable  --now  sssd