Problems with CTDB and GlusterFS

Sebastian Stellingwerff sebastian at otherstuff.nl
Mon Jun 20 14:41:02 UTC 2016


On 20/06/16 16:23, Amitay Isaacs wrote:
> Hi,
> 
> On Mon, Jun 20, 2016 at 11:41 PM, Sebastian Stellingwerff
> <sebastian at otherstuff.nl <mailto:sebastian at otherstuff.nl>> wrote:
> 
>     Hi,
> 
>     I'm setting up a Samba+CTDB+GlusterFS setup. GlusterFS seems to work
>     fine and we have it in use in production for some time without problems
>     it seems. However when setting up CTDB with this, one node just keeps
>     complaining about:
> 
>     2016/06/20 13:32:29.606345 [recoverd: 7079]: Taking out recovery lock
>     from recovery daemon
>     2016/06/20 13:32:29.606360 [recoverd: 7079]: Take the recovery lock
>     2016/06/20 13:32:29.607962 [recoverd: 7079]: ctdb_recovery_lock: Failed
>     to get recovery lock on '/mnt/gv0/ctdblock'
>     2016/06/20 13:32:29.608002 [recoverd: 7079]: Unable to get recovery lock
>     - retrying recovery
> 
>     It seems to be the node that's started last. I've searched around the
>     internet, but no luck. An old thread suggested enabling direct-io, but
>     this is the default these days and giving it as an explicit option
>     doesn't solve the problem.
> 
>     I've also tested locking with ping_pong which does not give me any
>     trouble, al results are as expected.
> 
>     Anyone here who can help me debug this?
> 
>     Thanks!
> 
>     --
>     Sebastian Stellingwerff
>     06-49136664
> 
> 
> From the log messages it appears you are either running ctdb 4.2.x or
> 2.5.x.  The code around recovery lock has changed quite a bit in the
> recent releases.  I would recommend testing with the latest stable
> release of ctdb 4.4.x.

I'm using 2:4.2.10+dfsg-0+deb8u and stuck with that version.

Gladly however I discovered the problem: The local firewalls where
prohibiting ctdb connections between the two devices.

Thanks!




-- 
Sebastian Stellingwerff
06-49136664
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x68C29FC1.asc
Type: application/pgp-keys
Size: 1722 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160620/a751c3e5/0x68C29FC1.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160620/a751c3e5/signature.sig>


More information about the samba-technical mailing list