[Sheepdog] create_cluster(1652) Failed to join the sheepdog group, try again

[Narendra Prasad Madanapalli]

Thanks Steve. It works on Fedora13 after disabling selinux/firewall. A
similar kind of problem I encounter when corosync is started by
specifying IPv6 addr in corosync.conf file as follows:

=======corosync.conf
compatibility: whitetank

totem {
        version: 2
        secauth: off
        threads: 0
        nodeid: 1
        interface {
                ringnumber: 0
                nodeid: 1
                bindnetaddr: fe80::21e:4cff:fe59:9936
                mcastaddr:  ff05::1
                mcastport: 5405
        }
}

logging {
        fileline: off
        to_stderr: no
        to_logfile: yes
        to_syslog: yes
        logfile: /var/log/cluster/corosync.log
        debug: off
        timestamp: on
        logger_subsys {
                subsys: AMF
                debug: off
        }
}

amf {
        mode: disabled

===================

Corosync started successfully but sheepdog throws the same 'try again'
errors in sheepdog.log. I ensure ip6tables are stopped before starting
shepdog. Here, I am trying to fix addr_to_str() to support for IPv6
addresses.  I would apreciate if you can provide pointers to overcome
this error



Thanks,
Narendra.

On Wed, Aug 11, 2010 at 9:47 PM, Steven Dake <sdake at redhat.com> wrote:
> On 08/11/2010 09:10 AM, Narendra Prasad Madanapalli wrote:
>>
>> Hi,
>>
>> I encounter mentioned error when sheep is started.
>>
>> I would appreciate if someone can help me to overcome these issues.
>>
>> Here is the details of corosync&  sheepdog:
>>
>> OS Distro: FC11
>>
>> Corosync:
>> corosynclib-devel-1.2.3-1.fc11.i586
>> corosync-1.2.3-1.fc11.i586
>> corosynclib-1.2.3-1.fc11.i586
>>
>
> You may have iptables enabled which blocks corosync from executing. Another
> common problem is selinux is enabled, which only works well on newer fedora
> versions.
>
> Regards
> -steve
>
>> Corosync log contents when it is started:
>> Aug 11 09:29:36 corosync [MAIN  ] Corosync Cluster Engine ('1.2.3'):
>> started and ready to provide service.
>> Aug 11 09:29:36 corosync [MAIN  ] Corosync built-in features: nss rdma
>> Aug 11 09:29:36 corosync [MAIN  ] Successfully read main configuration
>> file '/etc/corosync/corosync.conf'.
>> Aug 11 09:29:36 corosync [TOTEM ] Initializing transport (UDP/IP).
>> Aug 11 09:29:36 corosync [TOTEM ] Initializing transmit/receive
>> security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
>> Aug 11 09:29:36 corosync [TOTEM ] The network interface
>> [192.168.122.1] is now up.
>> Aug 11 09:29:36 corosync [SERV  ] Service engine loaded: corosync
>> extended virtual synchrony service
>> Aug 11 09:29:36 corosync [SERV  ] Service engine loaded: corosync
>> configuration service
>> Aug 11 09:29:36 corosync [SERV  ] Service engine loaded: corosync
>> cluster closed process group service v1.01
>> Aug 11 09:29:36 corosync [SERV  ] Service engine loaded: corosync
>> cluster config database access v1.01
>> Aug 11 09:29:36 corosync [SERV  ] Service engine loaded: corosync
>> profile loading service
>> Aug 11 09:29:36 corosync [SERV  ] Service engine loaded: corosync
>> cluster quorum service v0.1
>> Aug 11 09:29:36 corosync [MAIN  ] Compatibility mode set to whitetank.
>>  Using V1 and V2 of the synchronization engine.
>>
>>
>> corosync.conf:
>> # cat /etc/corosync/corosync.conf
>> # Please read the corosync.conf.5 manual page
>> compatibility: whitetank
>>
>> totem {
>>        version: 2
>>        secauth: off
>>        threads: 0
>>        interface {
>>                ringnumber: 0
>>                bindnetaddr: 192.168.122.1
>>                mcastaddr: 226.94.1.1
>>                mcastport: 5405
>>        }
>> }
>>
>> logging {
>>        fileline: off
>>        to_stderr: yes
>>        to_logfile: yes
>>        to_syslog: yes
>>        logfile: /tmp/corosync.log
>>        debug: off
>>        timestamp: on
>>        logger_subsys {
>>                subsys: AMF
>>                debug: off
>>        }
>> }
>>
>> amf {
>>        mode: disabled
>> }
>>
>> sheepdog.log:
>> Aug 11 09:48:05 worker_routine(215) started this thread 60
>> Aug 11 09:48:05 worker_routine(215) started this thread 61
>> Aug 11 09:48:05 worker_routine(215) started this thread 62
>> Aug 11 09:48:05 worker_routine(215) started this thread 63
>> Aug 11 09:48:06 create_cluster(1652) Failed to join the sheepdog
>> group, try again
>> Aug 11 09:48:07 create_cluster(1652) Failed to join the sheepdog
>> group, try again
>> Aug 11 09:48:08 create_cluster(1652) Failed to join the sheepdog
>> group, try again
>> Aug 11 09:48:09 create_cluster(1652) Failed to join the sheepdog
>> group, try again
>> Aug 11 09:48:10 create_cluster(1652) Failed to join the sheepdog
>> group, try again
>>
>>
>> Thanks,
>> Narendra.
>
>