Home » Blogs » sandip's blog

set_loginuid failed opening loginuid

Tue, 02/03/2009 - 10:51 — sandip

If this file doesn't exist:

/proc/<pid of crond>/loginuid

It's because the kernel doesn't have AUDIT enabled. So you get a bunch of errors in "/var/log/secure" with "set_loginuid failed opening loginuid".

Recompile kernel with audit support:

CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y

If recompiling of kernel is not an option then:

Comment the below lines from all pam.d files.

session required   &nbsp;    pam_loginuid.so

Find files via:

# grep -l pam_loginuid.so /etc/pam.d/*
/etc/pam.d/atd
/etc/pam.d/crond
/etc/pam.d/login
/etc/pam.d/remote
/etc/pam.d/sshd

Bookmark/Search this post with
  • del.icio.us
  • Digg
  • Facebook
  • identi.ca
  • LinkedIn
  • SlashDot
  • StumbleUpon
  • Technorati
  • Twitter

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Thu, 08/06/2009 - 14:26 — sandip audit_log_user_command(): Connection refused

The same goes for "audit_log_user_command(): Connection refused".

https://bugzilla.redhat.com/show_bug.cgi?id=401201

Tue, 02/12/2013 - 11:45 — sandip sudo update

updating sudo, should now fix this issue.

Comment