Not getting password prompt on console

[bk9000]

There is a RX6600 server which is not accessible from network or from console .

Everytime it gives the Console login prompt but doesnt provide password prompt , instead the login prompt reappears .

I am able to login to single user mode however for most of the commands , the system is throwing error message

Bus Error(coredump).

There is no ignite backup available . Please provide your valuable suggestions

[Matti_Kurkela]

That would seem like a hardware failure of some sort.

Do you have ANY type of backup of the system? An Ignite backup would have been the most convenient in case the system disk(s) needs to be replaced, but installing a basic OS from installation media, installing a backup/restore client, and then restoring the system directories from the last full backup could be a viable option too - it's just more work (and chance for mistakes) than restoring an Ignite backup.

But thinking about restoration is getting ahead of ourselves. First we need to get the server diagnosed and any faults fixed.

The server's top cover includes a diagnostic panel with a LED for each major internal component. Dark is good, amber is bad. What can you see?

If you press Control-B on the console, you should be able to access the iLO2 Management Processor, which has the hardware error logs. The commands are two-character combinations: MA for MAin menu, then SL for Show Logs, then select which logs specifically you want to view. By default, the logs are displayed in Keyword mode which is useful for HP(e) engineers, but rather cryptic for mere mortals. Press T when actually viewing the logs to switch them into Text mode, which might be more informative.

If the Management Processor has not been configured, you might need the factory default MP username/password to access it: it's username Admin, password Admin (note capitalization).

There is one more diagnostic tool: the Offline Diagnostic Environment.

https://support.hpe.com/hpsc/doc/public/display?docId=c02914985

[bk9000]

Hi Matti

As I said , I can login to the MP and go to single user mode without any issues .

However whenever I do a init 3 or let the system boot without interruption , I m stuck at the login prompt as I dont get the password prompt at all .

As soon I hit enter after entering username , I again get the Console Login prompt .

I even tried mentioning both username and password together in username@\ password but it doesnt work .

Also the server is not accessible through ssh as it gives connection refused error .

In single user mode , it gives the Bus Error(coredump) for most commands including ls -l or ll .

I dont have a ignite backup for this server .

[Bill Hassell]

This sounds like a possible chmod error, possibly someone trying to 'improve' security by changing the permissions on / and /usr. The worst command would be a chmod -R and could create the most damage. Since you can get a running shell in single user mode, the special directory /sbin may not have been impacted. Try this command:

# /sbin/ls -ld /*
dr-xr-xr-x   4 bin        bin          16384 Oct 31 15:16 /bin/
drwxr-xr-x   2 root       sys             96 Oct 20  2014 /cdrom/
dr-xr-xr-x  23 bin        bin           8192 Oct 31 17:04 /dev/
drwxr-xr-x   2 root       sys             96 Oct 20  2014 /dvd/
dr-xr-xr-x  42 bin        bin           8192 Nov 29 19:02 /etc/
drwxr-xr-x  11 root       root          8192 Sep  1  2016 /home/
dr-xr-xr-x  38 bin        bin           8192 Oct 31 15:16 /lib/
drwxr-xr-x   2 root       root            96 Oct 17  2014 /lost+found/
dr-xr-xr-x   1 root       root             1 Oct 31 17:01 /net/
dr-xr-xr-x  119 bin        bin           8192 Oct 31 15:20 /opt/
drwxr-xr-x  17 root       sys           8192 Nov 29 19:19 /root/
dr-xr-xr-x  16 bin        bin           8192 Oct 31 15:17 /sbin/
dr-xr-xr-x   9 bin        bin           8192 Nov 15 09:22 /stand/
dr-xr-x--x   3 root       sys             96 Oct 20  2014 /tcb/
drwxrwxrwt  10 root       root          8192 Nov 29 19:19 /tmp/
dr-xr-xr-x  22 bin        bin           8192 Oct 18  2014 /usr/
dr-xr-xr-x  32 bin        bin           8192 Nov 15 09:22 /var/

For /usr it should look something like this:

# /sbin/ls -ld /usr/*
drwxr-xr-x  20 adm        adm           8192 Oct 31 17:01 /usr/adm/
dr-xr-xr-x   4 bin        bin          16384 Oct 31 15:16 /usr/bin/
dr-xr-xr-x   6 bin        bin             96 Oct 17  2014 /usr/ccs/
dr-xr-xr-x   6 bin        bin             96 Oct 17  2014 /usr/conf/
dr-xr-xr-x  15 bin        bin           8192 Oct 17  2014 /usr/contrib/
dr-xr-xr-x   4 bin        bin             96 Oct 17  2014 /usr/dt/
dr-xr-xr-x   3 bin        bin           8192 Aug 21 11:44 /usr/etc/
dr-xr-xr-x   7 bin        bin             96 Oct 17  2014 /usr/examples/
dr-xr-xr-x  24 bin        bin           8192 Aug 21 11:55 /usr/include/
dr-xr-xr-x   3 bin        bin             96 Oct 17  2014 /usr/keysh/
dr-xr-xr-x   9 bin        bin           8192 Aug 21 12:29 /usr/lbin/
dr-xr-xr-x  38 bin        bin           8192 Oct 31 15:16 /usr/lib/
dr-xr-xr-x  17 bin        bin           8192 Aug 30 12:32 /usr/local/
drwxr-xr-x   2 root       root            96 Oct 17  2014 /usr/lost+found/
dr-xr-xr-x  33 bin        bin           8192 Oct 23  2014 /usr/man/
dr-xr-xr-x  10 bin        bin           8192 Oct 17  2014 /usr/newconfig/
drwxrwxrwt   2 bin        bin             96 Oct 18  2014 /usr/news/
dr-xr-xr-x   4 bin        bin             96 Oct 17  2014 /usr/obam/
dr-xr-xr-x   3 bin        bin             96 Oct 17  2014 /usr/old/
drwxrwxrwt   2 bin        bin             96 Nov 11  2014 /usr/preserve/
dr-xr-xr-x   2 bin        bin             96 Oct 17  2014 /usr/pub/
dr-xr-xr-x   8 bin        bin           8192 Oct 17  2014 /usr/sam/
dr-xr-xr-x   7 bin        bin          16384 Aug 21 12:29 /usr/sbin/
dr-xr-xr-x   8 bin        bin           8192 Oct 17  2014 /usr/share/
dr-xr-xr-x  13 bin        bin           8192 Mar 13  2015 /usr/spool/
drwxrwxrwt  12 root       root          8192 Nov 29 19:24 /usr/tmp/
dr-xr-xr-x   8 bin        bin           8192 Oct 17  2014 /usr/tsm/
dr-xr-xr-x   4 bin        bin             96 Oct 17  2014 /usr/vue/

Compare the first column permission values with your system. These are the correct and most secure permissions for these directories. /usr/bin and /usr/lib are critical directories. If the above directories do not match, there is a possibility that a chmod -R command has ruined all the executable. Here are some selected commands that must have the listed permissions:

# /sbin/ls -l /usr/bin/login /usr/bin/passwd /usr/bin/sh
-r-sr-xr-x   1 root       bin         161356 Mar 15  2011 /usr/bin/login
-r-sr-xr-x   4 root       bin         151400 May  3  2013 /usr/bin/passwd
-r-xr-xr-x   2 bin        bin         683104 Jul 31  2014 /usr/bin/sh

If your permissions do not match, there is a possibility that all of the files have been damaged. If you have another HP-UX system, you could try changing the permissions on the files in /usr/bin and /usr/lib to match your other system. NOTE: /usr/bin = 500 files /usr/lib = 10,000 files

This system may be unusable and impractical to repair. The only solution would be a reinstall of HP-UX. If you have no backup of any kind, you'll have to then add all the patches, applications, databases, etc.

[bk9000]

Thanks for the reponse Bill .

I can't check the permissions as ls -l or ll is throwing below error  .

Bus Error(coredump).

I can only do ls .

[Bill Hassell]

Sorry I wasn't clear for the two examples.
The command to use:

/sbin/ls -ld /

and

/sbin/ls -ld /usr

When you type ls by itself, the shell adds the path for you and you'll get /usr/ls.

I have edited my previous response to show the fullpath name.

[Dennis Handly]

> Bus Error(coredump).

Can you run file(1) on the core?  Can you run gdb?