On Fri, 2011-05-06 at 16:15 +0200, Andrew Beekhof wrote:
> On Fri, May 6, 2011 at 12:28 PM, Holger Teutsch <holger.teut...@web.de> wrote:
> > On Fri, 2011-05-06 at 11:03 +0200, Andrew Beekhof wrote:
> >> On Fri, May 6, 2011 at 9:53 AM, Andrew Beekhof <and...@beekhof.net> wrote:
> >> > On Thu, May 5, 2011 at 5:43 PM, Holger Teutsch <holger.teut...@web.de> 
> >> > wrote:
> >> >> On Fri, 2011-04-29 at 09:41 +0200, Andrew Beekhof wrote:
> >> >>> >>
> >> >>> > Unfortunately the devel code does not run at all in my environment 
> >> >>> > so I
> >> >>> > have to fix this first.
> >> >>>
> >> >>> Oh?  I ran CTS on it the other day and it was fine here.
> >> >>>
> >> >>
> >> >> I installed pacemaker-devel on top of a compilation of pacemaker-1.1. In
> >> >> addition I tried "make uninstall" for both versions and then again
> >> >> "make install" for devel. Pacemaker does not come up, crm_mon shows
> >> >> nodes as offline.
> >> >>
> >> >> I suspect reason is
> >> >> May  5 17:09:34 devel1 crmd: [5942]: notice: crmd_peer_update: Status 
> >> >> update: Client devel1/crmd now has status [online] (DC=<null>)
> >> >> May  5 17:09:34 devel1 crmd: [5942]: info: crm_update_peer: Node 
> >> >> devel1: id=1790093504 state=unknown addr=(null) votes=0 born=0 seen=0 
> >> >> proc=00000000000000000000000000111312 (new)
> >> >> May  5 17:09:34 devel1 crmd: [5942]: info: pcmk_quorum_notification: 
> >> >> Membership 0: quorum retained (0)
> >> >> May  5 17:09:34 devel1 crmd: [5942]: debug: do_fsa_action: 
> >> >> actions:trace: #011// A_STARTED
> >> >> May  5 17:09:34 devel1 crmd: [5942]: info: do_started: Delaying start, 
> >> >> no membership data (0000000000100000)
> >> >>                                                       
> >> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> >> May  5 17:09:34 devel1 crmd: [5942]: debug: register_fsa_input_adv: 
> >> >> Stalling the FSA pending further input: cause=C_FSA_INTERNAL
> >> >>
> >> >> Any ideas ?
> >> >
> >> > Hg version?  Corosync config?
> >> > I'm running -devel here right now and things are fine.
> >>
> >> Uh, I think I see now.
> >> Try http://hg.clusterlabs.org/pacemaker/1.1/rev/b94ce5673ce4
> >>
> 
> Yeah, I realized afterwards that it was specific to devel.
> What does your corosync config look like?
I run corosync-1.3.0-3.1.x86_64.
It's exactly the same config that worked with
pacemaker 1.1 rev 10608:b4f456380f60



# Please read the corosync.conf.5 manual page
compatibility: whitetank

aisexec {
        # Run as root - this is necessary to be able to manage
        # resources with Pacemaker
        user:           root
        group:          root
}

service {
        # Load the Pacemaker Cluster Resource Manager
        ver:            1
        name:           pacemaker
        use_mgmtd:      yes
        use_logd:       yes
}

totem {
        # The only valid version is 2
        version:        2

        # How long before declaring a token lost (ms)
        token:          5000

        # How many token retransmits before forming a new configuration
        token_retransmits_before_loss_const: 10

        # How long to wait for join messages in the membership protocol (ms)
        join:           60

        # How long to wait for consensus to be achieved before starting
        # a new round of membership configuration (ms)
        consensus:      6000

        # Turn off the virtual synchrony filter
        vsftype:        none

        # Number of messages that may be sent by one processor on
        # receipt of the token
        max_messages:   20

        # Limit generated nodeids to 31-bits (positive signed integers)
        clear_node_high_bit: yes

        # Disable encryption
        secauth:        off

        # How many threads to use for encryption/decryption
        threads:        0

        # Optionally assign a fixed node id (integer)
        # nodeid:       1234

        rrp_mode:       active

        interface {
                ringnumber:     0

                # The following values need to be set based on your environment
                bindnetaddr:    192.168.178.0
                mcastaddr:      226.94.40.1
                mcastport:      5409
        }

        interface {
                ringnumber:     1

                # The following values need to be set based on your environment
                bindnetaddr:    10.1.1.0
                mcastaddr:      226.94.41.1
                mcastport:      5411
        }
}

logging {
        fileline:       off
        to_stderr:      no
        to_logfile:     no
        to_syslog:      yes
        syslog_facility: daemon
        debug:          on
        timestamp:      off
}

amf {
        mode: disabled
}

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Reply via email to