[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] Problem with Pacemaker and Corosync



Attached are the logs with debug enabled.
Here is corosync.conf:

#compatibility: none

aisexec {
        user:   root
        group:  root
}

totem {
    version: 2
    secauth: off
    threads: 0

    token: 1000
    join: 60
    consenus: 4800
    vsftype: none
    max_messages: 20
    clear:node_high_bit: yes

    interface {
        ringnumber: 0
        bindnetaddr: 198.38.17.40
        mcastaddr: 226.94.1.1
        mcastport: 5405
    }
}

service {
        name: pacemaker
        ver: 0
}

logging {
    fileline: off
    to_stderr: yes
    to_syslog: yes
    to_file: yes
    logfile: /var/log/corosync.log
    debug: on
    timestamp: on
}

amf {
    mode: disabled
}


On Tue, Sep 1, 2009 at 2:33 AM, Andrew Beekhof<andrew beekhof net> wrote:
> try turning on debug, there's nothing in the logs that indicate why
> the lrmd is having a problem
>
> On Mon, Aug 31, 2009 at 3:12 PM, Thomas Georgiou<tageorgiou gmail com> wrote:
>> Hi,
>>
>> I have installed Pacemaker 1.0.5, Corosync 1.0.0, and Openais 1.0.1
>> from source according to the Clusterlabs docs.  However, when I go to
>> start corosync/pacemaker, I get error messages pertaining to lrm and
>> cibadmin -Q hangs and complains that the remote node is not available.
>>  Attached is the corosync log.
>>
>> Any ideas?
>>
>> Thomas Georgiou
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster redhat com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>>
>
> --
> Linux-cluster mailing list
> Linux-cluster redhat com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>

Attachment: corosync.log
Description: Binary data


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]