[opensuse-factory] 2.6.37-rc2 can't log in properly
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: pam_loginuid(login:session):set_loginuid failed Cheers, Stephen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/19/2010 12:33 PM, 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:
pam_loginuid(login:session):set_loginuid failed
I don't think this is a kernel issue. I'm running 2.6.37-rc2 on my development node with M3 and it works fine with both a console login (serial console using smart_agetty) and ssh. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkzmuMoACgkQLPWxlyuTD7J0owCgkfQLR6brQiuhxVZdu4PmtMLG EbQAoI9BeIAt88Z6u9/ZPKgk5NHKLg9n =AmDG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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 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 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
On Mon, Nov 22, 2010 at 05:16, Andreas Jaeger <aj@novell.com> 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 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
Andreas
This is with systemd, but saw this with sysinit as well. Stephen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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.
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.
Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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.
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, 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
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.
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. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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
On Tue, Nov 23, Andreas Jaeger wrote:
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...
Disable pam_loginuid with SysV init and boot with systemd. Afterwards, try to read and write /proc/self/loginuid. Shouldn't work, too.
It's /lib64/libpam.so.0
Ok, then you can ignore it, it's a follow up problem of the /proc/self/loginuid not writeable problem. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
I updated to systemd 13 and now it seems to work. I'll investigate once I can reproduce it again, 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
On Tuesday, November 23, 2010 10:24:58 am Andreas Jaeger wrote:
I updated to systemd 13 and now it seems to work. I'll investigate once I can reproduce it again,
I have this problem with systemd 13 and I'm sure the sysvinit works well. /proc is mounted as ro - simple mount /proc -o remount,rw fixes this problem. The sysvinit works well, init=/bin/bash ended up with rw /proc, so the problem is not in initrd. However when I run exec systemd from that bash, /proc became ro for unknown reason. What needs to be done is just remount /proc as rw, then everything works well and no pam magic is needed. I filled a https://bugzilla.novell.com/show_bug.cgi?id=656509 for that. Regards Michal Vyskocil
On Tuesday 30 November 2010 10:56:47 Michal Vyskocil wrote:
On Tuesday, November 23, 2010 10:24:58 am Andreas Jaeger wrote:
I updated to systemd 13 and now it seems to work. I'll investigate once I can reproduce it again,
I have this problem with systemd 13 and I'm sure the sysvinit works well. /proc is mounted as ro - simple mount /proc -o remount,rw fixes this problem. The sysvinit works well, init=/bin/bash ended up with rw /proc, so the problem is not in initrd. However when I run exec systemd from that bash, /proc became ro for unknown reason.
What needs to be done is just remount /proc as rw, then everything works well and no pam magic is needed.
I filled a https://bugzilla.novell.com/show_bug.cgi?id=656509 for that.
There have been previous bugs, where chroot services want to mount proc in their local roots, but forget to do --bind. Could that be it here too? Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Nov 23, 2010 at 10:08:35AM +0100, Andreas Jaeger wrote:
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?
The file is written.. It perhaps means /proc is still mounted r/o or not mounted at all, which does not make sense. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (7)
-
Anders Johansson -
Andreas Jaeger -
Jeff Mahoney -
Marcus Meissner -
Michal Vyskocil -
Stephen Shaw -
Thorsten Kukuk