Hi there,
(Please excuse my probably pityful english - it's not an excuse, but my
native language is French)
I just ran into the same problem :
- Made a fresh debootstrap install
- WGETed kernel 2.6.16.1, compiled it and its module (make menuconfig ;
make bzImage ; make modules ; make modules
On Fri, Mar 03, 2006 at 12:55:55PM -, Tom Northeast wrote:
> After a short while i get an error from each runlevel:
>
> INIT: id "1" respawning too fast: disabled for 5 minutes
[...]
This means that the inittab entry labelled "1" is exiting right away
every time
: Sarge NFS Root: "INIT: id "1"
respawning too fast"
Hi,
I've recently configure a netbooting system on my
network. I installed sarge with minimal packages with no "special" configuration
and chose the netbooting kernel. The system loads the kernel and the ini
all the way
to starting my daemons through inetd.
After Cron is succesfully started, it attempts to
bring up the login prompt. After a short while i get an error from each
runlevel:
INIT: id "1" respawning too fast: disabled for 5
minutes
INIT: id "2" respawning too fas
/dev/tty2: already in use
May 14 04:08:04 desk getty[7771]: /dev/tty2: already in use
May 14 04:08:14 desk init: Id "2" respawning too fast: disabled for 5
minutes
basically constantly, logcheck sends me several emails like this every
day. I updated util-linux to 2.12-7 on 5/3.
Why is
I had this problem for months and posted and nobody appeared to have the
solution.
A friend of mine did a google search and found something from a 2001
debian-user post; I can not say for sure that this will work. I solved my
problem by changing to mingetty as I had other reasons for wanting to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Every few weeks, I have difficulties after closing a console login
session. The error message is:
INIT: ID "2" respawning too fast: Disabled for 5 minutes
While the session is being respawned too fast, I obviously do not have
access
Thanks, that fixed it.
On Sunday, September 21, 2003, at 11:56 AM, Thomas Krennwallner wrote:
Hi!
On Sun Sep 21, 2003 at 10:59:15AM -0700, Steven Schlansker wrote:
On Sunday, September 21, 2003, at 09:25 AM, Thomas Krennwallner
wrote:
Would you post the content of file /etc/inittab to the li
Hi!
On Sun Sep 21, 2003 at 10:59:15AM -0700, Steven Schlansker wrote:
> On Sunday, September 21, 2003, at 09:25 AM, Thomas Krennwallner wrote:
> >Would you post the content of file /etc/inittab to the list? Seems
> >like there's a misconfigured line in it.
>
> I see a line which is suspect - it'
On Sunday, September 21, 2003, at 09:25 AM, Thomas Krennwallner wrote:
Would you post the content of file /etc/inittab to the list? Seems like
there's a misconfigured line in it.
I see a line which is suspect - it's commented as "Example how to put a
getty on a modem line."
S:12345:respawn:/sbin
Hi!
On Sun Sep 21, 2003 at 08:29:53AM -0700, Steven Schlansker wrote:
> Every five minutes, the entire screen fills with a usage line for
> getty, repeated some 10 times, and then INIT: Id "S" respawning too
> fast: disabled for 5 minutes. Five minutes later, the process
>
Every five minutes, the entire screen fills with a usage line for
getty, repeated some 10 times, and then INIT: Id "S" respawning too
fast: disabled for 5 minutes. Five minutes later, the process repeats.
It doesn't seem to break anything, but it's annoying. What could
On Monday 14 October 2002 12:13 am, Joey Quevedo wrote:
> Hi,
>
> I'm setting up my mgetty and got this error message:
>
> "INIT: Id "M0" respawning too fast: disabled for 5 minutes"
>
> What could be the cause of this?
>
i've never
On Mon, Oct 14, 2002 at 03:13:23PM +0800, Joey Quevedo wrote:
> I'm setting up my mgetty and got this error message:
>
> "INIT: Id "M0" respawning too fast: disabled for 5 minutes"
>
> What could be the cause of this?
It means that whatever's in th
On Mon, Oct 14, 2002 at 03:13:23PM +0800, Joey Quevedo wrote:
>
> I'm setting up my mgetty and got this error message:
>
> "INIT: Id "M0" respawning too fast: disabled for 5 minutes"
>
> What could be the cause of this?
I had a similar problem a
Hi,
I'm setting up my mgetty and got this error message:
"INIT: Id "M0" respawning too fast: disabled for 5 minutes"
What could be the cause of this?
Regards,
Joey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gt; Yesterday, however, when I tried to boot up it worked until gdm and I
>received the following messages:
>
>"Starting Gnome Display Manager: gdm.
>INIT: Id "1" respawning too fast: disabled for 5 minutes.
There is a known racecondition in init that gets triggered by
a 2.4 kernel. You need the latest sysvinit from woody.
Mike.
y, however, when I tried to boot up it worked until gdm and I
> received the following messages:
>
> "Starting Gnome Display Manager: gdm.
> INIT: Id "1" respawning too fast: disabled for 5 minutes.
> INIT: Id "1" respawning too fast: disabled for 5 min
:
"Starting Gnome Display Manager: gdm.
INIT: Id "1" respawning too fast: disabled for 5 minutes.
INIT: Id "1" respawning too fast: disabled for 5 minutes.
INIT: Id "1" respawning too fast: disabled for 5 minutes.
INIT: Id "1" respawning too fast: disabled for 5
> I discovered another problem:
>
> After booting my machine (info see below) with a newly compiled kernel
> 2.4.6, I get the following message on the "first console":
>
> INIT: Id "1" respawning too fast: disabling for 5 minutes
>
> After 5 minutes the same a
Jan Tammen wrote:
> I discovered another problem:
>
> After booting my machine (info see below) with a newly compiled kernel
> 2.4.6, I get the following message on the "first console":
>
> INIT: Id "1" respawning too fast: disabling for 5 minutes
>
>
Hello again,
I discovered another problem:
After booting my machine (info see below) with a newly compiled kernel
2.4.6, I get the following message on the "first console":
INIT: Id "1" respawning too fast: disabling for 5 minutes
After 5 minutes the same again ... however
I'm not sure why it happens exactly, but there is an easy
fix for it. As root, edit /etc/inittab. Towards the bottom
there will be a bunch of lines that look like the following:
1:2345:respawn:/sbin/getty -L 38400 tty1
2:23:respawn:/sbin/getty -L 38400 tty2
3:23:respawn:/sbin/getty -L 38400 tty3
4
lately i have been having a problem where the
console reports "INIT: ID5 is respawing to often and will be disabled for 5
minutes"
ID5 i figured out is tty5, because I cannot access
it when this happens (at first I thoguht it meant PID 5, which was
kswapd).
I remember reading that certai
ne baud_rate,... [termtype]
>--- this four lines repeated couple of times ---
>INIT: Id "S" respawning too fast: disabled for 5 minutes
>---
>
>I know, that responsible for that is this line in /etc/inittab :
>S:12345:respawn:/sbin/getty ttyS1
As you see above the usage for t
] [-t timeout] [-I initstring] [-H
login_host] line baud_rate,... [termtype]
--- this four lines repeated couple of times ---
INIT: Id "S" respawning too fast: disabled for 5 minutes
---
I know, that responsible for that is this line in /etc/inittab :
S:12345:respawn:/sbin/getty t
I recently installed Official Debian 2.2 r0. When the init process starts I
get the following messages:
Loading /usr/share/keymaps/i386/qwerty/gr.kmap.gz
findfile(): timeout waiting for undead child(ren) ?
After several repetitions, I get the message:
INIT: Id "1" respawning too fast
May 1999 06:09:59 +0800 (WST) ):
> |>hi,
> |>
> |>I just had my system hosed, but was able to recover in an hour with
> |>minimal (? will find out soon if not!) damage... however I'm getting the
> |>ol'
> |>
> |>INIT: Id "2" respawning too
hi,
I just had my system hosed, but was able to recover in an hour with
minimal (? will find out soon if not!) damage... however I'm getting the
ol'
INIT: Id "2" respawning too fast: disabled for 5 minutes.
Now I know WHY its doing this: my /dev/tty2 was hosed with the syst
29 matches
Mail list logo
