INIT: Command is respawning too rapidly.

[Grayh]

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:cons "/usr/sbin/getty console console # system console"

I have checked in the other entries for this viz...

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1231258

http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1
210736891995+28353475&threadId=897949

http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1
210737039282+28353475&threadId=1141996
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1128442
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=953916

And all the others I could get under the following link...

http://www11.itrc.hp.com/service/james/search.do?searchtext=INIT%3A+command+is+respawning+too+rapidly&submit.x=7&submit.y=5&hpl=1&todo=search&searchcriteria=allwords&from=forums&searchcategory=ALL&rn=25&presort=rank&source=7000&esc=support.itrc.hp.com&wpa=forums11.itrc.hp.com%3A80&origin=0&chkServStor=on

BUt Now the server is in hung state.I cannot login remotely nor when I connect the console... it got hung at the below error:-

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:cons "/usr/sbin/getty console console # system console"

[Deepak Kr]

You need to make arrangements to get a console login through MP login.

Once booted in single user mode this issue can be fixed.

[Grayh]

Hi,

I am able to log in from MP but, now where should i start.

[Fabio Ettore]

Hi,

Have you Itanium or PARISC system?
Have you this problem for the first time?
Any recent changes lately?

Do you know how to get single user mode?

Consider that message could be very generic and not help to a right direction, but getting single user mode it's just a first step.

Best regards,
Fabio

[Grayh]

Hi,

It is a PA-RISC Server and I know how to boot into single user mode.

Actually there was some issue with the NFS mount point.After it was fixed.This error started.

I am in single user mode...

what would be my next steps

[Grayh]

now the system boots and stops at the below error

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:cons "/usr/sbin/getty console console # system console"

unable to ping also

[Fabio Ettore]

Hi,

I guess there is one or more services that is preventing the system to complete the startup phase.
From single user mode you could put a set -x on top of /sbin/rc script (it calls then all rc scripts) and check if there more clues.

Best regards,
Fabio

[Fabio Ettore]

Just to clear better what I suggested:

- put set -x on top of /sbin/rc script;
- run rc script in single user mode:
cd /sbin
./rc

HTH.

Best regards,
Fabio

[Torsten.]

According to your last thread this is an old D-class server - why don't you tell this?

Do as advised and also check the console settings (graphical vs. serial).

[Grayh]

Now I get WARN EF00 on the console

[Fabio Ettore]

>Now I get WARN EF00 on the console
Could you give more details? What do you mean, when do you get that WARN? After start of services, when going to single user mode?

Please clear better.

Best regards,
Fabio

[Grayh]

Actually I do not see any messages on my laptop which I have connected using a Serial Cable...

I have done a TOc of the server and hard booted it.

After some time I get the following
"RUN F2F"
D380 CPU 01

On the front display pannel...

I do not get anything on my Hyperterminal... It is just blanc

[Fabio Ettore]

It sounds like it is doing lower HW tests.
I don't know those messages but I'd suspect also HW problems.

Hope it's not so.

[Grayh]

but to collect any logs... I should be able to see something on my laptop[which I have connected using a serial cable]

when i hard boot it I get -----fffS^ on the screen and nothing else...

I am struck there and dont know what to do

[Patrick Wallek]

"RUN F2F"
D380 CPU 01

Those messages are normal for a D box.

The "RUN F2F" basically means the system is up and running normally.

"D380 CPU 01" is telling you the model of the server and that you have 2 CPUs, 0 & 1.

[Tim Nelson]

With the old D and K servers you need to watch the lcd display.. I do not think you will get any type of console display until self-tests are completed. With an HP terminal it will display the LCD codes on the bottom line ( probably not with a laptop and serial cable ).

Somewhere it will either stop with an error, or record the last code before the error, or it may say run (i think).

Your userguide for this server may have the code definitions.

With init having respawing messages I would suspect some serial card, mux, or other same type of device or loose cable.

As a start, start unplugging external devices/cables until you can reduce to a working system.

[Grayh]

but to see where i error lies or any other issue with the server... I need to check the logs...

Here the case is I cannot get to the console itself...

I have tried changing the cable.. And the same hyperterminal is working on other servers but when it comes to this D380 server... I cant get anything on the console other than ----fffS^

I am thinking wat else I can do to see the error logs or check the core dump

[blah2blah]

The possible system states are listed below.
â ¢ FLT - A hardware error has been detected
â ¢ TEST - Hardware being tested
â ¢ INIT - Hardware being initialized
â ¢ SHUT - System being shutdown
â ¢ WARN - A non-optimal operating condition exist
â ¢ RUN - System is running the operating system
When the system is operating normally, the RUN message should display.

don't know if the codes are the same as on a "k", but for k's:
fxnf means:
(HP-UX) Indicates the system is running. An F in the first and fourth digits indicates the system is running normally.
The x is updated every five seconds with the length of the run queue at that time (an instantaneous reading not an average). It indicates the number of processes. Loads higher than nine display as A.
The n indicates the number of processors (1 or 2).

as far as the EF00, there are no codes that start with E on a k (E not used)

[Grayh]

Now as per the display on the front Pannel.. I can assume that the system is running normally... RUN F02F..

But I am unable to ping it
Unable to telnet it...

And when I connect a laptop using a serial port I do any get any messages on my hyperterminal...

[Torsten.]

You talked about a graphical console earlier - is this still connected?

[blah2blah]

you have a catch 22 there
you need a console to login to fix the problem. to use the console you need a getty. the getty not running is your problem that needs fixing.

you'll have to login some other way, through the lan, put in a console card etc.

do you have another 380 around to work with?

[blah2blah]

your hardware is probably ok
not sure how much of the os will work without a system console. the os is probably running really slow because it is spending most of its time reporting the INIT error. if this has been going on for a long time, you may have a file system filled with big log files

your only fix might be to boot a recovery cd and make you fixes

[Grayh]

Torsten... That's correct...

I have my laptop still connected to the Serial/Console port which I was using since yesterday.


Blah-to-blah..

I do not have another D380... Is there any other way I can connect to get the logs...

There is no Dumb terminial as well..

I was thinking there could be an issue with the serial port itself... I dont know

Is this very Normal in a D-Class Server..What is the best way to avoid these kind of issues in future...(I mean connect using a serial port or any other thing)

I am still wondering how to get the logs

[Grayh]

>e to boot a recovery cd and make you fixes

To boot with a recovery Cd.. I need to log in to the single user mode.. and again for that I need to see the console on my laptop.. so that I can inturrept it at the boot process..

[Torsten.]

There is a way to force the system to use the serial console, but at the moment I can't remember ...

I would take out the graphics card and use putty together with the serial port - restart the system and you will get the serial console...