Um, are you setting a nodeid in corosync.conf? Because I see this:
Nov 09 09:07:25 [2609] ha09a.mycharts.md crmd: crit: crm_get_peer: Node ha09a.mycharts.md and ha09a share the same cluster node id '973777088'! Which could easily explain why the cluster is massively confused. On Mon, Nov 12, 2012 at 10:02 AM, Andrew Beekhof <[email protected]> wrote: > On Sat, Nov 10, 2012 at 6:18 AM, Robinson, Eric <[email protected]> > wrote: >> Andrew, >> >>> > I updated to 1.1.8 from the clusterlabs-next repo. Now I am >>> back to the problem where no DC gets elected... >>> > >>> > Last updated: Thu Nov 8 10:10:06 2012 Last change: Fri Nov 2 >>> > 17:16:29 2012 Current DC: NONE 0 Nodes configured, unknown expected >>> > votes 0 Resources configured. >>> > >>> > >>> > This is what I installed this morning... >>> > >>> > [root@ha09a ~]# rpm -qa|egrep "coro|pacem" >>> > pacemaker-cli-1.1.8-4.el6.x86_64 >>> > pacemaker-libs-1.1.8-4.el6.x86_64 >>> > corosync-1.4.1-7.el6_3.1.x86_64 >>> > pacemaker-cluster-libs-1.1.8-4.el6.x86_64 >>> > corosynclib-1.4.1-7.el6_3.1.x86_64 >>> > pacemaker-1.1.8-4.el6.x86_64 >>> > >>> > >>> > Am I looking in the wrong place for the newest stuff? >>> >>> Thats the right place. >>> Logs? >>> >> >> >> Sorry for the delay. Here is a link to the corosync.log file. >> >> www.psmnv.com/downloads/corosync.log >> >> >> It is 24MB in size. If I let Pacemaker run for a couple of minutes, the log >> quickly grows to over 3GB. Something is happening over and over again and >> happening fast. > > There is definitely something weird going on. > We're logging this over and over: > > Nov 09 09:07:57 [2609] ha09a.mycharts.md crmd: debug: > crm_uptime: Current CPU usage is: 1s, 841720us > Nov 09 09:07:57 [2609] ha09a.mycharts.md crmd: debug: > crm_compare_age: Win: 1 vs 0 (seconds) > Nov 09 09:07:57 [2609] ha09a.mycharts.md crmd: error: > do_election_count_vote: Election 2 (owner: ha09a.mycharts.md) lost: > no-vote from ha09a.mycharts.md (We are not part of the cluster) > Nov 09 09:07:57 [2609] ha09a.mycharts.md crmd: debug: > crm_is_corosync_peer_active: ha09b.mycharts.md: unknown process list, > assuming active for now > Nov 09 09:07:57 [2609] ha09a.mycharts.md crmd: debug: > do_election_check: Ignore election check: we not in an election > Nov 09 09:07:57 [2609] ha09a.mycharts.md crmd: debug: > s_crmd_fsa: Processing I_PENDING: [ state=S_PENDING > cause=C_FSA_INTERNAL origin=do_election_count_vote ] > Nov 09 09:07:57 [2609] ha09a.mycharts.md crmd: debug: do_log: > FSA: Input I_PENDING from do_election_count_vote() received in state > S_PENDING > Nov 09 09:07:57 [2609] ha09a.mycharts.md crmd: debug: > crm_timer_start: Started Election Trigger (I_DC_TIMEOUT:20000ms), > src=13505 > > I'd really love to see the logs from ha09b. > > >> >> Here is the sequence I followed to produce the log. >> >> --started corosync on node1 (ha09a) >> --started corosync on node2 (ha09b) >> --used 'corosync-cfgtool -s' and 'corosync-objctl|grep member' to verify >> node memberships. >> --started pacemaker on node1 >> --started pacemaker on node2 >> --waited 30-45 seconds to allow some logs to accumulate >> >> >> >> --Eric >> >> >> >> >> >> >> >> >> >> >> >> Disclaimer - November 9, 2012 >> This email and any files transmitted with it are confidential and intended >> solely for General Linux-HA mailing list. If you are not the named addressee >> you should not disseminate, distribute, copy or alter this email. Any views >> or opinions presented in this email are solely those of the author and might >> not represent those of Physicians' Managed Care or Physician Select >> Management. Warning: Although Physicians' Managed Care or Physician Select >> Management has taken reasonable precautions to ensure no viruses are present >> in this email, the company cannot accept responsibility for any loss or >> damage arising from the use of this email or attachments. >> This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ >> _______________________________________________ >> Linux-HA mailing list >> [email protected] >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
