Re: [arch-general] Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup

2017-03-12 Thread David C. Rankin
On 03/12/2017 10:36 AM, Mauro Santos via arch-general wrote: > On 12-03-2017 14:00, David C. Rankin wrote: >> All, >> >> After update to Linux 4.10.1-1, Bind9 cannot connect to 127.0.0.1#953. This >> server has been flawless with Bind for 4 years. Now, for example attempting >> to >> sync

Re: [arch-general] Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup

2017-03-12 Thread Mauro Santos via arch-general
On 12-03-2017 14:00, David C. Rankin wrote: > All, > > After update to Linux 4.10.1-1, Bind9 cannot connect to 127.0.0.1#953. This > server has been flawless with Bind for 4 years. Now, for example attempting to > sync zones: It seems other people also have noticed problems:

Re: [arch-general] Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup

2017-03-12 Thread Doug Newgard
On Sun, 12 Mar 2017 09:36:48 -0500 "David C. Rankin" wrote: > Should I open a bug, and if so, which package do I open it under? There already is one, has been for a couple of days

Re: [arch-general] Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup

2017-03-12 Thread David C. Rankin
On 03/12/2017 09:24 AM, David C. Rankin wrote: > There is a BIG bug in one of those upgrades -- but which one? > If it helps, I had individually downgraded the following and tested, but named remained broken until I backed out the block of packages containing the kernel and gcc. I had

Re: [arch-general] Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup

2017-03-12 Thread David C. Rankin
On 03/12/2017 09:00 AM, David C. Rankin wrote: > For some reason the 'libseccomp sandboxing active' command never issues and > /etc/named.conf is never processed. I have not touched the configuration here > in a "long long time..." > > Is this a kernel bug, a libseccomp bug, what? Uugh...

[arch-general] Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup

2017-03-12 Thread David C. Rankin
All, After update to Linux 4.10.1-1, Bind9 cannot connect to 127.0.0.1#953. This server has been flawless with Bind for 4 years. Now, for example attempting to sync zones: # rndc -V sync --clean create memory context create socket manager create task manager create task create logging context