search for: ctdb1

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]:...

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

...FILE=1048576 PIDFile=/usr/local/samba/var/run/ctdb/ctdbd.pid ExecStart=/usr/local/samba/sbin/ctdbd_wrapper start ExecStop=/usr/local/samba/sbin/ctdbd_wrapper stop KillMode=control-group Restart=no [Install] WantedBy=multi-user.target ---- The errors has gone, but still throwing: Mar? 3 10:31:52 ctdb1 systemd[1]: Starting CTDB... Mar? 3 10:31:52 ctdb1 ctdbd[1375]: CTDB starting on node Mar? 3 10:31:52 ctdb1 ctdbd[1385]: Starting CTDBD (Version 4.11.6) as PID: 1385 Mar? 3 10:31:52 ctdb1 ctdbd[1385]: Created PID file /usr/local/samba/var/run/ctdb/ctdbd.pid Mar? 3 10:31:52 ctdb1 ctdbd[1385]: Remo...

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 >> /usr/local/samba/var/run/ctdb/ct...

...ExecStart=/usr/local/samba/sbin/ctdbd_wrapper start > ExecStop=/usr/local/samba/sbin/ctdbd_wrapper stop > KillMode=control-group > Restart=no > > [Install] > WantedBy=multi-user.target > > ---- > > The errors has gone, but still throwing: > > Mar? 3 10:31:52 ctdb1 systemd[1]: Starting CTDB... > Mar? 3 10:31:52 ctdb1 ctdbd[1375]: CTDB starting on node > Mar? 3 10:31:52 ctdb1 ctdbd[1385]: Starting CTDBD (Version 4.11.6) as > PID: 1385 > Mar? 3 10:31:52 ctdb1 ctdbd[1385]: Created PID file > /usr/local/samba/var/run/ctdb/ctdbd.pid > Mar? 3 10...

...ts.samba.org] Namens > Ralph Boehme via samba > Verzonden: dinsdag 3 maart 2020 10:13 > Aan: Micha Ballmann; Anoop C S > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] start/stop ctdb > > 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 > > /usr/local/samba/var/...

hi everybody, when using enable privileges = yes in smb.conf where does the permission get saved? I assume in the passdb backend or is there a tdb server specific file in /var/lib/samba? cause when i give a group the permission: net rpc -S pa-server1 rights grant 'NET\domadmin' SePrintOperatorPrivilege Enter root's password: Successfully granted rights. but when listing the

...9.52   OK (THIS NODE) pnn:1 192.168.199.53   OK pnn:2 192.168.199.49   OK Generation:1484961991 Size:3 hash:0 lmaster:0 hash:1 lmaster:1 hash:2 lmaster:2 Recovery mode:NORMAL (0) Recovery master:0 Now i have the problem that "testparm" outputs, for me not readable informations: root at ctdb1:~/ctdb# testparm Load smb config files from /usr/local/samba/etc/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) smb_panic_default: PANIC (pid 2490): messaging not initialized BACKTRACE: 28 stack frames:  #0 /usr/local/samba/lib/libsamba-util.so.0(log_stack_trac...

Dear all, I succeded in setting up a two node gluster-share (Replication) for samba. ?[root at ctdb1 test]# gluster peer status Number of Peers: 1 Hostname: 192.168.132.57 Uuid: 87159003-b9ec-4eba-9761-74178d406609 State: Peer in Cluster (Connected)? ?[root at ctdb1 test]# gluster volume info Volume Name: samba-vol Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks:...

...d2 brd ff:ff:ff:ff:ff:ff ??? inet 10.0.103.13/24 brd 10.0.103.255 scope global ens10 ??? inet6 fe80::5054:ff:fe43:10d2/64 scope link ----------- ?????? Checking file: /etc/hosts 127.0.0.1??? localhost 192.168.20.22??? addc-new.example.com??? addc-new #list of heartbeat network hosts # 10.0.103.11 ctdb1.heartbeat.example??? ctdb1 10.0.103.21 ctdb2.heartbeat.example??? ctdb2 10.0.103.13 ad1.heartbeat.example ad1 10.0.103.42 jumpi.heartbeat.example jumpi 10.0.103.12 gluster1.heartbeat.example gluster1 10.0.103.22 gluster2.heartbeat.example gluster2 10.0.103.23 ad2.heartbeat.example ad2 # The follow...

.../samba/sbin/smbd /usr/local/samba/sbin/nmbd /usr/local/samba/sbin/winbindd exit 0 ### Thy for your help! Best regards Micha Am 28.06.2018 um 11:05 schrieb Ralph Böhme via samba: > Hi Micha, > > On Thu, Jun 28, 2018 at 10:30:07AM +0200, Micha Ballmann via samba wrote: >> root at ctdb1:~/ctdb# testparm >> Load smb config files from /usr/local/samba/etc/smb.conf >> rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) >> smb_panic_default: PANIC (pid 2490): messaging not initialized >> >> BACKTRACE: 28 stack frames: >> ... &g...

...rd 10.0.103.255 scope global ens10 > ??? inet6 fe80::5054:ff:fe43:10d2/64 scope link > > ----------- > ?????? Checking file: /etc/hosts > > 127.0.0.1??? localhost > 192.168.20.22??? addc-new.example.com??? addc-new > #list of heartbeat network hosts > # > 10.0.103.11 ctdb1.heartbeat.example??? ctdb1 > 10.0.103.21 ctdb2.heartbeat.example??? ctdb2 > 10.0.103.13 ad1.heartbeat.example ad1 > 10.0.103.42 jumpi.heartbeat.example jumpi > 10.0.103.12 gluster1.heartbeat.example gluster1 > 10.0.103.22 gluster2.heartbeat.example gluster2 > 10.0.103.23 ad2.heart...

...8.199.49   OK > Generation:1484961991 > Size:3 > hash:0 lmaster:0 > hash:1 lmaster:1 > hash:2 lmaster:2 > Recovery mode:NORMAL (0) > Recovery master:0 > > Now i have the problem that "testparm" outputs, for me not readable > informations: > > root at ctdb1:~/ctdb# testparm > Load smb config files from /usr/local/samba/etc/smb.conf > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit > (16384) smb_panic_default: PANIC (pid 2490): messaging not initialized > > BACKTRACE: 28 stack frames: >  #0 /usr/local/samba/lib/lib...

Hello, We are setting up 2 AD machines: New machine with subnet 192.168.1.21: Version 4.10.11-SerNet-Debian-10.buster Bind version 9.11.5 Existing machine 1 with subnet 192.168.2.21 Version 4.10.11-SerNet-Debian-10.stretch Bind version 9.10.3 Existing machine 2 with subnet 192.168.3.21? Version 4.10.11-SerNet-Debian-10.stretch Bind version 9.10.3 All with BIND_DLZ backend, same

...>> Size:3 >> hash:0 lmaster:0 >> hash:1 lmaster:1 >> hash:2 lmaster:2 >> Recovery mode:NORMAL (0) >> Recovery master:0 >> >> Now i have the problem that "testparm" outputs, for me not readable >> informations: >> >> root at ctdb1:~/ctdb# testparm >> Load smb config files from /usr/local/samba/etc/smb.conf >> rlimit_max: increasing rlimit_max (1024) to minimum Windows limit >> (16384) smb_panic_default: PANIC (pid 2490): messaging not initialized >> >> BACKTRACE: 28 stack frames: >>  #0...

Hi to all! I've set up Zimbra LDAP (2.4) as master, and I want to use RHEL v5 LDAP (2.3) as a slave. This is relevant part of my slapd.conf on LDAP 2.3: # syncrepl directives syncrepl rid=101 provider=ldap://192.168.1.86 bindmethod=simple binddn="uid=zimbra,cn=admins,cn=zimbra" credentials=PASSword searchbase="dc=company,dc=com" schemachecking=on

Dear all, I have set up a two node workin gluster with glusterfs3.1 and Samba-Sernet 3.5. Everything is working great except MSOffice files (Word/Excell). On the gluster-vol they have the strange behavior That they rest read only, write protected. Every other type of files can be manged without problem, openoffice files too. So when I save a word file on the vol and try to change it it is write