topic Not able to login with any user in Operating System - HP-UX

Not able to login with any user

suneel — Fri, 05 Dec 2008 11:35:37 GMT

We are using hp-ux 11.11.

We got a requset as user are not able to login. we recovered the root password for the server but still not able to login with the new root password as well. This is an urgent thread.

Re: Not able to login with any user

saravanan08 — Fri, 05 Dec 2008 11:41:57 GMT

check wether the /etc/passwd file is present

if it is there means check for mistakes

Re: Not able to login with any user

Pete Randall — Fri, 05 Dec 2008 11:43:10 GMT

Reboot in single-user mode in order to get logged in as root (hpux -is at the ISL prompt). Then take a look at /etc/passwd to see if it's corrupt, or the permissions are wrong (should be -r--r--r--), etc., etc.

Pete

Re: Not able to login with any user

suneel — Fri, 05 Dec 2008 12:00:49 GMT

It seems to be fine.
# ls -l /etc/passwd
-r--r--r-- 1 root sys 1530 Dec 4 08:56 /etc/passwd

Our system is trusted system. Please reply.

Re: Not able to login with any user

Kenan Erdey — Fri, 05 Dec 2008 12:36:19 GMT

hi,

have you recently change it to trusted mode ? how long is your password ?

or what is in syslog ?

Re: Not able to login with any user

Ganesan R — Fri, 05 Dec 2008 12:42:55 GMT

Hi Suneel,

Atleast you need root login to troubleshoot further. If you can't even login as root then you probably need to boot into single user mode and reset the root password then start troubleshooting.

How did you get this below output if you are not able to login even as root user ?

>>>It seems to be fine.
# ls -l /etc/passwd
-r--r--r-- 1 root sys 1530 Dec 4 08:56 /etc/passwd <<<

Re: Not able to login with any user

OldSchool — Fri, 05 Dec 2008 14:32:48 GMT

if recently converted to trusted, then passwords longer than 8 chars got truncated to 8.

any special characters in the root password? as warned against in the "man passwd"

WARNING
Avoid password characters which have special meaning to the tty driver, such as # (erase) and @ (kill). You may not be able to login with these characters.

Re: Not able to login with any user

OldSchool — Fri, 05 Dec 2008 17:30:05 GMT

if the passwords were corrupted on a trusted system, you need to get more than /etc/password back .

the /tcb files and directories are required as well....

search to sysadmin forum for tcb

Re: Not able to login with any user

Johnson Punniyalingam — Sun, 07 Dec 2008 05:21:38 GMT

Hi,

>> User not able to login<<
>>root not able to login<<

ru trying to login root account at the Console or telnet/ssh ..? you need look for root & user account got locked ..?

try using the root account direct going infront of the Server,

1. why becoz it could be no root directly login allowed via telnet,ssh

2. /usr/lbin/getprpw -l root
(check for lockout=101000) --> meaning ur root account locked
3.Enable to its /usr/lbin/modprpw -k root

mentioned trusted system.? have you tries rlogin from ServerA to ServerB --. which have problem -> are you able to login

Re: Not able to login with any user

wci — Mon, 08 Dec 2008 05:14:11 GMT

Hi

If you have a logged in session as root to the system check your /etc/nsswitch.conf file's passwd field.
Just to make sure if you have the correct type either files or NIS or what ever you use.

Regards

WCI

Re: Not able to login with any user

Mark McDonald_2 — Mon, 08 Dec 2008 05:50:42 GMT

Has your dns server gone down? as part of the login attempt the server could be failing to reverse lookup the ip that you are logging in from, causing the login attempt to hang.

Re: Not able to login with any user

suneel — Mon, 08 Dec 2008 08:38:41 GMT

Hi all,

Thanks for your replies. the system was brought to trusted mode hence it was not working. I made the server to untrusted mode it resolved the issue.

Re: Not able to login with any user

suneel — Mon, 08 Dec 2008 08:42:39 GMT

Thnaks

Re: Not able to login with any user

OldSchool — Mon, 08 Dec 2008 15:38:15 GMT

"Thanks for your replies. the system was brought to trusted mode hence it was not working. I made the server to untrusted mode it resolved the issue."

well, it didn't really. it fixed a symptom. most likely, everybody that couldn't log in had password longer than 8 characters. during the transition to trusted, they go truncated to 8 characters.

in untrusted mode, anything after the 8th character is simply ignored (i believe). after the conversion, only 8 are known, and the remainder are not ignored. so if user continued to used say 10 characters, it wouldn't be accepted.