[ClusterLabs] Clone process appears running whereas not
arvidjaar at gmail.com
Sat Jun 6 04:29:55 EDT 2015
В Fri, 05 Jun 2015 18:22:14 +0200
Emmanuel Le Nohaïc <manu at lacavernedemanu.fr> пишет:
> Le 05/06/2015 16:43, Ken Gaillot a écrit :
> > On 06/05/2015 10:05 AM, Emmanuel Le Nohaïc wrote:
> >> Nodes are running Debian 8 with systemd. I think pacemaker reads
> >> output of anything like "systemctl status openvpn" and thinks that
> >> process is running because it appears running with :
> >> systemctl status openvpn (on CENTRAL1) ● openvpn.service - OpenVPN
> >> service Loaded: loaded (/etc/systemd/system/openvpn.service;
> >> disabled) Active: active (exited) since ven. 2015-06-05 15:45:07
> >> CEST; 11min ago Process: 732 ExecStart=/bin/true (code=exited,
> >> status=0/SUCCESS)
> > Pacemaker relies on the resource agent (systemd's openvpn service in
> > this case) to tell it whether the resource is running. If the agent
> > says yes when it's really no, Pacemaker can't do the right thing.
> > Why is ExecStart=/bin/true? That doesn't look right.
> This is the default openvpn unit file configuration.
> I replaced it by openvpn at server.service which contains
> Description=OpenVPN connection to %i
> ExecReload=/bin/kill -HUP $MAINPID
> Now it runs fine, thanks. I also did the necessary for timeout between
> nodes, it is now up to 10s.
> Last question, if openvpn process fails on one node, is it possible to
> monitor the system to re-add it automaticaly in the cluster when the
> openvpn processus will be available ? (without restart pacemaker).
Pacemaker should try to restart failed resource by default. If it is
not what you mean, could you explain what "re-add" means?
> I have to check for the VIP to turn on the other node when openvpn
> process fails and the cluster will just runs like we want ! :)
> Thanks for your feedback.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 181 bytes
Desc: OpenPGP digital signature
More information about the Users