Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of scr512@gmail.com designates
 209.85.217.175 as permitted sender)
MIME-Version: 1.0
Date: Mon, 4 Jun 2012 18:55:31 -0500
Message-ID: 
 <CAKBkivmfGw-FaHsXPQWE7LBg0N8C07A-Rd-9D7DnbJUkG1M0Ww@mail.gmail.com>
Subject: Any tips on killing/restarting a super-hung XAPI PID?
From: Jason Davis <scr512@gmail.com>
To: cloudstack-users@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d0401fde1e646d404c1ae443d

--f46d0401fde1e646d404c1ae443d
Content-Type: text/plain; charset=ISO-8859-1

I know that this is primarily CloudStack but I figured some of you grizzled
vets might know of some pointers for me from running your own CS
deployments with XS/XCP.

One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive to
XAPI calls being sent from the CS management server. In the past, a simple
xe-toolstack-restart would do the trick but the script timed out while
restarting the XAPI daemon.

I found the process and first tried to use a simple kill command but the
process was in a "defunct" state. I tried a kill -9 but no joy.

I then found the xapi.pid and manually deleted it and then tried to run
xe-toolstack-restart. Unfortunately this did not work and ultimately I had
to reboot the cluster node.

So... any other ideas on killing a zombie XAPI process? I've like to avoid
rebooting a host :)

--f46d0401fde1e646d404c1ae443d--