- Original Message -
> From: "Steven Silk"
> To: pacemaker@oss.clusterlabs.org
> Sent: Wednesday, May 30, 2012 8:16:56 PM
> Subject: [Pacemaker] Seems to be working but fails to transition to other
> node.
>
>
> All Concerned;
>
> I have been getting slapped around all day wit
On 5/30/2012 8:16 PM, Steven Silk wrote:
All Concerned;
I have been getting slapped around all day with this problem -
I can't solve it.
The system is only half done - I have not yet implemented the
nfs portion -
All Concerned;
I have been getting slapped around all day with this problem - I can't
solve it.
The system is only half done - I have not yet implemented the nfs portion -
but drbd part is not yet cooperating with corosync.
It appears to be working OK - but when I stop corosync on the DC - the
o
On 05/30/2012 03:41 PM, Stallmann, Andreas wrote:
> Hi!
>
>> Yes, that is default behaviour ... Pacemaker tries to stop, that fails so it
>> must assume (worst case) it is still running, now STONITH would trigger to
>> make sure the node including the resource is definitely down ... without
>>
On 05/30/2012 07:07 PM, Lutz Griesbach wrote:
> Hi there,
>
>
> im trying to setup a cluster on fedora17
>
> corosync-2.0.0-1.fc17.i686
> pacemaker-1.1.7-2.fc17.i686
>
> as i understand pacemaker packages are built without heartbeat
>
> [root@lgr-fed17-1 ~]# pacemakerd --features
> Pacemaker
On Tue, May 29, 2012 at 3:08 PM, Larry Brigman wrote:
> On Fri, May 25, 2012 at 3:40 PM, David Vossel wrote:
>> - Original Message -
>>> From: "Larry Brigman"
>>> To: "The Pacemaker cluster resource manager"
>>> Sent: Friday, May 25, 2012 5:27:21 PM
>>> Subject: Re: [Pacemaker] Removed
Hi there,
im trying to setup a cluster on fedora17
corosync-2.0.0-1.fc17.i686
pacemaker-1.1.7-2.fc17.i686
as i understand pacemaker packages are built without heartbeat
[root@lgr-fed17-1 ~]# pacemakerd --features
Pacemaker 1.1.7-2.fc17 (Build: ee0730e13d124c3d58f00016c3376a1de5323cff)
Suppor
Hi!
> Yes, that is default behaviour ... Pacemaker tries to stop, that fails so it
> must assume (worst case) it is still running, now STONITH would trigger to
> make sure the node including the resource is definitely down ... without
> STONITH it stays unmanaged until cleared.
STONITH is not
Hi Andreas,
On 05/29/2012 04:14 PM, Stallmann, Andreas wrote:
> Hi there,
>
>
>
> we have here a corosync/pacemaker cluster running tomcat. Sometimes our
> application running inside tomcat fails and tomcat dies.
>
>
>
> This – for some reason I don’t understand – leads to an “unmanaged
>
