Hi,
Recently I have installed Debian Lenny on
two different machines (different ram size, disks, Xeon dual and quad core,
filesystems both xfs and ext3, etc). Packages versions:
Dom0:
ii
libc6-xen
2.7-18lenny4
GNU C Library: Shared libraries [Xen version]
ii
libxenstore3.0
3.2.1-2
Xenstore communications library for Xen
ii linux-image-2.6.26-2-xen-686
2.6.26-24
Linux 2.6.26 image on i686, oldstyle Xen support
ii
linux-modules-2.6.26-2-xen-686
2.6.26-24
Linux 2.6.26 modules on i686
ii
xen-hypervisor-3.2-1-i386
3.2.1-2
The Xen Hypervisor on i386
ii xen-linux-system-2.6.26-2-xen-686
2.6.26-24
XEN system with Linux 2.6.26
image on i686
ii
xen-shell
1.8-3
Console based Xen administration utility
ii
xen-tools
3.9-4
Tools to manage Debian XEN virtual servers
ii
xen-utils-3.2-1
3.2.1-2
XEN administrative tools
ii
xen-utils-common
3.2.0-2
XEN administrative tools - common files
ii
xenstore-utils
3.2.1-2
Xenstore utilities for Xen
domU’s:
ii
libc6-xen
2.7-18lenny4
GNU C Library: Shared libraries [Xen version
ii linux-modules-2.6.26-2-xen-686
2.6.26-24
Linux 2.6.26 modules on i686
those are common for both installations.
Anly standard packages were installed using “apt-get”. No
compiling, no unstable releases…. There are 2-3 DomU’s on each
machine. There have very little usage (load average under 1.0). Both
installations was made about month ago. During this time domU’s are
randomly crashing. Interval between those crashes vary between single day and
week. There are no logs about reason of those crashes, just “Domain has
crashed” in xend.log and after that log about xen trying to respawn DomU
but previous instance is still running. Only a single DomU on machine is
crashing at a time – others run stable at the same time. Which DomU will
crash next time is undeterminable and random…
Funny, that times of most those crashes are
similar to MRTG executed from CRON (and log about this execution is often last
in syslog just before crash), however there are nothing specific in MRTG config
(getting cpu usage, load average, disk space) but using piped commands instead
of snmp (they are simple: cat /proc/meminfo | grep | awk… and so on)
Dom0 during those crashes is stable and
never crashed or been restarted…
Any suggestion how to solve this situation?
Downgrade / upgrade to some ”unstable” packages that are known to
be much more stable than those from default Lenny installation?
Home