named warns: max open files (1024) is smaller than max sockets (4096)

[Christian Reis]

Binary package hint: bind9

When starting up the Jaunty-current bind9 daemon, a warning is printed out in the daemon log which says:

   max open files (1024) is smaller than max sockets (4096)

ii bind9 1:9.5.1.dfsg.P2-1ubuntu0.3 Internet Domain Name Server

You can work around this with a "-S 1024" in /etc/defaults/bind9, but this has been reported to be a kernel bug that should have been fixed in 2.6.28: http://www.cyberciti.biz/faq/max-open-files-1024-smaller-than-max-sockets/ and yet, this server is running:

  Linux anthem 2.6.28-15-server #52-Ubuntu SMP Wed Sep 9 11:50:50 UTC 2009 i686 GNU/Linux

[Thierry Carrez (ttx)]

The kernel patch has been reverted in 2.6.28.5:

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commit;h=ad649a5df5b1d4e1feb3f03fc452d05ad217e339

So the issue in the kernel still stands.

[Andy Whitcroft (apw)]

@Christian -- as Thierry points out the fix though in 2.6.28 triggered very bad regressions for a number of userspace components and was reverted. As the message is simply a warning and easily worked round its not obvious that making any change under SRU would be justified. For lucid, it sees that the change remains reverted upstream pending resolution of the performance regressions.

[Christian Reis (kiko)]

Do you think it makes sense to fix this in bind instead, given the above?

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.