[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.