General discussion

Locked

Not able to login.

By iamsanchez ·
Running YPserver, DNSserver, and other services on a RH6.2 box. Also running other versions and other machines with a mixture of RH5.2, RH6.2, RH70, RH71.

My chanllenge is as follows. I recently upgraded one of the Linux boxes to RH72; which only job on the network is to provide CDburning services - that's it [This is the only box running 7.2 by the way]. Except that after the upgraded, I and a couple of other regular users cannot login to this machine; at console or remotely for that matter. Other users can login no problem as usual. I have checked "$ ypcat passwd", at this machine and I can clearly see the password file from my YPserver.

I have snipped the following lines from the most current /var/log/messages file: I have addedheadings for clarity.

From Console:
==============
Apr 5 11:12:25 roasting_machine login(pam_unix)[31459]: authentication failure; logname=LOGIN uid=0 euid=0 tty=tty2 ruser= rhost= user=rsanchez

From Kdm login:
===============
Apr 5 11:12:28 roasting_machine login[31459]: FAILED LOGIN 1 FROM (null) FOR rsanchez, Authentication failure


From Remote machine:
======================
Apr 5 11:09:46 roaster login[31483]: FAILED LOGIN 1 FROM machine.domain.com FOR rsanchez, Authentication failure

I know that I know that I and the other users involved have the right passwords.

Any ideas?

Thank you.

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Not able to login.

by Shanghai Sam In reply to Not able to login.

Not being very familiar with YPserver I can't provide much assitance for that, but I have a suggestion for squezing debugging info from logins which may help you trace the problem.

I would edit /etc/pam.d/system-auth, find the line
"auth sufficient /lib/security/pam_unix.so likeauth nullok" and add "debug" to the end of it. Then try logging in again.

You should get extra info in /var/log/messages and /var/log/secure. As soon as you have gathered all the information needed, you should remove the debug option as it has potential security holes.

Another possibility is the firewall that 7.2 will try to automaticly install. Try "service ipchains stop" to temporarly turn the firewall off. If this works, you should alter your rules, butto just turn them off remove /etc/sysconfig/ipchains.

Hope this is usefull to you.

Collapse -

Not able to login.

by iamsanchez In reply to Not able to login.

Poster rated this answer

Collapse -

Not able to login.

by ShyamKishore In reply to Not able to login.

This problem could be because of MD5 passwd schem. as the MD5 passwd will accept only 8 characters. You change your "yppasswd" to less or equal to 8 Characters, and try login to the new RH 7.2 system.

All the best.

Shyam

Collapse -

Not able to login.

by iamsanchez In reply to Not able to login.

Poster rated this answer

Back to Linux Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums