[ClusterLabs] Antw: Re: Pacemaker kill does not cause node fault ???
Ulrich.Windl at rz.uni-regensburg.de
Mon Feb 6 04:28:00 EST 2017
>>> RaSca <rasca at miamammausalinux.org> schrieb am 03.02.2017 um 14:00 in
<0de64981-904f-5bdb-c98f-9c59ee47b6c5 at miamammausalinux.org>:
> On 03/02/2017 11:06, Ferenc Wágner wrote:
>> Ken Gaillot <kgaillot at redhat.com> writes:
>>> On 01/10/2017 04:24 AM, Stefan Schloesser wrote:
>>>> I am currently testing a 2 node cluster under Ubuntu 16.04. The setup
>>>> seems to be working ok including the STONITH.
>>>> For test purposes I issued a "pkill -f pace" killing all pacemaker
>>>> processes on one node.
>>>> The node is marked as "pending", all resources stay on it. If I
>>>> manually kill a resource it is not noticed. On the other node a drbd
>>>> "promote" command fails (drbd is still running as master on the first
>>> I suspect that, when you kill pacemakerd, systemd respawns it quickly
>>> enough that fencing is unnecessary. Try "pkill -f pace; systemd stop
>> What exactly is "quickly enough"?
> What Ken is saying is that Pacemaker, as a service managed by systemd,
> have in its service definition file
> (/usr/lib/systemd/system/pacemaker.service) this option:
> Looking at  it is explained: systemd restarts immediately the process
> if it ends for some unexpected reason (like a forced kill).
Isn't the question: Is crmd a process that is expected to die (and thus need
restarting)? Or wouldn't one prefer to debug this situation. I fear that
restarting it might just cover some fatal failure...
>  https://www.freedesktop.org/software/systemd/man/systemd.service.html
> rasca at miamammausalinux.org
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
More information about the Users