Re: Xen 4.5 Development Update (RC4)

[Olaf Hering <olaf@aepfle.de>]

On Wed, Dec 17, Konrad Rzeszutek Wilk wrote:

> [root@l konrad]# systemctl status xenstored.service
> ● xenstored.service - The Xen xenstore
>    Loaded: loaded (/usr/lib/systemd/system/xenstored.service; disabled)
>    Active: failed (Result: timeout) since Wed 2014-12-17 16:39:35 EST; 2min 10s ago
>   Process: 790 ExecStart=/usr/lib/xen/bin/xenstored.sh --no-fork (code=exited, status=0/SUCCESS)
>   Process: 787 ExecStartPre=/bin/mkdir -p /var/run/xen (code=exited, status=0/SUCCESS)
>   Process: 784 ExecStartPre=/bin/rm -f /var/lib/xenstored/tdb* (code=exited, status=0/SUCCESS)
>   Process: 759 ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities (code=exited, status=0/SUCCESS)
>  Main PID: 790 (code=exited, status=0/SUCCESS)
> 
> Dec 17 16:38:05 l.oracle.com xenstored.sh[790]: Xen Storage Daemon, version 1.0
> Dec 17 16:39:35 l.oracle.com systemd[1]: xenstored.service start operation timed out. Terminating.
> Dec 17 16:39:35 l.oracle.com systemd[1]: Failed to start The Xen xenstore.
> Dec 17 16:39:35 l.oracle.com systemd[1]: Unit xenstored.service entered failed state.
> Dec 17 16:39:35 l.oracle.com systemd[1]: xenstored.service failed.
> [root@l konrad]# systemctl start xenstored.service
> 
> 
> [root@l ~]# ps -eff|grep xens
> root      2018  1993  0 16:41 pts/0    00:00:00 systemctl start xenstored.service
> root      2029     1  0 16:41 ?        00:00:00 /usr/sbin/oxenstored --no-fork
> root      2034  1766  0 16:42 hvc0     00:00:00 grep --color=auto xens
> 
> I think I have something misconfigured here..

Looks like what Marc reported. xenstored can not use the sockets. Does
running xenstored directly or via env(1) work any better?

ExecStart=@XENSTORED@ --no-fork
ExecStart=/usr/bin/env $XENSTORED --no-fork

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel