WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] xen 2.0.6, on_crash = 'restart' not restarting after crash

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen 2.0.6, on_crash = 'restart' not restarting after crash
From: Steve Wray <steve.wray@xxxxxxxxx>
Date: Mon, 30 Apr 2007 09:35:14 +1200
Delivery-date: Sun, 29 Apr 2007 14:34:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.5 (X11/20060813)
Hi all,

We have a xen instance (under xen 2.0.6) thats pretty unreliable; the
domU crashes fairly regularly.

Yes, we are trying to figure out why, but in the meantime I discovered
that there is a config option 'on_crash'.

We've implemented this in the config file for that xen domain and we
have this in the config file for the domain:

restart = 'always'

on_crash = 'restart'


The domain has indeed crashed since this was implemented and did not
appear to recover, at least not for the 6 minutes we gave it to restart
the domain:

[2007-04-30 09:06:19 xend] INFO (XendRoot:112) EVENT> xend.domain.exit
['domUhostname', '14', 'crash']
[2007-04-30 09:06:19 xend] INFO (XendRoot:112) EVENT>
xend.domain.destroy ['domUhostname', '14']
[2007-04-30 09:06:20 xend] INFO (XendRoot:112) EVENT> xend.domain.died
['domUhostname', '14']
[2007-04-30 09:12:03 xend] DEBUG (XendDomainInfo:720) init_domain>
Created domain=15 name=domUhostname memory=1200
[2007-04-30 09:12:03 xend] INFO (console:94) Created console id=14
domain=15 port=9615


The 'on_crash' option does appear to be part of 2.0.6, or at least the
documentation I've read suggests so and xen does not complain in the
least when the domain is started.

So, if on_crash does not restart a domain after a 'crash' (like it says
in the log) what does it do?

And are there any other things we can do to restart a domain after a crash?

Thanks!

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>