How to solved the "Access Denied" for Celladmin User

Asset ID:	1-71-1428394.1
Update Date:	2013-02-07
Keywords:

Solution Type Technical Instruction Sure

Solution 1428394.1 : How to solved the "Access Denied" for Celladmin User

Applies to:

Exadata Database Machine X2-2 Hardware - Version All Versions and later
Information in this document applies to any platform.

Goal

When signing on the Exadata Storage cell as the celladmin user, you may experience an access denied error. As the root user on the same storage cell, you are able to successfully switch user (su) to the celladmin user. However, on issuing a "usermod -U celladmin" command you may still be unable to signon as celladmin

This document describes why you may get an access denied error and how to resolved this.

Fix

You are getting the "access denied error" because the login of this user was tried with incorrect password and the account was locked.

In order to unlock the account to do the following steps :

1. Log on as root user.

2. Look at the permitted login failure attempts:

[root@cell1 ~]# cat /etc/pam.d/sshd | grep deny

Example :

auth required pam_tally2.so deny=5 onerr=fail

3. Look at actual failed login attempts and locked out accounts:

[root@cell1 ~]# /sbin/pam_tally2

Example :

Login failures latest failure from
celladmin 26 08/10/10 10:37:23 cell1.server.com
cellmonitor 9 08/10/10 10:26:24 cell1.server.com

In this case, there were 26 failures, but only 5 are permitted, so you need to reset the failure count as shown below.

4. Reset the failure counter for a user:

[root@cell1 pam.d]# /sbin/pam_tally2 --reset=0 -u celladmin

Example :

Login failures latest failure from
celladmin 26 08/10/10 10:37:23 cell1.server.com

Notice the command tells you how many failures occurred before resetting.

5. Verify the account is no longer locked out:

[root@cell1 pam.d]# /sbin/pam_tally2

Example :

Login failures latest failure from
cellmonitor 9 08/10/10 10:26:24 cell1.server.com

Now the celladmin entry is gone meaning 0 failed attempts

6. Try to log on again.

Attachments

This solution has no attachment