similar to: Dynamic updates of windows clients

Hallo Rowland I change the right from 600 (root:root) to 660 (root:bind) and i get following errormessage. 02-Apr-2017 14:56:15.190 client 192.168.99.6#54534 (client006.my.domain.de): query: client006.my.domain.de IN SOA + (192.168.99.8) 02-Apr-2017 14:56:15.194 client 192.168.99.6#64810 (client008.my.domain.de): query: client008.my.domain.de IN A + (192.168.99.8) 02-Apr-2017 14:56:15.199

Hallo Marc I change the loglevel to 10 database "dlopen /usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_9.so -d 10"; and i get following errors: 02-Apr-2017 18:47:44.389 samba_dlz: ldb: ldb_asprintf/set_errstring: No such Base DN: DC=client008.my.domain.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=my,DC=domain,DC=de 02-Apr-2017 18:47:44.389 samba_dlz: ldb: ldb_trace_response: DONE

Hallo Rowland If this parameter not for the internal dns? Ok. I changed the parameter. The same problem. The test with the internal dns. It looks good. service sernet-samba-ad stop service bind9 stop change server services = -dns to # server services = -dns samba_upgradedns --dns-backend=SAMBA_INTERNAL service sernet-samba-ad start netstat -tulpen | grep 53 (dns in running) I think i

On Sun, 2 Apr 2017 19:02:35 +0200 Karl Heinz Wichmann via samba <samba at lists.samba.org> wrote: > Hallo Marc > > I change the loglevel to 10 > > > database > "dlopen /usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_9.so -d 10"; > > and i get following errors: > > 02-Apr-2017 18:47:44.389 samba_dlz: ldb: ldb_asprintf/set_errstring: > No

Hello Rowland Yes i have a timeserver and time in correct and in sync with the client und server. named.conf ---------- include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include "/etc/bind/named.conf.default-zones"; # samba include "/etc/bind/named.conf.samba"; // logging logging { channel default_file { file

Hi Karl Im running for years with samba now with bind_dlz and on stock debian samba and bind runs fine. I went through your mails on the list and i noticed the following. > client006\$\@MY.DOMAIN.DE: updating zone 'MY.DOMAIN.DE/NONE': update > failed: rejected by secure update (REFUSED) > samba_dlz: disallowing update of signer=client006\$\@MY.DOMAIN.DE >

Hello Marc I changed the rights back to 600 and root:root to sam.ldb and i think the rights of sam.ldb.d directory are correct. -rw------- 1 root root 16M Apr 2 17:29 CN=CONFIGURATION,DC=MY,DC=DOMAIN,DC=DE.ldb -rw------- 1 root root 10M Apr 2 17:29 CN=SCHEMA,CN=CONFIGURATION,DC=MY,DC=DOMAIN,DC=DE.ldb -rw-rw---- 2 root bind 26M Apr 2 17:28 DC=DOMAINDNSZONES,DC=MY,DC=DOMAIN,DC=DE.ldb

> On 8 Nov 2017, at 9:03 pm, Nithya Balachandran <nbalacha at redhat.com> wrote: > > > That is not the log for the mount. Please check /var/log/glusterfs/var-lib-mountedgluster.log on the system on which you are running the mount process. > > Please provide the volume config details as well (gluster volume info) from one of the server nodes. > Oh I'm sorry, I

> Clarification for below logs: > > - 'dev_static' is the gluster volume. > - 'int-kube-01' is the gluster client. > - '10.51.70.151' is the first node in a three node (2 replica, 1 arbiter) gluster cluster. > - '/var/lib/kubelet/...../iss3dev-static' is a directory on the client that should be mounting

?Thanks .. Its the same option. Can you let me know your glusterfs client package version ?? On Thu, Aug 10, 2017 at 8:34 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > > short copy from a kubectl describe pod... > > Events: > FirstSeen LastSeen Count From SubObjectPath Type Reason Message > --------- -------- ----- ---- ------------- -------- ------

short copy from a kubectl describe pod... Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 5h 54s 173 kubelet, k8s-bootcamp-rbac-np-worker-6263f70 Warning FailedMount (combined from similar events): MountVolume.SetUp failed for volume "pvc-fa4b2621-7dad-11e7-8a44-062df200059f" : glusterfs:

On Thu, Aug 10, 2017 at 10:25 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > Just created the container from here: https://github.com/gluster/ > gluster-containers/tree/master/CentOS > > And used stock Kubernetes 1.7.3, hence the included volume plugin and > Heketi version 4. > > ? Regardless of the glusterfs client version this is supposed to work. One patch

As an another solution, if you are updating the system where you run application container to latest glusterfs ( 3.11) , this will be fixed as well as it support this mount option. --Humble On Thu, Aug 10, 2017 at 10:39 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > Ok, thanks. > > Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. >

Just created the container from here: https://github.com/gluster/gluster-containers/tree/master/CentOS And used stock Kubernetes 1.7.3, hence the included volume plugin and Heketi version 4. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 18:49: > ?Thanks .. Its the same option. Can you let me know your glusterfs client > package version ?? >

Yes, I tried to, but I didn't find a 3.11 centos-release-gluster package for CentOS. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 19:17: > As an another solution, if you are updating the system where you run > application container to latest glusterfs ( 3.11) , this will be fixed as > well as it support this mount option. > >

Ok, thanks. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 19:04: > On Thu, Aug 10, 2017 at 10:25 PM, Christopher Schmidt <fakod666 at gmail.com> > wrote: > >> Just created the container from here: >> https://github.com/gluster/gluster-containers/tree/master/CentOS >> >> And used stock Kubernetes 1.7.3, hence the

You might need to do a meta data cleanup before rejoining the DC: https://support.microsoft.com/en-us/kb/216498 Regards Davor Vusir -- Skickat fr?n mobilusken! -- ----- Ursprungligt meddelande ----- Fr?n: "Karl Heinz Wichmann" <wichmann-karl at web.de> Skickat: ?2015-?07-?02 20:16 Till: "samba at lists.samba.org" <samba at lists.samba.org> ?mne: [Samba] Rejoin

Hallo When rejoining a dc to the domain I get the following error message: [2015/07/02 11:51:44.089786, 0] ../source4/librpc/rpc/dcerpc_util.c:729(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for

Dear Davor We receive an error message at the command "list domains" ntdsutil metadata cleanup connections connect to server <DC with fsmo roles> quit select operation target error: error at handling the input invalid syntax -> list domains But the command is correct! Am 02.07.2015 um 21:11 schrieb Davor Vusir: > You might need to do a meta data cleanup before

I'm in no position, at the time being, to be of any good help and give advice. Sorry for that. Try do a meta data cleanup "the GUI way"; check DNS, System container, AD sites and services etc. And remove any remains of the old DC. Regards Davor -- Skickat fr?n mobilusken! -- ----- Ursprungligt meddelande ----- Fr?n: "Karl Heinz Wichmann" <karl-heinz.wichmann at