Hi Andrew,
I registered a problem in Bugzilla.
And I attached a file of crm_report.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5213
Best Regards,
Hideo Yamauchi.
--- On Thu, 2014/5/15, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > >> Your config looks reasonable... almost certain
Hi Andrwe,
> Here we go:
>
> https://github.com/ClusterLabs/pacemaker-1.0/blob/master/README.md
>
> If any additional bugs are found in 1.0, we should create a new entry at
> bugs.clusterlabs.org, add it to the above README and as long as 1.1 is
> unaffected: close the bug as WONTFIX.
All
On 15 May 2014, at 9:54 am, renayama19661...@ybb.ne.jp wrote:
> Hi Andrew,
>
>>> It is not necessary at all to revise it for Pacemaker1.0.
>>
>> Maybe we need to add KnownIssues.md to the repo for anyone thats slow to
>> update.
>> Are there any 1.0 bugs that really really need fixing or shall
Hi Andrew,
> >> Your config looks reasonable... almost certainly a bug in the PE.
> >> Do you happen to have the relevant pengine input file available?
> >
> > Really?
>
> I would expect that:
>
> colocation rsc_colocation-master-1 INFINITY: msPostgresql:Master A-master
>
> would only promot
On 15 May 2014, at 9:57 am, renayama19661...@ybb.ne.jp wrote:
> Hi Andrew,
>
> Thank you for comments.
>
>>> We do not want to be promoted to Master in the node that primitive resource
>>> does not start.
>>> Is there the setting of colocation and order which are not promoted to
>>> Master of
Hi Andrew,
Thank you for comments.
> > We do not want to be promoted to Master in the node that primitive resource
> > does not start.
> > Is there the setting of colocation and order which are not promoted to
> > Master of the Master node?
>
> Your config looks reasonable... almost certainly
Hi Andrew,
> > It is not necessary at all to revise it for Pacemaker1.0.
>
> Maybe we need to add KnownIssues.md to the repo for anyone thats slow to
> update.
> Are there any 1.0 bugs that really really need fixing or shall we move them
> all to the KnownIssues file?
That's a good idea.
In th
On 14 May 2014, at 8:00 pm, Sékine Coulibaly wrote:
> Hi Andrew,
>
> I came through some kind of solution, lightly different from what I used in
> my first post.
> You'll find it in the raw cibadmin attached to this post.
> BOUM,UFO,INGESTOR and QUOTAS all are applications and depend on ZK and
On 15 May 2014, at 1:39 am, Chris Adams wrote:
> I have a two node cluster for NFS service. The servers are running
> CentOS 6.5 with corosync-1.4.1 and pacemaker-1.1.10. They each have a
> pair of NICs bonded together running a VLAN trunk, with interfaces
> vlan10 and vlan11. The "main" IP o
I have a two node cluster for NFS service. The servers are running
CentOS 6.5 with corosync-1.4.1 and pacemaker-1.1.10. They each have a
pair of NICs bonded together running a VLAN trunk, with interfaces
vlan10 and vlan11. The "main" IP on each server is on vlan10, and
that's where the cluster c
Hi Andrew,
I came through some kind of solution, lightly different from what I used in
my first post.
You'll find it in the raw cibadmin attached to this post.
BOUM,UFO,INGESTOR and QUOTAS all are applications and depend on ZK and
Postgresql.
I'm somewhat stuck with 6.3 release for the moment. Ri
On 13 May 2014, at 3:14 pm, renayama19661...@ybb.ne.jp wrote:
> Hi All,
>
> We assume special resource constitution.
> Master of master-slave depends on primitive resource for the constitution.
>
> We performed the setting that Master stopped becoming it in Slave node
> experimentally.
>
>
>
On 12 May 2014, at 6:04 pm, david.miao wrote:
> I install fence_ipmilan with the command: yum install fence-agents
>
> My stonith configuration is as following:
> node master
> node slave
> ...
> primitive stonith-master stonith:fence_ipmilan \
>params ipaddr=192.168.1.36 login=root passwd=
On 14 May 2014, at 5:23 am, Ian wrote:
> David Vossel wrote:
>> does setting resource-stickiness help?
>> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#s-resource-options
>
>
> Thanks for the suggestion. Applied resource-stickiness=100 to the vm
14 matches
Mail list logo
