View previous topic :: View next topic |
Author |
Message |
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Tue Apr 05, 2005 11:11 am Post subject: Can't login anymore on new install after etc-update |
|
|
New AMD64 install, worked fine... Logged in, did a pretty large update (emerge -uav world), followed by etc-update... Now I can't login anymore. It still asks for a username, but anything I enter immediately returns "Login incorrect". I'm not even asked for a password.
I think it's a pam problem since I have USE="-*"... Any ideas? |
|
Back to top |
|
|
tomvollerthun Guru
Joined: 19 Mar 2005 Posts: 316
|
Posted: Tue Apr 05, 2005 11:19 am Post subject: |
|
|
Is it possible that etc-update "updated" your /etc/passwd?
That is the file in which the users are listed (among other information).
Does the root account work (what is the default passwd for root)?
If not, you should try and boot from your emergency disk and edit the /etc/passwd manually:
The columns in /etc/passwd are separated by colons: first column is username, second is password hash (or shadow flag)
So you just need to empty the second column (so that two consecutive colons follow the username) and then you have an open box. _________________ Computer science is no more about computers than astronomy is about telescopes.
Dijsktra
---------------
Don't believe my "Guru" status! |
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Tue Apr 05, 2005 6:33 pm Post subject: |
|
|
tomvollerthun wrote: | Is it possible that etc-update "updated" your /etc/passwd?
That is the file in which the users are listed (among other information).
Does the root account work (what is the default passwd for root)?
If not, you should try and boot from your emergency disk and edit the /etc/passwd manually:
The columns in /etc/passwd are separated by colons: first column is username, second is password hash (or shadow flag)
So you just need to empty the second column (so that two consecutive colons follow the username) and then you have an open box. |
I know how /etc/passwd works -- I don't think that's the problem for two reasons:
1) etc-update should ///NEVER/// touch passwords
2) It should still ask for a password... All answers would be wrong, but my PC doesn't even ask for a password anymore :'( |
|
Back to top |
|
|
polle Veteran
Joined: 28 Feb 2003 Posts: 1498 Location: Belgium
|
Posted: Tue Apr 05, 2005 7:16 pm Post subject: |
|
|
when you chroot aftter booting from the livecd and mounting your partitions
you could try this:
emerge -C pam pam-login
emerge pam pam-login |
|
Back to top |
|
|
Sorcerer'sApprentice Tux's lil' helper
Joined: 15 Jan 2005 Posts: 121 Location: Jesus College, Cambridge, England
|
Posted: Tue Apr 05, 2005 7:29 pm Post subject: |
|
|
A had a similar problem to yourself, and never worked out the cause of it (my /etc/passwd was absolutely fine, etc.). Doing emerge -e system using a Live-CD fixed it for me, although polle's solution seems less extreme if it works. _________________ "One of the major problems encountered in time travel is not that of accidentally becoming your own father or mother ... The major problem is quite simply one of grammar..."
Douglas Adams |
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Tue Apr 05, 2005 7:53 pm Post subject: |
|
|
polle wrote: | when you chroot aftter booting from the livecd and mounting your partitions
you could try this:
emerge -C pam pam-login
emerge pam pam-login |
BTW, why is this neccesary and how would this fix the problem? I'll try this... |
|
Back to top |
|
|
polle Veteran
Joined: 28 Feb 2003 Posts: 1498 Location: Belgium
|
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Tue Apr 05, 2005 8:09 pm Post subject: |
|
|
unmerging and reemerging pam and pam-login had absolutely no effect, as expected.
EDIT: It's not similar: he actually gets an error involving missing libraries et cetera, |
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Wed Apr 06, 2005 7:30 am Post subject: |
|
|
Kick. I still can't boot and I don't really feel like reinstalling. |
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Wed Apr 06, 2005 9:06 pm Post subject: |
|
|
Kick, FreeBSD works fine, yada yada yada. If I don't get an answer I'll retry the install. |
|
Back to top |
|
|
Deathwing00 Bodhisattva
Joined: 13 Jun 2003 Posts: 4087 Location: Dresden, Germany
|
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Sun Apr 10, 2005 1:51 pm Post subject: |
|
|
Might be, but I don't think so since I can actually change the root password.
Code: |
livecd / # cat /etc/passwd
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/man:/bin/false
postmaster:x:14:12:postmaster:/var/spool/mail:/bin/false
cron:x:16:16:cron:/var/spool/cron:/bin/false
ftp:x:21:21::/home/ftp:/bin/false
sshd:x:22:22:sshd:/dev/null:/bin/false
at:x:25:25:at:/var/spool/cron/atjobs:/bin/false
squid:x:31:31:Squid:/var/cache/squid:/bin/false
gdm:x:32:32:GDM:/var/lib/gdm:/bin/false
xfs:x:33:33:X Font Server:/etc/X11/fs:/bin/false
games:x:35:35:games:/usr/games:/bin/false
named:x:40:40:bind:/var/bind:/bin/false
mysql:x:60:60:mysql:/var/lib/mysql:/bin/false
postgres:x:70:70::/var/lib/postgresql:/bin/bash
apache:x:81:81:apache:/home/httpd:/bin/false
nut:x:84:84:nut:/var/state/nut:/bin/false
cyrus:x:85:12::/usr/cyrus:/bin/false
vpopmail:x:89:89::/var/vpopmail:/bin/false
alias:x:200:200::/var/qmail/alias:/bin/false
qmaild:x:201:200::/var/qmail:/bin/false
qmaill:x:202:200::/var/qmail:/bin/false
qmailp:x:203:200::/var/qmail:/bin/false
qmailq:x:204:201::/var/qmail:/bin/false
qmailr:x:205:201::/var/qmail:/bin/false
qmails:x:206:201::/var/qmail:/bin/false
postfix:x:207:207:postfix:/var/spool/postfix:/bin/false
smmsp:x:209:209:smmsp:/var/spool/mqueue:/bin/false
portage:x:250:250:portage:/var/tmp/portage:/bin/false
guest:x:405:100:guest:/dev/null:/dev/null
nobody:x:65534:65534:nobody:/:/bin/false
laurens:x:1000:100::/home/laurens:/bin/zsh
|
|
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Sun Apr 10, 2005 2:18 pm Post subject: |
|
|
SOLVED! I think.
etc-update wanted to update /etc/pam.d/login. I assumed it knew a lot more about that file than I did, so I let it. Changed it back to an old version (provided by SeanQ of #gentoo, many thanks of course), works fine now.
I won't mark this thread [SOLVED] until I've posted the file outputs, so it can actually help people. |
|
Back to top |
|
|
shade266 Guru
Joined: 29 Oct 2003 Posts: 593 Location: Internal
|
Posted: Fri May 13, 2005 1:54 am Post subject: |
|
|
racoontje wrote: | SOLVED! I think.
etc-update wanted to update /etc/pam.d/login. I assumed it knew a lot more about that file than I did, so I let it. Changed it back to an old version (provided by SeanQ of #gentoo, many thanks of course), works fine now.
I won't mark this thread [SOLVED] until I've posted the file outputs, so it can actually help people. |
Please update this thread when you can. I can't login as my_user at all. Of course Entrance has to use PAM as well as XDM so I am screwed either way. I have emerged and unmerged baselayout, shadow, edited my /etc/passwd file to no avail. This happened to me long ago running an x86 box and the re-emerge of baselayout solved the issue.
This current situation arose following an update of glibc. After I noticed an authentication failure, I immediately sought the permissions of my /home
directory along with /tmp. The permissions were intact and accurate so I think anyhow. I say this because I am able to login as my_user via virtual console without any problems. Which leaves me with the deduction of PAM being to blame.
I don't intend to thread-jack but instead aid in keeping the resolution to this issue contained within a thread which will provide real help to myself and others. There are many threads on the forums which address this matter but most are lacking specific details of the problem/resolution.
*Edit: XDM doesn't need PAM but I have PAM and pam-login installed so XDM is using PAM. _________________ I've been away for a long time, bear with me. |
|
Back to top |
|
|
teckian n00b
Joined: 21 Jan 2005 Posts: 5
|
Posted: Thu May 19, 2005 1:23 pm Post subject: Authentication upon boot |
|
|
I left my system over-night performing am "emerge -e system". Today when I tried to log in via the screen saver login, I get an error message. I then proceeded to switch to a virtual console (ctrl alt F*), and then tried to login to root. I was given an authentication error and thus could not login to any account. At first I taught I was hacked in some way, but now I see others are having similar issues, and I only wish to say that this command, when run can break your system. It seems like a nasty bug. Restarting my system did not help as I got loads of errors. I will take the advice above and try to boot with my live cd, and then chroot into my system and run "emerge -e system" and "etc-update". I hope this fixes the problem, as I do not wish to re-install. I will confirm if it works or not. Bye for now. _________________ The dawn of a new era started with the advent of Linux! For it taught the people to "FREE THEIR MIND FROM THE ILLUSION OF THE MATRIX " |
|
Back to top |
|
|
shade266 Guru
Joined: 29 Oct 2003 Posts: 593 Location: Internal
|
Posted: Thu May 19, 2005 9:37 pm Post subject: |
|
|
\Is there a way to reset the "default" permissions using the LiveCD?
nor has resolved the issue.
I've tried racoontje's fix as well with no luck. I am thinking the glibc emerge is where this problem originated for me. _________________ I've been away for a long time, bear with me. |
|
Back to top |
|
|
shade266 Guru
Joined: 29 Oct 2003 Posts: 593 Location: Internal
|
Posted: Fri May 20, 2005 12:29 am Post subject: |
|
|
shade266 wrote: | \Is there a way to reset the "default" permissions using the LiveCD?
nor has resolved the issue.
I've tried racoontje's fix as well with no luck. I am thinking the glibc emerge is where this problem originated for me. |
Is the above that dumb of a question? Simplified question I thought.
*bump _________________ I've been away for a long time, bear with me. |
|
Back to top |
|
|
bosyotech Tux's lil' helper
Joined: 29 Jan 2005 Posts: 79 Location: earth
|
Posted: Fri May 20, 2005 1:53 am Post subject: |
|
|
this happened to me before, it was caused by updating pam and pam-login and when i did etc-update without checking what was to be updated, no users can login even root. i had to boot to the livecd again chroot and redo roots password and after that, add again the users. it sucked bigtime, but ive learned an important thing never let etc-update update the files without looking into it first. _________________ of all the things i've lost, i miss my mind the most |
|
Back to top |
|
|
shade266 Guru
Joined: 29 Oct 2003 Posts: 593 Location: Internal
|
Posted: Fri May 20, 2005 11:59 pm Post subject: |
|
|
bosyotech wrote: | this happened to me before, it was caused by updating pam and pam-login and when i did etc-update without checking what was to be updated, no users can login even root. i had to boot to the livecd again chroot and redo roots password and after that, add again the users. it sucked bigtime, but ive learned an important thing never let etc-update update the files without looking into it first. |
etc-update is usually villified when a user doesn't review or know which files to overwrite and proceed to overwrite them all.
My situation wasn't a result of overwritten pam files however. I've removed and created a new user but was unable to access the previous
users' directories/files.
I will try what you suggested however because I didn't try to re-create a password for root followed up with re-creating the user. I will post the results.
*Edit: The aforementioned did not work. I am stumped after 4 days of trying to figure this out. Anyone have another idea? _________________ I've been away for a long time, bear with me. |
|
Back to top |
|
|
shade266 Guru
Joined: 29 Oct 2003 Posts: 593 Location: Internal
|
Posted: Sat May 21, 2005 1:21 am Post subject: |
|
|
*Bump
I know the weekend isn't peak support time on the forums, yet I am completely outta ideas and have read/executed/attempted all -literally- all that I've come across reading. _________________ I've been away for a long time, bear with me. |
|
Back to top |
|
|
aidy l33t
Joined: 07 Apr 2005 Posts: 915
|
Posted: Sat May 21, 2005 6:51 am Post subject: |
|
|
I also have this problem!! BUT, I can log in with GDM, and login to every user I have from an xterm... I can't login from pure console. Another strange thing: the console does not show the hostname before the username ( This is Adriaan.(none) ), but in the xterm everything is shown correctly.
EDIT:
The problem came, like teckian had, after an emerge --emptytree system.... |
|
Back to top |
|
|
shade266 Guru
Joined: 29 Oct 2003 Posts: 593 Location: Internal
|
Posted: Tue May 24, 2005 9:12 pm Post subject: |
|
|
Some deductive reasoning in regards to this thread being ignored:
1. Those of us with the continued inability to login as a non-root user is too ignorant to understand the solution to this problem.
2. I am too ignorant to learn and understand how to resolve my problem of not being able to login as a non-root user.
3. This problem is similar to a previous problem involving PAM and permission changes following an emerge -uD world or an update of glibc (which pertains to my issue). However, this current problem is a mutated version of which no current resolution exists.
4. racoonje has not found credible or a substantial amount of satisfation the solution he posted works and therefore cannot quantify the issue as solved. _________________ I've been away for a long time, bear with me. |
|
Back to top |
|
|
blackcell n00b
Joined: 17 Aug 2002 Posts: 56 Location: Oregon
|
Posted: Sat May 28, 2005 2:13 am Post subject: |
|
|
Well! Did anyone solve this issue????
I had a very similar problem and after two days of F* frustration I was finally able to gain access to my own machine. WTF happened!
After doing a emerge world update followed by etc-update is where all hell broke loose. All seemed fine until launching another term session as it would just hang and never get a bash prompt for root or a normal user. Hmm, this is odd.
I then decided to reboot (Fatal mistake!) and was unable to Login as root or a normal user. At the console login prompt I'd try to login as root followed by the password prompt. After typing in my root password it would just hang for 30 seconds and revert back to login prompt. No error messages. Same for normal user.
The packages that were updated were only 4 or 5 and PAM nor glibc was one of them.
It had something to do with baselayout because etc-update updated several associated files in which one was /etc/profile. That's when the login failed.
After reading a dozen or so forum posts and trying the solutions none of them worked for me. Booting off livecd and chroot'ing I noticed no files in /etc/pam.d nor my passwd file was touched. I concluded it had something to do with /etc/profile and or bash or bashrc causing this issue. I commented out the bottom half of /etc/profile dealing with /etc/bash/bashrc, rebooted, removed livecd, and was able to login.
Now, I'm unsure what exactly needs to be fixed dealing with /etc/bash/bashrc, my ~/.bashrc and /etc/profile. Something is definitely broken with Gentoo, namely something with baselayout 1.11.12-r1 because a user should never ever be locked out of his/her own machine after doing emerge update.
If anyone needs more details just ask.
Some developer please respond now. |
|
Back to top |
|
|
Apewall Apprentice
Joined: 01 Dec 2004 Posts: 248 Location: USA
|
Posted: Sat May 28, 2005 6:46 am Post subject: |
|
|
Doing an etc-update and not understanding or realising what you're updating can be quite devistating to your system.
this is usually caused by overuse of ACCEPT_KEYWORDS or forgetting to emerge -sync after an install.
Your fix: Boot from a livecd and re-emerge the files you updated with etc-update. _________________ Posting for dummies |
|
Back to top |
|
|
|