Re: Test Xen 4.8 RC4 not stable 27.10.16

[Wei Liu <wei.liu2@citrix.com>]

On Fri, Oct 28, 2016 at 04:01:54PM +0100, Juergen Schinker wrote:
> 
> 
> ----- On 28 Oct, 2016, at 13:07, Boris Ostrovsky boris.ostrovsky@oracle.com wrote:
> 
> > I believe at least on some distros /var/run should be soft-linked to
> > /run, otherwise whoever cleans up those directories (the command name
> > escapes me right now) will only remove files from /run and leave
> > /var/run (and therefore /var/run/xen/xenstored.pid) untouched.
> > 
> > And because xencommons checks for existence of this this file before
> > starting xenstored the latter never starts.
> > 
> > -boris
> 
> root@xen:~# ls -la /var/run/xen/xenstored.pid 
> -rw-r----- 1 root root 6 Oct 28 15:15 /var/run/xen/xenstored.pid
> 
>   
>    33 ?        00:00:00 xenwatch
>    34 ?        00:00:00 xenbus
>    45 ?        00:00:00 xenbus_frontend
>   785 ?        00:00:00 xen_pciback_wor
>  1137 ?        00:00:00 xenwatchdogd
>  1169 ?        00:00:00 xen-init-dom0
>  1175 ?        00:00:00 xenconsoled
> 
> Thats exactly what I'm sayin , maybe we need a more intelligent check to see if xenstored is running
> 
> not just a simple pid check
> 

But ... the pid check is the usual way of checking if a daemon is
active.

I think a bit work is required to work out why xenstored.pid stays
across reboot -- it is not supposed to work like that on a FHS compliant
system.

And how do other daemons work on your test host, presumably they will
see stale pid files as well.  Are there any other pid files under
/var/run? If so, do the corresponding daemon run properly?

Wei.

> J

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