Awesome problem: I can not login in HP UX

[Juan Vicente]

Hi all:

First to all, thanks a lot for your help!

That is my problem:
When I start up my Itanium-based machine, in the HP-UX Start-up progress are a few errors (see the rc.log below) There are some daemons that have an output like this: "pid xxxx killed due to text modification or page I/O error, see /etc/issue" and fail to start.

So, when start up ends, I put my user (even root) and password, and System return me the same error. I only can enter to the Itanium through X-manager.
This is the rc.log (some files are deleted)

**************************************************
HP-UX Start-up in progress
Wed Feb 1 08:03:08 WET 2006
**************************************************

Configure system crash dumps
Output from "/sbin/rc1.d/S080crashconf start":
----------------------------
EXIT CODE: 0

VxVM device node check
Output from "/sbin/rc1.d/S091vxvm-nodes-check start":
----------------------------

VxVM general startup
Output from "/sbin/rc1.d/S092vxvm-startup start":
----------------------------
Save system crash dump if needed
Output from "/sbin/rc1.d/S440savecrash start":
----------------------------
savecrash directory not set; defaulting to: /var/adm/crash
EXIT CODE: 2 - savecrash found no core dump to save
"/sbin/rc1.d/S440savecrash start" SKIPPED

Start evp
Output from "/sbin/rc1.d/S450evp.init start":
----------------------------
Start Internet services daemon
Output from "/sbin/rc2.d/S500inetd start":
----------------------------
/sbin/rc2.d/S500inetd[47]: 1380 Bus error(coredump)
EXIT CODE: 138
Unable to start Internet Services
"/sbin/rc2.d/S500inetd start" FAILED

Start dynamic routing daemon
Output from "/sbin/rc2.d/S510gated start":
----------------------------
"/sbin/rc2.d/S510gated start" SKIPPED
Start clock daemon
Output from "/sbin/rc2.d/S730cron start":
----------------------------
/sbin/rc2.d/S730cron[49]: 2206 Bus error(coredump)
ERROR CODE 138
"/sbin/rc2.d/S730cron start" FAILED

Start pty allocator daemon
Output from "/sbin/rc2.d/S230ptydaemon start":
----------------------------
Starting the ptydaemon
/sbin/rc2.d/S230ptydaemon[48]: 787 Bus error(coredump)
EXIT CODE: 138
"/sbin/rc2.d/S230ptydaemon start" FAILED

[Steven E. Protter]

Shalom,

If you can log on, even if just in X, do this:

tail -f /var/adm/syslog/syslog.log

Then try a normal network login.

You will get useful information to act on from syslog.

Could be a number of things, but the ptydaemon issue tells me maybe your terminal files are corrupt.

insf -e

Boot,

Try again.

SEP

[Yogeeraj_1]

hi Juan,

seems like the INETD is failing to start. What did you do before you started to get this problem? Any new installation/configuration?

please revert

kind regards
yogeeraj

[Ivan Ferreira]

Last time I had "bus error" I lost the connection to the physical disks. Ensure that you don't have hardware or disk failures, and the connections are good.

[Ajitkumar Rane]

Juan,

Starting the ptydaemon
/sbin/rc2.d/S230ptydaemon[48]: 787 Bus error(coredump)
EXIT CODE: 138
"/sbin/rc2.d/S230ptydaemon start" FAILED

the pty daemon is related to the login for telnet sessions. that it self is having an error. Since it is showing a bus error seems you need to log a call wiht HP

Rgds,

Ajit

[Peter Godron]

Juan,
all the times I received text modification or page I/O errors I could not find any log details, however I suspected a hardware problem with swap.
So I created a new swap area, removed the old and it worked.

Hope this helps.

[Robert-Jan Goossens]

Hi Juan,

There seems to be a problem with the /etc/inetd.conf file (as this is the first error). Try to boot into single user mode, check the inetd.conf file for errors.

To boot into single user mode (itanium)

See if you can open next doc.

Title: Booting IA64 systems manually
Document ID: IA64UXKBRC00014416

US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079994917

Europe
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079994917

Itterupt the boot procces to interact with the EFI shell

Manual boot of IA (IA-64) system

interrupt the autoboot process, select option to go to EFI shell or interrupt the bootloader.

If the boot interrupted at the EFI, then check/determine the EFI boot partition, by checking the output of map, dh, and set

Shell> dh
Shell> map
Shell> set

once you determine or find the boot device with the FAT32 (or FAT64). For the purpose of this documentation we will assume the boot disk has the mapping name of fs2

change to that FAT (FAT32 or FAT64) filesystem partition by typing

fs2:

at the EFI shell prompt as below

Shell> fs2:

this will bring you to the fs2 partition with the prompt as below.

fs2:\>

SINGLE USER MODE
fs2:\> hpux -is

You can either choose to interrupt the boot process at this point or just let it go. I will recommend that you interrupt it at this point otherwise it might go to default mode as noted in AUTO file.

If you interrupt it then it will go to the bootloader prompt

HPUX>

At this prompt, type boot -is

HPUX> boot vmunix -is

Regards,
Robert-Jan

[Bill Hassell]

The errors:

/sbin/rc2.d/S500inetd[47]: 1380 Bus error(coredump)
/sbin/rc2.d/S730cron[49]: 2206 Bus error(coredump)
/sbin/rc2.d/S230ptydaemon[48]: 787 Bus error(coredump)

indicate that something has corrupted the executables. Since inetd did not start, virtually all your network connections are dead. Did someone restore some files into the /usr directory recently, perhaps using a backup tape from a PA-RISC machine?