From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Can't manage virtual servers after upgrade
Date: Tue, 08 Sep 2009 10:50:55 -0400 [thread overview]
Message-ID: <1252421455.3349.31.camel@localhost.localdomain> (raw)
In-Reply-To: <E963DDE784034556A79E2965CA70312B@bangard>
On Fri, 2009-09-04 at 14:26 +0400, Alexander wrote:
> Hello!
>
> I have upgrade 3 servers in cluster to RHEL 5.4 and now i can't start virtual machine service via luci. In /var/log/messages i see errors:
>
> Sep 4 11:42:55 hwcl-n1 clurgmgrd[5374]: <notice> start on vm "vps-nagios" returned 1 (generic error)
> Sep 4 11:42:55 hwcl-n1 clurgmgrd[5374]: <warning> #68: Failed to start vm:vps-nagios; return value: 1
> Sep 4 11:42:55 hwcl-n1 clurgmgrd[5374]: <notice> Stopping service vm:vps-nagios
Did xend not start for some reason after the upgrade?
-- Lon
prev parent reply other threads:[~2009-09-08 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 10:26 [Cluster-devel] Can't manage virtual servers after upgrade Alexander
2009-09-08 14:50 ` Lon Hohberger [this message]
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=1252421455.3349.31.camel@localhost.localdomain \
--to=lhh@redhat.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).