Skip to content
Tags

, , , , , ,

XenD fails to start due to xml error

by karlkatzke on May 10th, 2009

Seeing this error message in /var/log/xen/xend.log? 

ERROR (SrvDaemon:347) Exception starting xend (no
element found: line 1, column 0)

You’ve got a corrupt xen status base. Go under /var/lib/xend/ and remove any xml files under any of those directories. Don’t delete the directories or sockets themselves.

I had this happen after a nice STONITH-induced reboot loop. Hint: When you’re setting up new devices in a cluster with STONITH, you might consider using “stonith-action=poweroff” so that when you create or encounter an error in your cluster configuration you don’t cause your machines to power cycle endlessly.

From → linux, sysadmin

3 Comments →
  1. Ted permalink

    Thanks! For some reason had this error, but the xen log files failed me this time.

  2. Tapas Mishra permalink

    Thanks you saved a lot of time for me.

  3. Thank you Karl. permalink

    How did you figure that out?

Leave a Reply

Note: XHTML is allowed. Your email address will never be published.

Subscribe to this comment feed via RSS