Yes that exactly, essentially we found that we had the connections set to 1000 and one client opened a few connections but they never closed, they then opened more and more naturally.
In the end one client had over 900 connections. Once we hit 1000 we ran a quick dig against the server and it failed/timed out. Although now that I think about it, to get BIND to run after compilation because it wanted to wite log files into /var/log I disabled apparmor temporarily and that allowed the write. I have no tested the packaged bind without apparmor, I can't imagine apparmor forcing bind to hold TCP connections open though, it was however one difference between the two versions of bind being run. Just for comparison none of our Debian or CentOS or Fedora boxes exhibit this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909950 Title: TCP connections never close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
