Sponsored Content
Operating Systems HP-UX Root account disabled and unable to access console Post 73305 by AaronC on Tuesday 31st of May 2005 05:43:32 AM
Old 05-31-2005
Root account disabled and unable to access console

Hi, hope someone could help me here:

Our root account was disabled on our production server this morning and usually we would login at the console to re-enable the account. However we are unable to get a login prompt at the console. The console displays the 8 options along the bottom and a cursor but no login prompt. We are able to login via telnet sessions but not as root.

I have tried holding down the 'd' key while switching the console on and the "Remote Mode" option has a '*' next to it. There is a console getty process running but I am unable to kill this as it is owned as root:

root 2796 1 0 May 25 console 0:00 /usr/sbin/getty console console

Can anyone advise how this can be resolved? Ideally we would like to get the console issue resolved first as we will need root access to shut down the applications running on the machine prior to any rebooting.

We are running HP-UX 11.00 on an L2000.

Thanks.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

create or modify user account to have same access as root

Is there a way to create or better yet modify a user account so it has the same privs as root? (6 Replies)
Discussion started by: xadamz23
6 Replies

2. UNIX for Dummies Questions & Answers

How do i access (mount, read & write) a floppy disk from the console, not being root?

welll, the title quite explains what i want to do thanks for your time! (4 Replies)
Discussion started by: kfaday
4 Replies

3. UNIX for Dummies Questions & Answers

Change other account password from root access

Hi, I have forgotten my personal account password but I still have the root access to the box. Please tell me how can I change my other account password by logging as root. Thanks. Rakesh :D (4 Replies)
Discussion started by: rakeshou
4 Replies

4. HP-UX

PAM status 28 - account disabled

I frequently rexec into a remote box to run a job, occaisionally I get the the error message "rexecd: Account Disabled" and in the remote box syslog I see "rexecd: PAM - status 28 PAM error message: account is disabled". After a 1/2 hour or so the problem goes away. Anyone shed any light on... (0 Replies)
Discussion started by: CBorgia
0 Replies

5. HP-UX

root - "Account is disabled"

Hi. I have an issue with root account. System doesn't let me to log on, because accound is disabled/locked. This problem since I have converted passwords file to data base using SAM. I didn't change user's parameters. Somebody knows how can i enable my root account back? (14 Replies)
Discussion started by: netwalker
14 Replies

6. Solaris

Sun Fire V890 - Unable to access RSC or Serial console

Hello Folks, I am having trouble to login to rsc or serial console of V890. The rsc2.2.3 has been configured with required parameters, resetrs and even rebooted. When serial port is connected to laptop, The hyper terminal does not get the console or POSt messages when the server is rebooting... (8 Replies)
Discussion started by: defflepord
8 Replies

7. Solaris

E25k domain server am unable to access console.

Hi Guys, I am working on the e25k server. There is 4 domain configured Once domain is down So I tried to access the console for the problem domain. using console -d B but its showing following error message. bash-2.05$ console -d B Domain administration permissions... (3 Replies)
Discussion started by: arumsun
3 Replies

8. AIX

P550 Unable to access Console

I have recently aquired the following machine: IBM,9113-550 Up until yesterday we could connect a dumb terminal to serial port 1 and get console login. However the dumb terminal died. We are now using a laptop with a null modem cable attached to serial port 1. This works perfectly for all of... (1 Reply)
Discussion started by: rsw7724
1 Replies

9. AIX

How to access root from console even if loginretries already reached

Hi, I wanted to know whether there is a setting in AIX to allow console login eventhough loginretries have already reached. What I mean is that loginretries applies to ssh/telnet connection but I can still login in console even after loginretries have been reached. Thanks. (2 Replies)
Discussion started by: depam
2 Replies

10. SCO

SCO 5.0.7 server - Message - Root Account is disabled - but allowing entry via daemon.

SCO 5.0.7 server on an HP Proliant ML350G5 with E200 raid controller. The message on the server during boot says this message in several places. "Root Account Disabled, but allowing entry via deamon" At this point, there are some hardware issues to work through first. One is that we don't... (2 Replies)
Discussion started by: cjdavis618
2 Replies
login(1)						      General Commands Manual							  login(1)

NAME
login - Signs the user on to the system SYNOPSIS
login [-p] [-h host] [[-f] user] The login command is used when a user initially signs on to the system and also by daemons, such as ftp, to create a user's environment. This security-sensitive command uses the Security Integration Architecture (SIA) routine as an interface to the security mechanism(s) that perform the actual user validation. See the matrix.conf(4) reference page for more information. OPTIONS
With the exception of -p, these options are available only to the superuser. Used by telnetd and other servers to list the host from which the connection was received. Used with a user name user on the command line to indicate that proper authentication was already done, and that no password needs to be requested. Causes the remainder of the environment to be preserved; otherwise, any previous environment is discarded. DESCRIPTION
The invocation of login for initial signon is made by a system program or server using the privileged -h and -f forms of the login command. If login is invoked without an argument, it asks for a user name, and, if appropriate, a password. Echoing is turned off (if possible) during the entering of the password, so it will not appear on the written record of the session. After a successful login, accounting files are updated. You are informed of the existence of mail, and the message of the day and the time of last login are displayed. The mail message, the message of the day, and the last login time are suppressed if there is a file in the home directory; this is mostly used to make life easier for users such as uucp. Security Note If you have enhanced security installed on your system, the login command prints the last successful and unsuccessful login times and ter- minal devices. If the account does not have a password and the authentication profile for the account requires one, login starts the passwd command to establish one for the account. The login command prohibits you from logging in if any of the following are true: The password for the account has expired and you cannot successfully change the password. The password lifetime for the account has passed. The administrative lock on the account was set. The maximum number of unsuccessful login attempts for the account was exceeded. The maximum number of unsuccessful login attempts for the ter- minal was exceeded. The administrative lock on the terminal was set. The terminal has an authorized user list and you are not on it. The terminal has time of day restrictions and the current time is not within them. The account was retired by the system administrator. The login command initializes the user and group IDs and the working directory, and then executes a command interpreter according to spec- ifications found in the password file. Argument 0 (zero) of the command interpreter is the name of the command interpreter with a leading - (dash). The login command also modifies the environment with information specifying home directory, command interpreter, terminal type (if avail- able), and user name. Security Note If you have enhanced security installed on your system, the login command always allows root to log in at the console to avoid the situa- tion where all accounts and terminals are locked. If either /etc/nologin_hostname or /etc/nologin exists, login prints the contents on your terminal and exits. The shutdown command creates /etc/nologin_hostname (or /etc/nologin in the case of a clusterwide shutdown) to stop users from logging in when the system or cluster is about to go down. Login is recognized by sh, csh, and ksh and executed directly (without forking). ERRORS
The user name or the password is invalid. Consult your system administrator. Security Note If you have enhanced security installed on your system, you may see the following diagnostic messages: The login command cannot invoke the passwd program. The passwd program is invoked, the user is unable to change the password, and the account requires one. is allowed The login command is allowing a root login at the system console, despite a condition that would normally not allow such a login. The account is locked for one of the reasons previously listed. The terminal is locked for one of the reasons previously listed. You are not on the authorized user list for the terminal. The current time is not within the current time-of-day restrictions for the terminal. After an unsuccessful login attempt, login waits a specified (configurable) amount of time before it prompts for another login attempt. If the account's password was changed by another user, login prints the time the password was changed and the user who changed it. If your password is about to expire, login warns you of the time of the impending expiration. Your system administrator sets the warning period. FILES
Contains user and accounting information. Contains login history. Contains last login time stamps. Mail directory. Message of the day. Contains user information. Stops logins. In a cluster, /etc/nologin is used instead. Suppresses mail notification, message of the day, and last login time. SEE ALSO
Commands: binmail(1), chfn(1), chsh(1), getty(8), init(8), Mail(1), mail(1), mailx(1), passwd(1), rlogin(1), shutdown(8) Function: getpass(3) Files: matrix.conf(4), passwd(4), utmp(4) Security login(1)
All times are GMT -4. The time now is 06:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy