topic INIT: Command is respawning too rapidly. in Operating System - HP-UX

INIT: Command is respawning too rapidly.

Mike_Ca Li — Mon, 29 Dec 2003 12:50:04 GMT

GenericSysName [HP Release B.11.11] (see /etc/issue)
Console Login: root
Password:
INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:samd "/usr/sam/lbin/samd # system mgmt daemon"

Why I can only login from console? Not network, etc...

Re: INIT: Command is respawning too rapidly.

Mike_Ca Li — Mon, 29 Dec 2003 12:53:48 GMT

Here is the top log:

System: unknown Mon Dec 29 12:53:11 2003
Load averages: 1.43, 1.17, 0.66
25 processes: 23 sleeping, 2 running
Cpu states:
LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
1.43 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%

Memory: 5388K (672K) real, 10056K (1180K) virtual, 41214K free Page# 1/2

TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
? 30 root 152 20 0K 512K run 0:00 0.24 0.24 vxfsd
tty0p0 336 root 178 20 564K 376K run 0:00 0.18 0.13 top
? 12 root -32 20 0K 32K sleep 0:01 0.13 0.13 ttisr
? 3 root 128 20 0K 32K sleep 0:00 0.08 0.08 statdaemon
? 19 root 147 20 0K 32K sleep 0:00 0.06 0.06 lvmkd
? 0 root 128 20 0K 0K sleep 0:04 0.02 0.02 swapper
? 1 root 168 20 448K 204K sleep 0:00 0.02 0.02 init
? 2 root 128 20 0K 32K sleep 0:00 0.02 0.02 vhand
? 4 root 128 20 0K 32K sleep 0:00 0.02 0.02 unhashdaemo
? 281 root 154 20 1628K 788K sleep 0:00 0.02 0.02 saprouter
? 283 root 138 0 288K 104K sleep 0:00 0.02 0.02 krsd
? 284 root 154 20 284K 96K sleep 0:00 0.02 0.02 sfd
? 287 root 168 20 136K 328K sleep 0:00 0.02 0.02 p_client
? 288 root 156 20 96K 200K sleep 0:00 0.02 0.02 uugetty
tty0p0 299 root 158 20 224K 252K sleep 0:00 0.02 0.02 ksh

Re: INIT: Command is respawning too rapidly.

Uday_S_Ankolekar — Mon, 29 Dec 2003 12:55:02 GMT

vi /etc/inittab file
samd:23456:respawn:/usr/sam/lbin/samd # system mgmt daemon

and replace respawn with off on above line.

samd:23456:off:/usr/sam/lbin/samd # system mgmt daemon

This should stop the error but you need to check why this errors coming.

-USA..

Re: INIT: Command is respawning too rapidly.

Uday_S_Ankolekar — Mon, 29 Dec 2003 13:12:09 GMT

Further to my comments:

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

From KB...
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."
Look at the /etc/hosts file and it should have only 2 entries:

127.0.0.1 server1
127.0.0.1 localhost loopback

This can be resolved by configuring the lan card and network settings

-USA..

Re: INIT: Command is respawning too rapidly.

Mike_Ca Li — Mon, 29 Dec 2003 13:12:52 GMT

I added S991startrouter (a softlink to /usr/sap/startrouter) in /sbin/rc2.d hoping to start the script when systems boots up. I think that was the cause of problem I just had. After I removed S991startrouter the system comes backup up normally. Where can I put S991startrouter to load at bootup?
I also notice that when I "ps -ef | grep saprouter" when it's loaded on boot up I can only see:
server:/usr/sap {392}> ps -ef | grep saprouter
root 6112 6111 10 13:07:40 console 0:00 /usr/sap/saprouter -r -W 30000 -R /usr/sap/saprouttab

However when I manually start saprouter script, I also see
root 6111 1 0 13:07:40 console 0:00 /usr/bin/tee -a /usr/sap/saprouter.log

server:/usr/sap {389}> more startrouter
#!/usr/bin/sh
#
# Start saprouter
#
LOGFILE=/usr/sap/saprouter.log
SRDIR=/usr/sap
if [ -f $SRDIR/saprouter ] ; then
echo "\nStarting saprouter Daemon " | /usr/bin/tee -a $LOGFILE
echo "----------------------------" | /usr/bin/tee -a $LOGFILE
$SRDIR/saprouter -r -W 30000 -R $SRDIR/saprouttab \
| /usr/bin/tee -a $LOGFILE &
fi

Re: INIT: Command is respawning too rapidly.

Kent Ostby — Mon, 29 Dec 2003 15:21:00 GMT

You probably want to put this in rc3.d.

Also, you want to try running the script from the command line prior to including it in the startup to make sure it works okay.

A lot of times the problem you are seeing is caused when a file with commands is placed in the /etc/rc.config.d directory.

If you had any files for your script in that directory, make sure they only contain environement variables to be "sourced" and not commands that you try to run.

Best regards,

Kent M. Ostby

Re: INIT: Command is respawning too rapidly.

Adisuria Wangsadinata_1 — Mon, 29 Dec 2003 21:08:09 GMT

Hi there,

I refer you the knowledge mine document about 'How do I fix the error : Init: Command is Respawning Too Rapidly' at this url below :

http://itrc.hp.com/cki/bin/doc.pl/screen=ckiSearchResults?mode=id&searchString=UXDNKBRC00000918

Hope this can help you.

Merry Xmas & Best Regards,
AW