thr3ads.net - samba - [Samba] ctdb + gluster9 = not working [Dec 2024]

If this information is useful, please help other people find it:
Share via:

Anton Shevtsov

2024-Dec-27 15:04 UTC

[Samba] ctdb + gluster9 = not working

Hi, i tried make a samba cluster (ctdb) with gluster9 (do not use vfs 
module)

But i get an errors.

[root at samba1 ctdb]# rpm -q samba samba-ctdb
samba-4.19.9-alt3.x86_64
samba-ctdb-4.19.9-alt3.x86_64

[root at samba1 ctdb]# grep -v '^#' /etc/ctdb/ctdb.conf
[cluster]
recovery lock = "/mnt/gluster/ctdb/.ctdb.lock"

[root at samba1 ctdb]# cat /etc/ctdb/public_addresses
192.168.160.180/0 ens19

[root at samba1 ctdb]# cat /etc/ctdb/nodes
192.168.160.151
192.168.160.152

[root at samba1 ctdb]# ifconfig ens19
ens19 ????Link encap:Ethernet ?HWaddr 52:E5:CB:32:76:73
 ?????????inet addr:192.168.160.151 ?Bcast:192.168.160.255 
 ?Mask:255.255.255.0
 ?????????inet6 addr: fe80::50e5:cbff:fe32:7673/64 Scope:Link
 ?????????UP BROADCAST RUNNING MULTICAST ?MTU:1500 ?Metric:1
 ?????????RX packets:175969 errors:0 dropped:0 overruns:0 frame:0
 ?????????TX packets:89201 errors:0 dropped:0 overruns:0 carrier:0
 ?????????collisions:0 txqueuelen:1000
 ?????????RX bytes:76548041 (73.0 MiB) ?TX bytes:6903963 (6.5 MiB)

[root at samba1 ctdb]# grep -A 1 cluster /etc/samba/smb.conf
# clusterstart
clustering = yes
include = registry
[root at samba1 ctdb]# mount | grep '/mnt/gluster'
gluster1:/gfs-volume on /mnt/glustertype fuse.glusterfs 
(rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)

[root at samba1 ctdb]# ll /mnt/gluster/
????? 12
drwxrwxrwx 2 root root 4096 ??? 27 15:43 ctdb/
drwxr-xr-x 5 root root 4096 ??? 27 11:55 ./
drwxr-xr-x 4 root root 4096 ??? 27 11:13 ../

[root at samba1 ctdb]# ll /mnt/gluster/ctdb/
????? 8
drwxrwxrwx 2 root root 4096 ??? 27 15:43 ./
drwxr-xr-x 5 root root 4096 ??? 27 11:55 ../


[root at samba1 ctdb]# systemctl start ctdb
[root at samba1 ctdb]# systemctl status ctdb
?ctdb.service - CTDB
 ????Loaded: loaded (/lib/systemd/system/ctdb.service; enabled; vendor 
preset: disabled)
 ????Active: active (running)since Fri 2024-12-27 19:46:54 +05; 4s ago
 ??????Docs: man:ctdbd(1)
man:ctdb(7)
 ???Process: 25430 ExecStart=/usr/sbin/ctdbd (code=exited, 
status=0/SUCCESS)
 ??Main PID: 25431 (ctdbd)
 ?????Tasks: 9 (limit: 4096)
 ????Memory: 11.2M
 ???????CPU: 147ms
 ????CGroup: /system.slice/ctdb.service
 ?????????????? 25431 /usr/sbin/ctdbd
 ?????????????? 25432 /usr/lib/ctdb/ctdb-eventd -P 25431 -S 14
 ?????????????? 25436 /usr/lib/ctdb/ctdb_lock_helper 25431 24 DB 
/var/lib/ctdb/persistent/secrets.tdb.0 0x400
 ?????????????? 25437 /usr/lib/ctdb/ctdb_lock_helper 25431 25 DB 
/var/lib/ctdb/persistent/passdb.tdb.0 0x400
 ?????????????? 25438 /usr/lib/ctdb/ctdb_lock_helper 25431 26 DB 
/var/lib/ctdb/persistent/account_policy.tdb.0 0x400
 ?????????????? 25439 /usr/lib/ctdb/ctdb_lock_helper 25431 27 DB 
/var/lib/ctdb/persistent/group_mapping.tdb.0 0x400
 ?????????????? 25440 /usr/lib/ctdb/ctdb_lock_helper 25431 28 DB 
/var/lib/ctdb/persistent/share_info.tdb.0 0x400
 ?????????????? 25441 /usr/lib/ctdb/ctdb_lock_helper 25431 29 DB 
/var/lib/ctdb/persistent/registry.tdb.0 0x400
 ?????????????? 25443 /usr/sbin/ctdbd

??? 27 19:46:54 samba1 systemd[1]: Starting CTDB...
??? 27 19:46:54 samba1 ctdbd[25430]: CTDB logging to location 
file:/var/log/log.ctdb
??? 27 19:46:54 samba1 systemd[1]: Started CTDB.

[root at samba1 ctdb]# tail -f /var/log/log.ctdb
2024-12-27T19:47:15.589971+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:16.590418+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:17.590589+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:18.591106+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:19.592017+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:19.594252+05:00 samba1 ctdb-recoverd[25443]: Leader 
broadcast timeout
2024-12-27T19:47:19.594308+05:00 samba1 ctdb-recoverd[25443]: Start 
election
2024-12-27T19:47:19.595217+05:00 samba1 ctdb-recoverd[25443]: Attempting 
to take cluster lock ("/mnt/gluster/ctdb/.ctdb.lock")
2024-12-27T19:47:19.609195+05:00 samba1 ctdbd[25431]: 
ctdb_mutex_fcntl_helper: Unable to open "/mnt/gluster/ctdb/.ctdb.lock"
-
(No such file or directory)
2024-12-27T19:47:19.609458+05:00 samba1 ctdb-recoverd[25443]: Unable to 
take cluster lock - unknown error
2024-12-27T19:47:20.592340+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:21.592817+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:22.593165+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:23.593353+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:24.593899+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:24.597347+05:00 samba1 ctdb-recoverd[25443]: Leader 
broadcast timeout
2024-12-27T19:47:24.597406+05:00 samba1 ctdb-recoverd[25443]: Start 
election
2024-12-27T19:47:24.598139+05:00 samba1 ctdb-recoverd[25443]: Attempting 
to take cluster lock ("/mnt/gluster/ctdb/.ctdb.lock")
2024-12-27T19:47:24.611930+05:00 samba1 ctdbd[25431]: 
ctdb_mutex_fcntl_helper: Unable to open "/mnt/gluster/ctdb/.ctdb.lock"
-
(No such file or directory)
2024-12-27T19:47:24.612311+05:00 samba1 ctdb-recoverd[25443]: Unable to 
take cluster lock - unknown error
2024-12-27T19:47:25.594971+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:26.595420+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED
2024-12-27T19:47:27.596496+05:00 samba1 ctdbd[25431]: 
CTDB_WAIT_UNTIL_RECOVERED

Why?

-- 
*Anton*

Martin Schwenke

2024-Dec-28 23:25 UTC

head link

[Samba] ctdb + gluster9 = not working

Hi Anton,

On Fri, 27 Dec 2024 20:04:07 +0500, Anton Shevtsov via samba
<samba at lists.samba.org> wrote:
> Hi, i tried make a samba cluster (ctdb) with gluster9 (do not use vfs 
> module)
> 
> But i get an errors.
> 
> [root at samba1 ctdb]# rpm -q samba samba-ctdb
> samba-4.19.9-alt3.x86_64
> samba-ctdb-4.19.9-alt3.x86_64
> 
> [root at samba1 ctdb]# grep -v '^#' /etc/ctdb/ctdb.conf
> [cluster]
> recovery lock = "/mnt/gluster/ctdb/.ctdb.lock"
[...]
> ??? 27 19:46:54 samba1 systemd[1]: Starting CTDB...
> ??? 27 19:46:54 samba1 ctdbd[25430]: CTDB logging to location 
> file:/var/log/log.ctdb
> ??? 27 19:46:54 samba1 systemd[1]: Started CTDB.
> 
> [root at samba1 ctdb]# tail -f /var/log/log.ctdb
> [...]
> 2024-12-27T19:47:24.597406+05:00 samba1 ctdb-recoverd[25443]: Start
election
> 2024-12-27T19:47:24.598139+05:00 samba1 ctdb-recoverd[25443]: Attempting to
take cluster lock ("/mnt/gluster/ctdb/.ctdb.lock")
> 2024-12-27T19:47:24.611930+05:00 samba1 ctdbd[25431]:
ctdb_mutex_fcntl_helper: Unable to open "/mnt/gluster/ctdb/.ctdb.lock"
- (No such file or directory)
> 2024-12-27T19:47:24.612311+05:00 samba1 ctdb-recoverd[25443]: Unable to
take cluster lock - unknown error
> [...]
> Why?
Good question!  This took me a few guesses... because it certainly isn't
obvious! :-)

You don't need the double-quotes around the recovery lock setting.
They are not inserted by the log messages, so must be maintained from
ctdb.conf and not stripped.  Samba (and CTDB) log files can handle
values containing whitespace, so quoting isn't required.

If your Linux distribution included the quotes in the sample
configuration file then you should report a bug because the example is
misleading.  If not, you're just unlucky because you did something sane
but it didn't work.

peace & happiness,
martin

Seemingly Similar Threads

Search for more apparently analagous threads

samba - Dec 2024 - ctdb + gluster9 = not working

[Samba] ctdb + gluster9 = not working

[Samba] ctdb + gluster9 = not working

Seemingly Similar Threads