On Thu, Apr 14, 2011 at 11:58:43PM +0800, ruozeng wang wrote:
> Yes, I've tried some of the xen command , but all of them return this error
> :
> "*Unable to connect to xend: No such file or dirctory. Is xend running?*"
>
> Then I found the infomation in xend-debug.log, which I've send in last mail.
>
> Here is the content of xend.log:
>
> *[2011-04-13 20:35:52 6937] DEBUG (tcp:96) Listening on :8002
> [2011-04-13 20:35:52 6937] ERROR (SrvDaemon:349) Exception starting xend
> ((98, 'Address already in use'))
> Traceback (most recent call last):
> File "usr/lib/python2.5/site-**packages/xen/xend/server/**SrvDaemon.py",
> line 339, in run
> relocate.listenRelocation()
> File "usr/lib/python2.5/site-**packages/xen/xend/server/**relocate.py",
> line 159, in listenRelocation
> hosts_allow = hosts_allow)
> File "usr/lib/python2.5/site-**packages/xen/web/tcp.py", line 38, in
> __init__
> connection.SocketListener.__**init__(self, protocol_class)
> File "usr/lib/python2.5/site-**packages/xen/web/connection.**py", line 89,
> in __init__
> self.sock = self.createSocket()
> File "usr/lib/python2.5/site-**packages/xen/web/tcp.py", line 97, in
> createSocket
> sock.bind((self.interface, self.port))
> File "<string>", line 1, in bind
> error: (98, 'Address already in use')
> [2011-04-13 20:35:52 6936] INFO (SrvDaemon:220) Xend exited with status 1.
>
>
> *
> but since I set loglevel to DEBUG in xend-config.sxp, it changed to this:
>
> *[2011-04-14 23:40:21 6477] INFO (SrvDaemon:332) Xend Daemon started
> [2011-04-14 23:40:21 6477] INFO (SrvDaemon:336) Xend changeset: unavailable.
> [2011-04-14 23:40:21 6477] DEBUG (tcp:96) Listening on :8002
> [2011-04-14 23:40:22 6477] DEBUG (XendNode:332) pscsi record count: 10
> [2011-04-14 23:40:22 6477] DEBUG (XendCPUPool:747) recreate_active_pools*
>
> When I enter "xend start", the output infomation is like this:
> *
> root@ruozeng-desktop2:~# xend start
> There is already a pid file /var/run/dhclient.eth0.pid with pid 5962
> killed old client process, removed PID file
> Internet Systems Consortium DHCP Client V3.0.6
> Copyright 2004-2007 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> Listening on LPF/eth0/00:1d:7d:57:23:12
> Sending on LPF/eth0/00:1d:7d:57:23:12
> Sending on Socket/fallback
> DHCPRELEASE on eth0 to 172.21.201.1 port 67
> Nothing to flush.
> There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
> Internet Systems Consortium DHCP Client V3.0.6
> Copyright 2004-2007 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> Listening on LPF/eth0/00:1d:7d:57:23:12
> Sending on LPF/eth0/00:1d:7d:57:23:12
> Sending on Socket/fallback
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
> DHCPOFFER of 172.21.6.114 from 172.21.6.254
> DHCPREQUEST of 172.21.6.114 on eth0 to 255.255.255.255 port 67
> DHCPACK of 172.21.6.114 from 172.21.6.254
> bound to 172.21.6.114 -- renewal in 41866 seconds.
> *
How did you get it to do a dhclient on eth0? Can you just
re-install the toolstack from the hg tree? I am really not sure
why it is in such a state.
> Then it stucked here. I have to use control-c to interrupt.
>
> If I use ps -A, it shows that there are four "xend" process :
>
> *6306 pts/0 00:00:00 xend
> 6376 ? 00:00:00 kworker/1:2
> 6442 ? 00:00:00 dhclient3
> 6474 pts/0 00:00:00 blktapctrl <defunct>
> 6475 ? 00:00:00 xend <defunct>
> 6476 ? 00:00:00 xend
> 6477 ? 00:00:00 xend
> *
> And some other xen related processes, xenbus, etc.
>
> ruozeng.w
> 2011-4-14
>
> 2011/4/14 Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
>
> > On Thu, Apr 14, 2011 at 08:22:24PM +0800, ruozeng wang wrote:
> > > This is from /var/log/xen/xend-debug.log:
> >
> > Look also in the xend.log file, and make sure to turn on the DEBUg
> > options in your /etc/xen/xend-config.sxp file. And read through the
> > file please.
> >
> > Have you tried using 'xl'?
> >
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home