Description of problem: xm fails to communicate with the xend service. Version-Release number of selected component (if applicable): xen-3.0.1-4 and xen-3.0.2-0.FC5.1 from updates-testing How reproducible: Always Steps to Reproduce: 1. /sbin/service xend start 2. xm list 3. Actual results: Error: Error connecting to xend: No such file or directory. Is xend running? Expected results: A list showing Dom0 Additional info: Runing FC5 with the latest updates as of 05/11/2006. (yum update). uname -r output: 2.6.16-1.2111_FC5xen0 selinux is disabled in /etc/selinux/config: SELINUX=disabled I've tried both xen rpms from updates, as well as updates-testing. both versions create these .pid files in /var/run: -rwS--x--T 1 root root 5 May 11 11:13 xenconsoled.pid -rw-r--r-- 1 root root 4 May 11 11:13 xend.pid -rw------- 1 root root 5 May 11 11:13 xenstore.pid some of the attributes for xenconsoled.pid seem odd btw... out of all of those pid files, only the xend.pid has a matching, running process with the same id. xend.pid: 1516 xenstore.pid: 1510 xenconsoled.pid: 1515 ps ax|grep "xen" 1513 ? S 0:00 python /usr/sbin/xend start 1516 ? Sl 0:00 python /usr/sbin/xend start netstat -a -n -p|grep python with updates-testing version of xen (xen-3.0.2-0.FC5.1) shows: tcp 0 0 0.0.0.0:8002 0.0.0.0:* LISTEN 1516/python netstat -a -n -p|grep python with updates version of xen ( xen-3.0.1-4) shows an additional listening socket: tcp 0 0 0.0.0.0:8002 0.0.0.0:* LISTEN 1593/python unix 2 [ ACC ] STREAM LISTENING 5306 1593/python /var/lib/xend/relocation-socket Other things to note: socket and socket_ro are created in /var/run/xendstored when the xend service is started, and /var/lib/xenstored/tdb is created as well. Stopping the xend service, doesn't wipe out any .pid file, nor those the socket, socket_ro or that tdb file, but the running processes do die. running /usr/sbin/xend trace_start shows these exceptions: --cut-- | 102 try: | 103 inst | ! Exception: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendNode.py", line 103, in instance inst NameError: global name 'inst' is not defined | 104 except: | 105 inst = XendNode() | |> XendNode.py:__init__ | | 31 self.xc = xen.lowlevel.xc.xc() --cut-- --cut-- | 546 try: | 547 inst | ! Exception: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 547, in instance inst NameError: global name 'inst' is not defined | 548 except: | 549 inst = XendDomain() | |> XendDomain.py:__init__ | | 60 self.domains = {} | | 61 self.domains_lock = threading.RLock() --cut-- --cut-- | | 17 if not xs_handle: | | 18 xs_handle = xen.lowlevel.xs.xs() | | ! Exception: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle xs_handle = xen.lowlevel.xs.xs() RuntimeError: (111, 'Connection refused') | | < xenstore/xsutil.py:xshandle --cut-- with more of those 111, 'Connection refused' following... I've included the complete xend.trace file.
Created attachment 128908 [details] trace file of starting xend with the option "trace_start"
I have same problems with latest kernel-xen0-2.6.16-1.2111_FC5, works well after reboot to older kernel kernel-xen0-2.6.16-1.2096_FC5. May be it is a kernel problem.
Created attachment 128970 [details] Extract from /var/log/xend.log
*** This bug has been marked as a duplicate of 190899 ***