[Linux-cluster] rgmanager gets stuck on shutdown, if no services are running on its node.

Lon Hohberger lhh at redhat.com
Fri Dec 10 18:24:56 UTC 2010


On Thu, 2010-12-09 at 06:58 +0000, Jankowski, Chris wrote:
> Lon,
> 
> I think that I got to the bottom of the problem:
> 
> If there are *no* services running on a node and you issue "shutdown -h now" on the node, then when it comes to shutting down rgmanger, it executes the following sequence:
> 
> 1. Outputs "Shutting down" message to /var/adm/messages
> 2. Waits for the "status_poll_interval" value of seconds
> 3. Outputs the message: "Shutdown complete, exiting" and completes its own shutdown.
> 
> In my case, I had <rm status_poll_interval="3600"/>, as my service scripts do not have a viable check of their status, and the status check messages were clogging up the /var/adm/messages file.  So, rgmanager appeared to be stuck, whereas it was just really waiting.

You should just turn off status checks for your script:

  <rm>
    <service name="foo" >
      <script name="myscript" file... >
        <!-- 1 year status check interval -->
        <action name="status" depth="*" interval="1y" />
      </script>
      ..
    </service
    ..
  </rm>

That should make things work.

-- Lona




More information about the Linux-cluster mailing list