<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>I replaced "target_role" with "target-role", but I get the same error regarding "target-role" (eg. </span>ERROR: DRBD_data: attribute target_role does not exist).</div><div><span> I also tried removing that attribute, but it seems to break my config. Should I post the whole XML? I don't want to spam the list if it's not necessary.<br></span></div><div><br><span></span></div><div><span>Drew<br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"><b><span style="font-weight:bold;"></span></b></font><br></div>Date: Mon, 23 Jul 2012 14:17:08 -0400 (EDT)<br>From: David Vossel <<a ymailto="mailto:dvossel@redhat.com"
href="mailto:dvossel@redhat.com">dvossel@redhat.com</a>><br>To: The Pacemaker cluster resource manager<br> <<a ymailto="mailto:pacemaker@oss.clusterlabs.org" href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>Subject: Re: [Pacemaker] Some errors after upgrading from heartbeat<br> 2.1 cluster<br>Message-ID: <<a ymailto="mailto:1268593649.150738.1343067428434.JavaMail.root@redhat.com" href="mailto:1268593649.150738.1343067428434.JavaMail.root@redhat.com">1268593649.150738.1343067428434.JavaMail.root@redhat.com</a>><br>Content-Type: text/plain; charset=utf-8<br><br>----- Original Message -----<br>> From: "Drew Morone" <<a ymailto="mailto:andrewmorone@yahoo.com" href="mailto:andrewmorone@yahoo.com">andrewmorone@yahoo.com</a>><br>> To: <a ymailto="mailto:pacemaker@oss.clusterlabs.org"
href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>> Sent: Monday, July 23, 2012 10:51:23 AM<br>> Subject: [Pacemaker] Some errors after upgrading from heartbeat 2.1 cluster<br>> <br>> <br>> <br>> <br>> Hi,<br>> I'm new to this list and have been searching for a solution for a few<br>> weeks to a problem I'm having, but not seeing anything similar to<br>> what i'm seeing.<br>> <br>> <br>> We have a 2 node active/standby cluster with the following services:<br>> drbd<br>> nfs<br>> dhcpd<br>> <br>> <br>> We currently upgraded our OS from Debian Lenny, to Squeeze, which in<br>> turn upgraded heartbeat to hearbeat(3.0.3) /pacemaker(1.0.9) . The<br>> upgrade actually went pretty well following this example:<br>> <a href="http://www.linux-ha.org/doc/users-guide/_upgrading_from_crm_enabled_heartbeat_2_1_clusters.html"
target="_blank">http://www.linux-ha.org/doc/users-guide/_upgrading_from_crm_enabled_heartbeat_2_1_clusters.html</a><br>> <br>> and everything seems to work well, no down time, no loss of data. My<br>> only issue is that I'm getting some errors with some of the resource<br>> attributes and parameters, eg running 'crm configure verify' I'll<br>> get stuff like this:<br>> <br>> ERROR: DRBD_data: attribute target_role does not exist<br>> ERROR: DRBD_data: parameter target_role does not exist<br>> <br>> <br>> <br>> Here's the section of the converted schema it's complaining about:<br>> <primitive id="DRBD_data" class="heartbeat" type="drbddisk"><br>> <meta_attributes id="primitive-DRBD_data.meta"><br>> <nvpair id="nvpair.meta.auto-19" name="target_role" value="started"/><br><br>I believe the meta attribute is target-role not target_role.<br><br>-- Vossel<br><br>>
</meta_attributes><br>> <instance_attributes id="instance_attributes.id179586"><br>> <nvpair id="nvpair.id178988" name="target_role" value="started"/><br>> <nvpair name="target_role" value="drbd0" id="nvpair.id178172"/><br>> </instance_attributes><br>> </primitive><br>> <br>> <br>> I'm assuming that those parameters are no longer used, or used<br>> differently in the heartbeat/pacemaker configurations. We upgraded<br>> to the new schema format. I don't want to rebuild the configuration<br>> from scratch, but I'm thinking maybe I might have to. Unless these<br>> errors are benign. Everything seems to work properly.<br>> <br>> <br>> Drew<br>> _______________________________________________<br>> Pacemaker mailing list: <a ymailto="mailto:Pacemaker@oss.clusterlabs.org" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>> <a
href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>> <br>> Project Home: <a href="http://www.clusterlabs.org/" target="_blank">http://www.clusterlabs.org</a><br>> Getting started:<br>> <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>> Bugs: <a href="http://bugs.clusterlabs.org/" target="_blank">http://bugs.clusterlabs.org</a><br>> <br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 23 Jul 2012 12:38:21 -0700<br>From: David Barchas <<a ymailto="mailto:dave@barchas.com" href="mailto:dave@barchas.com">dave@barchas.com</a>><br>To: <a ymailto="mailto:pacemaker@oss.clusterlabs.org" href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>Subject: Re: [Pacemaker] None of the standard agents in
ocf:heartbeat<br> are working in centos 6<br>Message-ID: <<a ymailto="mailto:2EDD049E45D549E69571B95D5F355D72@barchas.com" href="mailto:2EDD049E45D549E69571B95D5F355D72@barchas.com">2EDD049E45D549E69571B95D5F355D72@barchas.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br><br><br>On Monday, July 23, 2012 at 7:48 AM, David Barchas wrote:<br><br>> <br>> > Date: Mon, 23 Jul 2012 14:15:27 +0300<br>> > From: Vladislav Bogdanov<br>> > <br>> > 23.07.2012 08:06, David Barchas wrote:<br>> > > Hello.<br>> > > <br>> > > I have been working on this for 3 days now, and must be so stressed out<br>> > > that I am being blinded to what is probably an obvious cause of this. In<br>> > > a word, HELP.<br>> > > <br>> > <br>> > <br>> > setenforce 0 ?<br>> > <br>> i am familiar with it but have never had to disable it. I would be
surprised for packages in standard repos.<br>> However, I am going to try that anyway just to make sure. <br>> <br>> thanks for the help!<br>> dave<br>> <br><br>That worked...<br>Aside from the fact that I have probably spent about 5 hours per each letter of that solution and that nowhere on the tubes is that even mentioned regarding the base agents, I am grateful. Thank you. You may have just saved me from having a stroke. <br><br>Now however, I need to understand why?<br>What are my risks? I imagine none, since this is storage server with almost no access.<br>What does this tell me was actually wrong? Do I blame SElinux or the agents or pacemaker? Any way to figure it out?<br><br>thanks again, and the rest of you who lent your brains to me.<br><br>dave<br><br><br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a
href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20120723/9e5d1a47/attachment-0001.html" target="_blank">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20120723/9e5d1a47/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 3<br>Date: Mon, 23 Jul 2012 21:42:10 +0200<br>From: Marcus Osdoba <<a ymailto="mailto:marcus.osdoba@googlemail.com" href="mailto:marcus.osdoba@googlemail.com">marcus.osdoba@googlemail.com</a>><br>To: The Pacemaker cluster resource manager<br> <<a ymailto="mailto:pacemaker@oss.clusterlabs.org" href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>Subject: [Pacemaker] lxc resource fixes<br>Message-ID: <<a ymailto="mailto:500DA912.3010209@googlemail.com" href="mailto:500DA912.3010209@googlemail.com">500DA912.3010209@googlemail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-15; format=flowed<br><br>Dear
mailinglist,<br><br>I am using lxc in a pacemaker clustered environment.<br>I have noted, that the current version in git is not capable to work <br>with 0.7.5 correctly.<br><br>The lxc-ps command changed in 0.7.5, too. So I have applied the same fix <br>as the last commit on lxc in resource-agent.git [0].<br><br>[1] and [2] are cosmetical fixes. I think it's better to give a warning, <br>when the container is stopped instead of cleanly halted.<br><br>Regarding [3], at least in Debian based systems, it's possible to launch <br>the lxc-halt command to perform a clean shutdown of the container. <br>Therfore, I enhanced the current lxc-ocf version to support an additonal <br>optional parameter named shutdownmethod. It defaults to the current <br>behaviour, which is sending SIGPWR to init/systemd processes inside the <br>container. Alternatively, it's possible to command an lxc-halt to the <br>container (which does not require the requested powerfail-line
in inittab).<br><br><br>Please consider committing [0] at least and think about the alternative <br>halt-method [3].<br><br>Thanks in advance and kind regards,<br>Marcus<br><br><br>[0] <br><a href="https://gitorious.org/debian/resource-agents/commit/f7b8fba8809d34c537e95a1aeaa2bc64463a9049" target="_blank">https://gitorious.org/debian/resource-agents/commit/f7b8fba8809d34c537e95a1aeaa2bc64463a9049</a><br><br>[1] <br><a href="https://gitorious.org/debian/resource-agents/commit/08c321a5c92793d6b43bbffef980fdabaa1df1ce" target="_blank">https://gitorious.org/debian/resource-agents/commit/08c321a5c92793d6b43bbffef980fdabaa1df1ce</a><br><br>[2] <br><a href="https://gitorious.org/debian/resource-agents/commit/42838ca854557a06ee9669cea9e1c560b5b50d46" target="_blank">https://gitorious.org/debian/resource-agents/commit/42838ca854557a06ee9669cea9e1c560b5b50d46</a><br><br>[3] <br><a
href="https://gitorious.org/debian/resource-agents/commit/cc3bdb5968d0a28a695acc93c23a4cf1f09749f6" target="_blank">https://gitorious.org/debian/resource-agents/commit/cc3bdb5968d0a28a695acc93c23a4cf1f09749f6</a><br><br><br><br>------------------------------<br><br>Message: 4<br>Date: Tue, 24 Jul 2012 11:50:54 +1000<br>From: Andrew Beekhof <<a ymailto="mailto:andrew@beekhof.net" href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>><br>To: The Pacemaker cluster resource manager<br> <<a ymailto="mailto:pacemaker@oss.clusterlabs.org" href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>Subject: Re: [Pacemaker] None of the standard agents in ocf:heartbeat<br> are working in centos 6<br>Message-ID:<br> <CAEDLWG1L8_6BbtzP=8QoQiMFt3Pp8BcWGnEKD+<a ymailto="mailto:T_0xUUha5jMg@mail.gmail.com"
href="mailto:T_0xUUha5jMg@mail.gmail.com">T_0xUUha5jMg@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>On Tue, Jul 24, 2012 at 5:38 AM, David Barchas <<a ymailto="mailto:dave@barchas.com" href="mailto:dave@barchas.com">dave@barchas.com</a>> wrote:<br>><br>> On Monday, July 23, 2012 at 7:48 AM, David Barchas wrote:<br>><br>><br>> Date: Mon, 23 Jul 2012 14:15:27 +0300<br>> From: Vladislav Bogdanov<br>><br>> 23.07.2012 08:06, David Barchas wrote:<br>><br>> Hello.<br>><br>> I have been working on this for 3 days now, and must be so stressed out<br>> that I am being blinded to what is probably an obvious cause of this. In<br>> a word, HELP.<br>><br>><br>> setenforce 0 ?<br>><br>> i am familiar with it but have never had to disable it. I would be surprised<br>> for packages in standard repos.<br><br>No-one has written an selinux policy for pacemaker yet.<br>I would
imagine that will come in the next month or so.<br><br>> However, I am going to try that anyway just to make sure.<br>><br>> thanks for the help!<br>> dave<br>><br>><br>> That worked...<br>> Aside from the fact that I have probably spent about 5 hours per each letter<br>> of that solution and that nowhere on the tubes is that even mentioned<br>> regarding the base agents, I am grateful. Thank you. You may have just saved<br>> me from having a stroke.<br>><br>> Now however, I need to understand why?<br>> What are my risks? I imagine none, since this is storage server with almost<br>> no access.<br>> What does this tell me was actually wrong? Do I blame SElinux or the agents<br>> or pacemaker? Any way to figure it out?<br>><br>> thanks again, and the rest of you who lent your brains to me.<br>><br>> dave<br>><br>><br>><br>><br>>
_______________________________________________<br>> Pacemaker mailing list: <a ymailto="mailto:Pacemaker@oss.clusterlabs.org" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>><br>> Project Home: <a href="http://www.clusterlabs.org/" target="_blank">http://www.clusterlabs.org</a><br>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>> Bugs: <a href="http://bugs.clusterlabs.org/" target="_blank">http://bugs.clusterlabs.org</a><br>><br><br><br><br>------------------------------<br><br>Message: 5<br>Date: Mon, 23 Jul 2012 19:32:03 -0700<br>From: David Barchas <<a ymailto="mailto:dave@barchas.com"
href="mailto:dave@barchas.com">dave@barchas.com</a>><br>To: The Pacemaker cluster resource manager<br> <<a ymailto="mailto:pacemaker@oss.clusterlabs.org" href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>Subject: Re: [Pacemaker] None of the standard agents in ocf:heartbeat<br> are working in centos 6<br>Message-ID: <-4283991851919095708@unknownmsgid><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>--Sent mobile--<br><br>On Jul 23, 2012, at 6:58 PM, Andrew Beekhof <andrew@.net> wrote:<br><br>> On Tue, Jul 24, 2012 at 5:38 AM, David Barchas <dave@.com> wrote:<br>>><br>>> On Monday, July 23, 2012 at 7:48 AM, David Barchas wrote:<br>>><br>>><br>>> Date: Mon, 23 Jul 2012 14:15:27 +0300<br>>> From: Vladislav Bogdanov<br>>><br>>> 23.07.2012 08:06, David Barchas wrote:<br>>><br>>>
Hello.<br>>><br>>> I have been working on this for 3 days now, and must be so stressed out<br>>> that I am being blinded to what is probably an obvious cause of this. In<br>>> a word, HELP.<br>>><br>>><br>>> setenforce 0 ?<br>>><br>>> i am familiar with it but have never had to disable it. I would be surprised<br>>> for packages in standard repos.<br>><br>> No-one has written an selinux policy for pacemaker yet.<br>> I would imagine that will come in the next month or so.<br><br>Ahhhh. I have never had to deal with SELinux before. Other<br>coro/pace/drbd installs of mine have been other less enterprise level<br>distros like Ubuntu. Simple things always get me.<br><br>><br>>> However, I am going to try that anyway just to make sure.<br>>><br>>> thanks for the help!<br>>> dave<br>>><br>>><br>>> That worked...<br>>> Aside from the fact
that I have probably spent about 5 hours per each letter<br>>> of that solution and that nowhere on the tubes is that even mentioned<br>>> regarding the base agents, I am grateful. Thank you. You may have just saved<br>>> me from having a stroke.<br>>><br>>> Now however, I need to understand why?<br>>> What are my risks? I imagine none, since this is storage server with almost<br>>> no access.<br>>> What does this tell me was actually wrong? Do I blame SElinux or the agents<br>>> or pacemaker? Any way to figure it out?<br>>><br>>> thanks again, and the rest of you who lent your brains to me.<br>>><br>>> dave<br>>><br>>><br>>><br>>><br>>> _______________________________________________<br>>> Pacemaker mailing list: <a ymailto="mailto:Pacemaker@oss.clusterlabs.org"
href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>>><br>>> Project Home: <a href="http://www.clusterlabs.org/" target="_blank">http://www.clusterlabs.org</a><br>>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>>> Bugs: <a href="http://bugs.clusterlabs.org/" target="_blank">http://bugs.clusterlabs.org</a><br>><br>> _______________________________________________<br>> Pacemaker mailing list: <a ymailto="mailto:Pacemaker@oss.clusterlabs.org" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker"
target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>><br>> Project Home: <a href="http://www.clusterlabs.org/" target="_blank">http://www.clusterlabs.org</a><br>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>> Bugs: <a href="http://bugs.clusterlabs.org/" target="_blank">http://bugs.clusterlabs.org</a><br><br><br><br>------------------------------<br><br>Message: 6<br>Date: Tue, 24 Jul 2012 13:10:43 +0900<br>From: Yuichi SEINO <<a ymailto="mailto:seino.cluster2@gmail.com" href="mailto:seino.cluster2@gmail.com">seino.cluster2@gmail.com</a>><br>To: Jiaju Zhang <<a ymailto="mailto:jjzhang@suse.de" href="mailto:jjzhang@suse.de">jjzhang@suse.de</a>><br>Cc: The Pacemaker cluster resource manager<br> <<a ymailto="mailto:pacemaker@oss.clusterlabs.org"
href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>Subject: Re: [Pacemaker] Do you need to execute crm_ticket on<br> arbitrator?<br>Message-ID:<br> <CAMb0o5Lk+Yj8=<a ymailto="mailto:5rX3AxWHrk7DgvaHuTeQYngho3Mm-sex26ejA@mail.gmail.com" href="mailto:5rX3AxWHrk7DgvaHuTeQYngho3Mm-sex26ejA@mail.gmail.com">5rX3AxWHrk7DgvaHuTeQYngho3Mm-sex26ejA@mail.gmail.com</a>><br>Content-Type: text/plain; charset=UTF-8<br><br>> Yes, arbitrator is not using cib. I'm fine with removing the crm_ticket<br>> calling logic on arbitrator. An implementation detail on this issue<br>> would be to keep the modularity of the code structure, that is,<br>> proposer, acceptor and learner is the terminology of paxos algorithm,<br>> site and arbitrator is the GEO clustering terminology, I'd like each<br>> component to be more independent and its internal logic is transparent<br>> to other
components.<br>><br>> Thanks,<br>> Jiaju<br>><br>><br><br>Hi jiaju,<br><br>I understand the answer. Do you fix this problem on the next development?<br><br>And, I know that the following function will be developed when you<br>work the next development.<br><br>* new catch-up code<br>* the refactoring of the transport layer<br><br>I would like to know if there are other functions.<br><br>Sincerely,<br>Yuichi<br><br>-- <br>Yuichi SEINO<br>METROSYSTEMS CORPORATION<br>E-mail:<a ymailto="mailto:seino.cluster2@gmail.com" href="mailto:seino.cluster2@gmail.com">seino.cluster2@gmail.com</a><br><br><br><br>------------------------------<br><br>Message: 7<br>Date: Tue, 24 Jul 2012 12:25:05 +0800<br>From: Jiaju Zhang <<a ymailto="mailto:jjzhang@suse.de" href="mailto:jjzhang@suse.de">jjzhang@suse.de</a>><br>To: Yuichi SEINO <<a ymailto="mailto:seino.cluster2@gmail.com"
href="mailto:seino.cluster2@gmail.com">seino.cluster2@gmail.com</a>><br>Cc: The Pacemaker cluster resource manager<br> <<a ymailto="mailto:pacemaker@oss.clusterlabs.org" href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>Subject: Re: [Pacemaker] Do you need to execute crm_ticket on<br> arbitrator?<br>Message-ID: <<a ymailto="mailto:1343103905.3396.5.camel@linux-jjzhang.site" href="mailto:1343103905.3396.5.camel@linux-jjzhang.site">1343103905.3396.5.camel@linux-jjzhang.site</a>><br>Content-Type: text/plain; charset="UTF-8"<br><br>On Tue, 2012-07-24 at 13:10 +0900, Yuichi SEINO wrote:<br>> > Yes, arbitrator is not using cib. I'm fine with removing the crm_ticket<br>> > calling logic on arbitrator. An implementation detail on this issue<br>> > would be to keep the modularity of the code structure, that is,<br>> > proposer, acceptor and learner is the
terminology of paxos algorithm,<br>> > site and arbitrator is the GEO clustering terminology, I'd like each<br>> > component to be more independent and its internal logic is transparent<br>> > to other components.<br>> ><br>> > Thanks,<br>> > Jiaju<br>> ><br>> ><br>> <br>> Hi jiaju,<br>> <br>> I understand the answer. Do you fix this problem on the next development?<br><br>Yes.<br><br>> <br>> And, I know that the following function will be developed when you<br>> work the next development.<br>> <br>> * new catch-up code<br>> * the refactoring of the transport layer<br>> <br>> I would like to know if there are other functions.<br><br>To add more policies and make booth more configurable, add watchdog<br>daemon.<br><br>Also you can raise your feature request if you think something need to<br>be
implemented;)<br><br>Thanks,<br>Jiaju<br><br><br><br><br><br>------------------------------<br><br>Message: 8<br>Date: Tue, 24 Jul 2012 07:25:24 +0300<br>From: Vladislav Bogdanov <<a ymailto="mailto:bubble@hoster-ok.com" href="mailto:bubble@hoster-ok.com">bubble@hoster-ok.com</a>><br>To: The Pacemaker cluster resource manager<br> <<a ymailto="mailto:pacemaker@oss.clusterlabs.org" href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>Subject: Re: [Pacemaker] None of the standard agents in ocf:heartbeat<br> are working in centos 6<br>Message-ID: <<a ymailto="mailto:500E23B4.8070901@hoster-ok.com" href="mailto:500E23B4.8070901@hoster-ok.com">500E23B4.8070901@hoster-ok.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>24.07.2012 04:50, Andrew Beekhof wrote:<br>> On Tue, Jul 24, 2012 at 5:38 AM, David Barchas <<a ymailto="mailto:dave@barchas.com"
href="mailto:dave@barchas.com">dave@barchas.com</a>> wrote:<br>>><br>>> On Monday, July 23, 2012 at 7:48 AM, David Barchas wrote:<br>>><br>>><br>>> Date: Mon, 23 Jul 2012 14:15:27 +0300<br>>> From: Vladislav Bogdanov<br>>><br>>> 23.07.2012 08:06, David Barchas wrote:<br>>><br>>> Hello.<br>>><br>>> I have been working on this for 3 days now, and must be so stressed out<br>>> that I am being blinded to what is probably an obvious cause of this. In<br>>> a word, HELP.<br>>><br>>><br>>> setenforce 0 ?<br>>><br>>> i am familiar with it but have never had to disable it. I would be surprised<br>>> for packages in standard repos.<br>> <br>> No-one has written an selinux policy for pacemaker yet.<br>> I would imagine that will come in the next month or so.<br>> <br><br>Highly appreciated. However lrmd part may be not as easy to
implement<br>properly as it seems at the first glance.<br><br><br><br><br><br>------------------------------<br><br>_______________________________________________<br>Pacemaker mailing list<br><a ymailto="mailto:Pacemaker@oss.clusterlabs.org" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br><br><br>End of Pacemaker Digest, Vol 56, Issue 54<br>*****************************************<br><br><br> </div> </div> </div></body></html>