out the result.
>
> Kind regards
>
> fatcharly
>
>
> ---- Original-Nachricht ----
>> Datum: Fri, 20 Jul 2012 12:21:47 -0400 (EDT)
>> Von: Jake Smith
>> An: The Pacemaker cluster resource manager
>> Betreff: Re: [Pacemaker] problem with pacemaker/coro
> Datum: Tue, 24 Jul 2012 15:13:39 +0200
> Von: fatcha...@gmx.de
> An: Jake Smith , The Pacemaker cluster resource manager
>
> Betreff: Re: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3
> Hi,
>
> here are the results of the corosync status. Can´t find a proble
t; Von: Jake Smith
> An: The Pacemaker cluster resource manager
> Betreff: Re: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3
>
> - Original Message -
> > From: fatcha...@gmx.de
> > To: "Jake Smith" , "The Pacemaker cluster resource
>
- Original Message -
> From: fatcha...@gmx.de
> To: "Jake Smith" , "The Pacemaker cluster resource
> manager"
> Sent: Friday, July 20, 2012 11:50:52 AM
> Subject: Re: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3
>
> Hi Jake,
- Original Message -
> From: fatcha...@gmx.de
> To: "Jake Smith" , "The Pacemaker cluster resource
> manager"
> Sent: Friday, July 20, 2012 11:50:52 AM
> Subject: Re: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3
>
> Hi Jake,
corosync on CentOS 6.3
>
> - Original Message -
> > From: fatcha...@gmx.de
> > To: pacemaker@oss.clusterlabs.org
> > Sent: Friday, July 20, 2012 6:08:45 AM
> > Subject: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3
> >
> > Hi,
> &g
- Original Message -
> From: fatcha...@gmx.de
> To: pacemaker@oss.clusterlabs.org
> Sent: Friday, July 20, 2012 6:08:45 AM
> Subject: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3
>
> Hi,
>
> I´m using a pacemaker+corosync bundle to run a pound bas
: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3
> Hi,
>
> I´m using a pacemaker+corosync bundle to run a pound based loadbalancer.
> After an update on CentOS 6.3 there is some mismatch of the node status.
> Via crm_mon on one node eveything looks fine while on the other n
Hi,
I´m using a pacemaker+corosync bundle to run a pound based loadbalancer. After
an update on CentOS 6.3 there is some mismatch of the node status. Via crm_mon
on one node eveything looks fine while on the other node everything is offline.
Everything was fine on CentOS 6.2.
Node powerpound:
