Re: Unbound 1.7.1 failing on some kvm servers

2018-05-29 Thread W.C.A. Wijngaards via Unbound-users
Hi Andreas, James, On 29/05/18 20:46, A. Schulze via Unbound-users wrote: > > > Am 29.05.2018 um 09:07 schrieb A. Schulze via Unbound-users: > >> I'll try to recompile the Debian package to catch configure output ... >> @James: which Debian Version? > > OK, here are the logs and patched

Re: Unbound 1.7.1 failing on some kvm servers

2018-05-29 Thread James Cloos via Unbound-users
> "WW" == W C A Wijngaards writes: >> Once the call to glibc's genentropy(3) fails, it immediately sends a >> SIGKILL. WW> But in your strace you have a call to getrandom() that fails. compat/getentropy_linux.c calls genentropy(3) which calls getrandom(2). >> Indeed,

Re: Unbound 1.7.1 failing on some kvm servers

2018-05-29 Thread W.C.A. Wijngaards via Unbound-users
Hi Andreas, On 29/05/18 09:07, A. Schulze via Unbound-users wrote: > > > Am 28.05.2018 um 23:01 schrieb James Cloos via Unbound-users: >> >> I don't have the configure output; this is debian's compile > I'll try to recompile the Debian package to catch configure output ... > @James: which

Re: Unbound 1.7.1 failing on some kvm servers

2018-05-29 Thread A. Schulze via Unbound-users
Am 28.05.2018 um 23:01 schrieb James Cloos via Unbound-users: > > I don't have the configure output; this is debian's compile I'll try to recompile the Debian package to catch configure output ... @James: which Debian Version? Andreas

Re: Unbound 1.7.1 failing on some kvm servers

2018-05-29 Thread W.C.A. Wijngaards via Unbound-users
Hi James, On 28/05/18 23:01, James Cloos wrote: >> "WW" == W C A Wijngaards via Unbound-users >> writes: > >>> Unbound *always* should fall back to urandom(4) when getentropy(3) >>> results in ENOSYS, even when compiled against a kernel which advertizes >>> support for getrandom(2). >

Re: Unbound 1.7.1 failing on some kvm servers

2018-05-28 Thread James Cloos via Unbound-users
> "WW" == W C A Wijngaards via Unbound-users > writes: >> Unbound *always* should fall back to urandom(4) when getentropy(3) >> results in ENOSYS, even when compiled against a kernel which advertizes >> support for getrandom(2). WW> But Unbound does that! WW> It falls back to that when

Re: Unbound 1.7.1 failing on some kvm servers

2018-05-28 Thread W.C.A. Wijngaards via Unbound-users
Hi James, On 25/05/18 19:06, James Cloos via Unbound-users wrote: >> James Cloos via Unbound-users writes: > >> I have a number of kvm instances running debian where unbound 1.7.1 >> fails. > > An LD_PRELOAD lib which implments getentropy(3) via read(3)ing >

Re: Unbound 1.7.1 failing on some kvm servers

2018-05-25 Thread James Cloos via Unbound-users
> James Cloos via Unbound-users writes: > I have a number of kvm instances running debian where unbound 1.7.1 > fails. An LD_PRELOAD lib which implments getentropy(3) via read(3)ing urandom(4) solved the bug. Unbound *always* should fall back to urandom(4) when