It is Freescale e6500 processor. Nobody here has tried running it in LE
mode so it is going to take some doing.
We are going to add some debug logs to figure out where does corosync
initialization get stalled.
If you have have suggestions, pls let us know.
-Thanks
Nikhil
On Mon, May 2, 2016 at 1
On 04/25/2016 07:28 AM, Lars Ellenberg wrote:
> On Thu, Apr 21, 2016 at 12:50:43PM -0500, Ken Gaillot wrote:
>> Hello everybody,
>>
>> The release cycle for 1.1.15 will be started soon (hopefully tomorrow)!
>>
>> The most prominent feature will be Klaus Wenninger's new implementation
>> of event-dr
On 04/19/2016 10:47 AM, Vladislav Bogdanov wrote:
> Hi,
>
> Just found an issue with node is silently unfenced.
>
> That is quite large setup (2 cluster nodes and 8 remote ones) with
> a plenty of slowly starting resources (lustre filesystem).
>
> Fencing was initiated due to resource stop failu
On 04/22/2016 05:55 PM, Adam Spiers wrote:
> Ken Gaillot wrote:
>> On 04/21/2016 06:09 PM, Adam Spiers wrote:
>>> Ken Gaillot wrote:
Hello everybody,
The release cycle for 1.1.15 will be started soon (hopefully tomorrow)!
The most prominent feature will be Klaus Wenninger
On 04/27/2016 09:08 AM, Klechomir wrote:
> Hi List,
> I have two major problems related to the VirtualDomain live migration
> and failover in general.
> I'm using Pacemaker 1.1.8, which is very stable and used to do
> everything right to me.
I completely understand staying on an older version that
On 04/26/2016 03:33 AM, Bogdan Dobrelya wrote:
> Is it possible to run several instances of a Corosync/Pacemaker clusters
> on a node? Can a node be a member of several clusters, so they could put
> resources there? I'm sure it's doable with separate nodes or containers,
> but that's not the case.
On 05/02/2016 03:45 PM, Jan Pokorný wrote:
> Hello Radoslaw,
>
> On 02/05/16 11:47 -0500, Radoslaw Garbacz wrote:
>> When testing pacemaker I encountered a start error, which seems to be
>> related to reported libqb segmentation fault.
>> - cluster started and acquired quorum
>> - some nodes faile
Hello Radoslaw,
On 02/05/16 11:47 -0500, Radoslaw Garbacz wrote:
> When testing pacemaker I encountered a start error, which seems to be
> related to reported libqb segmentation fault.
> - cluster started and acquired quorum
> - some nodes failed to connect to CIB, and lost membership as a result
Hi,
Firstly thank you for such a great tool.
When testing pacemaker I encountered a start error, which seems to be
related to reported libqb segmentation fault.
- cluster started and acquired quorum
- some nodes failed to connect to CIB, and lost membership as a result
- restart solved the proble
So what I understand what you are saying is, if the HW is bi-endian, then
enable LE on PPC. Is that right?
Need to check on that.
On Mon, May 2, 2016 at 12:49 PM, Nikhil Utane
wrote:
> Sorry about my ignorance but could you pls elaborate what do you mean by
> "try to ppcle"?
>
> Our target platf
Sorry about my ignorance but could you pls elaborate what do you mean by
"try to ppcle"?
Our target platform is ppc so it is BE. We have to get it running only on
that.
How do we know this is LE/BE issue and nothing else?
-Thanks
Nikhil
On Mon, May 2, 2016 at 12:24 PM, Jan Friesse wrote:
> As
11 matches
Mail list logo
