It may be necessary to run the steps from this KB on your Aria Operations appliances if you experience the following issues:
The following video shows the process for Aria Operations 8.0 to 8.12.
In versions 8.14 and newer, the configuration file to edit is /etc/security/faillock.conf
and the line to comment out is even_deny_root
(see Step 11 below)
e
key to enter edit mode.elevator=noop audit=1
"rw init=/bin/bash
mount -o remount,rw /
passwd
vi /etc/security/faillock.conf
Note: In versions 8.0 through 8.12, the file to edit is /etc/pam.d/system-auth
even_deny_root
directive by placing a # character at the beginning of the line#even_deny_root
#pam_tally2.so onerr=fail deny=3 unlock_time=900 root_unlock_time=900 file=/var/log/tallylog
:wq
sync
reboot -f
Note: If the reboot command fails, restart the Virtual Machine through vCenter.
vi /etc/security/faillock
Note: In versions 8.0 through 8.12, the file to edit is /etc/pam.d/system-auth
even_deny_root
directive by uncommenting it (removing the # character at the beginning of the line)even_deny_root
pam_tally2.so onerr=fail deny=3 unlock_time=900 root_unlock_time=900 file=/var/log/tallylog
:wq
NOTE: If the Aria Operations nodes are managed by Aria Suite Lifecycle or part of VMware Cloud Foundation, see the Additional Information section for additional steps necessary to update the root password stored in the Aria Suite Lifecycle locker.