Stanislav,
> Hi Ken,
thanks for the info, I will try 2.3.4 or maybe even 2.3.3 like in
original compilation guide.
also maybe you are hitting same problem as was discussed on list in
thread (Corosync: 100% cpu (corosync 2.3.5, libqb 0.17.1, pacemaker 1.1.13)
Solution is ether apply
Hi Andrew,
yeah, sorry about that, I need good glasses, it's working now. However
(and It maybe slight off-topic of my initial mail) the cluster is
reeeaally slow, the nodes appear online after 1-2 min after corosync
and pacemaker start and CPU is often at 100% for corosync process,
resource
Hi Ken,
thanks for the info, I will try 2.3.4 or maybe even 2.3.3 like in
original compilation guide.
Best,
Stan
2015-08-28 19:04 GMT+02:00 Ken Gaillot kgail...@redhat.com:
On 08/28/2015 10:59 AM, Stanislav Kopp wrote:
Hi Andrew,
yeah, sorry about that, I need good glasses, it's working
Hi all,
I'm trying to run corosync2 + pacemaker setup on Debian Jessie (only
for testing purpose), I've successfully compiled all components using
this guide: http://clusterlabs.org/wiki/Compiling_on_Debian
Unfortunately, if I run crm_mon I don't see any nodes.
