[Pkg-xen-devel] Bug#655301: Bug#655301: Bug#655301: Bug#655301: xcp-xapi fails to start

[Mike McClurg]

On Mon, Jan 16, 2012 at 11:49 PM, Jonathan Ludlam
<Jonathan.Ludlam at eu.citrix.com> wrote:
> I actually ran into a problem very similar to this myself this morning - it came from the fact that the init scripts were reordered at some point, and I still had the old init script ordering.
>
> I sorted it temporarily by starting the scripts by hand - the normal order is:
>
> 20: xcp-fe, xend, xcp-v6d
> 22: xcp-squeezed
> 23: xcp-xapi
>
> If you manually start the scripts in this order does it work?
>
> It's interesting that your /proc/xen isn't mounted though - that should happen in the xend init script, and that should have worked.
>

I think that we put a line in the xcp-xapi init script that quit
without error if it found a xend pid file. This means that to start
xapi you need to either 1) edit /etc/init.d/xend so that xend is never
actually run, or 2) first let xend start, and then do 'service xend
stop' to kill xend, and then do a 'service xcp-xapi start'.

Neither of those is very attractive. Perhaps we could instead have the
user create a /etc/default/xen file, which will contain a
"TOOLSTACK=foo" line. If that file exists, and only if TOOLSTACK=xapi,
we could then, within the xcp-xapi init script, check to see if xend
is running, and if so, shut it down. This allows us to use xend as a
common xen init script, but forces the user to explicitly say that
they want to use xapi over xend.

I would feel better about killing xend from within the xcp-xapi init
file if we were to it this way. Thoughts?

Mike