Displaying 8 results from an estimated 8 matches for "ctdb_lock_helper".
2017 Apr 19
6
CTDB problems
...2017/04/19 12:10:31.168891 [ 5417]: Vacuuming child process timed out
for db brlock.tdb
2017/04/19 12:11:39.250169 [ 5417]: Unable to get RECORD lock on
database brlock.tdb for 500 seconds
===== Start of debug locks PID=9372 =====
8084 /usr/sbin/smbd brlock.tdb.2 7044 7044
20931 /usr/libexec/ctdb/ctdb_lock_helper brlock.tdb.2 7044 7044 W
21665 /usr/sbin/smbd brlock.tdb.2 174200 174200
----- Stack trace for PID=21665 -----
2017/04/19 12:11:39.571097 [ 5417]: /etc/ctdb/debug_locks.sh: line 73:
gstack: command not found
----- Stack trace for PID=8084 -----
2017/04/19 12:11:39.571346 [ 5417]: /etc/ctdb/debug_l...
2018 Feb 26
2
答复: [ctdb] Unable to take recovery lock - contention
...322 ctdbd[6602]: Ignoring persistent database 'ctdb.tdb.2'
2018/02/12 19:38:54.576339 ctdbd[6602]: Ignoring persistent database 'ctdb.tdb.0'
2018/02/12 19:38:54.576364 ctdbd[6602]: Freeze db: ctdb.tdb
2018/02/12 19:38:54.576393 ctdbd[6602]: Set lock helper to "/usr/libexec/ctdb/ctdb_lock_helper"
2018/02/12 19:38:54.579527 ctdbd[6602]: Set runstate to SETUP (2)
2018/02/12 19:38:54.881828 ctdbd[6602]: Keepalive monitoring has been started
2018/02/12 19:38:54.881873 ctdbd[6602]: Set runstate to FIRST_RECOVERY (3)
2018/02/12 19:38:54.882020 ctdb-recoverd[7182]: monitor_cluster starting
2...
2017 Apr 20
0
CTDB problems
...e messages come from deep in TDB.
Could the filesystem be full?
> [...]
> Here are some logs from earlier, where we think we had a stuck smbd task:
>
> 28657 /usr/sbin/smbd locking.tdb.2 9848 9848 W
> 28687 /usr/sbin/smbd locking.tdb.2 186860 186860 W
> 18214 /usr/libexec/ctdb/ctdb_lock_helper locking.tdb.2 216548 216550 W
> 30945 /usr/sbin/smbd brlock.tdb.2.20170419.102626.697770650.corrupt
> [...]
> ----- Stack trace for PID=30945 -----
> ----- Process in D state, printing kernel stack only
> [<ffffffffa05b253d>] __fuse_request_send+0x13d/0x2c0 [fuse]
> [<...
2018 Feb 26
2
[ctdb] Unable to take recovery lock - contention
...322 ctdbd[6602]: Ignoring persistent database 'ctdb.tdb.2'
2018/02/12 19:38:54.576339 ctdbd[6602]: Ignoring persistent database 'ctdb.tdb.0'
2018/02/12 19:38:54.576364 ctdbd[6602]: Freeze db: ctdb.tdb
2018/02/12 19:38:54.576393 ctdbd[6602]: Set lock helper to "/usr/libexec/ctdb/ctdb_lock_helper"
2018/02/12 19:38:54.579527 ctdbd[6602]: Set runstate to SETUP (2)
2018/02/12 19:38:54.881828 ctdbd[6602]: Keepalive monitoring has been started
2018/02/12 19:38:54.881873 ctdbd[6602]: Set runstate to FIRST_RECOVERY (3)
2018/02/12 19:38:54.882020 ctdb-recoverd[7182]: monitor_cluster starting
2...
2018 Feb 26
0
答复: [ctdb] Unable to take recovery lock - contention
...322 ctdbd[6602]: Ignoring persistent database 'ctdb.tdb.2'
2018/02/12 19:38:54.576339 ctdbd[6602]: Ignoring persistent database 'ctdb.tdb.0'
2018/02/12 19:38:54.576364 ctdbd[6602]: Freeze db: ctdb.tdb
2018/02/12 19:38:54.576393 ctdbd[6602]: Set lock helper to "/usr/libexec/ctdb/ctdb_lock_helper"
2018/02/12 19:38:54.579527 ctdbd[6602]: Set runstate to SETUP (2)
2018/02/12 19:38:54.881828 ctdbd[6602]: Keepalive monitoring has been started
2018/02/12 19:38:54.881873 ctdbd[6602]: Set runstate to FIRST_RECOVERY (3)
2018/02/12 19:38:54.882020 ctdb-recoverd[7182]: monitor_cluster starting
2...
2018 Feb 26
0
[ctdb] Unable to take recovery lock - contention
...322 ctdbd[6602]: Ignoring persistent database 'ctdb.tdb.2'
2018/02/12 19:38:54.576339 ctdbd[6602]: Ignoring persistent database 'ctdb.tdb.0'
2018/02/12 19:38:54.576364 ctdbd[6602]: Freeze db: ctdb.tdb
2018/02/12 19:38:54.576393 ctdbd[6602]: Set lock helper to "/usr/libexec/ctdb/ctdb_lock_helper"
2018/02/12 19:38:54.579527 ctdbd[6602]: Set runstate to SETUP (2)
2018/02/12 19:38:54.881828 ctdbd[6602]: Keepalive monitoring has been started
2018/02/12 19:38:54.881873 ctdbd[6602]: Set runstate to FIRST_RECOVERY (3)
2018/02/12 19:38:54.882020 ctdb-recoverd[7182]: monitor_cluster starting
2...
2018 May 04
2
CTDB Path
Hello,
at this time i want to install a CTDB Cluster with SAMBA 4.7.7 from SOURCE!
I compiled samba as follow:
|./configure| |--with-cluster-support
||--with-shared-modules=idmap_rid,idmap_tdb2,idmap_ad|
The whole SAMBA enviroment is located in /usr/local/samba/.
CTDB is located in /usr/local/samba/etc/ctdb.
I guess right that the correct path of ctdbd.conf (node file, public
address file
2018 May 07
2
CTDB Path
...db
2018/05/07 15:31:40.979126 ctdbd[2093]: Attached to database
'/usr/local/samba/var/lib/ctdb/persistent/ctdb.tdb.1' with flags 0x400
2018/05/07 15:31:40.979225 ctdbd[2093]: Freeze db: ctdb.tdb
2018/05/07 15:31:40.979306 ctdbd[2093]: Set lock helper to
"/usr/local/samba/libexec/ctdb/ctdb_lock_helper"
2018/05/07 15:31:40.992886 ctdbd[2093]: Set runstate to SETUP (2)
2018/05/07 15:31:41.098136 ctdbd[2093]: Keepalive monitoring has been
started
2018/05/07 15:31:41.098283 ctdbd[2093]: Set runstate to FIRST_RECOVERY (3)
2018/05/07 15:31:41.098653 ctdb-recoverd[2160]: monitor_cluster starting...