login
Search
Hi.
I have been trying to figure out why iam experiencing this problem.
When i reboot the machine and want to login, I enter the username and the password, where after the machine just hangs ... and then says "timeout after 60 seconds"
Sometimes, i can login, but after a short while the same problem occurs.. this time when i try to "su".
I have not found any information about this anywhere on the net, so i have no clues.
Anyone have some ideas whats happening with this ?
I can post more info if needed.
Thank you.
Do you have someting in the root login script ?
that may be attempting to connect somewhere, or maybe do a DNS lookup or something ?
As it is happening with "su", as well as login, it seems to be indicating a problem in the shell area.
This is login locally. We,re
This is login locally.
We aren't talking on a remote machine.
About your comment, that it seems to be a problem in the shell area, well so far so good :/
anyone ? please? Im about to
anyone ? please?
Im about to go back to 2.4.23 because of this issue, i cant keep rebooting the machines so i can login ...
what a xmas :(
login
is it root or every user?
It happens with every user.
It happens with every user.
It happens at random times, it can happen right after I reboot the machine and want to login, and can't, and have to reboot again.
It might happen, that I reboot the machine and sucessfully login, I can 'startx' and it can go 5 minutes or 2 days before it happens again... completly random.
Last time it happened i had an uptime of almost 3 days.. then when i was going to 'su', kapow, it happened again, and I had to reboot the machine (hard reboot).
Searching on google Ive found many hits about this, but none recent about kernel 2.6.
There is absolutly nothing on the syslog regarding this matter ( metalog is my logger )
Ive tried to install PAM again but no difference.
Right now: 10:30:43 up 18:44, 3 users, load average: 0.10, 0.10, 0.18
Been going ok, and i can "su" and login and logout without any problem, however this is like a ticking bomb that can explode at any time.
I can post more details about the configuration if needed, I dont know where to look for the source of the error.
Thanks.
This could help you: http:
This could help you:
http://forums.gentoo.org/viewtopic.php?p=676245#676245
It may be metalog
I experienced the same problem when I tried to use a 2.6 kernel. I believe the problem comes from metalog. I stopped metalog and all of a sudden I was able to login from anywhere with no trouble whatsoever.
I hope this helps.
Carl
I have had the same problem
I have had the same problem on a 2.4.18 debian. The solution consisted in killing then restarting syslogd
I suspect the reason was I had deleted an active logfile last week and the logfile did not recreate itself after that.