Written May 10, 2009 in linux, sysadmin

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.

1 comment on ' XenD fails to start due to xml error '

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

      Written by Ted on November 02, 2009 at 1:14pm

Leave a comment

name (req'd)

email (req'd)

website