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

[Xen-devel] xend crashing

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xend crashing
From: Matt Ayres <matta@xxxxxxxxxxxx>
Date: Thu, 10 Feb 2005 12:18:17 -0500
Delivery-date: Thu, 10 Feb 2005 17:19:38 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: TekTonic
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Hi,

I don't have access to the prior e-mails regarding xend crashing, but I
just experienced it again.  xfrd starts, but xend does not.  Here are
the last few lines of a strace of 'xend start'

open("/usr/lib/python/xen/xend/server/domain.pyc", O_RDONLY|O_LARGEFILE)
= 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=2943, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7ba5000
read(9, ";\362\r\n\331\224\4Bc\0\0\0\0\0\0\0\0\3\0\0\0@\0\0\0s\\"...,
4096) = 2943
fstat64(9, {st_mode=S_IFREG|0644, st_size=2943, ...}) = 0
read(9, "", 4096)                       = 0
close(9)                                = 0
munmap(0xb7ba5000, 4096)                = 0
close(6)                                = 0
close(3)                                = 0
geteuid32()                             = 0
fork()                                  = 31360
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 31360
--- SIGCHLD (Child exited) @ 0 (0) ---
close(7)                                = 0
munmap(0xb7c2f000, 4096)                = 0
rt_sigaction(SIGINT, NULL, {0x4c805080, [], 0}, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, NULL, 8) = 0
close(8)                                = 0
exit_group(0)                           = ?


nothing in /var/log/xend.log except for:

[2005-02-10 12:11:05 xend] INFO (SrvDaemon:607) Xend Daemon started


I know this isn't much information. Nothing is in xfrd.log or xend-
debug.log.  How can I turn on debugging to get more useful information
to provide?  I'm running FC3 and have the very latest updates
installed.  
-- 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] xend crashing, Matt Ayres <=