CentOS 5 :: Freezing At Starting Xend After Update
Apr 18, 2011
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 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 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.
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?
Fedora 14 is freezing while starting services. what I know is that the system is passing kernel verification. Is there a way to choose which service to start during bootup?
I have CentOS 5.4, and am trying to install mailman.sudo yum install mailmanlook fine, tries to install Package 3:mailman-2.1.9-4.el5.i386, gets to "Installing: mailman [#### ] 1/1"and then freezes with #'s about 80% across. There it stays, until I kill -9 from a different shell.yum-complete-transaction just repeats the same experience.yum update works fine, everything else updates without trouble.
I updated the kernel on a ubuntu machine yesterday. No problems so far. But after rebooting I couldn't login via SSH anymore. The session freezes right after authentication. Doesn't matter wether its pubkey or keyboard-interactive.
I couldn't find any hints so far. auth.log does not seem to show any warnings/errors.
Strange thing is: I'm able to log in via SFTP (SCP). I can even use WinSCP to open a "unix like" shell, but it only works for basic commands.
Here is the output of auth.log, when logging in via SFTP/SCP
Code:
This is the output when trying to open a real ssh session:
I had Ubuntu working perfectly until I installed updates for the proprietary Nvidia drivers.Now Ubuntu freezes at the Ubuntu loading screen. Im using Ubuntu 10.04 64bit.I used to know how to access the terminal at bootup but I no longer remember.
I have a fresh install of CentOS 5.5 on small thin client system with a 80G HDDs, 1 GB ram [URL], I have run into an issue where the system just locks up and freezes and I can no longer access it, cant ping it, cant use webmin and cant view its web pages. The system seemed to be running fine unitl I left it to do some updates via webmin as it informed me there were 118 updates. I really only use the system as a LAN captive network server, and it is currently in the testing phase for this setup. The install went on with no issues and it ran fine, but now every so often within 12 hours it just locks up and I have to reboot. kdump shows no logs so I am finding hard to work out what is going on. but have installed it on 5 of my servers 4x ibm x335 and this . I intend to use the mini server for a captive portal system displaying advertising and promotions to wireless clients.
I've been having problems for a while with my pc at work and after a bout with a similar desktop I figured out that it somehow relates to the kernel updates from 5.3 to 5.4. I have two machines with identical motherboards (Asus M3a32-mvp), cpu ( athlon 64 X2 6400) and memory (8 gigs Corsair) with different video cards.
My desktop at work started with Centos 5.2 and was kept updated to 5.4 along the way. The other PC is my desktop at home and it started out at 5.3 and stayed there until recently mainly because my wife mostly uses it so I just never got around to doing updates.
Here is the problem, a while back the work PC started doing weird things, it would stutter, freeze up, sometime the mouse cursor would freeze into a cross hair and sometimes completely lock me out where even the keyboard wouldn't work so I had to kill power to reboot anf get control back. I eventually discovered that if I still had keyboard access I could jump to a console window, log in and killall nautilus or killall gnome-panel and I might get things back to normal for a while. I can even log in with another machine to use the killall commands if the keyboard locks up. I checked TOP during these episodes to see what was killing the system, I figured something was running a muck and gobbling up processing time or memory but nothing shows that appears to be off.
Like I said the home system was on 5.3 and not showing the stuttering problems so I even considered that the video card drivers might be causing something, that is until I tried to update the home system and got the same issues.
I had a hard drive failing at home so I figured I'd back up the data and reinstall the main system on a new one so I could start over with a clean system. This time I started from 5.4. Almost imediately I discovered the freezing problems after the complete install so after trying a few things I wiped and reloaded, couldn't mess around too long with it as the wife was really complaining about not having a PC, a 5.3 version. Bingo, now the system functions perfectly, no stuttering or freezing up. I then used yum updates to updates everything but the kernel. This also seemed to give me a system without freezes so I stopped there with the home machine.
Just to be clear the home pc used the standard yum repositories defaulted in the setup i didn't add any so it isn't a 3rd party repo causing the problems with the home machine. So it looks like the updates from 5.3 to 5.4 regarding the kernel seem to be causing me problems.
It's getting so bad at work I'm planning on wiping and reloading a 5.3 version and going from there but that's alot of work so I'd really like to just fix what is going on with the 5.4 version.
I'm having a bit of a problem with a CentOS install I'm working on.This computer is an Asus M2A-VM mobo with the latest bios and a fully patched CentOS 5.3 system.The system randomly freezes and I've been able to narrow it down to what i think is ACPI issues with the chipset since the system is rock stable if I use the ACPI=off option in grub. However, when I do, I get messages about OHCI and EGCI controllers not having the correct PCI IRQ or somesuch and my USB don't work. Since this system has a usb keyboard, mice and printer, that's a bit of an issue!The system boots fine but will freeze after a random amount of time, sometimes even during startup (after the X Window system has been opened).
I'm at the end of my rope here as I'm admittedly pretty new to Linux (about 2 months experience although I've succesfully set up 5 systems and a zimbra server in that time - slowly learning when I'm trying to do something) and I've been scouring the net to try and find a solution to no avail.I know this particular chipset seems to be very trouble prone if I look around but the only thing I could find about issues like mine was related to ACPI with the chipset but that supposedly solved in earlier kernel revisions (and I have the latest kernel).troubleshoot the defective part of ACPI on my chipset would be appreciated so I can turn off the offending ACPI "feature".
PS : I also get an error message when booting : ACPI expecting a [REFERENCE] package element, found type F7B953PC
I need to copy files over from a Solaris 2.6 box to my machine running Centos 5.3. I have to use RCP since the Solaris box is so old that is the only inter-machine copy command available.How do I enable rshd services on my centos box? Detailed explanation would be apperciated since I am from the ssh generation.
I updated my Suse 11.1 distribution and suddenly Firefox stopped working. I went to a terminal and typed in "firefox" and nothing happened. No error message, no nothing. It just stood there.
If I did the sae as root or as another user, then Firefox would load as usual.
The issue for me was that I was using NoMachine (NX) to access my machine. It adds some lines to the LD_PRELOAD session variable. I removed the variable content et voila! I've got my Firefox working again
To check if you're in the same potential situation, do a "set | grep LD" and check the result. If you've got "LD_PRELOAD=" with nothing afterwards, you're not in the same case as me. Good luck finding our fix. If you see "LD_PRELOAD=some stuff here" then you may be in the same case as me. The type in "LD_PRELOAD=" and hit enter to clean he variable. Then in the same terminal type in "firefox" and it should just work.
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 ran an update after installing the OpenSuse 11.2 Gnome Live CD and could not start Gnome.Signing in would only get me a blank screen with wallpaper.Changing the display manager in /etc/sysconfig/displaymanager to kdm (from the default gdm) resolves this issue for me:DISPLAYMANAGER="kdm"
I get the message when I try to deploy a virtual machine in the virt-mnager. Unable to complete install: "Post operation failed: xend_post: error from xend daemon: (xend.err "Error creating domain: device model "usr/lib64/xen/bin/qemu-dm" not found") Unable to complete install '<class 'libvirt.libvirtError'> POST operation failed: xend_post: error from xen daemon: (xend.err "Error creating domain: device model '/usr/lib64/xen/bin/qemu-dm' not found") Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1555, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 973, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1038, in _do_install "install") File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1009, in _create_guest dom = self.conn.createLinux(start_xml, 0) File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1277, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err "Error creating domain: device model '/usr/lib64/xen/bin/qemu-dm' not found")
I updated my fc12 x86_64 server today, and one of the updated included kernel 2.6.31.12-174.2.3.fc12.x86_64 from the previous one of kernel-2.6.31.9-174.fc12.x86_64.When I boot with that kernel, it stops when my logical volumes that are built on a raid 5 array (linux software raid built using mdadm) are not there.I can start them afterward with mdadm --auto-detect which seemingly loads the appropriate modules and starts the array, but I have never had to do this before.
Reading the mdadm man page, it mentions that this is generally done by the initrd. So, I am guessing the initrd that came with the new kernel is missing something.
I just installed today's updates (apart from XFCE, which I had installed from Robby's website) and get the following error when I try to start exaile:
Code: INFO : Loading Exaile 0.3.0.1... INFO : Loading settings... INFO : Setting up deferred idle manager function... INFO : Loading plugins... INFO : Loading collection... INFO : Loading devices... INFO : HAL Providers: [<cd.CDHandler object at 0x15c2e50>] INFO : Loading interface... /usr/lib64/exaile/xlgui/__init__.py:82: GtkWarning: Unable to locate theme engine in module_path: "thinice", 'ExaileWindow', 'exaile') Segmentation fault
I'm looking at the changelogs and can't figure out which one is the culprit.
this is probably something trivial but how can I auto start gdm on CentOS 5.4??I had to perform a text install due to Anaconda having some issues as I'm running Cent on Sun's VirtualBox.I have tried to add chkconfig --add gdm which didn't work, also there is no init.d script either for gdm so not sure if it's in a directory somewhere or if I have to create it manually??IF I run simply gdm from teh cli then everything is ok and starts fine....
Just used Synaptic to update my video driver for the XFX RADEON R250x. It was working before when I had installed the drivers from the AMD site. But I was told I needed to use the kernel compatible, so I did this update. Now it boots up and hangs with blank screen where it would usually go to login. I've got a boot disc where I can boot into and we can look at the logs ....
I loaded the Pre-Release version of Ubuntu 10.10.1 32 bit workstation. It ran mostly fine for about a 2 months. Then I did an online update and it told me that I had to reboot. When I did, I booted to a splash screen and then a dead machine with a black screen where control-alt-delete does nothing, no disk activity, no mouse, no keyboard, totally dead. Had to hit reset button. I booted to a suse partition and hacked the grub entry to remove the splash and silent to get more spew at boot time. The last thing before the screen goes black is starting NBD client. I have my email and various directories on my central server so I need NFS. Is there a way I can hack my way to get it to boot even without NFS temporarily to possibly rebuild the nbd kernel module? I have looked at the /var/log/ syslog, daemon, debug, kern messages and gdm log files and don't see any indication of why it crashed. Where else can I look?
I recentlly updated my Centos 5.5 to 5.6 usnig yum update, and since then, the QT4 designer cannot be started. If I'm running it (I installed it from source to /usr/local/qt..) the command stuck and nothing happens. The wierd thing is that if I'm running "strace /usr/local/qt/bin/designer4" the program starts.
I usually run my updates every Friday, my last good update was 4-Mar-2011. I could not update this week and got an error -"PackageKit Error repo-not-available: File '/repodata/repomd.xml' not found on medium http://download.opensuse.org/repositories/openSUSE:/Tumbleweed:/Raw/openSUSE_Tumbleweed_standard/'"I get a similar error message when starting Yast Software Management.Is this related to the 11.4 release? I'm waiting for fewer bugs before I upgrade to 11.4, so I'd like to be able to keep current with 11.3.