LinuxQuestions.org - "INIT: Respawning too fast: Disabled for 5 minutes"??

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - "INIT: Respawning too fast: Disabled for 5 minutes"?? (https://www.linuxquestions.org/questions/debian-26/init-respawning-too-fast-disabled-for-5-minutes-457370/)

"INIT: Respawning too fast: Disabled for 5 minutes"??

I am running an embedded system with pebble (based on debian). Im communicating via serial port and have configured lilo and inittab to do this. The system boots up fine and everything loads fine, (Im communicating through a computer with minicom). However, upon login

"INIT: Respawning too fast: Disabled for 5 minutes"??

begins to appear constantly. I cant figure out why this is happening do I have the wrong baud rates or is there a problem with the system??

Here is the inittab:

Code:

# /etc/inittab: init(8) configuration.

# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# # (my hacks marked ###(rs))



# The default runlevel.

id:2:initdefault:



# Boot-time system configuration/initialization script.

# This is run first except when booting in emergency (-b) mode.

si::sysinit:/etc/init.d/rcS



# What to do in single-user mode.

~~:S:wait:/sbin/sulogin



# /etc/init.d executes the S and K scripts upon change

# of runlevel.

#

# Runlevel 0 is halt.

# Runlevel 1 is single-user.

# Runlevels 2-5 are multi-user.

# Runlevel 6 is reboot.



l0:0:wait:/etc/init.d/rc 0

l1:1:wait:/etc/init.d/rc 1

l2:2:wait:/etc/init.d/rc 2

l3:3:wait:/etc/init.d/rc 3

l4:4:wait:/etc/init.d/rc 4

l5:5:wait:/etc/init.d/rc 5

l0:0:wait:/etc/init.d/rc 0

l1:1:wait:/etc/init.d/rc 1

l2:2:wait:/etc/init.d/rc 2

l3:3:wait:/etc/init.d/rc 3

l4:4:wait:/etc/init.d/rc 4

l5:5:wait:/etc/init.d/rc 5

l6:6:wait:/etc/init.d/rc 6

# Normally not reached, but fallthrough in case of emergency.

z6:6:respawn:/sbin/sulogin



# What to do when CTRL-ALT-DEL is pressed.

ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now



# Action on special keypress (ALT-UpArrow).

#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."

# What to do when the power fails/returns.

pf::powerwait:/etc/init.d/powerfail start

pn::powerfailnow:/etc/init.d/powerfail now

po::powerokwait:/etc/init.d/powerfail stop



# /sbin/getty invocations for the runlevels.

#

# The "id" field MUST be the same as the last

# characters of the device (after "tty").

#

# Format:

#  <id>:<runlevels>:<action>:<process>

#

# Note that on most Debian systems tty7 is used by the X Window System,

# so if you want to add more getty's go ahead but skip tty7 if you run X.

#

#1:2345:respawn:/sbin/getty 38400 tty1

#2:23:respawn:/sbin/getty 38400 tty2

#3:23:respawn:/sbin/getty 38400 tty3

#4:23:respawn:/sbin/getty 38400 tty4

#5:23:respawn:/sbin/getty 38400 tty5

#6:23:respawn:/sbin/getty 38400 tty6



# Example how to put a getty on a serial line (for a terminal)

#

T0:23:respawn:/sbin/getty -L ttyS0 38400 vt100

#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100



# Example how to put a getty on a modem line.

#

#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

###(rs)    NC:23:respawn:start-stop-daemon -S -c nocat --exec ###/usr/local/nocat/bin/gateway -- -F

also, everything runs fine, its just really annoying
and it only happens with minicom, not with an ssh terminal

Code:

#2:23:respawn:/sbin/getty 38400 tty2

Do you know if /dev/tty2 exists?

Here is a link to a text-terminal-howto that covers a few possabilities, such as modem initilization error, and even having a stuck key on the terminal.
http://www.technocage.com/~caskey/do...inal-HOWTO.txt

If the baud rate were wrong, I would expect that you would see just garbage from mgetty instead of the respawning error message.

Thanks for responding but it turns out the inittab i posted contains a commented line, which was not commented before I posted this, apparantly I was running two seperate terminals or something?

This is the old inittab

Code:

# /etc/inittab: init(8) configuration.

# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# # (my hacks marked ###(rs))



# The default runlevel.

id:2:initdefault:



# Boot-time system configuration/initialization script.

# This is run first except when booting in emergency (-b) mode.

si::sysinit:/etc/init.d/rcS



# What to do in single-user mode.

~~:S:wait:/sbin/sulogin



# /etc/init.d executes the S and K scripts upon change

# of runlevel.

#

# Runlevel 0 is halt.

# Runlevel 1 is single-user.

# Runlevels 2-5 are multi-user.

# Runlevel 6 is reboot.



l0:0:wait:/etc/init.d/rc 0

l1:1:wait:/etc/init.d/rc 1

l2:2:wait:/etc/init.d/rc 2

l3:3:wait:/etc/init.d/rc 3

l4:4:wait:/etc/init.d/rc 4

l5:5:wait:/etc/init.d/rc 5

l0:0:wait:/etc/init.d/rc 0

l1:1:wait:/etc/init.d/rc 1

l2:2:wait:/etc/init.d/rc 2

l3:3:wait:/etc/init.d/rc 3

l4:4:wait:/etc/init.d/rc 4

l5:5:wait:/etc/init.d/rc 5

l6:6:wait:/etc/init.d/rc 6

# Normally not reached, but fallthrough in case of emergency.

z6:6:respawn:/sbin/sulogin



# What to do when CTRL-ALT-DEL is pressed.

ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now



# Action on special keypress (ALT-UpArrow).

#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."

# What to do when the power fails/returns.

pf::powerwait:/etc/init.d/powerfail start

pn::powerfailnow:/etc/init.d/powerfail now

po::powerokwait:/etc/init.d/powerfail stop



# /sbin/getty invocations for the runlevels.

#

# The "id" field MUST be the same as the last

# characters of the device (after "tty").

#

# Format:

#  <id>:<runlevels>:<action>:<process>

#

# Note that on most Debian systems tty7 is used by the X Window System,

# so if you want to add more getty's go ahead but skip tty7 if you run X.

#

##!!!!!!! THIS IS THE LINE I COMMENTED !!!!!!!!!!!###

1:2345:respawn:/sbin/getty 38400 tty1

##!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!###

#2:23:respawn:/sbin/getty 38400 tty2

#3:23:respawn:/sbin/getty 38400 tty3

#4:23:respawn:/sbin/getty 38400 tty4

#5:23:respawn:/sbin/getty 38400 tty5

#6:23:respawn:/sbin/getty 38400 tty6



# Example how to put a getty on a serial line (for a terminal)

#

T0:23:respawn:/sbin/getty -L ttyS0 38400 vt100

#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100



# Example how to put a getty on a modem line.

#

#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

###(rs)    NC:23:respawn:start-stop-daemon -S -c nocat --exec ###/usr/local/nocat/bin/gateway -- -F

Thus simply commenting the line above fixed the problem. However, after previously running into a "depmod:: char-major-4 missing" error I also added the alias
"alias::char-major-4 off"
to the modules.conf file.

Just as an addition, because I did not find it documented anywhere and just did run into the issue:

This error may also happen if the parameters to getty are wrong. For example, I had
T0:2345:respawn:/sbin/getty -L ttyS0 115300 vt100
causing this. The error is that 115300 is an invalid baud rate. The correct one is 115200.