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 migration takes many seconds too (no such problem with same IPaddr2 resource on Debian's Wheezy or Ubuntu's 14.04 pacemakers) Once again, I dont really see errors in corosync.log http://pastebin.com/zLwQJaqu besides maybe
crmd: warning: do_log: FSA: Input I_DC_TIMEOUT from crm_timer_popped() received in state S_PENDING and many CPU warnings. Best, Stan 2015-08-28 6:09 GMT+02:00 Andrew Beekhof <and...@beekhof.net>: > >> On 25 Aug 2015, at 1:45 am, Stanislav Kopp <stask...@gmail.com> wrote: >> >> 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. >> >> ####################################### >> Last updated: Mon Aug 24 17:36:00 2015 >> Last change: Mon Aug 24 17:17:42 2015 >> Current DC: NONE >> 0 Nodes configured >> 0 Resources configured >> ######################################## >> >> I don't see any errors in corosync log either: http://pastebin.com/bJX66B9e > > really? > > Aug 24 17:16:10 [1723] pm1 crmd: error: cluster_connect_quorum: > Corosync quorum is not configured > > Looks like you forgot to uncomment: > > #provider: corosync_votequorum > >> >> This is my corosync.conf >> >> ############################################### >> >> # Please read the corosync.conf.5 manual page >> totem { >> version: 2 >> >> crypto_cipher: none >> crypto_hash: none >> >> interface { >> ringnumber: 0 >> bindnetaddr: 192.168.122.0 >> mcastport: 5405 >> ttl: 1 >> } >> transport: udpu >> } >> >> logging { >> fileline: off >> to_logfile: yes >> to_syslog: no >> logfile: /var/log/cluster/corosync.log >> debug: off >> timestamp: on >> logger_subsys { >> subsys: QUORUM >> debug: off >> } >> } >> >> nodelist { >> node { >> ring0_addr: 192.168.122.172 >> #nodeid: 1 >> } >> >> node { >> ring0_addr: 192.168.122.113 >> #nodeid: 2 >> } >> } >> >> quorum { >> # Enable and configure quorum subsystem (default: off) >> # see also corosync.conf.5 and votequorum.5 >> #provider: corosync_votequorum >> } >> >> #################################### >> >> used components: >> >> pacemaker: 1.1.12 >> corosync: 2.3.5 >> libqb: 0.17.1 >> >> >> Did I miss something? >> >> Thanks! >> Stan >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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 _______________________________________________ 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