Re: [Pacemaker] Cluster tools
Maxwell, Jamison [HDS] JMaxwell@... writes: Pssh complained about wanting python-2.5, but I wasn't going to downgrade from 2.6, so I skipped the dependency. I've tested several areas within the shell and all appears well... crmsh (with pssh) from the SUSE ha repo works just fine, the only issue I've had is that users in the haclient group can no longer connect to the cluster. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Cluster tools
Andrew Beekhof andrew@... writes: I believe this should make everyone happy: https://github.com/beekhof/pacemaker/commit/3c9275e Are you able to test it? I cloned the repo and used the pacemaker.spec.in file. I did have to tweak the spec file a bit to get it to build: %global specversion 8 #%global upstream_version HEAD %global upstream_version 1.1.8 #%global upstream_prefix ClusterLabs-pacemaker %global upstream_prefix pacemaker Version: 1.1.8 Stopped pacemaker and restarted cman. With the new packages installed (running crm_mon as root) I got: Could not establish cib_ro connection: Connection refused (111) Rebooted the server then I could connect to crm_mon as root. Still no joy as an unprivileged user though: Attempting connection to the cluster...Could not establish cib_ro connection: No such file or directory (2) Brett ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] crm resource cleanup / reprobe
Hi, On Thu, Mar 14, 2013 at 02:55:52PM +, Hinds, Luke (NSN - GB/Farnborough) wrote: Hi, What are the key differences between 'crm resource cleanup' and 'crm resource reprobe'? The first removes all status records of the resource. One consequence is that CRM orders a probe on all nodes afterwards. reprobe just does the latter. Also I would like to clarify, 'crm resource cleanup' only removes the failed actions and does not attempt to restart the resource or change the cluster in anyway? Yes. It's simply clears the failed events and resets the fail count for the relevant node? Right. Thanks, Dejan Thanks in advance for any community help, Luke ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] mysql/drbd on wheezy active/passive setup issues
Hi, On Thu, Mar 14, 2013 at 12:21:04PM -0400, christopher barry wrote: Hi, I get this when I run ocf-tester: ocf-tester -n p_mysql /usr/lib/ocf/resource.d/heartbeat/mysql Beginning tests for /usr/lib/ocf/resource.d/heartbeat/mysql... /usr/sbin/ocf-tester: 214: /usr/sbin/ocf-tester: xmllint: not found You need xmllint. It's in libxml2-tools on openSUSE 12.2. Hmm, perhaps it should be a dependency of resource-agents. Thanks, Dejan * rc=127: Your agent produces meta-data which does not conform to ra-api-1.dtd * rc=1: Demoting a start resource should not fail * rc=1: Promote failed * rc=1: Demote failed mysql[6876]: ERROR: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) mysql[6876]: ERROR: Failed to set read-only Aborting tests I'm not even sure I'm running that tester correctly. Q: why does the agent get shipped if the metadata is incorrect? Or is that just a warning? Oddly, I can login as root to mysql without issue, both with and without a password, so that error appears to be a red herring. I had a look at the resource script: /usr/lib/ocf/resource.d/heartbeat/mysql I noticed it had defaults if nothing was set. I changed the socket location in the default to match debian's default, removed the instance attributes from my CIB so it would use defaults, and I get the same outcome. How can I get actual error output so I can debug this? I'm sure the issue is trivial, but I just can't see what the issue is! There has to be a better way to troubleshoot/debug this kind of thing. The info in the corosync.log is just not very helpful for me. Thanks for any insight you can give. Regards, Christopher On Wed, 2013-03-13 at 18:13 -0400, christopher barry wrote: Thanks, I'll have a go with that. -C On Wed, 2013-03-13 at 22:58 +0100, emmanuel segura wrote: Hello Use ocf-tester to debug your resource 2013/3/13 christopher barry cba...@rjmetrics.com Greetings all, I'm almost there, and figure I just have something small out of place. Wondering if you can view my setup here: https://zerobin.permutation.net/?d8664af27a7de3be#Bh3fBAupeEw3RhBWOlvDomyPkoOzvD5ajTCk6+a1MW0= and let me know what you think. If you need more data to understand what could be wrong, please let me know. Thanks, Christopher ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org -- esta es mi vida e me la vivo hasta que dios quiera ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Cluster tools
Hi, On Thu, Mar 14, 2013 at 03:03:21PM -0400, Maxwell, Jamison [HDS] wrote: I was actually able to get the crm shell back onto a system that I had upgraded unawares of the removal of the tool. How bad an idea is that? I downloaded RPMs for crmsh-1.2.5-55 and pssh-1.4.3 and installed them. Pssh complained about wanting python-2.5, but I wasn't going to downgrade from 2.6, so I skipped the dependency. I've tested several areas within the shell and all appears well... pssh makes the history feature more comfortable in some situations. Otherwise, it's not required. Thanks, Dejan Jamison Maxwell Sr. Systems Administrator HD Supply - Facilities Maintenance -Original Message- From: matonb [mailto:mat...@ltresources.co.uk] Sent: Thursday, March 14, 2013 8:30 AM To: pacema...@clusterlabs.org Subject: Re: [Pacemaker] Cluster tools Are you able to test it? Happy to, have you rolled an RPM ? ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] problem on moving resource
Hi, On Thu, Mar 14, 2013 at 05:35:54PM -0300, Charles Mean wrote: Hey Guys, I am running heartbeat 3.0.5 and pacemaker 1.1.7 with two hosts(host01, host02). The thing is, when I try to define host01 as the preferred by the following command: crm configure location prefer-host01 NginxHA_and_ClusterIP 100: host01 This message show up: WARNING: prefer-host01: referenced node host01 does not exist Seems to be this one: https://savannah.nongnu.org/bugs/?38036 Will test with the configuration you provided. Thanks, Dejan So I tried to change the node name by its id(f6610e2a-d942-48ab-9455-2b16e018dd25): crm configure location prefer NginxHA_and_ClusterIP 100: f6610e2a-d942-48ab-9455-2b16e018dd25 And it looks like good, but I can not really move the resource from host02 to host01 when host01 become healthy(even after the stickiness). Follow my configuration: # crm configure show node $id=68c284e1-8793-4e5b-b7f0-83d1d5978a4d host02 node $id=f6610e2a-d942-48ab-9455-2b16e018dd25 host01 primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip=192.168.2.100 cidr_netmask=24 nic=eth0 \ op monitor interval=1s primitive NginxHA ocf:heartbeat:nginx \ params configfile=/etc/nginx/nginx.conf httpd=/usr/sbin/nginx port=80 status10url=/nginx_status \ op monitor interval=10s timeout=30s \ op start interval=0 timeout=40s \ op stop interval=0 timeout=60s group NginxHA_and_ClusterIP ClusterIP NginxHA location prefer-host01 NginxHA_and_ClusterIP 100: f6610e2a-d942-48ab-9455-2b16e018dd25 colocation NginxHA_with_ClusterIP inf: ClusterIP NginxHA order NginxHA_after_ClusterIP inf: ClusterIP NginxHA property $id=cib-bootstrap-options \ dc-version=1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff \ cluster-infrastructure=Heartbeat \ stonith-enabled=false \ no-quorum-policy=ignore rsc_defaults $id=rsc-options \ resource-stickiness=100 According to pacemaker, the configuration is OK: # crm_verify -L; echo Status: $? Status: 0 Do you know what is going on with this setup ? Thank you ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] resource modification and resource agent update
Hi, On Thu, Mar 14, 2013 at 11:48:16PM -0400, Matthew O'Connor wrote: Hi!! Two quick questions. 1. I have a resource that many other resources depend on. I need to modify this base resource, but if I modify this resource while it is online, will pacemaker restart it to effect the changes? I would expect that if it does, it will necessitate restarting all dependent resources as well - is this correct? You can update the agent without restarting. But disable monitoring beforehand: shell scripts don't like being updated while they're running. 2. I'm still stuck on Pacemaker 1.1.5 and 1.1.6 (different clusters). My resource agents are rather out of date, and I haven't gotten around to compiling 1.1.8 from the sources (it's...a long story). Can I update the resource agents to whatever is latest and greatest, or is there a cross-dependency between the Pacemaker version and the resource agent revisions? I'm hoping I can update, since they're all pretty much just shell-scripts, right? AFAIK, there are no dependencies on the particular pacemaker version. Thanks, Dejan Thanks for your help!! -- Matthew ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] resource modification and resource agent update
Am 15.03.2013 um 10:49 schrieb Dejan Muhamedagic deja...@fastmail.fm: Hi, On Thu, Mar 14, 2013 at 11:48:16PM -0400, Matthew O'Connor wrote: Hi!! Two quick questions. 1. I have a resource that many other resources depend on. I need to modify this base resource, but if I modify this resource while it is online, will pacemaker restart it to effect the changes? I would expect that if it does, it will necessitate restarting all dependent resources as well - is this correct? You can update the agent without restarting. But disable monitoring beforehand: shell scripts don't like being updated while they're running. putting the resource in unmanaged mode, thought? crm resource meta RESOURCE set is-managed false -- LF ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] resource modification and resource agent update
15.03.2013 13:52, Leon Fauster wrote: Am 15.03.2013 um 10:49 schrieb Dejan Muhamedagic deja...@fastmail.fm: Hi, On Thu, Mar 14, 2013 at 11:48:16PM -0400, Matthew O'Connor wrote: Hi!! Two quick questions. 1. I have a resource that many other resources depend on. I need to modify this base resource, but if I modify this resource while it is online, will pacemaker restart it to effect the changes? I would expect that if it does, it will necessitate restarting all dependent resources as well - is this correct? You can update the agent without restarting. But disable monitoring beforehand: shell scripts don't like being updated while they're running. putting the resource in unmanaged mode, thought? No, monitors are still run in unmanaged mode. Global maintainance-mode=true disables them. Or just temporary delete 'op monitor' lines from affected resources. crm resource meta RESOURCE set is-managed false -- LF ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Cluster tools
Correct me if I am wrong, but I believe crm_mon and the other crm_* commands are provided by pacemaker-cli, not by crmsh. (At least in the RHEL repos.) The reason I wanted crmsh back so badly was because I had entered and documented several aliases to make managing the cluster more convenient for my colleagues and didn't want to have to re-write my doco... Is the HA community abandoning crmsh and why? Jamison Maxwell Sr. Systems Administrator HD Supply - Facilities Maintenance -Original Message- From: matonb [mailto:mat...@ltresources.co.uk] Sent: Friday, March 15, 2013 4:52 AM To: pacema...@clusterlabs.org Subject: Re: [Pacemaker] Cluster tools Andrew Beekhof andrew@... writes: I believe this should make everyone happy: https://github.com/beekhof/pacemaker/commit/3c9275e Are you able to test it? I cloned the repo and used the pacemaker.spec.in file. I did have to tweak the spec file a bit to get it to build: %global specversion 8 #%global upstream_version HEAD %global upstream_version 1.1.8 #%global upstream_prefix ClusterLabs-pacemaker %global upstream_prefix pacemaker Version: 1.1.8 Stopped pacemaker and restarted cman. With the new packages installed (running crm_mon as root) I got: Could not establish cib_ro connection: Connection refused (111) Rebooted the server then I could connect to crm_mon as root. Still no joy as an unprivileged user though: Attempting connection to the cluster...Could not establish cib_ro connection: No such file or directory (2) Brett ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Cluster tools
On 2013-03-15T10:05:30, Maxwell, Jamison [HDS] jmaxw...@pbp1.com wrote: Is the HA community abandoning crmsh and why? The HA community is NOT abandoning crmsh. crmsh remains supported by the community, *and* on SLE HA. We are and will continue to develop it. RHT has made a decision not to support it on RHEL, but instead to develop pcs; but that doesn't reflect a community decision. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Experience is the name everyone gives to their mistakes. -- Oscar Wilde ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] resource modification and resource agent update
On Fri, Mar 15, 2013 at 04:16:52PM +0300, Vladislav Bogdanov wrote: 15.03.2013 13:52, Leon Fauster wrote: Am 15.03.2013 um 10:49 schrieb Dejan Muhamedagic deja...@fastmail.fm: Hi, On Thu, Mar 14, 2013 at 11:48:16PM -0400, Matthew O'Connor wrote: Hi!! Two quick questions. 1. I have a resource that many other resources depend on. I need to modify this base resource, but if I modify this resource while it is online, will pacemaker restart it to effect the changes? I would expect that if it does, it will necessitate restarting all dependent resources as well - is this correct? You can update the agent without restarting. But disable monitoring beforehand: shell scripts don't like being updated while they're running. putting the resource in unmanaged mode, thought? No, monitors are still run in unmanaged mode. Global maintainance-mode=true disables them. Right. Probably the simplest option. Or just temporary delete 'op monitor' lines from affected resources. Or add enabled=false to the op. Thanks, Dejan crm resource meta RESOURCE set is-managed false -- LF ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Cluster tools
Thanks for the explanation! Jamison Maxwell Sr. Systems Administrator HD Supply - Facilities Maintenance -Original Message- From: Lars Marowsky-Bree [mailto:l...@suse.com] Sent: Friday, March 15, 2013 10:35 AM To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] Cluster tools On 2013-03-15T10:05:30, Maxwell, Jamison [HDS] jmaxw...@pbp1.com wrote: Is the HA community abandoning crmsh and why? The HA community is NOT abandoning crmsh. crmsh remains supported by the community, *and* on SLE HA. We are and will continue to develop it. RHT has made a decision not to support it on RHEL, but instead to develop pcs; but that doesn't reflect a community decision. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Experience is the name everyone gives to their mistakes. -- Oscar Wilde ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] problem on moving resource
On Fri, Mar 15, 2013 at 10:46:48AM +0100, Dejan Muhamedagic wrote: Hi, On Thu, Mar 14, 2013 at 05:35:54PM -0300, Charles Mean wrote: Hey Guys, I am running heartbeat 3.0.5 and pacemaker 1.1.7 with two hosts(host01, host02). The thing is, when I try to define host01 as the preferred by the following command: crm configure location prefer-host01 NginxHA_and_ClusterIP 100: host01 This message show up: WARNING: prefer-host01: referenced node host01 does not exist I couldn't reproduce this. The crmsh version shipped with pacemaker 1.1.7 is quite old. I'd suggest updating to crmsh 1.2.5. Thanks, Dejan Seems to be this one: https://savannah.nongnu.org/bugs/?38036 Will test with the configuration you provided. Thanks, Dejan So I tried to change the node name by its id(f6610e2a-d942-48ab-9455-2b16e018dd25): crm configure location prefer NginxHA_and_ClusterIP 100: f6610e2a-d942-48ab-9455-2b16e018dd25 And it looks like good, but I can not really move the resource from host02 to host01 when host01 become healthy(even after the stickiness). Follow my configuration: # crm configure show node $id=68c284e1-8793-4e5b-b7f0-83d1d5978a4d host02 node $id=f6610e2a-d942-48ab-9455-2b16e018dd25 host01 primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip=192.168.2.100 cidr_netmask=24 nic=eth0 \ op monitor interval=1s primitive NginxHA ocf:heartbeat:nginx \ params configfile=/etc/nginx/nginx.conf httpd=/usr/sbin/nginx port=80 status10url=/nginx_status \ op monitor interval=10s timeout=30s \ op start interval=0 timeout=40s \ op stop interval=0 timeout=60s group NginxHA_and_ClusterIP ClusterIP NginxHA location prefer-host01 NginxHA_and_ClusterIP 100: f6610e2a-d942-48ab-9455-2b16e018dd25 colocation NginxHA_with_ClusterIP inf: ClusterIP NginxHA order NginxHA_after_ClusterIP inf: ClusterIP NginxHA property $id=cib-bootstrap-options \ dc-version=1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff \ cluster-infrastructure=Heartbeat \ stonith-enabled=false \ no-quorum-policy=ignore rsc_defaults $id=rsc-options \ resource-stickiness=100 According to pacemaker, the configuration is OK: # crm_verify -L; echo Status: $? Status: 0 Do you know what is going on with this setup ? Thank you ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] resource modification and resource agent update
15.03.2013 18:38, Dejan Muhamedagic wrote: [ ... ] putting the resource in unmanaged mode, thought? No, monitors are still run in unmanaged mode. Global maintainance-mode=true disables them. Right. Probably the simplest option. Or just temporary delete 'op monitor' lines from affected resources. Or add enabled=false to the op. Ah, did not know, thanks for the hint. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Monitor interval vs. timeout
I have a few questions about monitors. * Is the timeout counted from each monitor attempt individually, or from the oldest attempt, or from the newest? * Does it make more sense to set the interval shorter than the timeout, or longer? * Would setting timeout and interval to the same value potentially cause problems? ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Nagios in pacemaker
hi all, i installed pacemaker 1.8.7 in two node two resource. res_nagios_1lsb:nagiosres_httpd_1 lsb:httpd resource move is ok but problem is when resource moved to primary/secondary node the nagios check_ping give me high response time with critical status,which is runing nice when corosync service is not started. pls help me thx in advance___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
