Operating System - HP-UX
1833538 Members
2974 Online
110061 Solutions
New Discussion

Re: How to handle this error: Init: Command is respawning too rapidly.......

 
Jeffrey Shannon
Contributor

How to handle this error: Init: Command is respawning too rapidly.......

I installed 11.i onto an older k-class server and I am receiving the following error:
Init: Command is respawning too rapidly.
id: samd "/usr/sam/lbin/samd #system mgmt daemon"

4 REPLIES 4
Alex Glennie
Honored Contributor

Re: How to handle this error: Init: Command is respawning too rapidly.......

The error can be stopped by commenting out the line in the /etc/inittab
file until the lan/networking information is configured.

#ups::respawn:rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf
#samd:23456:respawn:/usr/sam/lbin/samd # system mgmt daemon
ems1::bootwait:/sbin/rm -f /etc/opt/resmon/persistence/runlevel4_flag
ems2::bootwait:/sbin/cat /etc/opt/resmon/persistence/reboot_flag
ems3:3456:wait:/usr/bin/touch /etc/opt/resmon/persistence/runlevel4_flag
ems4:3456:respawn:/etc/opt/resmon/lbin/p_client

NOTE:
The init q command must be issued for the changes to the
/etc/inittab file to be re-read and to take effect.

This error is being generated because the system was installed as a standalone,
without configuring the network card or network settings. The sam daemon (samd)
is not able to resolve the hostname and network configuration. A look at
the /etc/hosts file showed only 2 entries:

127.0.0.1 server1
127.0.0.1 localhost loopback

This issue is resolved by configuring the lan card and network settings
A. Clay Stephenson
Acclaimed Contributor

Re: How to handle this error: Init: Command is respawning too rapidly.......

Hi:

I fould this thread which seems to be your problem; it was related to not having the hosts file properly configured.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x2907c7af36b7d5118ff10090279cd0f9,00.html

If it ain't broke, I can fix that.
Santosh Nair_1
Honored Contributor

Re: How to handle this error: Init: Command is respawning too rapidly.......

This typically happens because initd it trying to start some process and it can't. Since the process is set up to respaw, initd try again and again...so to slow it down, init waits 5 minutes hoping that things will be fixed by then.

First start by commenting out the line starting the samd, i.e. the line with /usr/sam/lbin/samd in /etc/inittab. Then tell initd to reread the configuration file (init q). Then try to debug why the samd process will not start...start by looking at syslog.

Hope this helps.

-Santosh
Life is what's happening while you're busy making other plans
Sanjay_6
Honored Contributor

Re: How to handle this error: Init: Command is respawning too rapidly.......