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-bugs

[Xen-bugs] [Bug 483] New: Random crashes of a xen instance

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 483] New: Random crashes of a xen instance
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 18 Jan 2006 15:27:15 +0000
Delivery-date: Wed, 18 Jan 2006 15:39:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=483

           Summary: Random crashes of a xen instance
           Product: Xen
           Version: 2.0
          Platform: All
               URL: http://creme.schottelius.org/~nico/linux/debug/xen/
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: nico-linux-xen@xxxxxxxxxxxxxxx


Hello!

One of our servers freezes randomly. Sometimes it takes about 30 minutes and
sometime it takes several hours.

I put all information I found together at the url above.

When the instance freezes, the xenserver (domain0) is still running perfectly.
The freezed server is still reachable via ping. nmap says that all the ports
where services are behind are still open.

Though it's impossible to get anything but low level network traffic (ping,
tcp-handshake) from the system.

When using xm sysrq, it is possible to send 's-u-b' and reboot it. Most
times. The console (xm console srsyg01) is also freezed, but it displays
all infrormation, which come from sysrq
(See: http://creme.schottelius.org/~nico/linux/debug/xen/sysrq-after-freeze)

What can we do to debug it?

Before those crashes appeared this server had another problem:
Sometimes it took extremly long to reach it, ping times grow up to
10 to 16 seconds in a 100Mbit/s Lan (Normal ping times are 0.9ms).

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 483] New: Random crashes of a xen instance, bugzilla-daemon <=