Discussion Locked

Not able to login.

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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.

4 replies

by shanghai sam

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.

by shyamkishore

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

This discussion is closed to new replies.