Re: [ClusterLabs] Fwd: Postgres pacemaker cluster failure

We tried to fix ldap issue with nss_initgroups_ignoreusers option in nslcd.conf for postgres and hacluster users. So cluster shouldn't contact ldap server every 15 seconds when it checks psql with postgres user: /usr/lib/postgresql/9.5/bin/pg_isready -h /var/run/postgresql/ -p 5432 We have two

Re: [ClusterLabs] [EXTERNAL] Re: "node is unclean" leads to gratuitous reboot

On 7/11/19 6:52 AM, Users wrote: On Thu, Jul 11, 2019 at 12:58 PM Lars Ellenberg wrote: On Wed, Jul 10, 2019 at 06:15:56PM +, Michael Powell wrote: Thanks to you and Andrei for your responses. In our particular situation, we want to be able to operate

Re: [ClusterLabs] [EXTERNAL] What's the best practice to scale-out/increase the cluster size? (was: "node is unclean" leads to gratuitous reboot)

Thanks again for the feedback. As a novice to Pacemaker, I am learning a great deal and have a great deal more to learn. I'm afraid I was not precise in my choice of the term "stand-alone". As you point out, our situation is really case b) "as the 2-node cluster but only one is up at the

Re: [ClusterLabs] failed resource resurection - failcount/cleanup etc ?

On Thu, 2019-07-11 at 10:39 +0100, lejeczek wrote: > On 10/07/2019 15:50, Ken Gaillot wrote: > > On Wed, 2019-07-10 at 11:26 +0100, lejeczek wrote: > > > hi guys, possibly @devel if they pop in here. > > > > > > is there, will there be, a way to make cluster deal with failed > > > resources in

Re: [ClusterLabs] [EXTERNAL] Re: "node is unclean" leads to gratuitous reboot

On Thu, Jul 11, 2019 at 12:58 PM Lars Ellenberg wrote: > > On Wed, Jul 10, 2019 at 06:15:56PM +, Michael Powell wrote: > > Thanks to you and Andrei for your responses. In our particular > > situation, we want to be able to operate with either node in > > stand-alone mode, or with both nodes

Re: [ClusterLabs] [EXTERNAL] Re: "node is unclean" leads to gratuitous reboot

On Wed, Jul 10, 2019 at 06:15:56PM +, Michael Powell wrote: > Thanks to you and Andrei for your responses. In our particular > situation, we want to be able to operate with either node in > stand-alone mode, or with both nodes protected by HA. I did not > mention this, but I am working on

Re: [ClusterLabs] failed resource resurection - failcount/cleanup etc ?

On 10/07/2019 15:50, Ken Gaillot wrote: > On Wed, 2019-07-10 at 11:26 +0100, lejeczek wrote: >> hi guys, possibly @devel if they pop in here. >> >> is there, will there be, a way to make cluster deal with failed >> resources in such a way that cluster would try not to give up on >> failed >>

[ClusterLabs] What's the best practice to scale-out/increase the cluster size? (was: "node is unclean" leads to gratuitous reboot)

On 7/11/19 2:15 AM, Michael Powell wrote: > Thanks to you and Andrei for your responses. In our particular situation, we > want to be able to operate with either node in stand-alone mode, or with both > nodes protected by HA. I did not mention this, but I am working on upgrading > our

Re: [ClusterLabs] Adding HAProxy as a Resource

Hi I am using the resource agents built from clusterlabs and when I add the systemd resource I am getting the below error . $ sudo pcs resource create HAPROXY systemd:haproxy op monitor interval=2s Error: Agent 'systemd:haproxy' is not installed or does not provide valid metadata: Metadata

Re: [ClusterLabs] Adding HAProxy as a Resource

On 2019-07-11 09:31, Somanath Jeeva wrote: Hi All, I am using HAProxy in my environment which I plan to add to pacemaker as resource. I see no RA available for that in resource agent. Should I write a new RA or is there any way to add it to pacemaker as a systemd service. Hello, haproxy

[ClusterLabs] Adding HAProxy as a Resource

Hi All, I am using HAProxy in my environment which I plan to add to pacemaker as resource. I see no RA available for that in resource agent. Should I write a new RA or is there any way to add it to pacemaker as a systemd service. With Regards Somanath Thilak J