Thanks for the details, Jan.
We have cross-compiled the same way.
However because of space constraints on target we copied selected folders.
For this issue, I made a softlink for pacemaker-1.0.rng to point to
pacemaker-next.rng
and that did the trick. :)
I am not getting the error and the node
On 05/06/2016 12:40 PM, Nikhil Utane wrote:
> Hi,
>
> I used the blackbox feature which showed the reason for failure.
> As I am cross-compiling pacemaker on a build machine and later moving
> the binaries to the target, few binaries were missing. After fixing
> that and bunch of other
On 05/05/2016 11:25 AM, Nikhil Utane wrote:
> Thanks Ken for your quick response as always.
>
> But what if I don't want to use quorum? I just want to bring up
> pacemaker + corosync on 1 node to check that it all comes up fine.
> I added corosync_votequorum as you suggested. Additionally I also
Hi,
Continuing with my adventure to run Pacemaker & Corosync on our big-endian
system, I managed to get past the corosync issue for now. But facing an
issue in running Pacemaker.
Seeing following messages in corosync.log.
pacemakerd: warning: pcmk_child_exit: The cib process (2) can no
