Operating System - HP-UX
1753954 Members
7444 Online
108811 Solutions
New Discussion юеВ

Re: We think we have a broken server and need help to find out why

 
Johnson Zhu
Advisor

We think we have a broken server and need help to find out why

According to the Database the alt root password had been set but it did not work!

We attempted to reset it but hit a major obstacle.

We did not have root access to the host, or more correctly the host would not let you enter the root password.

At Console:

login: root
Password:
Account is disabled but console login is allowed.
Login incorrect

Wait for login retry: ..
login: root
Password:
Account is disabled but console login is allowed.
Login incorrect

Telnet fails.

Same behaviour as unprivledged user.

Wait for login retry: ..
login: shielbre
Password:
Login incorrect

ssh to unpriveledged user works

su - just says sorry

mou077 hosts oracledb0832t and oracledb0831d

After advising the Oracle DBA's we renooted the host to try and correct the issue, no change.

We rebooted the host into single user mode - we could still not reset the root password in single user mode either

Eventually I changed the UID on my account to "0" and brought the server back up.

On reboot we also found we could not run SAM or swinstall with the following errors:

Starting the terminal version of sam...

To move around in sam:

- use the "Tab" key to move between screen elements
- use the arrow keys to move within screen elements
- use "Ctrl-F" for context-sensitive help anywhere in sam

On screens with a menubar at the top like this:

------------------------------------------------------
|File View Options Actions Help|
| ---- ---- ------- ------------------------------- ---|

- use "Tab" to move from the list to the menubar
- use the arrow keys to move around
- use "Return" to pull down a menu or select a menu item
- use "Tab" to move from the menubar to the list without selecting a menu item
- use the spacebar to select an item in the list

On any screen, press "CTRL-K" for more information on how to use the keyboard.

Press "Return" to continue...
sam: Couldn't bring up the initial window. This may occur when
you specify an incorrect display.

TERM was set to vt100

I was able to get them to run using the X interface.

We have untrusted the system, nulled the root password and re-trusted the system all to no avail.

Command passwd root gives the following:

root@mou077:#passwd root
Changing password for root
Old password:
Sorry.

and we only type at the end of the command. It is like multiple 's are embedded in the command some how.

I have tried creating a new account and the system will not let you set the password, SAM(X) reset's the password but you do not get any opportunity to enter it.
2 REPLIES 2
Johnson Zhu
Advisor

Re: We think we have a broken server and need help to find out why

This issue has been fixed by doing the following steps. The reason was determined by /dev/tty is corrupted.

1. remove old /dev/tty to /dev/tty.old
2. run insf -e to re-create /dev/tty
crw-rw-rw- 1 bin bin 207 0x000000 May 6 01:37 /dev/tty

Now we are able to change the root passwd and SAM starts functioning.

However we still not allow to log into root with the passwd just changed in the GSP console.

Password: ogtoghutwaxy Hyphenation: og-togh-u-twax-y
Enter password:
Password: dapkodoodibu Hyphenation: dap-kod-ood-ib-u
Enter password:

3. run insf -evd cn to recreate /dev/console
4. There is a reoccurring error keeps showing in the console: id: sfd "/sbin/sfd", to fix it by comment out "#sfd:123456:respawn:/sbin/sfd" in /etc/inittab
5. reboot server

Now everything back to normal. The root password has been changed.

But, I really what to know why caused /dev/tty corrupted? Now I have another server has the exactly same problem. Please help. Thank you in advance.
Dennis Handly
Acclaimed Contributor

Re: We think we have a broken server and need help to find out why

>I really what to know why caused /dev/tty corrupted?

Did you save the ll(1) output for /dev/tty before you recreated it?
It could also have been the getty going bad?