Hi all,
I've had this error rear it's ugly head again and I'm not exactly sure why. The output in /var/log/message is:
crond[14764]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14765]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14811]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14842]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
This seems to happen every 5 minutes. Probably caused by the cacti cron jobs running. It looks to have started after the last krb5 updates - however this could be coincidence.
$ cat crond # # The PAM configuration file for the cron daemon # # auth sufficient pam_rootok.so auth required pam_env.so auth include system-auth account required pam_access.so account include system-auth #session required pam_loginuid.so session include system-auth
I commended out pam_loginuid.so - as I remember reading somewhere that this was the cause of this issue, however it hasn't made a difference this time...
Does anyone have any insight in this?
-- Steven Haigh
Email: netwiz@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897
On Sat, Sep 15, 2007 at 12:15:30PM +1000, Steven Haigh wrote:
Hi all,
I've had this error rear it's ugly head again and I'm not exactly sure why. The output in /var/log/message is:
crond[14764]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
I've seen this when using a non-standard kernel without the correct CONFIG_AUDIT and CONFIG_AUDITSYSCALL options set.
If you're running a kernel without those options then you can remove the pam_loginuid from PAM (sshd,crond,login,remote and possibly others)
On 15/09/2007, at 2:26 PM, Stephen Harris wrote:
On Sat, Sep 15, 2007 at 12:15:30PM +1000, Steven Haigh wrote:
Hi all,
I've had this error rear it's ugly head again and I'm not exactly sure why. The output in /var/log/message is:
crond[14764]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
I've seen this when using a non-standard kernel without the correct CONFIG_AUDIT and CONFIG_AUDITSYSCALL options set.
If you're running a kernel without those options then you can remove the pam_loginuid from PAM (sshd,crond,login,remote and possibly others)
Bingo. That was the cause (and fix) of the problem. Turned those options on in the kernel, and now all is good.
-- Steven Haigh
Email: netwiz@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897