On 23/08/16 07:23 +0200, Gabriele Bulfon wrote: > Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the > "--with-corosync". > How is Corosync looking for his own version?
The situation may be as easy as building corosync from GitHub-provided automatic tarball, which is never a good idea if upstream has its own way of proper release delivery: http://build.clusterlabs.org/corosync/releases/ (specific URLs are also being part of the corosync announcements on this list) The issue with automatic tarballs already reported: https://github.com/corosync/corosync/issues/116 -- Jan (Poki)
pgpQE2w5U4jgY.pgp
Description: PGP signature
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org