In /var/log/secure, twice every minute I was receiving the following message:<br />
<br />
Jul 5 11:06:01 li5-33 crond[21428]: pam_loginuid(crond:session): set_loginuid failed opening loginuid<br />
<br />
Googling this message indicates the reason is that the /proc filesystem is read-only and so the pam_loginuid module cannot write the audit information there. A read-only proc filesystem appears to be the default, and usage of pam_loginuid also appears to be the default.<br />
<br />
Commenting out pam_loginuid from the /etc/pam.d/crond file resolved the issue.
↧