Mailing List Archive

Problems starting xend
Hi

I have managed to fix my networking issues.

However, I am still having problems starting xend.

When I try and start xend via "sudo xend start" it appears to start
( and the log claims it has started ) :-

[2005-06-09 20:14:09 xend] INFO (SrvDaemon:610) Xend Daemon started
[2005-06-10 18:56:12 xend] INFO (SrvDaemon:610) Xend Daemon started
[2005-06-10 19:00:28 xend] INFO (SrvDaemon:610) Xend Daemon started
[2005-06-11 10:57:49 xend] INFO (SrvDaemon:610) Xend Daemon started
[2005-06-11 11:45:55 xend] INFO (SrvDaemon:610) Xend Daemon started
[2005-06-11 12:00:08 xend] INFO (SrvDaemon:610) Xend Daemon started



but "sudo xend status" shows nothing.

ifconfig shows :-

eth0 Link encap:Ethernet HWaddr 00:0D:61:1A:E2:25
inet addr:81.77.153.206 Bcast:255.255.255.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:161 errors:0 dropped:0 overruns:0 frame:0
TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24562 (23.9 KiB) TX bytes:28627 (27.9 KiB)
Interrupt:19 Base address:0xe000

eth1 Link encap:Ethernet HWaddr 00:04:5A:8C:67:6A
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1282 (1.2 KiB)
Interrupt:17 Base address:0xe400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5717 errors:0 dropped:0 overruns:0 frame:0
TX packets:5717 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1503288 (1.4 MiB) TX bytes:1503288 (1.4 MiB)

xen-br0 Link encap:Ethernet HWaddr 00:0D:61:1A:E2:25
inet addr:84.67.38.123 Bcast:255.255.255.255
Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:138 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16408 (16.0 KiB) TX bytes:8254 (8.0 KiB)

which looks correct.


However, when I then try and start a new domain via

"xm create -c config vmid=1"

I get the following error :-


stewart@gateway:~$ xm create -c config vmid=1
Using config file "config".
(111, 'Connection refused')
Error: Error connecting to xend, is xend running?
stewart@gateway:~$

Any ideas what's going wrong here ?

Regards


Stewart




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
Couldn't help but notice your on a non-priveleged account and not using
sudo on your "stewart@gateway:~$ xm create -c config vmid=1"...could this
be the problem? Try as root perhaps.

Hope this helps,
John Fairbairn


> Hi
>
> I have managed to fix my networking issues.
>
> However, I am still having problems starting xend.
>
> When I try and start xend via "sudo xend start" it appears to start
> ( and the log claims it has started ) :-
>
> [2005-06-09 20:14:09 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-10 18:56:12 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-10 19:00:28 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-11 10:57:49 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-11 11:45:55 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-11 12:00:08 xend] INFO (SrvDaemon:610) Xend Daemon started
>
>
>
> but "sudo xend status" shows nothing.
>
> ifconfig shows :-
>
> eth0 Link encap:Ethernet HWaddr 00:0D:61:1A:E2:25
> inet addr:81.77.153.206 Bcast:255.255.255.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:161 errors:0 dropped:0 overruns:0 frame:0
> TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:24562 (23.9 KiB) TX bytes:28627 (27.9 KiB)
> Interrupt:19 Base address:0xe000
>
> eth1 Link encap:Ethernet HWaddr 00:04:5A:8C:67:6A
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.0.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:1282 (1.2 KiB)
> Interrupt:17 Base address:0xe400
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:5717 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5717 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1503288 (1.4 MiB) TX bytes:1503288 (1.4 MiB)
>
> xen-br0 Link encap:Ethernet HWaddr 00:0D:61:1A:E2:25
> inet addr:84.67.38.123 Bcast:255.255.255.255
> Mask:255.255.255.255
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:138 errors:0 dropped:0 overruns:0 frame:0
> TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:16408 (16.0 KiB) TX bytes:8254 (8.0 KiB)
>
> which looks correct.
>
>
> However, when I then try and start a new domain via
>
> "xm create -c config vmid=1"
>
> I get the following error :-
>
>
> stewart@gateway:~$ xm create -c config vmid=1
> Using config file "config".
> (111, 'Connection refused')
> Error: Error connecting to xend, is xend running?
> stewart@gateway:~$
>
> Any ideas what's going wrong here ?
>
> Regards
>
>
> Stewart
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


--
In the game of life it takes a root prompt to really foul up.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
Stewart,

Can you 'ps ax' to see if xend is actually running (it'll be a python
process).

If so, run 'netstat -ltno' to see if a python process is listening on
port 8000 on any interface.

If that's working then check your firewall to see if you are blocking
connections to localhost:8000.

James

Stewart Outram wrote:
> Hi
>
> I have managed to fix my networking issues.
>
> However, I am still having problems starting xend.
>
> When I try and start xend via "sudo xend start" it appears to start
> ( and the log claims it has started ) :-
>
> [2005-06-09 20:14:09 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-10 18:56:12 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-10 19:00:28 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-11 10:57:49 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-11 11:45:55 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-06-11 12:00:08 xend] INFO (SrvDaemon:610) Xend Daemon started
>
>
>
> but "sudo xend status" shows nothing.
>
> ifconfig shows :-
>
> eth0 Link encap:Ethernet HWaddr 00:0D:61:1A:E2:25
> inet addr:81.77.153.206 Bcast:255.255.255.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:161 errors:0 dropped:0 overruns:0 frame:0
> TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:24562 (23.9 KiB) TX bytes:28627 (27.9 KiB)
> Interrupt:19 Base address:0xe000
>
> eth1 Link encap:Ethernet HWaddr 00:04:5A:8C:67:6A
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.0.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:1282 (1.2 KiB)
> Interrupt:17 Base address:0xe400
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:5717 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5717 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1503288 (1.4 MiB) TX bytes:1503288 (1.4 MiB)
>
> xen-br0 Link encap:Ethernet HWaddr 00:0D:61:1A:E2:25
> inet addr:84.67.38.123 Bcast:255.255.255.255
> Mask:255.255.255.255
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:138 errors:0 dropped:0 overruns:0 frame:0
> TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:16408 (16.0 KiB) TX bytes:8254 (8.0 KiB)
>
> which looks correct.
>
>
> However, when I then try and start a new domain via
>
> "xm create -c config vmid=1"
>
> I get the following error :-
>
>
> stewart@gateway:~$ xm create -c config vmid=1
> Using config file "config".
> (111, 'Connection refused')
> Error: Error connecting to xend, is xend running?
> stewart@gateway:~$
>
> Any ideas what's going wrong here ?
>
> Regards
>
>
> Stewart
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
OK xend is failing after start somehow. Let's have a look at your
xend-debug.log. Can you also check your memory utilisation (e.g. with
'top') - you have a load of stuff running and if the oom killer is
kicking in then xend may be suffering.

Please post replies to the list rather than just to me. Others here may
be interested and able to help.

For reference, there was a typo in my netstat command line suggestion,
should have been 'netstat -ltnp' to get the process names. (Irrelevant
now since xend isn't running.)

James

Stewart Outram wrote:
> Hi James
>
> Thanks for your reply.
>
>
> stewart@gateway:~$ sudo ps ax
> PID TTY STAT TIME COMMAND
> 1 ? S 0:00 init [2]
> 2 ? SN 0:00 [ksoftirqd/0]
> 3 ? S< 0:00 [events/0]
> 4 ? S< 0:00 [khelper]
> 9 ? S< 0:00 [kthread]
> 16 ? S< 0:00 [kblockd/0]
> 28 ? S 0:00 [khubd]
> 108 ? S 0:00 [pdflush]
> 109 ? S 0:00 [pdflush]
> 111 ? S< 0:00 [aio/0]
> 110 ? S 0:00 [kswapd0]
> 694 ? S 0:00 [kseriod]
> 741 ? S 0:00 [xenblkd]
> 767 ? S< 0:00 [ata/0]
> 793 ? S< 0:00 [kmirrord/0]
> 795 ? S 0:00 [kjournald]
> 843 ? S<s 0:00 udevd
> 2728 ? S 0:00 [kjournald]
> 3320 ? S<s 0:00 dhclient3 -pf /var/run/dhclient.eth0.pid
> -lf /var/run 5341 ? Ss 0:00 /sbin/syslogd -u syslog
> 5356 ? Ss 0:00 /bin/dd bs 1 if /proc/kmsg
> of /var/run/klogd/kmsg
> 5358 ? Ss 0:00 /sbin/klogd -P /var/run/klogd/kmsg
> 5382 ? Ss 0:00 /usr/bin/gdm
> 5397 ? Ss 0:00 /usr/sbin/cupsd -F
> 5407 ? S 0:00 /usr/bin/gdm
> 5567 ? S 0:30 /usr/X11R6/bin/X :0 -br -audit 0
> -auth /var/lib/gdm/: 5634 ? Ss 0:00 /usr/bin/dbus-daemon-1
> --system
> 5671 ? Ss 0:01 /usr/sbin/hald --drop-privileges
> 5685 ? Ss 0:00 /usr/sbin/inetd
> 5855 ? Ss 0:00 /usr/lib/postfix/master
> 5872 ? S 0:00 pickup -l -t fifo -u -c
> 5873 ? S 0:00 qmgr -l -t fifo -u -c
> 5904 ? Ss 0:00 /usr/sbin/nmbd -D
> 5906 ? Ss 0:00 /usr/sbin/smbd -D
> 5916 ? S 0:00 /usr/sbin/smbd -D
> 5921 ? Ss 0:00 /usr/sbin/sshd
> 5971 ? Ss 0:00 /usr/sbin/atd
> 5982 ? Ss 0:00 /usr/sbin/cron
> 6003 tty1 Ss+ 0:00 /sbin/getty 38400 tty1
> 6004 tty2 Ss+ 0:00 /sbin/getty 38400 tty2
> 6005 tty3 Ss+ 0:00 /sbin/getty 38400 tty3
> 6006 tty4 Ss+ 0:00 /sbin/getty 38400 tty4
> 6007 tty5 Ss+ 0:00 /sbin/getty 38400 tty5
> 6008 tty6 Ss+ 0:00 /sbin/getty 38400 tty6
> 6107 ? Ss 0:00 x-session-manager
> 6171 ? Ss 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch
> --exit-with-s 6174 ? S 0:00 /usr/bin/dbus-launch
> --exit-with-session x-session-ma 6175 ? Ss 0:00 dbus-daemon-1
> --fork --print-pid 8 --print-address 6
> 6177 ? S 0:01 /usr/lib/gconf2/gconfd-2 5
> 6182 ? S 0:00 /usr/bin/gnome-keyring-daemon
> 6600 ? Ss
> 0:00 /usr/lib/bonobo-activation/bonobo-activation-server - 6602 ?
> S 0:01 /usr/lib/control-center/gnome-settings-daemon --oaf-a 6605 ?
> S 0:00 /usr/lib/gamin/gam_server
> 6954 ? S 0:00 xscreensaver -nosplash
> 6997 ? Ss 0:00 gnome-smproxy
> --sm-config-prefix /.gnome-smproxy-vq8V 6999 ? Ss 0:01
> metacity --sm-save-file 1113688837-9713-3830850673.ms 7001 ? Ss
> 0:00 gnome-volume-manager --sm-config-prefix /gnome-volume 7003 ?
> Ss 0:01 gnome-panel --sm-config-prefix /gnome-panel-sv8HlD/ - 7005 ?
> Ss 0:02 nautilus --sm-config-prefix /nautilus-gDhqyF/ --sm-cl 7009 ?
> Ss 0:00 gnome-cups-icon --sm-config-prefix /gnome-cups-icon-E 7011 ?
> Ss 0:00 update-notifier --sm-config-prefix /update-notifier-Y 7013 ?
> Ss 0:00 /usr/lib/evolution/2.2/evolution-alarm-notify --sm-co 7044 ?
> S 0:00 gnome-cups-icon --sm-config-prefix /gnome-cups-icon-E 7049 ?
> S 0:01 /usr/lib/gnome-panel/wnck-applet --oaf-activate-iid=O 7051 ?
> S 0:00 /usr/lib/gnome-applets/trashapplet --oaf-activate-iid 7052 ?
> S 0:00 nautilus --sm-config-prefix /nautilus-gDhqyF/ --sm-cl 7053 ?
> S 0:00 nautilus --sm-config-prefix /nautilus-gDhqyF/ --sm-cl 7055 ?
> S 0:00 /usr/lib/gnome-vfs2/gnome-vfs-daemon --oaf-activate-i 7056 ?
> S 0:00 /usr/lib/evolution/2.2/evolution-alarm-notify --sm-co 7057 ?
> S 0:00 /usr/lib/evolution/2.2/evolution-alarm-notify --sm-co 7061 ?
> S 0:00 /usr/lib/gnome-vfs2/gnome-vfs-daemon --oaf-activate-i 7062 ?
> S 0:00 /usr/lib/gnome-vfs2/gnome-vfs-daemon --oaf-activate-i 7063 ?
> S 0:00 /usr/lib/gnome-applets/trashapplet --oaf-activate-iid 7064 ?
> S 0:00 /usr/lib/gnome-applets/trashapplet --oaf-activate-iid 7065 ?
> S 0:00 /usr/lib/gnome-applets/trashapplet --oaf-activate-iid 7066 ?
> S 0:00 /usr/lib/gnome-applets/trashapplet --oaf-activate-iid 7080 ?
> S 0:00 /usr/lib/evolution/2.2/evolution-exchange-storage --o 7109 ?
> S 0:00 /usr/lib/nautilus-cd-burner/mapping-daemon
> 7110 ? S 0:00 nautilus --sm-config-prefix /nautilus-gDhqyF/
> --sm-cl 7116 ? S 0:00 gnome-panel
> --sm-config-prefix /gnome-panel-sv8HlD/ - 7117 ? S 0:00
> gnome-panel --sm-config-prefix /gnome-panel-sv8HlD/ - 7118 ? S
> 0:00 nautilus --sm-config-prefix /nautilus-gDhqyF/ --sm-cl 7119 ?
> S 0:00 nautilus --sm-config-prefix /nautilus-gDhqyF/ --sm-cl 7120 ?
> S 0:00 /usr/lib/evolution/2.2/evolution-exchange-storage --o 7121 ?
> S 0:00 /usr/lib/evolution/2.2/evolution-exchange-storage --o 7123 ?
> S 0:00 /usr/lib/evolution/evolution-data-server-1.2 --oaf-ac 7124 ?
> S 0:00 nautilus --sm-config-prefix /nautilus-gDhqyF/ --sm-cl 7133 ?
> S 0:00 /usr/lib/evolution/evolution-data-server-1.2 --oaf-ac 7134 ?
> S 0:00 /usr/lib/evolution/evolution-data-server-1.2 --oaf-ac 7143 ?
> S 0:00 /usr/lib/evolution/evolution-data-server-1.2 --oaf-ac 7149 ?
> S 0:00 /usr/lib/gnome-panel/notification-area-applet --oaf-a 7151 ?
> S 0:00 /usr/lib/gnome-applets/mixer_applet2 --oaf-activate-i 7153 ?
> S 0:00 /usr/lib/gnome-panel/clock-applet --oaf-activate-iid= 7693 ?
> S 0:00 xfrd
> 10459 ? S 0:01 gnome-terminal
> 10464 ? S 0:00 gnome-pty-helper
> 10466 ? S 0:00 gnome-terminal
> 10467 ? S 0:00 gnome-terminal
> 10524 pts/1 Ss 0:00 bash
> 10645 ? S 0:02 evolution-2.2
> 10649 ? Z 0:00 [netstat] <defunct>
> 10651 ? S 0:00 evolution-2.2
> 10652 ? S 0:00 evolution-2.2
> 10658 ? S 0:00 evolution-2.2
> 10659 ? S 0:00 evolution-2.2
> 10661 ? S 0:00 evolution-2.2
> 10662 ? S 0:00 evolution-2.2
> 10744 pts/1 R+ 0:00 ps ax
> stewart@gateway:~$
>
> stewart@gateway:~$ netstat -ltno
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State Timer
> tcp 0 0 0.0.0.0:8002 0.0.0.0:*
> LISTEN off (0.00/0/0)
> tcp 0 0 0.0.0.0:139 0.0.0.0:*
> LISTEN off (0.00/0/0)
> tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN off (0.00/0/0)
> tcp 0 0 127.0.0.1:631 0.0.0.0:*
> LISTEN off (0.00/0/0)
> tcp 0 0 127.0.0.1:25 0.0.0.0:*
> LISTEN off (0.00/0/0)
> tcp 0 0 0.0.0.0:445 0.0.0.0:*
> LISTEN off (0.00/0/0)
> stewart@gateway:~$
>
>
>
> Mmmmm Doesn't look like xend is running to me.
>
> The Firewall is disabled and the networking ( including the bridge ) is
> working ok.
>
>
> Regards
>
> Stewart
>
>
>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
On Sun, 2005-06-12 at 15:47 +0100, James Bulpin wrote:
> OK xend is failing after start somehow. Let's have a look at your
> xend-debug.log. Can you also check your memory utilisation (e.g. with
> 'top') - you have a load of stuff running and if the oom killer is
> kicking in then xend may be suffering.
>
> Please post replies to the list rather than just to me. Others here may
> be interested and able to help.
>
> For reference, there was a typo in my netstat command line suggestion,
> should have been 'netstat -ltnp' to get the process names. (Irrelevant
> now since xend isn't running.)
>
> James
>

Hi James

xend-debug.log :-


stewart@gateway:/var/log$ cat xend-debug.log
network start bridge=xen-br0 netdev=eth0 antispoof=no
Traceback (most recent call last):
File "/usr/sbin/xend", line 121, in ?
sys.exit(main())
File "/usr/sbin/xend", line 107, in main
return daemon.start()
File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 525, in
start
self.run()
File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 615, in run
SrvServer.create(bridge=1)
File "/usr/lib/python/xen/xend/server/SrvServer.py", line 47, in
create
xend = SrvRoot()
File "/usr/lib/python/xen/xend/server/SrvRoot.py", line 29, in
__init__
self.get(name)
File "/usr/lib/python/xen/xend/server/SrvDir.py", line 69, in get
val = val.getobj()
File "/usr/lib/python/xen/xend/server/SrvDir.py", line 39, in getobj
self.obj = klassobj()
File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 25, in
__init__
self.xd = XendDomain.instance()
File "/usr/lib/python/xen/xend/XendDomain.py", line 798, in instance
inst = XendDomain()
File "/usr/lib/python/xen/xend/XendDomain.py", line 60, in __init__
self.domain_db = self.db.fetchall("")
File "/usr/lib/python/xen/xend/XendDB.py", line 69, in fetchall
for k in dircache.listdir(dpath):
File "/usr/lib/python2.4/dircache.py", line 25, in listdir
mtime = os.stat(path).st_mtime
OSError: [Errno 2] No such file or directory:
'/var/lib/xen/xend-db/domain/'
directory: '/var/lib/xen/xend-db/domain/'
n/xend-db/domain/'
such file or directory: '/var/lib/xen/xend-db/domain/'
'/var/lib/xen/xend-db/domain/'
stewart@gateway:/var/log$

and top :-

top - 16:50:38 up 10 min, 2 users, load average: 0.13, 0.32, 0.27
Tasks: 110 total, 1 running, 108 sleeping, 0 stopped, 1 zombie
Cpu(s): 6.6% us, 3.2% sy, 1.4% ni, 72.6% id, 16.1% wa, 0.1% hi,
0.0% si
Mem: 144108k total, 141892k used, 2216k free, 2852k buffers
Swap: 522072k total, 6404k used, 515668k free, 40664k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1 root 16 0 1536 488 436 S 0.0 0.3 0:00.36 init
2 root 34 19 0 0 0 S 0.0 0.0 0:00.03 ksoftirqd/0
3 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 events/0
4 root 10 -5 0 0 0 S 0.0 0.0 0:00.02 khelper
9 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kthread
16 root 10 -5 0 0 0 S 0.0 0.0 0:00.04 kblockd/0
28 root 15 0 0 0 0 S 0.0 0.0 0:00.00 khubd
108 root 15 0 0 0 0 S 0.0 0.0 0:00.06 pdflush
109 root 15 0 0 0 0 S 0.0 0.0 0:00.08 pdflush
111 root 20 -5 0 0 0 S 0.0 0.0 0:00.00 aio/0
110 root 15 0 0 0 0 S 0.0 0.0 0:00.26 kswapd0
694 root 25 0 0 0 0 S 0.0 0.0 0:00.00 kseriod
741 root 25 0 0 0 0 S 0.0 0.0 0:00.00 xenblkd
767 root 11 -5 0 0 0 S 0.0 0.0 0:00.00 ata/0
793 root 11 -5 0 0 0 S 0.0 0.0 0:00.00 kmirrord/0
795 root 15 0 0 0 0 S 0.0 0.0 0:00.07 kjournald
846 root 11 -5 1516 336 284 S 0.0 0.2 0:00.10 udevd
stewart@gateway:/var/log$

pS I have 1Gb total phys memory in this machine and I allocated 150Mb
via grub for Xen boot. Maybe I need more?

Regards


Stewart




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
Stewart Outram wrote:
> xend-debug.log :-
[...]
> OSError: [Errno 2] No such file or directory:
> '/var/lib/xen/xend-db/domain/'
> directory: '/var/lib/xen/xend-db/domain/'
> n/xend-db/domain/'
> such file or directory: '/var/lib/xen/xend-db/domain/'
> '/var/lib/xen/xend-db/domain/'

I'm surprised xend didn't make that directory for itself. You did start
xend as root didn't you? Try 'mkdir /var/lib/xen/xend-db/domain' and see
if that helps.

> pS I have 1Gb total phys memory in this machine and I allocated 150Mb
> via grub for Xen boot. Maybe I need more?

150MB may be enough so long as you don't have all the gnome and
evolution stuff running as in your earlier 'ps'.

James

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
Hi James

The good news is that I now have it working.

I have managed to create a new Domain based on the ttylinux image and
log in as root.

I had to manually sudo mkdir /var/lib/xen/xend-db

and then

sudo mkdir /var/lib/xen/xend-db/domain

and

sudo mkdir /var/lib/xen/xend-db/vnet

as well to get it to start for some reason ??

BTW I have compiled from source and I am using the

vmlinuz-2.6.11.10-xen0 and vmlinuz-2.6.11.10-xenU patched kernels if
that helps.

Many thanks for your help.

It's a very interesting project.

Stewart


> I'm surprised xend didn't make that directory for itself. You did start
> xend as root didn't you? Try 'mkdir /var/lib/xen/xend-db/domain' and see
> if that helps.

>
> > pS I have 1Gb total phys memory in this machine and I allocated 150Mb
> > via grub for Xen boot. Maybe I need more?
>
> 150MB may be enough so long as you don't have all the gnome and
> evolution stuff running as in your earlier 'ps'.
>
> James
>


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
On 6/12/05, Stewart Outram <stewart@soutram.fsnet.co.uk> wrote:
> Hi James
>
> The good news is that I now have it working.
>
> I have managed to create a new Domain based on the ttylinux image and
> log in as root.
>
> I had to manually sudo mkdir /var/lib/xen/xend-db
>
> and then
>
> sudo mkdir /var/lib/xen/xend-db/domain
>
> and
>
> sudo mkdir /var/lib/xen/xend-db/vnet
>

this is a known problem with system using python 2.4, and it is still
in TODO list.

regards,
aq

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
On 6/13/05, aq <aquynh@gmail.com> wrote:
> On 6/12/05, Stewart Outram <stewart@soutram.fsnet.co.uk> wrote:
> > Hi James
> >
> > The good news is that I now have it working.
> >
> > I have managed to create a new Domain based on the ttylinux image and
> > log in as root.
> >
> > I had to manually sudo mkdir /var/lib/xen/xend-db
> >
> > and then
> >
> > sudo mkdir /var/lib/xen/xend-db/domain
> >
> > and
> >
> > sudo mkdir /var/lib/xen/xend-db/vnet
> >
>
> this is a known problem with system using python 2.4, and it is still
> in TODO list.

Ian has just removed the related item in TODO list, so i guess this
problem has been solved? anybody know how it has been solved then?

Mark, did you fix this bug?

regards,
aq

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
RE: Problems starting xend [ In reply to ]
> Ian has just removed the related item in TODO list, so i
> guess this problem has been solved? anybody know how it has
> been solved then?

In the unstable tree, xend no longer manages the database -- that's what
xenstore is for.

I guess it should still be listed as a bug for 2.0, though.

It's a fairly odd one, as xend does attempt to create the directory.
Probably trivial to debug with a bit of tracing, though.

Patches welcome :-)

Ian

> Mark, did you fix this bug?
>
> regards,
> aq
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
On 6/14/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > Ian has just removed the related item in TODO list, so i
> > guess this problem has been solved? anybody know how it has
> > been solved then?
>
> In the unstable tree, xend no longer manages the database -- that's what
> xenstore is for.
>
> I guess it should still be listed as a bug for 2.0, though.
>
> It's a fairly odd one, as xend does attempt to create the directory.
> Probably trivial to debug with a bit of tracing, though.
>
> Patches welcome :-)

indeed, just checked out and the reason is pretty simple ;-)

- python 2.3 doesnt complain if dircache.listdir() execute on
non-existent directory.
- python 2.4 spit out an error and stop on the same situation.

now the problem is how to fix it. i propose checking for and make
necessary directories from Makefile, and that is clean enough. any
comment, Ian?

regards,
aq

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
RE: Problems starting xend [ In reply to ]
> indeed, just checked out and the reason is pretty simple ;-)
>
> - python 2.3 doesnt complain if dircache.listdir() execute on
> non-existent directory.
> - python 2.4 spit out an error and stop on the same situation.
>
> now the problem is how to fix it. i propose checking for and
> make necessary directories from Makefile, and that is clean
> enough. any comment, Ian?

Thanks for investigating.

Having empty directories under /var in an install tar ball doesn't seem
the right soloution. We could fix it in install.sh, but by far the best
soloution would be to create the directories from within xend. Let's
catch the exception from listdir and create the directory.

Best,
Ian

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
On 6/14/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > indeed, just checked out and the reason is pretty simple ;-)
> >
> > - python 2.3 doesnt complain if dircache.listdir() execute on
> > non-existent directory.
> > - python 2.4 spit out an error and stop on the same situation.
> >
> > now the problem is how to fix it. i propose checking for and
> > make necessary directories from Makefile, and that is clean
> > enough. any comment, Ian?
>
> Thanks for investigating.
>
> Having empty directories under /var in an install tar ball doesn't seem
> the right soloution. We could fix it in install.sh, but by far the best
> soloution would be to create the directories from within xend. Let's
> catch the exception from listdir and create the directory.
>

i have another idea on solution to this problem.

the root of problem is XendDB::fetchall(): this method calls
dircache.listdir("dir-name"). python 2.3 has odd behavior: it doesnt
complain if the "dir-name" is non-existent, and still returns an empty
list. meanwhile, python 2.4 (properly) generates an exception and
stops.

it is tempting to make a directory in fetchall() in this case, but i
dont like that solution, because it would slightly change the semantic
of this method. the directory should be created later if needed, when
xend saves data.

in this patch, i adapt the trick from XendDB of -unstable: returns an
empty list in case the directory is non-existent. this is same as the
behaviour of python 2.3 on current code.

note that this problem only occurs with -stable and -testing, and this
patch is against -testing ChangeSet@1.1899

Signed-off-by: Nguyen Anh Quynh <aquynh@gmail.com>


$ diffstat xendmkdir.patch
XendDB.py | 14 ++++++++------
1 files changed, 8 insertions(+), 6 deletions(-)
Re: Problems starting xend [ In reply to ]
On Sun, Jun 12, 2005 at 05:06:55PM +0100, James Bulpin wrote:
> >such file or directory: '/var/lib/xen/xend-db/domain/'
> >'/var/lib/xen/xend-db/domain/'
>
> I'm surprised xend didn't make that directory for itself. You did start
> xend as root didn't you? Try 'mkdir /var/lib/xen/xend-db/domain' and see
> if that helps.

I recently had a similar experience with the 2.0.6 install kit in an
Ubuntu Hoary (server install plus a few req'd packages) test setup.
Had to create both .../domain and .../vnet by hand to get xend to run.
And yeah, I know for sure I was running xend as root, as I would have
had trouble installing the kit or creating the directories if I hadn't
been. :-/

I was working from a writeup done by some folks at Clarkson that I
found by way of https://wiki.ubuntu.com/XenVirtualMachine, so that's
where I appended my notes on the experience. I had meant (still do,
too) to add relevant bits to the Xen wiki when I got a bit further
along, but I've been busy with other projects for a few days.

--
One Zone to rule them all, One Zone to find them,
One Zone to name them all and in the domain bind them,
In the Land of DotCom where the Spammers lie.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Re: Problems starting xend [ In reply to ]
On 6/20/05, Martin Maney <maney@two14.net> wrote:
> On Sun, Jun 12, 2005 at 05:06:55PM +0100, James Bulpin wrote:
> > >such file or directory: '/var/lib/xen/xend-db/domain/'
> > >'/var/lib/xen/xend-db/domain/'
> >
> > I'm surprised xend didn't make that directory for itself. You did start
> > xend as root didn't you? Try 'mkdir /var/lib/xen/xend-db/domain' and see
> > if that helps.
>
> I recently had a similar experience with the 2.0.6 install kit in an
> Ubuntu Hoary (server install plus a few req'd packages) test setup.
> Had to create both .../domain and .../vnet by hand to get xend to run.
> And yeah, I know for sure I was running xend as root, as I would have
> had trouble installing the kit or creating the directories if I hadn't
> been. :-/

yes, Hoary uses python 2.4, so you will have the trouble.

the patch i provided would fix this problem (Ian, please pick up it)

regards,
aq

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Problems starting xend [ In reply to ]
My configuration is as follows:

P4 1.7Ghz, 512MB RAM
Linux distro: XOS
Xen version: 2.0.6 binary
Installed: brctl, twisted, iproute, Zop, python-logging and (all that are
required)

I am able to boot using xen kernel. However, problems arise when i run xend.
Actual output appended below.

# xend start
/usr/lib/python/xen/xend/server/SrvDaemon.py:28: RuntimeWarning: Python C API
version mismatch for
module xen.lowlevel.xu: This Python has API version 1011, module
xen.lowlevel.xu has version 1012
.
from xen.lowlevel import xu
Traceback (most recent call last):
File "/usr/sbin/xend", line 27, in ?
from xen.xend.server import SrvDaemon
File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 35, in ?
from xen.xend.server import SrvServer
File "/usr/lib/python/xen/xend/server/SrvServer.py", line 28, in ?
from twisted.web import server, static
ImportError: No module named web

Any help would be appreciated.

Thanks in advance.

--
Asaf Maruf Ali
PING Systems
Network Security-Linux-Consulting
605, 6th Floor,
Clifton Centre, Block 5,
Clifton, Karachi-75600
Pakistan
Tel # 5872438, 5868275
Fax # 5868927
http://www.ping.com.pk
"PING is a Micro$oft free environment"

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