Christine Caulfield <ccaulfie@xxxxxxxxxx> writes:
> On 19/04/13 12:52, Fabio M. Di Nitto wrote:
>
>> On 4/19/2013 1:31 PM, Ferenc Wagner wrote:
>>
>>> "Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx> writes:
>>>
>>>> votequorum is not supported in 1.4.x series.
>>>> You want to upgrade to corosync 2.3.x.
>>>
>>> Do you mean it's unreliable and should not be used in 1.4, even though
>>> it may seem to work?
>>
>> The basic might work, but a lot of fixes to handle some corner cases are
>> only in 2.3.
>>
>>> I'd like to stick with stock distro (Debian
>>> wheezy) packages if possible, but don't want to risk cluster operation.
>>
>> I am fairly sure there is corosync 2.3 in experimental.
>>
>>> I also use clvm, which requires OpenAIS compatibility, if I understand
>>> it right.
>>
>> It only depends how clvmd has been built. openais is not a requirement
>> for operations as there are other preferred locking methods for clvmd
>> (dlm specifically).
>
> Also clvmd in openais mode depends on the Lck service in openais. I
> think this service is best described as "unreliable" :/
Okay, I'm listening. So I installed corosync-2.3.0 from the
experimental distribution. However, I found the OpenAIS compatibility
gone and I couldn't start clvmd (2.02.95) with its corosync interface.
As per strace, it connects to the @"cpg" socket and receives SHM names,
which it opens, maps and closes:
/dev/shm/qb-cpg-request-22999-23629-19-header
/dev/shm/qb-cpg-request-22999-23629-19-data
/dev/shm/qb-cpg-response-22999-23629-19-header
/dev/shm/qb-cpg-response-22999-23629-19-data
/dev/shm/qb-cpg-event-22999-23629-19-header
/dev/shm/qb-cpg-event-22999-23629-19-data
After these, it tries to connect to @"corosync.ipc" but gets
ECONNREFUSED and then exits with the following message:
Cannot initialise Corosync quorum service: 6
Can't initialise cluster interface
The corresponding corosync debug logs:
[QB ] IPC credentials authenticated (22999-23629-19)
[QB ] connecting to client [23629]
[QB ] shm size:1048576; real_size:1048576; rb->word_size:262144
[QB ] shm size:1048576; real_size:1048576; rb->word_size:262144
[QB ] shm size:1048576; real_size:1048576; rb->word_size:262144
[MAIN ] connection created
[CPG ] lib_init_fn: conn=0x7f4e8000cb50, cpd=0x7f4e8000eb24
[QB ] HUP conn (22999-23629-19)
[QB ] qb_ipcs_disconnect(22999-23629-19) state:2
[QB ] epoll_ctl(del): Bad file descriptor (9)
[MAIN ] cs_ipcs_connection_closed()
[CPG ] exit_fn for conn=0x7f4e8000cb50
[MAIN ] cs_ipcs_connection_destroyed()
[QB ] Free'ing ringbuffer: /dev/shm/qb-cpg-response-22999-23629-19-header
[QB ] Free'ing ringbuffer: /dev/shm/qb-cpg-event-22999-23629-19-header
[QB ] Free'ing ringbuffer: /dev/shm/qb-cpg-request-22999-23629-19-header
and corosync-quorumtool reports:
Quorum information
------------------
Date: Mon Apr 22 16:16:40 2013
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 16777343
Ring ID: 8
Quorate: Yes
Votequorum information
----------------------
Expected votes: 1
Highest expected: 1
Total votes: 1
Quorum: 1
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
16777343 1 localhost (local)
What am I missing here? Why clvmd does not like corosync? Would the
cman interface be any better? "Whither cman" suggests it's being phased
out... So what's the contemporary way to set up a cluster with clvm and
pacemaker?
--
Thanks,
Feri.
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
