How To Solve BuG:INIT: Id "X" respawning too fast : disabled for 5 minutes
First ,I enter the system in text mode and edit the file "/ect/inittab" to setup the graphical interface .
Edit the following text : id:3:initdefault to id:5:initdefault:
Save the file then reboot .
When the systen re-setup, it shows
"INIT:Id "X" rewpawning too fast : desabled for 5 minutes"
Then five minutes later ,the message showed again!
What's wrong with my linux !I am looking for the answer.....
Following is some information I found.
http://www.unixguide.net/linux/faq/09.24.shtml
In most distributions this means that the system is booting by default
into runlevel 5, which is supposed to respawn (re-start again after
it's been exited) a graphical login via xdm, kdm, gdm, or whatever,
and the system can't locate the program.
However, "Id" can also indicate the absence or misconfiguration of
another program, like mingetty, if init tries to respawn itself more
than 10 times in 2 minutes.
Id "x" is the number in the leftmost column of the /etc/inittab file:
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
Commenting the offending line out and then fixing the errant program
and testing on the command line will allow you to see any error
messages that go to standard error output (console) if the errors are
not going to the system log file. Uncomment the line and restart init
with "kill -SIGHUP 1" or "telinit q" to cause init to reinitialize and
reread the /etc/inittab file.
Some systems, however, rewrite /etc/inittab when booting. In that
case, refer to the init man page, and/or the settings in
/etc/sysconfig/init.
Refer to the init and /etc/inittab man pages for detailed information.
[Carl King]
http://linuxgazette.net/issue46/tag/5.html
Id "x" respawning too fast: Murdered Mysteriously
From Kelley Butch on Tue, 07 Sep 1999
James,
I've been running LINUX on my Thinkpad 600 for a few months now with good results. The other day I experienced a power outage and the system went down. Now, during boot-up and just before the "log-in" screen I get this:
According to /var/run/gdm.pid, gdm was already running (process id) but seems to have been murdered mysteriously. INIT: Id "x" respawning too fast: disabled for 5 minutes
and after 5 minutes I get the same error.
I removed the pid file thinking that would solve the problem, but the pid file gets recreated and the errors start over again.
The culprit seems to be the last line in my inittab file: x:5:respawn:/etc/X11/prefdm -nodaemon
- (this is a link to /usr/bin/gdm)
Thanks in advance,
Butch
Oh yeah! I've seen that on some Red Hat 6.x systems. ' prefdm' is a symbolic link to your preferred display manager (the original xdm, the newer kdm for KDE, or the culprit of your problem the gdm, GNOME display manager).
Try starting the system in single-user mode (or running the command ' telinit 3' to switch to the "normal" multi-user mode without any display manager (graphical login) running. Then remove the PID file and any stray core files in the root, /root and similar directories.
You might also want to look for any UNIX domain sockets under the
/tmp directory and
/var. You can use the command command: '
find /tmp /var -type s -ls' to look for them.
You'll normally find a couple of them under /var for things like the printer (might also be under /dev) and gpmctl (console mouse and cut/paste support) as well as one or two sockets for your X server(s). Those would normally be in the /tmp/.X11-unix/ directory and be named X0, X1, etc. (If you've never run multiple concurrent X sessions then you'll only see X0 under there).
You probably don't have to do anything with those sockets. However, it might make sense to blow away the one's under /tmp. X will (re-)create those as necessary.
The fact that the version of GNOME gdm that shipped with Red Hat 6.x can't gracefully handle (clean up after) an inadvertant shutdown or other mishap is very disappointing.
Personally I still think GNOME is still beta quality code. (Or at least it was when RH 6.x shipped). It dumps core files all of the place, can't figure out whether there is a living process that owns a 'dead' socket, etc.
Oh well. At least it's getting a bit better.
I did grope around a bit at the GNOME web site: http://www.gnome.org.
I did NOT see this question listed in their FAQ (which surprises me, since I would think that this would be a very commonly encountered problem among RH6/GNOME users). However, I did find a link to a bug tracking system. From there I searched for messages related to our "murdered mysteriously" problem. There was some indication that Martin K. Petersen is the contact for gdm and that he posted patches to resolve that (and several other) gdm issues.
I also saw several references to a gdm2 (which presumably is a second version of the GNOME display manager).
In any event, you may want to download a set of updates to your version of GNOME. Hopefully the fix to this problem is included therein. (I'm pretty sure that the GNOME CVS sources are updated, I just don't know if there are RH RPMs of the latest versions and patches readily available).
http://www.linuxquestions.org/questions/showthread.php?s=&forumid=2&threadid=328156
INIT:Id "x" respawning too fast,disabled for 5 minutes. ( post #1)
my os is redhat9.0 ,the graphic interface disappeared suddenly!
so i reboot my computer as root,then it prints:
INIT: Id "x" respawning too fast, disabled for 5 minutes.
and when use ctrl+alt+f5 or f6,it is ok!but when ctrl+alt+f7,there is nothing on the screen!
what is the problem?
i am a newbie,so please expain more in detail,3Q!!
http://www.linuxaid.com.cn/tips/1/2/12807291.shtml
为什么会出现INIT: Id "1" respawning too fast: disabled for 5 minutes当使用/etc/inittab里面的某个程序，例如mgetty来接受modem拨入，同时系统又重新启动或者几个拨入都不成功；又或者登录提示数次被取消（例如用ctrl+D），都会出现这种提示。
原因在于，当init通过/etc/inittab来启动某个程序的时候，如果这个程序连续几次被很快地终止，那么在/etc/inittab里面对应的条目就会被禁用并不再启动。正常情况下程序应该在被结束后两分钟后重新启动，这个问题不应该归咎于init的bug。
解决方法是：
首先，很多程序有自己的日志或者把他们的syslog写到/var/log/messages或者这个目录下面类似的日志里面，所以可以查看这些日志来得到错误信息。你也可以手动在shell下面启动这些程序来得到错误信息，但是记得不要改动/etc/inittab里面的项目。你可以以root身份使用init q命令使得这些无效的命令重新可以使用。
http://blog.csdn.net/Haohappy2004/archive/2004/09/18/108914.aspx
不知道什么原因，启动不了X，报错：
init: Id "x" respawning too fast: disabled for 5 minutes
记下解决过程：
找了些资料，：
http://www.unixguide.net/linux/faq/09.24.shtml不过报错没有具体指出X=多少，所以没法使用注释掉以下某一行的方法。
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6查看/var/log/message中的日志，也没有具体说明是哪里出错。。
于是切换到命令行
vi /etc/inittab
将id=5改成id=3，从文本界面登录。
重启 reboot
然后
startx
启动失败，但得到具体的出错信息！原来几个文件(libmodle***)找不到。locate libmodle
总之找到这几个文件，cp到/usr/lib
然后将
/etc/inittab中id改回5，默认启动X窗口。
reboot
搞定