similar to: Does CTDB run under LXC containers?

I'm using libvirt_lxc and that has an XML based configuration. Based on what I've read, I think I need to add this to the ctdb container's config: <features> <capabilities policy='default'> <sys_nice state='on'/> </capabilities> </features> That didn't do the trick though. I need to figure out how to turn on all caps to

On 2015-08-04 at 19:27 +0200, Ralph Böhme wrote: > Hi Peter, > > On Tue, Aug 04, 2015 at 10:11:56AM -0700, Peter Steele wrote: > > We're transitioning from a VM based environment to one that uses LXC based > > containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. > > The same packages running under LXC however seem to have issues: > > >

I'm using libvirt_lxc to create and manage various containers. I need to enable certain capabilities in a container to support ctdb, and as a quick solution I decided to just enable them all. I *thought* this would do the trick, adding the following XML to my container config: <features> <capabilities policy='allow'> </capabilities> </features> After

Hi Peter, On Tue, Aug 04, 2015 at 10:11:56AM -0700, Peter Steele wrote: > We're transitioning from a VM based environment to one that uses LXC based > containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. > The same packages running under LXC however seem to have issues: > > # systemctl start ctdb.service > Job for ctdb.service failed. See 'systemctl

Hi, i updated the variables for my scenario. But CTDB wont start: Mar? 3 09:50:50 ctdb1 systemd[1]: Starting CTDB... Mar? 3 09:50:50 ctdb1 ctdbd[24663]: CTDB starting on node Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Starting CTDBD (Version 4.11.6) as PID: 24667 Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Created PID file /usr/local/samba/var/run/ctdb/ctdbd.pid Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Removed

Hello, i'm still trying to find out what is the right path for ctdb.conf (ubuntu 18.04, samba was compiled from source!!). When im trying to start CTDB without any config file, my log in /usr/local/samba/var/log/log.ctdb shows me: 2018/05/07 12:56:44.363513 ctdbd[4503]: Failed to read nodes file "/usr/local/samba/etc/ctdb/nodes" 2018/05/07 12:56:44.363546 ctdbd[4503]: Failed to

Hi Marin - again thank you for the help. I can't believe I coundn't find any info about this big configuration change. Even the Samba WIKI doesn't really spell this out at all in instructs you to use ctdbd.conf. Do I need to enable the 20.nfs_ganesha.check script file at all, or will the config itself take care of that? Also, are there any recommendations on which nfs-checks.d

Hi Max, On Wed, 2 Oct 2019 15:08:43 +0000, Max DiOrio <Max.DiOrio at ieeeglobalspec.com> wrote: > As soon as I made the configuration change and restarted CTDB, it crashes. > > Oct 2 11:05:14 hq-6pgluster01 systemd: Started CTDB. > Oct 2 11:05:21 hq-6pgluster01 systemd: ctdb.service: main process exited, code=exited, status=1/FAILURE > Oct 2 11:05:21 hq-6pgluster01

Hi, i configured a running three node CTDB SAMBA cluster (hope so). Virtual ip's are floating between the nodes after faling one of them. Im using SAMBA 4.11.6 on Ubuntu 18.04. Samba was compiled from source. I configured some systemD start/stop scripts for samba (smbd, nmbd) and winbind, also disabled them for manage via ctdb. I enabled ctdb to mange samba and winbind via this

Hi there ? I seem to be having trouble wrapping my brain about the CTDB and ganesha configuration. I thought I had it figured out, but it doesn?t seem to be doing any checking of the nfs-ganesha service. I put nfs-ganesha-callout as executable in /etc/ctdb I create nfs-checks-ganesha.d folder in /etc/ctdb and in there I have 20.nfs_ganesha.check In my ctdbd.conf file I have: # Options to

# tdbtool /usr/local/samba/var/lib/ctdb/persistent/account_policy.tdb.0 check Database integrity is OK and has 18 records. Guess no? Am 03.03.2020 um 10:42 schrieb Ralph Boehme: > tdbtool /usr/local/samba/var/lib/ctdb/persistent/account_policy.tdb.0 check

Hi List, I set up a ctdb cluster a couple months back. Things seemed pretty solid for the first 2-3 weeks, but then I started getting reports of people not being able to access files, or some times directories. It has taken me a while to figure some stuff out, but it seems the common denominator to this happening is vacuuming timeouts for locking.tdb in the ctdb log, which might go on

Hi again, First, i revert to a snapashot with samba 4.7.7 and upgraded it to 4.7.8. I got no issue with my settings and "testparm" outputs as expected. Next i tried again upgrade to samba 4.8.3. But i got the same error like an email before. Yes i guess its a problem that "tesparm" cant read the registry. When im removing "include = registry" and add my global

------------------原始邮件------------------ 发件人：朱尚忠10137461 收件人：samba@lists.samba.org <samba@lists.samba.org> 日 期 ：2018年02月26日 17:10 主 题 ：[ctdb] Unable to take recovery lock - contention When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The

When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The following the ctdb logs: 2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting on node 2018/02/12 19:38:51.528921 ctdbd[6602]: Starting CTDBD (Version 4.6.10) as PID: 6602 2018/02/12 19:38:51.529060

On 03/03/2020 09:13, Ralph Boehme via samba wrote: > Am 3/3/20 um 10:05 AM schrieb Micha Ballmann via samba: >> Mar? 3 09:50:50 ctdb1 systemd[1]: Starting CTDB... >> Mar? 3 09:50:50 ctdb1 ctdbd[24663]: CTDB starting on node >> Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Starting CTDBD (Version 4.11.6) as >> PID: 24667 >> Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Created PID file

Ubuntu 14.04, ctdb 2.5.3, samba 4.1.11. CTDB is working with IP takeover between the 2 nodes. The machine is joined to the domain. Any help with the following errors would be most gratefully received. 1. connect to socket error: ctdb status 2014/08/16 15:32:03.248034 [23255]: client/ctdb_client.c:267 Failed to connect client socket to daemon. Errno:Connection refused(111) common/cmdline.c:156

On 03/11/16 13:12, Ralph Böhme wrote: > >> Hi there, >> >> Can you send your smb.conf so I can compare it to mine? > sure. It's a virtual cluster in LXC containers with 3 nodes, > filesystem is a bind mount with ext4. > > # cat /var/lib/lxc/ctdb-node0/rootfs/opt/samba/etc/smb.conf > [global] > clustering = yes > ctdbd socket =

Thanks, i added "Environment=PATH=$PATH:/usr/local/samba/bin:/bin". Needed also to add "/bin" because couldnt find "sleep". Thats the script now: ---- [Unit] Description=CTDB Documentation=man:ctdbd(1) man:ctdb(7) After=network-online.target time-sync.target ConditionFileNotEmpty=/usr/local/samba/etc/ctdb/nodes [Service]

There is a 3 nodes ctdb cluster is running. When one of 3 nodes is powered down, lots of logs will be wrote to log.ctdb. node1: repeat logs: 2018/09/04 04:35:06.414369 ctdbd[10129]: Recovery has started 2018/09/04 04:35:06.414944 ctdbd[10129]: connect() failed, errno=111 2018/09/04 04:35:06.415076 ctdbd[10129]: Unable to run startrecovery event node2: repeat logs: 2018/09/04 04:35:09.412368