On Thu, Nov 01, 2012 at 11:05:04AM +1100, Andrew Beekhof wrote:
> On Thu, Nov 1, 2012 at 7:40 AM, Jacek Konieczny wrote:
> > On Wed, Oct 31, 2012 at 05:33:03PM +1100, Andrew Beekhof wrote:
> >> I havent seen that before. What version?
> >
> > Pacemaker 1.1.8, corosync 2.1.0, cluster-glue 1.0.11
>
On Thu, Nov 1, 2012 at 7:40 AM, Jacek Konieczny wrote:
> On Wed, Oct 31, 2012 at 05:33:03PM +1100, Andrew Beekhof wrote:
>> I havent seen that before. What version?
>
> Pacemaker 1.1.8, corosync 2.1.0, cluster-glue 1.0.11
I think you want these two patches:
https://github.com/beekhof/pacemaker/c
On Wed, Oct 31, 2012 at 05:33:03PM +1100, Andrew Beekhof wrote:
> I havent seen that before. What version?
Pacemaker 1.1.8, corosync 2.1.0, cluster-glue 1.0.11
> On Wed, Oct 31, 2012 at 12:42 AM, Jacek Konieczny wrote:
> > Hello,
> >
> > Probably this is not a critical problem, but it become an
I havent seen that before. What version?
On Wed, Oct 31, 2012 at 12:42 AM, Jacek Konieczny wrote:
> Hello,
>
> Probably this is not a critical problem, but it become annoying during
> my cluster setup/testing time:
>
> Whenever I restart corosync with 'systemctl restart corosync.service' I
> get