.src.rpm
and
Source RPM : corosync-2.3.0-1.fc18.src.rpm
Rainer
Gesendet: Donnerstag, 09. Mai 2013 um 04:31 Uhr
Von: Andrew Beekhof and...@beekhof.net
An: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff: Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 08
Von:Andrew Beekhof and...@beekhof.net
An:The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 08/05/2013, at 4:53 PM, Andrew Beekhof and...@beekhof.net wrote:
On 08/05/2013, at 4:08 PM, Andrew Beekhof and...@beekhof.net wrote
.src.rpm
Rainer
Gesendet: Donnerstag, 09. Mai 2013 um 04:31 Uhr
Von: Andrew Beekhof and...@beekhof.net
An: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff: Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 08/05/2013, at 4:53 PM, Andrew Beekhof
@oss.clusterlabs.org
Betreff: Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 03/05/2013, at 4:46 AM, Rainer Brestan rainer.bres...@gmx.net wrote:
Hi Lars,
i have tried 1.1.9-2 from download area at clusterlabs for RHEL6 with
corosync 1.4.1-17, also running with 1.1.7-6 at the other node.
I have
successful
Rainer
Gesendet: Freitag, 03. Mai 2013 um 01:30 Uhr
Von: Andrew Beekhof and...@beekhof.net
An: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff: Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 03/05/2013, at 4:46 AM, Rainer Brestan rainer.bres
On 08/05/2013, at 4:53 PM, Andrew Beekhof and...@beekhof.net wrote:
On 08/05/2013, at 4:08 PM, Andrew Beekhof and...@beekhof.net wrote:
On 03/05/2013, at 8:46 PM, Rainer Brestan rainer.bres...@gmx.net wrote:
Now i have all the logs for some combinations.
Corosync: 1.4.1-7 for all
and...@beekhof.net
An:The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 03/05/2013, at 4:46 AM, Rainer Brestan rainer.bres...@gmx.net wrote:
Hi Lars,
i have tried 1.1.9-2 from download area at clusterlabs for RHEL6 with corosync
Marowsky-Bree l...@suse.com
An:pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 2013-04-24T11:44:57, Rainer Brestan rainer.bres...@gmx.net wrote:
Current DC: int2node2 - partition WITHOUT quorum
Version: 1.1.8-7.el6-394e906
This may not be the answer you want
as first impression.
Rainer
Gesendet: Dienstag, 30. April 2013 um 17:16 Uhr
Von: Lars Marowsky-Bree l...@suse.com
An: pacemaker@oss.clusterlabs.org
Betreff: Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 2013-04-24T11:44:57, Rainer Brestan rainer.bres...@gmx.net wrote:
Current DC
On 2013-04-24T11:44:57, Rainer Brestan rainer.bres...@gmx.net wrote:
Current DC: int2node2 - partition WITHOUT quorum
Version: 1.1.8-7.el6-394e906
This may not be the answer you want, since it is fairly unspecific. But
I think we noticed something similar when we pulled in 1.1.8, I don't
On 24/04/2013, at 7:44 PM, Rainer Brestan rainer.bres...@gmx.net wrote:
Pacemaker log of int2node2 with trace setting.
https://www.dropbox.com/s/04ciy2g6dfbauxy/pacemaker.log?n=165978094
On int2node1 (1.1.7) the trace setting did not create the pacemaker.log file.
Ah, yes, 1.1.7 wasn't so
@oss.clusterlabs.org
Betreff:Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 15/04/2013, at 7:08 PM, Pavlos Parissis pavlos.paris...@gmail.com wrote:
Hoi,
I upgraded 1st node and here are the logs
https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node1.debuglog
https
On 15/04/2013, at 7:08 PM, Pavlos Parissis pavlos.paris...@gmail.com wrote:
Hoi,
I upgraded 1st node and here are the logs
https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node1.debuglog
https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node2.debuglog
Enabling
Hoi,
I upgraded 1st node and here are the logs
https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node1.debuglog
https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node2.debuglog
Enabling tracing on the mentioned functions didn't give at least to me any
more information.
On 12/04/2013 09:37 μμ, Pavlos Parissis wrote:
Hoi,
As I wrote to another post[1] I failed to upgrade to 1.1.8 for a 2 node
cluster.
Before the upgrade process both nodes are using CentOS 6.3, corosync
1.4.1-7 and pacemaker-1.1.7.
I followed the rolling upgrade process, so I stopped
On 15/04/2013, at 7:31 AM, Pavlos Parissis pavlos.paris...@gmail.com wrote:
On 12/04/2013 09:37 μμ, Pavlos Parissis wrote:
Hoi,
As I wrote to another post[1] I failed to upgrade to 1.1.8 for a 2 node
cluster.
Before the upgrade process both nodes are using CentOS 6.3, corosync
1.4.1-7
Hoi,
As I wrote to another post[1] I failed to upgrade to 1.1.8 for a 2 node
cluster.
Before the upgrade process both nodes are using CentOS 6.3, corosync
1.4.1-7 and pacemaker-1.1.7.
I followed the rolling upgrade process, so I stopped pacemaker and then
corosync on node1 and upgraded to
17 matches
Mail list logo
