Re: [ClusterLabs] corosync/pacemaker on ~100 nodes cluser

On 08/23/2016 11:46 AM, Klaus Wenninger wrote: > On 08/23/2016 06:26 PM, Radoslaw Garbacz wrote: >> Hi, >> >> I would like to ask for settings (and hardware requirements) to have >> corosync/pacemaker running on about 100 nodes cluster. > Actually I had thought that 16 would be the limit for full

[ClusterLabs] Solved: pacemakerd quits after few seconds with some errors

Found the 2 reasons: 1) I had to use gcc 4.8 for libqb to use internal memory barries this still did not solve the crash but changed the way it crashed the subdaemons 2) /usr/var/run is not writable to everyone, but pacemakerd subdaemons want to create socket files here with hacluster user, and

Re: [ClusterLabs] corosync/pacemaker on ~100 nodes cluser

On 08/23/2016 06:26 PM, Radoslaw Garbacz wrote: > Hi, > > I would like to ask for settings (and hardware requirements) to have > corosync/pacemaker running on about 100 nodes cluster. Actually I had thought that 16 would be the limit for full pacemaker-cluster-nodes. For larger deployments

Re: [ClusterLabs] Entire Group stop on stopping of single Resource (Jan Pokorn?)

Thanks, Jaspal Singla On Mon, Aug 22, 2016 at 7:42 PM, wrote: > Send Users mailing list submissions to > users@clusterlabs.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://clusterlabs.org/mailman/listinfo/users > or, via

Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

I found that pacemakerd leaves a core file where I launch it, nad here is the output from "mdb core": sonicle@xstorage1:/sonicle/etc/cluster/corosync# mdb core Loading modules: [ libc.so.1 ld.so.1 ] $C 08047a48 libqb.so.0.18.0`qb_thread_lock+0x16(0, feef9875, 8047a9c, fe9eb842, fe9ff000,

Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

About the hacluster/haclient user/group, I staft to think that cib can't connect because it's started by pacemakerd with user hacluster, even though pacemakerd is started as root. Instead, just before pacemakerd is able to connect with the same call, but that is the root user. So I tried to run

Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

Sure I did: created the new corosync package and installed on the dev machine before building and creating the new pacemaker package on the dev machine. Sonicle S.r.l. : http://www.sonicle.com Music:

Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

Ok, looks like Corosync now runs fine with its version, but then pacemakerd fails again with new errors on attrd and other daemons it tries to fork. The main reason seems around ha signon and cluster process group api. Any idea? Gabriele

Re: [ClusterLabs] corosync.log is 5.1GB in a short period

On 08/23/2016 08:31 AM, Kristoffer Grönlund wrote: > 朱荣 writes: > >> Hello: >> I has a problem about corosync log, my corosync log is increase to 5.1GB in >> a short time. >> Then I check the corosync log, it’s show me the same message in short >> period,like the attachment.

Re: [ClusterLabs] corosync.log is 5.1GB in a short period

朱荣 writes: > Hello: > I has a problem about corosync log, my corosync log is increase to 5.1GB in a > short time. > Then I check the corosync log, it’s show me the same message in short > period,like the attachment. > What happened about corosync? Thank you! > my corosync

Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

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