Init: command is respawning too... getty console console

[jasonK_1]

Hi,

I just update the IP in the netconf, /etc/hosts and reboot the system. However, I got INIT: command is respawning too rapidly. Will try again in 5 minutes. Check for possible errors. id:cons "/usr/sbin/getty console consolde"

I already looked through this link http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=623782 but with no success. Any idea?

[Michael Steele_2]

Hi

a) Did you change inittab?
b) Do you have an old copy? If not then refer to /usr/newconfig/etc/inittab
c) Can you get to single user mode? If so review /etc/rc.log and syslog.log.
d) What is "..."/usr/sbin/getty console consolde..." - Is consolde your typo or not a typo? Cuz this may be your problem.

[jasonK_1]

a) Did you change inittab?
No
b) Do you have an old copy? If not then refer to /usr/newconfig/etc/inittab
Yes, but how can I restore it? The system just hang there. Can I restore it from Ignite or from single user mode? I tried Ignite but there is not option for restoring a single file. About single user mode, I got in just fine but how do I mount the tape drive?
If I decided to use the /usr/newconfig/etc/inittab, will it cause other issues?

c) Can you get to single user mode? If so review /etc/rc.log and syslog.log.
/etc/rc.log was created in Oct 1, 2009 -> nothing unusual
syslog.log -> nothing unusual

d) What is "..."/usr/sbin/getty console consolde..." - Is consolde your typo or not a typo? Cuz this may be your problem.
Sorry it's a typo

I forgot to mention before the line INIT: Command is respawning too rapidly, there is a line saying: usage: /sbin/rc {start|stop|start_msg|stop_msg}. I think this line is the cause but I don't know where to look. Please see the attachment picture for detail

[Johnson Punniyalingam]

p_client is the persistence client that is used by the EMS (Event Monitoring Service). It makes sure that the persistent requests stored in the persistence database /etc/opt/resmon/persistence are registered with the EMS registrar that then starts the EMS monitors.

EMS monitors are used by the Online Diagnostic to report events from devices. There are also other monitors for other products available, e.g. Serviceguard, LVM disks, System resources, ATM, Hyperfabric etc.

[Johnson Punniyalingam]

You can Check below Thread

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1258258802730+28353475&threadId=1224828

Check /etc/rc.log & rc.log.old for more information ?why p_client didn't startup ?

>>just update the IP in the netconf<<

This also give bit clue that, suspect you have may made wrong entry ,

you can try boot the server into Single - User mode

cp -p cp -p /etc/rc.config.d/netconf.bk /etc/rc.config.d/netconf

hope you had backup of the netconf & inittab file


you can just revert back above mentioned files and boot server.


Hope this Helps,

Johnson

[Michael Steele_2]

Hi

Restore a single file from ignite like this

mt -f /dev/rmt/?mn rew

mt -f /dev/rmt/?mn fsf 1

tar -xvf /dev/rmt/?mn dir/filename

[jasonK_1]

Hi,

Thanks all...I found the problem. I looked at the last boot which was Oct 1, 2009 and all the files in the /etc/rc.config.d/ that are older than Oct 1, 2009. It turned out on Oct 5 I installed SSH which created two files. So I just moved them somewhere else and the system up now is up. Wew... I am so relieve... I have been reading all over the HP forum and I think I got that idea from a post somewhere

Thanks all,
Jason

[jasonK_1]

Thanks all for helping me on Saturday night :)