Summary: | gentoo-sources-2.8.28-r2 will not allow user login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | georgi |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | critical | CC: | georgi |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
georgi
2009-02-17 23:41:29 UTC
(In reply to comment #0) > Upgrading to 2.8.28-r2 from 2.8.28-r1 (same config) causes "permission denied" > messages whenerer a user tries to log in in any way (tty, ssh, kdm...). Only > root can log in normally. Syslog does not say much more than PAM is refusing > log in. I can provide the precise message if necessary. Yes, I think that the precice message will be help us identifying the problem further. The message in my syslog is: login: pam_unix(login:session): session opened for user godji by LOGIN(uid=0) login: Permission denied godji is my username. As I said, it doesn't help much. Let me know if I can provide more information. The bug remains in 2.6.28-r3. Does anyone have any ideas? I can't possibly be the only one hitting this one. This bug is still present in 2.6.28-r4! I can confirm this for 2.6.29 as well. I'm concerned now because I can no longer upgrade my kernel, and there are things in 29 I'd love to try. Could someone please help me debug this? Where should I look for the cause? What happens if you create a new user. Can you login with that? Anything extraneous in /etc/passwd ? Yes, I can log in just fine with a new user! I think you might be on to something. I do not see anything problematic in /etc/passwd. Should I post that file? Yeah, let's take a look. Would you be able to remove a user that does not work and re add them back and then try to login ? root:x:0:0:root:/root:/bin/bash bin:x:1:1:bin:/bin:/bin/false daemon:x:2:2:daemon:/sbin:/bin/false adm:x:3:4:adm:/var/adm:/bin/false lp:x:4:7:lp:/var/spool/lpd:/bin/false sync:x:5:0:sync:/sbin:/bin/sync shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown halt:x:7:0:halt:/sbin:/sbin/halt mail:x:8:12:mail:/var/spool/mail:/bin/false news:x:9:13:news:/usr/lib/news:/bin/false uucp:x:10:14:uucp:/var/spool/uucppublic:/bin/false operator:x:11:0:operator:/root:/bin/bash man:x:13:15:man:/usr/share/man:/bin/false postmaster:x:14:12:postmaster:/var/spool/mail:/bin/false smmsp:x:209:209:smmsp:/var/spool/mqueue:/bin/false portage:x:250:250:portage:/var/tmp/portage:/bin/false nobody:x:65534:65534:nobody:/:/bin/false sshd:x:22:22:added by portage for openssh:/var/empty:/sbin/nologin cron:x:16:16:added by portage for cronbase:/var/spool/cron:/sbin/nologin ntp:x:123:123:added by portage for ntp:/dev/null:/sbin/nologin godji:x:1000:1000:Georgi Chulkov:/home/godji:/bin/bash messagebus:x:101:1001:added by portage for dbus:/dev/null:/sbin/nologin pulse:x:102:1004:added by portage for pulseaudio:/var/run/pulse:/sbin/nologin haldaemon:x:103:1005:added by portage for hal:/dev/null:/sbin/nologin postgres:x:70:70:added by portage for postgresql-server:/var/lib/postgresql:/bin/bash rpc:x:111:111:added by portage for portmap:/dev/null:/sbin/nologin festival:x:104:18:added by portage for festival:/dev/null:/sbin/nologin hsqldb:x:105:1008:added by portage for hsqldb:/dev/null:/bin/sh ldap:x:439:439:added by portage for openldap:/usr/lib64/openldap:/sbin/nologin mysql:x:60:60:added by portage for mysql:/dev/null:/sbin/nologin penguin:x:9000:9000::/home/penguin:/bin/bash godji is the user that causes problems. penguin is the new user that does not. Well, there might be something extraneous in that file. Can tell from a cut and paste. But, I thinking there's an issue with this file, and it's not a kernel bug. I'm sorry, but I couldn't understand what you were trying to tell me. Is there some other file you wanted to see? The fact that pointing GRUB to a different kernel causes drastically different behavior means that the kernel is involved. Even if the bug is in userspace, there is _something_ that has changed in the kernel, namely between 2.6.28-r1 and 2.6.28-r2. It appears the problem was a line in /etc/security/limits.conf: godji - nofile unlimited The use of unlimited (as opposed to a specific large number) triggers this: https://bugzilla.redhat.com/show_bug.cgi?id=485955 Why a kernel upgrade triggers it and why it worked before are still beyond me. |