<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re:  INIT: Command is respawning too rapidly. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127060#M448949</link>
    <description>Sorry, I'm on the other side of the globe (= very different time zone) and actually on my summer vacation, so I won't answer to any work-like phone calls nor chat requests... &lt;BR /&gt;I'll answer what I can, whenever I can, but I won't spoil my long-awaited vacation over this.&lt;BR /&gt;&lt;BR /&gt;Here's what I noticed from the startup output:&lt;BR /&gt;&lt;BR /&gt;---------&lt;BR /&gt;/dev/vg01/oracle_9i :&lt;BR /&gt;vxfs fsck: sanity check: /dev/vg01/oracle_9i needs checking&lt;BR /&gt;vxfs fsck: fsck read failure bno = 4583504, off = 0, len = 2048&lt;BR /&gt;full file system check requir&lt;BR /&gt;/dev/vg01/lvolopt :&lt;BR /&gt;vxfs fsck: sanity check failed: read of super-block on /dev/vg01/lvolopt failed:&lt;BR /&gt;I/O error&lt;BR /&gt;cannot open device /dev/vg01/lvolopt&lt;BR /&gt;file system check failure, aborting ... &lt;BR /&gt;[...]&lt;BR /&gt;/dev/vg01/lvolusr :&lt;BR /&gt;vxfs fsck: sanity check failed: read of super-block on /dev/vg01/lvolusr failed:&lt;BR /&gt;I/O error&lt;BR /&gt;cannot open device /dev/vg01/lvolusr&lt;BR /&gt;file system check failure, aborting ... &lt;BR /&gt;----------&lt;BR /&gt;&lt;BR /&gt;Your vg01 has apparently taken some major damage. Unfortunately, your /usr and /opt filesystems seem to be on the damaged portions of vg01, so this damage has seriously crippled the OS.&lt;BR /&gt;&lt;BR /&gt;If /usr is not available, that explains the "INIT: Command is respawning too rapidly" error messages. The console login prompt is produced by /usr/sbin/getty, and that obviously cannot run if /usr is not there. That also would explain why most of the startup scripts are failing: they require /usr/bin/ksh or some other tools from /usr to execute successfully.&lt;BR /&gt;&lt;BR /&gt;Basically, you have two ways to access the machine now: either get it to boot to single-user mode or start it up using the recovery mode of the installation CD. Both of these require a working console. Your vg00 seems to be fine, so the single-user boot should still provide you with a shell access.&lt;BR /&gt;&lt;BR /&gt;You probably must TOC the server again to get it to boot to single-user mode: the current state seems like a dead-end. As there is no getty running on the console, the system is incapable of receiving any meaningful input from the console.&lt;BR /&gt;&lt;BR /&gt;Exactly how did you get the console messages (in the message you posted at Aug 29, 2008 19:35:32 GMT)?&lt;BR /&gt;&lt;BR /&gt;Does the server have a display and/or PS/2 keyboard connected? If it has, try using them instead of/in addition to Hyperterminal &amp;amp; serial cable: the system might prefer them over a serial console. &lt;BR /&gt;&lt;BR /&gt;If that does not help, disconnect any PS/2 mouse/keyboard from the server, make sure the laptop is connected and Hyperterminal is running, and TOC the server again. Most PA-RISC machines with integrated keyboard connector (like the D-class) will automatically switch to accepting input from the serial console port if there is no keyboard directly attached to the machine at the time it's doing self tests.&lt;BR /&gt;&lt;BR /&gt;After successfully getting to the single-user mode, your next problems will be:&lt;BR /&gt;&lt;BR /&gt;- How to get replacement disks, suitable for your old D-class (to replace the failed disk(s) of vg01)&lt;BR /&gt;&lt;BR /&gt;- If the LVs of your vg01 are mirrored, you may be able to recover some of all of the data by activating the vg01 volume group with "vgchange -q n -a y vg01". But you should prepare to restore from backups. (You *do* have backups, right?)&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Sat, 30 Aug 2008 07:52:35 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2008-08-30T07:52:35Z</dc:date>
    <item>
      <title>INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127021#M448910</link>
      <description>INIT: Command is respawning too rapidly.&lt;BR /&gt;Will try again in 5 minutes.&lt;BR /&gt;Check for possible errors.&lt;BR /&gt;id:cons "/usr/sbin/getty console console # system console" &lt;BR /&gt;&lt;BR /&gt;I have checked in the other entries for this viz...&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1231258" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1231258&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1" target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1&lt;/A&gt;&lt;BR /&gt;210736891995+28353475&amp;amp;threadId=897949&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1" target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1&lt;/A&gt;&lt;BR /&gt;210737039282+28353475&amp;amp;threadId=1141996&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1128442" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1128442&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=953916" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=953916&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;And all the others I could get under the following link...&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www11.itrc.hp.com/service/james/search.do?searchtext=INIT%3A+command+is+respawning+too+rapidly&amp;amp;submit.x=7&amp;amp;submit.y=5&amp;amp;hpl=1&amp;amp;todo=search&amp;amp;searchcriteria=allwords&amp;amp;from=forums&amp;amp;searchcategory=ALL&amp;amp;rn=25&amp;amp;presort=rank&amp;amp;source=7000&amp;amp;esc=support.itrc.hp.com&amp;amp;wpa=forums11.itrc.hp.com%3A80&amp;amp;origin=0&amp;amp;chkServStor=on" target="_blank"&gt;http://www11.itrc.hp.com/service/james/search.do?searchtext=INIT%3A+command+is+respawning+too+rapidly&amp;amp;submit.x=7&amp;amp;submit.y=5&amp;amp;hpl=1&amp;amp;todo=search&amp;amp;searchcriteria=allwords&amp;amp;from=forums&amp;amp;searchcategory=ALL&amp;amp;rn=25&amp;amp;presort=rank&amp;amp;source=7000&amp;amp;esc=support.itrc.hp.com&amp;amp;wpa=forums11.itrc.hp.com%3A80&amp;amp;origin=0&amp;amp;chkServStor=on&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;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:-&lt;BR /&gt;&lt;BR /&gt;INIT: Command is respawning too rapidly.&lt;BR /&gt;Will try again in 5 minutes.&lt;BR /&gt;Check for possible errors.&lt;BR /&gt;id:cons "/usr/sbin/getty console console # system console" &lt;BR /&gt;</description>
      <pubDate>Thu, 28 Aug 2008 20:53:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127021#M448910</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-28T20:53:56Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127022#M448911</link>
      <description>You need to make arrangements to get a console login through MP login.&lt;BR /&gt;&lt;BR /&gt;Once booted in single user mode this issue can be fixed.&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Aug 2008 23:09:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127022#M448911</guid>
      <dc:creator>Deepak Kr</dc:creator>
      <dc:date>2008-08-28T23:09:47Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127023#M448912</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I am able to log in from MP but, now where should i start.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Aug 2008 10:56:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127023#M448912</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-29T10:56:43Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127024#M448913</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Have you Itanium or PARISC system?&lt;BR /&gt;Have you this problem for the first time?&lt;BR /&gt;Any recent changes lately?&lt;BR /&gt;&lt;BR /&gt;Do you know how to get single user mode?&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Fabio</description>
      <pubDate>Fri, 29 Aug 2008 11:46:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127024#M448913</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2008-08-29T11:46:27Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127025#M448914</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;It is a PA-RISC Server and I know how to boot into single user mode.&lt;BR /&gt;&lt;BR /&gt;Actually there was some issue with the NFS mount point.After it was fixed.This error started.&lt;BR /&gt;&lt;BR /&gt;I am in single user mode... &lt;BR /&gt;&lt;BR /&gt;what would be my next steps</description>
      <pubDate>Fri, 29 Aug 2008 12:10:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127025#M448914</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-29T12:10:25Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127026#M448915</link>
      <description>now the system boots and stops at the below error&lt;BR /&gt;&lt;BR /&gt;INIT: Command is respawning too rapidly.&lt;BR /&gt;Will try again in 5 minutes.&lt;BR /&gt;Check for possible errors.&lt;BR /&gt;id:cons "/usr/sbin/getty console console # system console" &lt;BR /&gt;&lt;BR /&gt;unable to ping also</description>
      <pubDate>Fri, 29 Aug 2008 12:53:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127026#M448915</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-29T12:53:36Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127027#M448916</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I guess there is one or more services that is preventing the system to complete the startup phase.&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Fabio</description>
      <pubDate>Fri, 29 Aug 2008 12:58:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127027#M448916</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2008-08-29T12:58:50Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127028#M448917</link>
      <description>Just to clear better what I suggested:&lt;BR /&gt;&lt;BR /&gt;- put set -x on top of /sbin/rc script;&lt;BR /&gt;- run rc script in single user mode:&lt;BR /&gt;cd /sbin&lt;BR /&gt;./rc&lt;BR /&gt;&lt;BR /&gt;HTH.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Fabio</description>
      <pubDate>Fri, 29 Aug 2008 13:00:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127028#M448917</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2008-08-29T13:00:20Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127029#M448918</link>
      <description>According to your last thread this is an old D-class server - why don't you tell this?&lt;BR /&gt;&lt;BR /&gt;Do as advised and also check the console settings (graphical vs. serial).</description>
      <pubDate>Fri, 29 Aug 2008 13:02:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127029#M448918</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-08-29T13:02:00Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127030#M448919</link>
      <description>Now I get WARN EF00 on the console</description>
      <pubDate>Fri, 29 Aug 2008 14:10:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127030#M448919</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-29T14:10:50Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127031#M448920</link>
      <description>&amp;gt;Now I get WARN EF00 on the console&lt;BR /&gt;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?&lt;BR /&gt;&lt;BR /&gt;Please clear better.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Fabio</description>
      <pubDate>Fri, 29 Aug 2008 14:20:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127031#M448920</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2008-08-29T14:20:25Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127032#M448921</link>
      <description>Actually I do not see any messages on my laptop which I have connected using a Serial Cable...&lt;BR /&gt;&lt;BR /&gt;I have done a TOc of the server and hard booted it.&lt;BR /&gt;&lt;BR /&gt;After some time I get the following &lt;BR /&gt;"RUN F2F" &lt;BR /&gt; D380       CPU 01&lt;BR /&gt;&lt;BR /&gt;On the front display pannel...&lt;BR /&gt;&lt;BR /&gt;I do not get anything on my Hyperterminal... It is just blanc</description>
      <pubDate>Fri, 29 Aug 2008 14:40:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127032#M448921</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-29T14:40:39Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127033#M448922</link>
      <description>It sounds like it is doing lower HW tests.&lt;BR /&gt;I don't know those messages but I'd suspect also HW problems.&lt;BR /&gt;&lt;BR /&gt;Hope it's not so.</description>
      <pubDate>Fri, 29 Aug 2008 14:50:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127033#M448922</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2008-08-29T14:50:14Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127034#M448923</link>
      <description>but to collect any logs... I should be able to see something on my laptop[which I have connected using a serial cable]&lt;BR /&gt;&lt;BR /&gt;when i hard boot it  I get -----fffS^ on the screen and nothing else...&lt;BR /&gt;&lt;BR /&gt;I am struck there and dont know what to do</description>
      <pubDate>Fri, 29 Aug 2008 15:06:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127034#M448923</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-29T15:06:51Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127035#M448924</link>
      <description>"RUN F2F"&lt;BR /&gt;D380 CPU 01&lt;BR /&gt;&lt;BR /&gt;Those messages are normal for a D box.&lt;BR /&gt;&lt;BR /&gt;The "RUN F2F" basically means the system is up and running normally.&lt;BR /&gt;&lt;BR /&gt;"D380 CPU 01" is telling you the model of the server and that you have 2 CPUs, 0 &amp;amp; 1.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Aug 2008 15:07:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127035#M448924</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2008-08-29T15:07:28Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127036#M448925</link>
      <description>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 ).&lt;BR /&gt;&lt;BR /&gt;Somewhere it will either stop with an error, or record the last code before the error, or it may say run (i think).&lt;BR /&gt;&lt;BR /&gt;Your userguide for this server may have the code definitions.&lt;BR /&gt;&lt;BR /&gt;With init having respawing messages I would suspect some serial card, mux, or other same type of device or loose cable.&lt;BR /&gt;&lt;BR /&gt;As a start, start unplugging external devices/cables until you can reduce to a working system.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Aug 2008 15:13:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127036#M448925</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2008-08-29T15:13:19Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127037#M448926</link>
      <description>but to see where i error lies or any other issue with the server... I need to check the logs...&lt;BR /&gt;&lt;BR /&gt;Here the case is I cannot get to the console itself...&lt;BR /&gt;&lt;BR /&gt;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^&lt;BR /&gt;&lt;BR /&gt;I am thinking wat else I can do to see the error logs or check the core dump&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Aug 2008 16:26:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127037#M448926</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-29T16:26:27Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127038#M448927</link>
      <description>The possible system states are listed below.&lt;BR /&gt;â ¢ FLT - A hardware error has been detected&lt;BR /&gt;â ¢ TEST - Hardware being tested&lt;BR /&gt;â ¢ INIT - Hardware being initialized&lt;BR /&gt;â ¢ SHUT - System being shutdown&lt;BR /&gt;â ¢ WARN - A non-optimal operating condition exist&lt;BR /&gt;â ¢ RUN - System is running the operating system&lt;BR /&gt;When the system is operating normally, the RUN message should display.&lt;BR /&gt;&lt;BR /&gt;don't know if the codes are the same as on a "k", but for k's:&lt;BR /&gt;fxnf means:&lt;BR /&gt;(HP-UX) Indicates the system is running. An F in the first and fourth digits indicates the system is running normally. &lt;BR /&gt;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. &lt;BR /&gt;The n indicates the number of processors (1 or 2). &lt;BR /&gt;&lt;BR /&gt;as far as the EF00, there are no codes that start with E on a k (E not used)</description>
      <pubDate>Fri, 29 Aug 2008 16:37:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127038#M448927</guid>
      <dc:creator>blah2blah</dc:creator>
      <dc:date>2008-08-29T16:37:35Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127039#M448928</link>
      <description>Now as per the display on the front Pannel.. I can assume that the system is running normally... RUN F02F..&lt;BR /&gt;&lt;BR /&gt;But I am unable to ping it&lt;BR /&gt;Unable to telnet it...&lt;BR /&gt;&lt;BR /&gt;And when I connect a laptop using a serial port I do any get any messages on my hyperterminal...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Aug 2008 16:41:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127039#M448928</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-29T16:41:19Z</dc:date>
    </item>
    <item>
      <title>Re:  INIT: Command is respawning too rapidly.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127040#M448929</link>
      <description>You talked about a graphical console earlier - is this still connected?</description>
      <pubDate>Fri, 29 Aug 2008 16:43:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-command-is-respawning-too-rapidly/m-p/5127040#M448929</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-08-29T16:43:39Z</dc:date>
    </item>
  </channel>
</rss>

