Linux - Server This forum is for the discussion of Linux Software used in a server related context. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
08-05-2011, 12:16 PM
|
#1
|
Member
Registered: Apr 2010
Location: India /Hyderabad
Distribution: RedHat, CentOS
Posts: 273
Rep:
|
"init: Id "x" respawning too fast: disabled for 5 minutes."
First of all HHHIIIIIIIIIIIIIII to all of my new friends on linuxquestions.org. i started posting from today. wish me all the best.
i was installing all the servers and unistalling when i was practing but suddently i lost gui and only cmd line is working and getting the error "init: Id "x" respawning too fast: disabled for 5 minutes." for every 10 or fifteen min. please help me.

Last edited by Gil@LQ; 08-05-2011 at 12:19 PM.
|
|
|
08-05-2011, 01:19 PM
|
#2
|
Member
Registered: Nov 2005
Distribution: Raspbian, Debian, Ubuntu
Posts: 386
Rep: 
|
'init' is essentially the first process that runs on the system. If you do a display like 'ps- ef', it is PID 1.
Depending on what distro you are running and what level you are at, init uses a file /etc/inittab to start daemons at initialization or restart them if they crash (respawn).
'systemd' is a replacement for the traditional System V init. The man page for systemd (man systemd) says
Quote:
systemd is a system and service manager for Linux operating systems. When run as first process on boot (as PID 1), it
acts as init system that brings up and maintains userspace services.
|
Whether your system is using init or systemd, what has happened is that 'x', the Linux graphical environment has crashed, init (or systemd) is trying to restart it because it is defined with respawn, and it is repeatedly crashing. After it has crashed so many times in a short period, the system decides to disable the respawn mechanism for 5 minutes.
Has the system installed successfully and allowed you to boot and log into a graphical console? Or does this happen every time you install?
|
|
1 members found this post helpful.
|
08-07-2011, 09:44 AM
|
#3
|
Member
Registered: Apr 2010
Location: India /Hyderabad
Distribution: RedHat, CentOS
Posts: 273
Original Poster
Rep:
|

Quote:
Originally Posted by tommylovell
'init' is essentially the first process that runs on the system. If you do a display like 'ps- ef', it is PID 1.
Depending on what distro you are running and what level you are at, init uses a file /etc/inittab to start daemons at initialization or restart them if they crash (respawn).
'systemd' is a replacement for the traditional System V init. The man page for systemd (man systemd) says
Whether your system is using init or systemd, what has happened is that 'x', the Linux graphical environment has crashed, init (or systemd) is trying to restart it because it is defined with respawn, and it is repeatedly crashing. After it has crashed so many times in a short period, the system decides to disable the respawn mechanism for 5 minutes.
Has the system installed successfully and allowed you to boot and log into a graphical console? Or does this happen every time you install?
|
istalled successfully and was working fine but when i was trying to install send mail squirrel mail suddenly i got this issue.
Thank you very much in adv
Last edited by Gil@LQ; 08-07-2011 at 09:47 AM.
|
|
|
08-07-2011, 11:00 AM
|
#4
|
Member
Registered: Nov 2005
Distribution: Raspbian, Debian, Ubuntu
Posts: 386
Rep: 
|
You have two options.
The first, assuming you have a maintenance contract with Red Hat, is to open a problem with them.
The second option would be to start a new thread that is titled "Squirrel Mail crashes X" and describe exactly what you are doing. (I think starting it in "Linux - Desktop" would be more appropriate, not Linux - Server, as most servers don't even run a GUI.)
Don't forget to mention your distro and version info (ie. RHELx.x). (This would not be considered a "duplicate post" as the topic is considerably different from this thread.) Hopefully someone with Squirrel Mail expertise will have some advice.
|
|
|
08-07-2011, 12:05 PM
|
#5
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,187
|
The "respawning too fast" message is telling you that your X-server (or xorg.conf file) is miss-configured, and the X-server is crashing when it tries to start and trying to restart too fast or too often.
From the command line, look at /var/log/Xorg.0.log to see why the X-server crashed, and fix the problem.
|
|
|
08-08-2011, 11:25 AM
|
#6
|
Member
Registered: Apr 2010
Location: India /Hyderabad
Distribution: RedHat, CentOS
Posts: 273
Original Poster
Rep:
|
Quote:
Originally Posted by tommylovell
You have two options.
The first, assuming you have a maintenance contract with Red Hat, is to open a problem with them.
The second option would be to start a new thread that is titled "Squirrel Mail crashes X" and describe exactly what you are doing. (I think starting it in "Linux - Desktop" would be more appropriate, not Linux - Server, as most servers don't even run a GUI.)
Don't forget to mention your distro and version info (ie. RHELx.x). (This would not be considered a "duplicate post" as the topic is considerably different from this thread.) Hopefully someone with Squirrel Mail expertise will have some advice.
|
Hi tommy you were right, squirrel mail crashed, so i googled and finally found that insalling xorg,gdm and gnome will cure it certainly it did. Thank you for you response by the way it was rhel 5 . cheers have a nice time.
|
|
|
08-08-2011, 11:27 AM
|
#7
|
Member
Registered: Apr 2010
Location: India /Hyderabad
Distribution: RedHat, CentOS
Posts: 273
Original Poster
Rep:
|
Quote:
Originally Posted by PTrenholme
The "respawning too fast" message is telling you that your X-server (or xorg.conf file) is miss-configured, and the X-server is crashing when it tries to start and trying to restart too fast or too often.
From the command line, look at /var/log/Xorg.0.log to see why the X-server crashed, and fix the problem.
|
it was correct i installed xorg,gdm and gnome and it's done. thank's for your hint.
---------- Post added 08-08-11 at 10:27 AM ----------
thank you
|
|
|
06-04-2013, 04:49 AM
|
#8
|
LQ Newbie
Registered: Jun 2013
Posts: 1
Rep: 
|
Solved
Hi there,
I had the same issue.
But I solved it .. yeayh
You said:
hevilp wrote:
initab
"x:5:respawn:/usr/bin/lxdm >/dev/null 2>&1"
I was missing a "s",
and you are, too.
It is not /usr/bin/lxdm
but /usr/sbin/lxdm
wrong
x:5:respawn:/usr/bin/lxdm >/dev/null 2>&1
right
x:5:respawn:/usr/sbin/lxdm >& /dev/null
cheers,
Anand Gupta
|
|
|
All times are GMT -5. The time now is 01:55 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|