Hi,
This appears to be the same problem I was having a
couple of days ago:
http://list.linux-vserver.org/archive/vserver/msg11023.html
Comment out the "pam_loginuid.so" in /etc/pam.d/* and
I believe your problem will go away.
jorgy
--- jcpetit@syspark.com wrote:
> Hello,
>
> login via ssh on a vserver does not work anymore
> after the last new
> nupdate of pam from Centos4/Redhat ES4:
> pam-0.77-66.11
>
> After the user is logged on, the session dies with
> the following message:
>
> Oct 14 00:00:01 sedna pam_loginuid[8627]:
> set_loginuid failed opening
> loginuid
> Oct 14 00:00:01 sedna pam_loginuid[8627]:
> set_loginuid failed
> Oct 14 00:00:01 sedna crond[8627]: Cannot
> make/remove an entry for the
> specified session
>
> I found something on the redhat bug lists:
>
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159974
>
> It seems the new pam is using a /proc/<pid>/loginuid
> and for security
> reasons, the vserver is not able to access it.
>
> Maybe RedHat will have a solution in the near
> future?....
> I hope so, but for the moment, anybody knows how to
> resolve the problem
> with some config (CAP ?)
>
> regards,
> Jess
>
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
>
http://list.linux-vserver.org/mailman/listinfo/vserver
>
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Fri Oct 14 18:51:40 2005