xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "dwight at supercomputer.org" <dwight@supercomputer.org>
To: xen-devel@lists.xensource.com
Subject: XCP - FYI - An easy way to wedge (and fix) a Cloud
Date: Tue, 8 Jun 2010 09:04:31 -0700	[thread overview]
Message-ID: <201006080904.31362.dwight@supercomputer.org> (raw)

This is mostly FYI. I know someone else is going to run into this.

It turns out that it's real easy to wedge an entire Cloud with
the default configurations in XCP 0.1.1. We saw this recently
with our Development Cloud.

It turns out that /var/log had filled up the root filesystem on
the master.  500M+ worth of messages in there. After I tracked 
down the problem, and freed this space up, everything started  
working again.

When this happens, various things either fail mysteriously 
(including a failure of the slaves and master to reboot),
xsconsole wedging (on the master and slaves), and OpenXenCenter 
not being able to connect, and at best messages that aren't
helpful.

I would recommend, at the very least, that compression of the
logs in logrotate.conf be turned on. I'd also strongly  recommend
that this be the default in release 0.5.

Myself, I've taken this further, by putting logrotate into the
hourly cronjob. And we're going to change our automatic 
installation scripts to put /var on a separate, large disk 
volume, not on the root filesystem.

Having /var separate from the root filesystem is generally
a wise move for servers, so that /var doesn't impact the root.

I'd also add that having grub available would've been helpful.

   -dwight-

             reply	other threads:[~2010-06-08 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 16:04 dwight at supercomputer.org [this message]
2010-06-08 19:08 ` XCP - FYI - An easy way to wedge (and fix) a Cloud Pasi Kärkkäinen
2010-06-08 20:36 ` Daniel Stodden
2010-06-09 16:58   ` dwight at supercomputer.org
2010-06-09 18:02     ` Roger Cruz
2010-06-10 10:07     ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201006080904.31362.dwight@supercomputer.org \
    --to=dwight@supercomputer.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).