Re: [ClusterLabs] (no subject)

On 24/05/17 04:36 PM, Christopher Pax wrote: > TO ADMIN: I am going to resubmit this question. please delete this thread. > > thanks We don't delete messages (and couldn't really if we wanted to anyway, given it is email based). I am sure responders will reply to the new thread. cheers, madi

[ClusterLabs] resource monitor logging

I am running postgresql as a resource in corosync. and there is a monitor process that kicks off every few seconds to see if postgresql is alive (it runs a select now()). My immediate concern is that it is generating alot of logs in auth.log, and I am wondering of this is normal behavior? Is there

Re: [ClusterLabs] (no subject)

TO ADMIN: I am going to resubmit this question. please delete this thread. thanks On Wed, May 24, 2017 at 4:10 PM, Christopher Pax wrote: > In reference to previous email (which I accidentally sent without details) > > I am running postgresql as a resource in corosync. and

Re: [ClusterLabs] (no subject)

In reference to previous email (which I accidentally sent without details) I am running postgresql as a resource in corosync. and there is a monitor process that kicks off every few seconds to see if postgresql is alive (it runs a select now). My immediate conserning is that it is generating alot

[ClusterLabs] (no subject)

## ## /var/log/auth.log ## May 24 15:23:19 ssinode02-g2 runuser: pam_unix(runuser:session): session opened for user postgres by (uid=0) May 24 15:23:19 ssinode02-g2 runuser: pam_unix(runuser:session): session closed for user postgres May 24 15:23:19 ssinode02-g2 runuser: pam_unix(runuser:session):

[ClusterLabs] ClusterIP won't return to recovered node

I suspect this has been asked before and apologize if so, a google search didn't seem to find anything that was helpful to me ... I'm setting up an active/active two-node cluster and am having an issue where one of my two defined clusterIPs will not return to the other node after it (the

Re: [ClusterLabs] Pacemaker occasionally takes minutes to respond

Hi Klaus, Thank you for your response. I tried many things, but no luck. We have many pacemaker clusters with 99% identical configurations, package versions, and only this one causes issues. (BTW we use unicast for corosync, but this is the same for our other clusters as well.) I checked all

[ClusterLabs] Node attribute disappears when pacemaker is started

Hi, After loading the node attribute, when I start pacemaker of that node, the attribute disappears. 1. Start pacemaker on node1. 2. Load configure containing node attribute of node2. (I use multicast addresses in corosync, so did not set "nodelist {nodeid: }" in corosync.conf.) 3. Start

Re: [ClusterLabs] In N+1 cluster, add/delete of one resource result in other node resources to restart

Thanks Aswathi. (My account had stopped working due to mail bounces, never seen that occur on gmail accounts) Ken, Answers to your questions are below: *1. Using force option* A) During our testing we had observed that in some instances the resource deletion would fail and that's why we added

Re: [ClusterLabs] In N+1 cluster, add/delete of one resource result in other node resources to restart

blank response for thread to appear in mailbox..pls ignore On Tue, May 23, 2017 at 4:21 AM, Ken Gaillot wrote: > On 05/16/2017 04:34 AM, Anu Pillai wrote: > > Hi, > > > > Please find attached debug logs for the stated problem as well as > > crm_mon command outputs. > > In