Root account is disabled

[Mohd Syafid Abdullah]

Hi Guru,
I have problem when trying to log in using root into my HP-UX 11 Oracle Development server.
The error prompt "account locked in the commercial security database".
Im trying to telnet, also failed.

Can Guru tell me what is going on in my server and how to solve this matter.

Please help.

[Paul_481 · Accepted solution]

Hi,

If your root account is disabled in the OS level, the only solution for you is to go to single user mode and change the password there.

#shutdown -ry 0
interrupt during boot
interact with ISL
ISL> hpux -is

at single usermode
#passwd
change your root password.

Regards,
Paul

[Mohd Syafid Abdullah]

Hi Paul,

Thanks for the solutions.
I try and it works.
Can u explain actually what make the root login locked?
FYI, I do not change the root password quite long time.

TQ

[Paul_481]

Hi,

One probable cause is that your root password expires, root password should not have any expiration.

You can do it on sam or on the commandline.

#/usr/lbin/modprpw -m exptm=0 root

just man modprpw for details.

Regards,
Paul

[Paul_481]

Hi,

The command modprpw is only available in a trusted system. I suggest try to do it in SAM if your system is not trusted.

Regards,
Paul

[Mohd Syafid Abdullah]

Hi Paul,

I can run the command line and thanks for yr solution.

Tq again.

[Florian Heigl (new acc)]

Please check if there are bad logins for root logged in /var/adm/syslog/syslog.log or when issueing the command "lastb"

for example in the following there's on of my systems that was under constant attack of some script kiddies (at 19:59 I got annoyed and shut them out):

# lastb | head
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58
root ssh:notty Wed Feb 16 19:58


if You're running a trusted system too many bad logins could lock the root account.

But hopefully it was some problem with password aging. In any case there should be a info in sys- or auditlogs.