similar to: Problems with bind9_dlz when rndc is reloaded

Displaying 20 results from an estimated 6000 matches similar to: "Problems with bind9_dlz when rndc is reloaded"

2017 Jan 12
2
Problems with bind9_dlz when rndc is reloaded
Mathias, Thanks for your reply. Please, try to start your bind with some debug level and run commando "rndc reload" and see the end of the log. I saw samba source code and found the destroy dns function in dlz_bind9.c and called by turture blz_bind9.c. When dlz_bind9.c is shutting down, I get this error when I try to update dns. update failed: NOTAUTH Failed nsupdate: 2
2017 Jan 12
2
Problems with bind9_dlz when rndc is reloaded
Using your log parameters, the shutting down message is not showed, but when I reload rndc a get the same effect. Everything is working fine until bond9_dlz needs to reload (and no restart) rndc. When this happens, I need to restart bind and everything works fine again. I'm starting named with named -d 3 -u named and using /var/log/messages. See log using your parameters: # rndc reload
2017 Jan 12
0
Problems with bind9_dlz when rndc is reloaded
Hi Roger, I'm using Samba as AD DC in version 4.5.0 on Centos 7 with Bind9_DLZ DNS backend, Bind is 9.9.4 and I don't have that issue. I tried reload my bind using systemctl at first and no issue, then I tried "rdnc reload" to be sure rndc was used, still no issue. By no issue I don't mean log are clean, I mean the DNS service is working well (tested using dig commands).
2017 Jan 12
0
Problems with bind9_dlz when rndc is reloaded
I've added logs (dirty and quickly): logging { channel "request" { file "/var/named/named.run" size 10m; print-time yes; print-category yes; severity debug; }; category default { request; }; category security { request; }; }; Reload DNS service using systemctl once, twice, then restart Bind, reload it using rndc and no complain about log file and
2017 Jan 27
2
Problems with bind9_dlz when rndc is reloaded
Hello! After updating (only one dc) for samba 4.5.3 is occurring duplicate zone errors, when I run rndc reload Samba_dlz: Ignoring duplicate zone This replied to all my dcs ... When I run: Samba_dnsupdate --verbose --all-names I get the error Update failed: NOTAUTH .... .... Update failed: NOTAUTH Failed nsupdate: 2 Failed update of 21 entries Like this topic to have reference to this,
2017 Jan 12
0
Problems with bind9_dlz when rndc is reloaded
Hum... what are these logs related to GeoIP? Perhaps this answer will be a bit rough... anyway: MS AD is complex. Samba team did a great job to reproduce its behaviour but MS product are not reputed to be too stable, so a work-in-progress reproduction of such tool has few chances to be too stable. DNS is complex by itself, especially when using Bind as backend: Bind can do lot of things related
2017 Feb 03
3
Problems with winbind cache
Hi guys!! I'm facing problem with Samba 4 + winbind that I spent some days to solve that without success and I'll appreciate any help. I self compile samba 4 and apparently everything is working fine. I installed samba on six distributed servers at remote branch offices and all users, groups, dns and other components are replicating with success. But last week I saw that windind
2017 Feb 03
3
Problems with winbind cache
Try cleaning up your smb.conf also.   >   vfs objects = dfs_samba4, acl_xattr Bit lower. >   vfs objects = recycle full_audit Set this as : vfs objects = dfs_samba4, acl_xattr, recycle full_audit   Your using : >   winbind nss info = rfc2307 So remove these lines >   idmap config * : backend = tdb >   idmap config *:range = 70001-80000 >   idmap config
2017 Feb 03
0
Problems with winbind cache
Try changing your nsswitch.conf to passwd: files winbind sss shadow: files sss group: files winbind sss now do. net cache flush restart winbind wbinfo -u wbinfo -g getent passwd username getent passwd groupname Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Roger Lovato via > samba >
2013 Sep 12
2
samba4+bind9.9 will not start: samba_dlz: dns_rdata_fromtext: buffer-0x7f1c0cbcd680:1: near 'hostmaster.domain.de': not a valid number
Hello, running on Debian jessie 64bit samba 4.0.8 and bind 9.9 but with the description from https://wiki.samba.org/index.php/Dns-backend_bind I run into the following problem: # named -u bind -g 2>&1 |tee named.log 12-Sep-2013 15:43:07.287 starting BIND 9.9.3-rpz2+rl.13214.22-P2-Debian-1:9.9.3.dfsg.P2-4 -u bind -g 12-Sep-2013 15:43:07.287 built with '--prefix=/usr'
2017 Apr 02
3
samba Digest, Vol 172, Issue 2
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
2009 Jul 09
2
[LLVMdev] Wrong encoding of movd on x64
Hi all, I believe I've found a bug in the encoding of the movd instruction on x64. Here's some IR code to reproduce it: external global i8*, align 1 ; <i8**>:0 [#uses=1] external global i8*, align 16 ; <i8**>:1 [#uses=1] declare void @abort() define internal void @2() { %1 = load i8** @0, align 1 ; <i8*> [#uses=1] %2 =
2009 Jul 09
0
[LLVMdev] Wrong encoding of movd on x64
On Thu, Jul 9, 2009 at 8:44 AM, Nicolas Capens<nicolas at capens.net> wrote: > I believe I’ve found a bug in the encoding of the movd instruction on x64. > Here’s some IR code to reproduce it: [snip > Note the last movq. What was probably intended to be generated was “movd > ecx, mm0”. LLVM mistakenly sets the ‘wide’ bit of the REX prefix to 1, > turning movd into movq. Also,
2017 Nov 07
2
after DCs migration to 4.7, two things
Hi, I migrated our DCs from 4.5/internal dns to 4.7.1/bind9_dlz. Short summary of the steps taken: - added a new temp dc, - removed the old DCs - cleaned sam database - installed new DCs, with their old dns/ip - removed the temp dc again - synced sysvol and all is looking well: no db errors, no replication issues, ldapcmp matches across DCs, etc. So, I took things to production today, and
2015 Apr 11
3
Winbind not able to start
On 11/04/15 18:54, Timo Altun wrote: > Good evening, > > unfortunately one problem emerged during the change from my testing > environment to a small portion of the live environment. > The automatic dns updates of the windows clients do not seem to work > in the live environment. I changed the AD DC IP from another subnet to > 192.168.111.90, without reprovisioning.
2011 Oct 26
0
[LLVMdev] Lowering to MMX
On Oct 26, 2011, at 1:18 PM, Nicolas Capens wrote: > On 24/10/2011 9:50 PM, Bill Wendling wrote: >> On Oct 20, 2011, at 8:42 AM, Nicolas Capens wrote: >> >>> Hi all, >>> >>> I'm working on a graphics project which uses LLVM for dynamic code >>> generation, and I noticed a major performance regression when upgrading >>> from LLVM
2015 Mar 19
5
Dynamic DNS Updates not working. samba_dnsupdate : RuntimeError: (sambalist: to exclusive) kinit for [DC@Realm] failed (Cannot contact any KDC for requested realm)
Good morning! First of all thanks Rowland for the fast answer yesterday! I realized that samba-technical might have been the wrong mailing list and switched it to the normal samba users list (hopefully it worked, as it does get a bit confusing with spamgourmets sendto addresses!). Unfortunately the problem with samba_dnsupdate remains after the changes. I did changed the smb.conf, krb5.conf, and
2010 Aug 31
0
[LLVMdev] "equivalent" .ll files diverge after optimizations are applied
Using MM registers is wrong unless the user has specifically asked for it, which doesn't seem to be the case here. In the awesome MMX architecture, touching an MM register makes subsequent x87 operations fail unless an EMMS instruction is issued first; none of the compilers here are smart enough to insert EMMS instructions in the right places, so the only safe thing is not to use
2011 Oct 26
2
[LLVMdev] Lowering to MMX
Hi Bill, Comments inline: On 24/10/2011 9:50 PM, Bill Wendling wrote: > On Oct 20, 2011, at 8:42 AM, Nicolas Capens wrote: > >> Hi all, >> >> I'm working on a graphics project which uses LLVM for dynamic code >> generation, and I noticed a major performance regression when upgrading >> from LLVM 2.8 to 3.0-rc1 (LLVM 2.9 didn't support Win64 so I
2010 Aug 31
2
[LLVMdev] "equivalent" .ll files diverge after optimizations are applied
Here's the optimized versions: $ opt -std-compile-opts unopt-pass.ll -o - | llvm-dis -o - [...] define %3 @_ZN7WebCore15GraphicsContext19roundToDevicePixelsERKNS_9FloatRectE(%"class.WebCore::GraphicsContext"* %this, %"struct.WebCore::FloatRect"* %rect) nounwind ssp align 2 { %roundedOrigin = alloca %"class.WebCore::FloatSize", align 4 ;