CentOS 5 :: System Hangs During Boot - "Starting Xend:"
Nov 29, 2009
I am booting centos 5.3 on x86-64 machine. The system hands at line "Starting xend:". Is there any way to skip starting xend service during boot or disable it during boot so the system finally reboots.
I just finished installing CentOS 5.2 x86_64 on a Dell Dimension 3100 (Pentium 4 with 64-bit support). On the first boot, after completing the final config steps (firewall, SELinux, time server, etc), the boot hangs on "Starting xend:". I have completed a successful installation on another Dell machine (different processor), with the same installation options (I recorded all of the steps and followed them for the second installation).
I had a server running Centos 5.5, which i have Webmin installed.. The other day i saw that there were updates available so i installed them, and now i have Centos 5.6 installed. I just had to reboot my server to move it, and now it wont boot. It is freezing at "Starting xend:"
I've followed this guide [URL] after rebooting the system hang at: starting ati external events daemon [OK] This line start blinking for a while, then nothing happen. I am using a radeon hd 4225. (I'm booting with acpi=off).
I don't exactly when this started, but I hadn't booted my mythbuntu box for a while. When I boot it now, it hangs after grub at 'Starting Up...'. I was running 9.10 64bit, with 4GB Ram installed on an AMD64 3700+ ASUS A8N5X mobo. How can I resolve this? Can I modify boot options by hitting the Esc key before grub? What options should I use? I made no changes myself, it just happened on the next reboot. I hope that I won't have to burn a livecd. I only say that because the only machine that I have with a decent burner is my 9.10 box.
I am booting centos 5.4 on machine. The system hangs at line "Applying iptables firewall rules".Is there any way to skip starting iptables service during boot or disable it during boot so the system finally reboots.
I've been using ubuntu for a couple of years rather successfully on my dual-boot Vista/Ubuntu. It upgraded to 8.0(4?) LTS, 10.04LTS and I kept it there until this afternoon I followed the instructions on the ubuntu site to open up a terminal and update-manager --somearg to provide me with a nice little "Upgrade" button on the update manager. I clicked said button per the instructions, let it do it's downloading and whatever else it does. The last step of the installation is a system reboot. I let it do that, and then my grub menu comes up as more-or-less this:
If I select the top one, I get: Code: Starting up ... with a blinking cursor under the S for a LONG time (used the power switch after ~40 mins). I tried the second 2.6.32-32 option for recovery mode. It spit a bunch of gibberish to the screen for a couple seconds and then stopped, presumably doing the same thing, just with 100% more gibberish. I tried booting into Vista, that worked fine. Just to reiterate, I've not yet seen a 10 LTS login screen or desktop, and can't get one yet (just a "Starting up ...") Just to add, I did try searching, but since the only info I had to go on was 8 LTS to 10 LTS upgrade, and "Starting up ...", well those are just hard keywords to get any meaningful info.
service xend status returns nothing - simply moves to next line service xend start does the same thing xm list ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Error: Unable to connect to xend: No such file or directory. Is xend running?
red hat 5 update 4 64bit. linux newby. on an interactive boot i can ping -t my vm linux server from my physical MS XP workstation and a vm W2000 64 bit server until xend is started, after that i get destination unreachable. if i choose not to start xend on the interactive boot i retain connectivity. i have read some blogs that imply this might be a bug - is this so? do I need xend on my vm red hat box that is a database server?
red hat 5 update 4 64bit. on an interactive boot i can ping -t my vm linux server from my physical MS XP workstation and a vm W2000 64 bit server until xend is started, after that i get destination unreachable. if i choose not to start xend on the interactive boot i retain connectivity. i have read some blogs that imply this might be a bug - is this so? do I need xend on my vm red hat box that is a database server?
I trying to set up a LDAP server using openLDAP / db4. The server runs fine but I cannot get the client to work. Client and server are on the same machine, as for now. The problem seems to be in PAM. However I cannot start the system-config-authentication tool which should do the trick.
Several of the the items in the menu System --> Administration do not function. They say they are starting but fail to come up then disappear of the task bar. Is there anywhere i can look to see why it has failed to come up?
All item in the menu except; Display, Hardware, Server Settings, System Monitor
I have linux in my system with windows (dual boot). Now when I start my PC. It shows me only Linux, in splash screen. but when i press ENTER key on this. It starts in windows not in linux. And I completely unable to boot my system in linux.
I recently installed centos 5.5 on a new system, details below. All worked fine for a couple of weeks, then the system froze up. No network access, no keyboard/mouse, blank screen. Had to reboot. Happened again about a week later. Then started happening every couple of days, then daily, and today it happened three times.
I see nothing unusual in any of the logs. The freezing does not seem to be correlated with any particular activity. Happened in both gnome and kde. While it's up, everything seems to work fine. I looked on the intel site for a new driver for this chipset but didn't find a linux version. I tried different versions of this same kernel (PAE, centosplus etc) but have not tried an older kernel.
I installed memtest86 (with yum) but when I try to start it from grub, the screen goes blank for a few seconds, then it reboots. Can't get it to start. Tried a bootable memtest86 cd that worked before (couple of years ago) and it wouldn't boot from it (bios is set to boot first from cd). Maybe this is a strong hint?
My next steps are to burn a new cd of memtest86 and try that. And/or to start removing ram to see if any of them are the culprit. In the meantime I'm asking if any of you have had similar problems with this architecture, or have other suggestions of things I could try. I don't have pieces of hardware lying around that I can easily swap in and out, unfortunately. If all this fails I'll try FC13. Any advice on whether or not you think that might fix the problem would be appreciated, before I go to the trouble.code...
I'm running Debian Squeeze on a Dell Studio Laptop, and this morning my computer woke up and gnome was randomly frozen. I dismissed this as a random error and proceeded to hard-reboot the computer. It now will not boot at all. After multiple attempts, every time the boot process hangs on "Starting GNOME display manager gdm3." I even left it there for 2 hours while I was gone to see if it would get past the hang. It did not, and was still stopped at that same line when I got back. get my system back. I have a live CD available to perform maintenance if anyone has an idea of what's wrong.
I did a fresh install of Ubuntu 10.04 on a desktop. I then did the system updates and on the reboot the system now hangs at the splash screen before the login screen. I only get a blinking cursor on the text-based terminals. I don't see the grub menu, I assume because Ubuntu is the only OS on this machine. So I can't boot to single user or text-only mode.
Have just installed 5.4 64 bit on an AMD64 x2 system with 4 GB ram running ESXi4.Text based install went fine, but on reboot starting up it gets as far as 'Starting udev' and just hangs. Checking the performance in ESXi it appears to be using 100% cpu.I have left it for half an hour and it does not progress and the only thing to do is to power cycle the VM.I have searched and found a few suggestions for kernel parameters but they did not make any difference. I can't even get in to a command line as it doesn't boot up far enough.I have reinstalled it several times and also checked the MD5 of the downloaded file and all appears Ok.
I have a SSH box which is command line only and no X, this will be used remote and i'm trying to get the wireless network configured to start at boot. I'm using wpa_supplicant as the access point is secure with WPA2 At present if I send the following commands the machine will connect to the wifi and be reachable via ssh
I just recently purchased a DELL PowerEdge 2850 and have tried installing CentOS 5.4 on it. After the install completes and it does a first boot I get the following error on the DELL console: PROC 1ERROR, PROC 2ERROR E07F0. The monitor remains black and the system hangs. Just out of curiosity I installed Fedora 11 on it to see if it was a hardware problem. Fedora installed and booted no problem. I rebooted with Fedora installed several times and left it running for 24 hours. Everything is working great. Is there something I am missing in the CentOS 5.4 install?
Below is the Hardware Config: Dell PowerEdge 2850 PERC 4eDi RAID Controller 8GB PC-5300 ECC Memory 2 Intel Xeon CPU Dual Core 2.8GHz 800FSB 4MB Cache - SL8MA ATI Radeon 7000 Video Card
I am trying to boot the CentOS live cd off of usb. I used unetbootin to put CentOS on my 8gb usb drive after downloading the DVD iso. During boot it loads the image and continues until it reaches this point.
>Linux agpgart interface v0.101 (c) Dave Jones >Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
After this it hangs and won't continue. I am using a Compaq evo n800w and the bios is just updated to the latest version.
i have 5.4 installed on a super-micro server motherboard (has two gigabit ether ports). when i boot while its initializing everything it gets to the "starting eth0" and just stays there?
right before it boots up and says press any key for options i press a key and choose "centos (2.6.18-164.el5)" and it boots up fine but when i choose "centos (2,6,18-164.el5xen)" the problem occurs. and that is the default boot option.
I have a problem with the kernel update to 220.127.116.11. Up until 2.6.33.x my system boots fine, but with this update the boot stops at the moment that the mouse cursor should become visible. To resolve the problem, I've gone back to 2.6.33.x and removed the 2.6.34 kernel but I wonder what happens with the next kernel update. Anyone else having this problem?
I have updated to the new kernel that was available from 11.2 and now I cant use my system.
It boots up into kde 4.3.5 and then right when its just finishing it freezes everytime and I hear that last tone of the bootup sound ring continually until I force a shutdown. Anyone else have this issue with the update?