On Tuesday 23 November 2010 09:58:57 Thorsten Kukuk wrote:
On Tue, Nov 23, Andreas Jaeger wrote:
On Tuesday 23 November 2010 09:49:26 Thorsten Kukuk wrote:
On Mon, Nov 22, Andreas Jaeger wrote:
On Friday 19 November 2010 18:33:24 Stephen Shaw wrote:
I'm not sure if there were some other updates that I finally hit when I rebooted or not.
I just upgraded to the 2.6.37-rc2 kernel running on factory and everything seems to boot ok, except I can't log in properly. The prompt on the console comes up and it lets me put my user and password in. It acts like it accepts it (which I think it does), but gives me this error:
Cannot make/remove an entry for the specified session
When I booted to init=/bin/bash I looked at the logs
(/var/log/messages/) and found this error: Are you running SysVinit or systemd?
pam_loginuid(login:session):set_loginuid failed
I saw this with systemd but could not point out the problem. If I login using kdm, it fails but if I login first at the console it seems to be ok...
I see the following error message: Nov 22 10:51:14 byrd login[2312]: pam_loginuid(login:session): Cannot open /proc/self/loginuid: Read-only file system
That sounds like a kernel bug or mount problem, not sure. Nothing PAM can do here.
Any suggestions on how to debug this? It's impossible to log in at this point.
Disable pam_loginuid (rescue system, init=/bin/bash, I think you will know enough ways how to do that ;), boot the system normal and login. Afterwards, look if you can read and write into /proc/self/loginuid.
Using SysV init solved the problem as well for me. I need to debug this while it's broken... Kay, is there a way to have a simple shell open for login on a console to debug?
Nov 22 10:51:14 byrd login[2312]: pam_loginuid(login:session): set_loginuid failed Nov 22 10:51:14 byrd login[2312]: pam_systemd(login:session): Moving new user session for tux into control group /user/tux/7c. Nov 22 10:51:14 byrd login[2312]: Cannot make/remove an entry for the specified session
From whom is the last message coming? It's not login itself.
No idea,
You could run a string/grep over the used/installed PAM modules. It's /lib64/libpam.so.0
Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org