Re: Unbound 1.13.0rc1 pre-release

On Thu, 26 Nov 2020 12:15:19 +0100 Wouter Wijngaards via Unbound-users wrote: > Hi Tuomo, > > Thanks for the stack trace, does this commit help in fixing the issue: > https://github.com/NLnetLabs/unbound/commit/67a0614db700aa6ed596a3563aff6767c69170fe Now I upgraded to 1.13.0rc2 and haven't sen

Re: Unbound 1.13.0rc1 pre-release

Hi Tuomo, Thanks for the stack trace, does this commit help in fixing the issue: https://github.com/NLnetLabs/unbound/commit/67a0614db700aa6ed596a3563aff6767c69170fe It stops the readagain from activating after failed ssl handshake deletes the data. The error you spotted in the logs is also igno

Re: Unbound 1.13.0rc1 pre-release

On Wed, 25 Nov 2020 12:47:13 +0100 George Thessalonikefs via Unbound-users wrote: > Hi Tuomo, > > Could you check if it still happens without the auth-zone? > Could you also share that part of the configuration file? Does this help? #0 SSL_do_handshake (s=0x9c50d9f3b8ee943f) at ssl_lib.c:2776

Re: Unbound 1.13.0rc1 pre-release

On Wed, 25 Nov 2020 12:47:13 +0100 George Thessalonikefs via Unbound-users wrote: > Hi Tuomo, > > Could you check if it still happens without the auth-zone? > Could you also share that part of the configuration file? I'm testing one system without these auth-zones and two systems with rootcache

Re: Unbound 1.13.0rc1 pre-release

Hi Tuomo, Could you check if it still happens without the auth-zone? Could you also share that part of the configuration file? Best regards, -- George On 25/11/2020 12:31, Tuomo Soini via Unbound-users wrote: On Tue, 24 Nov 2020 20:25:31 +0200 Tuomo Soini via Unbound-users wrote: kernel: tr

Re: Unbound 1.13.0rc1 pre-release

On Tue, 24 Nov 2020 20:25:31 +0200 Tuomo Soini via Unbound-users wrote: > kernel: traps: unbound[18976] general protection ip:7f5fde56a471 > sp:7fff060abb80 error:0 in libssl.so.1.0.2k[7f5fde525000+67000] > More information about system if this helps to narrow problem down: Basic dns resolver w

Re: Unbound 1.13.0rc1 pre-release

Hi Yuri, If this is similar to an older issue (https://web.archive.org/web/2020091909/https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4227) then the fix in https://github.com/NLnetLabs/unbound/commit/d05c259458364ac7705d030d1106c4041956d908 may do it. Best regards, Wouter On 24/11/2020

Re: Unbound 1.13.0rc1 pre-release,Re: Unbound 1.13.0rc1 pre-release

>> ./unittest fail on i686 on all Linux variants I build for. >> >> assertion failure testcode/unitregional.c:68 > > This should be fixed in commit > https://github.com/NLnetLabs/unbound/commit/4e8a1ede3b41e9b4a93cb664fbc3f48b1521f62b I can confirm that this also fixes it on NetBSD/i386 8.0, the

Re: Unbound 1.13.0rc1 pre-release

On Tue, 24 Nov 2020 20:04:26 +0200 Tuomo Soini via Unbound-users wrote: > It was too early to say that - now it segfaulted. > Log gives this hint. kernel: traps: unbound[18976] general protection ip:7f5fde56a471 sp:7fff060abb80 error:0 in libssl.so.1.0.2k[7f5fde525000+67000] -- Tuomo Soini F

Re: Unbound 1.13.0rc1 pre-release

On Tue, 24 Nov 2020 19:38:49 +0200 Tuomo Soini via Unbound-users wrote: > Indeed. I added two post 1.13.0rc1 changes and now it works. It was too early to say that - now it segfaulted. -- Tuomo Soini Foobar Linux services +358 40 5240030 Foobar Oy pgpH0yLWhbiKc.pgp Desc

Re: Unbound 1.13.0rc1 pre-release

On Tue, 24 Nov 2020 17:07:46 +0100 Wouter Wijngaards wrote: > Hi Tuomo, > > This should be fixed in commit > https://github.com/NLnetLabs/unbound/commit/4e8a1ede3b41e9b4a93cb664fbc3f48b1521f62b Indeed. I added two post 1.13.0rc1 changes and now it works. -- Tuomo Soini Foobar Linux services

Re: Unbound 1.13.0rc1 pre-release

W. libevent as fresh as possible. built from sources. v2.1.12. 24.11.2020 22:35, Wouter Wijngaards via Unbound-users пишет: Hi Yuri, This looks like it is in the TLS handshake routine, and I do not really expect any issues here, so I wonder if it is because on Solaris there is an older

Re: Unbound 1.13.0rc1 pre-release

Hi Yuri, This looks like it is in the TLS handshake routine, and I do not really expect any issues here, so I wonder if it is because on Solaris there is an older version of libevent (if that is what is happening for you). Or use --without-libevent or --with-libevent=no to use an internal select(

Re: Unbound 1.13.0rc1 pre-release

Different stacktrace: (dbx) where current thread: t@7 =>[1] evmap_io_del_(0xfd7ff9e00400, 0x3c, 0xfd7f9dd81800, 0xfd7f9ed3a680, 0x9, 0xfd7ffe2dfe80), at 0x5a768f   [2] event_del_nolock_(), at 0x59f854   [3] event_del(), at 0x5a0af4   [4] comm_point_listen_for_rw(), at 0x5503fb  

Re: Unbound 1.13.0rc1 pre-release

No. Still crashes. 24.11.2020 22:07, Wouter Wijngaards via Unbound-users пишет: Hi Tuomo, This should be fixed in commit https://github.com/NLnetLabs/unbound/commit/4e8a1ede3b41e9b4a93cb664fbc3f48b1521f62b Best regards, Wouter On 24/11/2020 16:50, Tuomo Soini wrote: On Tue, 24 Nov 2020 15:28

Re: Unbound 1.13.0rc1 pre-release

Hi Tuomo, This should be fixed in commit https://github.com/NLnetLabs/unbound/commit/4e8a1ede3b41e9b4a93cb664fbc3f48b1521f62b Best regards, Wouter On 24/11/2020 16:50, Tuomo Soini wrote: > On Tue, 24 Nov 2020 15:28:55 +0100 > Wouter Wijngaards via Unbound-users > wrote: > >> Hi, >> >> Unbound

Re: Unbound 1.13.0rc1 pre-release

Hi RayG, Thanks for the detail! It looks like the sort order on item removal is not the same as when it was inserted and this is caused by the removal code in the wrong order that happens in the case of this closure order. There is a commit that fixes it, I think (I have not reproduced the case,

Re: Unbound 1.13.0rc1 pre-release

Debug build produced following stacktrace: t@3 (l@3) terminated by signal SEGV (no mapping at the fault address) Current function is reuse_cmp_addrportssl   144   r = sockaddr_cmp(&r1->addr, r1->addrlen, &r2->addr, r2->addrlen); (dbx) where current thread: t@3 =>[1] reuse_cmp_addrportss

Re: Unbound 1.13.0rc1 pre-release

On Tue, 24 Nov 2020 15:28:55 +0100 Wouter Wijngaards via Unbound-users wrote: > Hi, > > Unbound 1.13.0rc1 pre-release is available: > https://nlnetlabs.nl/downloads/unbound/unbound-1.13.0rc1.tar.gz > sha256 > a55e8b5dfc290867017e7fbb75f1023ee2f6234943f870a5c24694b0908d7c17 pgp > https://nlnetlab

RE: Unbound 1.13.0rc1 pre-release

Hi Wouter, This is the entry in the event log Windows 20H2 19042.630 I have 3 of them and they are all the same. Faulting application name: unbound.exe, version: 1.13.0.1, time stamp: 0x5fbd149c Faulting module name: unbound.exe, version: 1.13.0.1, time stamp: 0x5fbd149c Exception code: 0xc

Re: Unbound 1.13.0rc1 pre-release

Hi RayG, On 24/11/2020 16:45, RayG via Unbound-users wrote: BTW does this new release include a fix for my RPZ issue that George was looking at? Unfortunately no, this is still ongoing. -- George

Re: Unbound 1.13.0rc1 pre-release

Confirm. It crashes repeatedly with stacktrace: (dbx) where current thread: t@2 =>[1] reuse_cmp(0xfd7ffc5fed08, 0x0, 0x28, 0x0, 0xfd7ffe6f5000, 0x37961626504), at 0x4eb85e   [2] rbtree_find_less_equal(), at 0x4dc2e9   [3] 0x4eba25(), at 0x4eba25   [4] pending_tcp_query(), at 0x50b69

RE: Unbound 1.13.0rc1 pre-release

Hi Wouter, Sorry this update just crashes... This is the tail of the log file - I have a complete log if required. BTW does this new release include a fix for my RPZ issue that George was looking at? 24/11/2020 15:41:08 unbound.exe[13260:2] info: sending query: www.tm.lg.prod.aadmsa.akadns.ne

Re: Unbound 1.13.0rc1 pre-release

Hi Yuri, Can you tell me what the logs look like with verbosity 5 or so? I do not recall your previous configuration, was there anything particular about it? Best regards, Wouter On 24/11/2020 15:59, Yuri via Unbound-users wrote: > H. > > Built successfully, but not work. > >  dig ya.ru >

Re: Unbound 1.13.0rc1 pre-release

H. Built successfully, but not work.  dig ya.ru ; <<>> DiG 9.11.13 <<>> ya.ru ;; global options: +cmd ;; connection timed out; no servers could be reached With previous configuration. 24.11.2020 20:28, Wouter Wijngaards via Unbound-users пишет: Hi, Unbound 1.13.0rc1 pre-release is avai