[gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Jean Blignaut]

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

I get this message repeatedly on the console after booting a simple GNAP
iso in vmware:

 

Init: Id "s0" respawning too fast: disabled for 5 minutes

 

What does this mean?

 

----I also see this in the log:

 

agetty: ttyS0: ioctl: Input/output error

 

----and while booting I saw some thing like:

 

error communicating with the kernel

 

 

----my overly.conf contains (I don't have any conf files in overly for
htbinit or openvpn tho so am not surprised by htb and vpn errors in
log):

 

EMPTY_ROOTPASS=yes

 

IP_RELAY=no

 

#use two network cards

NBCARDS=2

 

TC_TYPE=htbinit

USE_TC=yes

USE_SSH=yes

USE_VPN=yes

 

# Start the 'shorewall' firewall script at startup

USE_FW=yes

FW_TYPE=shorewall

 

# Use South African Standard Time (UTC+2)

#TIMEZONE=SAST

 

# Use a french keyboard layout

KEYMAP=us

 

# Time server


[-- Attachment #2: Type: text/html, Size: 6906 bytes --]

Re: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Hans-Werner Hilse]

Hi,

On Wed, 5 Apr 2006 14:13:32 +0200 "Jean Blignaut" <jean@megaweb.biz>
wrote:

> Init: Id "s0" respawning too fast: disabled for 5 minutes
> 
> What does this mean?

The inittab entry named "s0" exits with errors in too short intervals.
It's a "respawn" entry.

> ----I also see this in the log:
> 
> agetty: ttyS0: ioctl: Input/output error

I think this will likely cause it as there's apparently a getty set up
to listen on the serial line #1. Most likely, that device doesn't exist
(yet) at that point. Probably compiled as a module?

> error communicating with the kernel

I've never seen this before (but I'm not using serial console), but I
think it may be from agetty, too.

So you'll want to check your inittab or kernel config, depending on
whether you want a serial console or not.

-hwh
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Hanni Ali]

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

I had something like this happen whe I was using mingetty to autologin and
it wasn't installed. Possibly modules problem but fist check you have agetty
installed/configured correctly.

Hanni




On 05/04/06, Hans-Werner Hilse <hilse@web.de> wrote:
>
> Hi,
>
> On Wed, 5 Apr 2006 14:13:32 +0200 "Jean Blignaut" <jean@megaweb.biz>
> wrote:
>
> > Init: Id "s0" respawning too fast: disabled for 5 minutes
> >
> > What does this mean?
>
> The inittab entry named "s0" exits with errors in too short intervals.
> It's a "respawn" entry.
>
> > ----I also see this in the log:
> >
> > agetty: ttyS0: ioctl: Input/output error
>
> I think this will likely cause it as there's apparently a getty set up
> to listen on the serial line #1. Most likely, that device doesn't exist
> (yet) at that point. Probably compiled as a module?
>
> > error communicating with the kernel
>
> I've never seen this before (but I'm not using serial console), but I
> think it may be from agetty, too.
>
> So you'll want to check your inittab or kernel config, depending on
> whether you want a serial console or not.
>
> -hwh
> --
> gentoo-embedded@gentoo.org mailing list
>
>


--
E-mail: hanni.ali@gmail.com
Mobile: 07985580147
Website: www.ainkaboot.co.uk

[-- Attachment #2: Type: text/html, Size: 1830 bytes --]

RE: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Jean Blignaut]

-----Original Message-----
From: Hans-Werner Hilse [mailto:hilse@web.de] 
Sent: Wednesday, April 05, 2006 2:43 PM
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] init Id "s0" respawning too fast:
disabled for 5 minutes

Hi,

On Wed, 5 Apr 2006 14:13:32 +0200 "Jean Blignaut" <jean@megaweb.biz>
wrote:

>> Init: Id "s0" respawning too fast: disabled for 5 minutes
>> 
>> What does this mean?

>The inittab entry named "s0" exits with errors in too short intervals.
>It's a "respawn" entry.

Thanx I've just discovered the inittab myself and rebuilt GNAP iso to
hopefully not have this prob any more as I don't foresee using a serial
console for my application.
----nope just tried still get the "respawning too fast" error even with
the s0 line commented out---

>> ----I also see this in the log:
>> 
>> agetty: ttyS0: ioctl: Input/output error

>I think this will likely cause it as there's apparently a getty set up
>to listen on the serial line #1. Most likely, that device doesn't exist
>(yet) at that point. Probably compiled as a module?

>> error communicating with the kernel

>I've never seen this before (but I'm not using serial console), but I
>think it may be from agetty, too.

Ipt_owner: pid, sid and command matching is broken on SMP.

And

RTNETLINK answers: Invalid argument
We have an error talking to the kernel

Having noticed where this error happens now I would say its probably
shorewall since both these happen after * Starting firewall ...

>So you'll want to check your inittab or kernel config, depending on
>whether you want a serial console or not.

>-hwh
>-- 
>gentoo-embedded@gentoo.org mailing list


-- 
gentoo-embedded@gentoo.org mailing list

RE: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Jean Blignaut]

[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]

I haven't installed any thing just using the standard stuff - its my
first time with gnap - wasn't going to go too complicated

 

I'm going to burn to disc and test on real hardware maybe it's a vm
issue

 

________________________________

From: Hanni Ali [mailto:hanni.ali@gmail.com] 
Sent: Wednesday, April 05, 2006 2:57 PM
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] init Id "s0" respawning too fast:
disabled for 5 minutes

 

I had something like this happen whe I was using mingetty to autologin
and it wasn't installed. Possibly modules problem but fist check you
have agetty installed/configured correctly.

Hanni





On 05/04/06, Hans-Werner Hilse <hilse@web.de> wrote:

Hi,

On Wed, 5 Apr 2006 14:13:32 +0200 "Jean Blignaut" <jean@megaweb.biz>
wrote:

> Init: Id "s0" respawning too fast: disabled for 5 minutes 
>
> What does this mean?

The inittab entry named "s0" exits with errors in too short intervals.
It's a "respawn" entry.

> ----I also see this in the log:
>
> agetty: ttyS0: ioctl: Input/output error 

I think this will likely cause it as there's apparently a getty set up
to listen on the serial line #1. Most likely, that device doesn't exist
(yet) at that point. Probably compiled as a module?

> error communicating with the kernel 

I've never seen this before (but I'm not using serial console), but I
think it may be from agetty, too.

So you'll want to check your inittab or kernel config, depending on
whether you want a serial console or not. 

-hwh
--
gentoo-embedded@gentoo.org mailing list




-- 
E-mail: hanni.ali@gmail.com 
Mobile: 07985580147
Website: www.ainkaboot.co.uk 


[-- Attachment #2: Type: text/html, Size: 5799 bytes --]

Re: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Hans-Werner Hilse]

Hi,

On Wed, 5 Apr 2006 15:01:53 +0200 "Jean Blignaut" <jean@megaweb.biz>
wrote:

> ----nope just tried still get the "respawning too fast" error even
> with the s0 line commented out---

Does the error claim that it's still the "s0" line? If so, you must
have make a mistake when commenting it out like editing the
wrong /etc/inittab or similar (initrd regeneration, etc.pp.).

> Ipt_owner: pid, sid and command matching is broken on SMP.

That's from iptables. So I guess you're right when stating:

> Having noticed where this error happens now I would say its probably
> shorewall since both these happen after * Starting firewall ...

Looking at the error message, your probably trying to use "-m owner".
But it does look like more of a warning rather than an error (or are
you matching PID, SID or command string?). That said, PID/GID matching
should work.

-hwh
-- 
gentoo-embedded@gentoo.org mailing list

RE: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Jean Blignaut]

-----Original Message-----
From: Hans-Werner Hilse [mailto:hilse@web.de] 
Sent: Wednesday, April 05, 2006 3:43 PM
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] init Id "s0" respawning too fast:
disabled for 5 minutes

Hi,

On Wed, 5 Apr 2006 15:01:53 +0200 "Jean Blignaut" <jean@megaweb.biz>
wrote:

>> ----nope just tried still get the "respawning too fast" error even
>> with the s0 line commented out---

> Does the error claim that it's still the "s0" line? If so, you must
> have make a mistake when commenting it out like editing the
> wrong /etc/inittab or similar (initrd regeneration, etc.pp.).


No mistake as far is I can tell after checking the /etc/inittab on the
booted gnap virtual machine I decided to try  changing runlevels from 3
to 4 and back again this seems to have worked cause I havn't seen the
message since -- this leads me to believe that some thing else is
enabling the s0 tty, something that ignores inittab
As a matter of interest: the I/O error hasn't shown up in the logs since
I first commented out s0 line in inittab

>> Ipt_owner: pid, sid and command matching is broken on SMP.

> That's from iptables. So I guess you're right when stating:

>> Having noticed where this error happens now I would say its probably
>> shorewall since both these happen after * Starting firewall ...

> Looking at the error message, your probably trying to use "-m owner".
> But it does look like more of a warning rather than an error (or are
> you matching PID, SID or command string?). That said, PID/GID matching
> should work.

I'll have to test and see what works and what doesn't don't know too
much about the inner workings of shorewall and my knowledge of iptables
matching is -slim-

> -hwh
> -- 
> gentoo-embedded@gentoo.org mailing list


-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Hans-Werner Hilse]

Hi,

On Wed, 5 Apr 2006 15:58:57 +0200 "Jean Blignaut" <jean@megaweb.biz>
wrote:

> On Wed, 5 Apr 2006 15:01:53 +0200 "Jean Blignaut" <jean@megaweb.biz>
> wrote:
> 
> >> ----nope just tried still get the "respawning too fast" error even
> >> with the s0 line commented out---
> 
> > Does the error claim that it's still the "s0" line? If so, you must
> > have make a mistake when commenting it out like editing the
> > wrong /etc/inittab or similar (initrd regeneration, etc.pp.).
> 
> No mistake as far is I can tell after checking the /etc/inittab on the
> booted gnap virtual machine I decided to try  changing runlevels from
> 3 to 4 and back again this seems to have worked cause I havn't seen
> the message since [...]

well, a reboot, changing runlevels or at least a "telinit q" is
necessary to make init aware of the changed inittab. I didn't mention
this before...

> -- this leads me to believe that some thing else is
> enabling the s0 tty, something that ignores inittab
> As a matter of interest: the I/O error hasn't shown up in the logs
> since I first commented out s0 line in inittab

OK, then it worked. But please note that the "s0" is the name of the
inittab entry (read "man inittab") and doesn't per se specificate a
device. That's done in another place and the correct device name is
ttyS0 (capital "S"). The line could have a totally different name.

Anyway, the inittab issue seems to be gone for you, that was just a
clarification. All that seem to be left is your firewall problem
(doesn't seem to be embedded-specific, so you might want to ask on
-security or -user).

> I'll have to test and see what works and what doesn't don't know too
> much about the inner workings of shorewall and my knowledge of
> iptables matching is -slim-

Sorry, I can't help here as I'm not using any firewall builders. But
you should disable lines that e.g. specify that only certain
applications are allowed to access the net (that would probably be
command matching).

As a side note: You *did* compile full netfilter support into your
kernel, didn't you?

-hwh
-- 
gentoo-embedded@gentoo.org mailing list

RE: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Jean Blignaut]

 
>> No mistake as far is I can tell after checking the /etc/inittab on
the
>> booted gnap virtual machine I decided to try  changing runlevels from
>> 3 to 4 and back again this seems to have worked cause I havn't seen
>> the message since [...]

> well, a reboot, changing runlevels or at least a "telinit q" is
> necessary to make init aware of the changed inittab. I didn't mention
> this before...

>> -- this leads me to believe that some thing else is
>> enabling the s0 tty, something that ignores inittab
>> As a matter of interest: the I/O error hasn't shown up in the logs
>> since I first commented out s0 line in inittab

> OK, then it worked. But please note that the "s0" is the name of the
> inittab entry (read "man inittab") and doesn't per se specificate a
> device. That's done in another place and the correct device name is
> ttyS0 (capital "S"). The line could have a totally different name.

I had a feeling that might be the case

> Anyway, the inittab issue seems to be gone for you

Not quite. See I DID reboot because I made a new GNAP iso image with my
version of inittab in the overlay etc directory -- it STILL boots with
the 'INIT: Id "s0" respawning too fast: disabled for 5 minutes' message
showing up every 5 minutes.
It only seems to stop after I change the runlevel by hand I'm confused
as to why this is the case does GNAP first use its own version of
inittab BEFORE replacing it with the one from the overlay?
Or is there some other mechanism that's attempting to start the console
on ttyS0?

ps aux shows tty[123456] but no ttyS0

...hang on I just caught it while it had a tts/0 tho running
/sbin/agetty -L -I 19200 ttys0 vt100 

-- 
gentoo-embedded@gentoo.org mailing list

RE: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Jean Blignaut]

I've removed tts/0 and ttyS0 lines from /etc/securetty booting now...

Nope my favorite respawning message is still there

The only other place I see tts is in /etc/udev/rules.d/50-udev.rules
And some how I don't think that's a place I want to remove it from

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Hans-Werner Hilse]

Hi,

On Wed, 5 Apr 2006 16:47:39 +0200 "Jean Blignaut" <jean@megaweb.biz>
wrote:

> I've removed tts/0 and ttyS0 lines from /etc/securetty booting now...

Should not make a difference, because this file is not directly checked
by init.

> Nope my favorite respawning message is still there

Hm. Is there by chance any initrd/initramfs that may contain an
additional inittab? Those would be loaded by the bootloader or compiled
into the kernel image.

> The only other place I see tts is in /etc/udev/rules.d/50-udev.rules
> And some how I don't think that's a place I want to remove it from

Yep, should be absolutely unnecessary. That respawning message is from
init and such due to issues within inittab. Whatever inittab that may
be.

-hwh
-- 
gentoo-embedded@gentoo.org mailing list