Public bug reported:
I see this in bind logs constantly. The machine is a machine with 88
procs, and about 132 GB ram. https://kb.isc.org/docs/aa-00508 sheds some
light on the issues, which require re-compilation of bind9.
Apr 07 12:01:54 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:01:59 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:01 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:02 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:03 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:03 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:04 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:05 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:05 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:06 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:06 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:07 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:07 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:08 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:09 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:09 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:02:23 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:03:10 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:03:12 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:03:20 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:03:27 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:03:33 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:03:57 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:03:58 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:03:59 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
Apr 07 12:04:00 maas2 named[373]: sockmgr 0x7fa0b8b0a010: maximum number of FD
events (64) received
lines 1-27
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827923
Title:
Constant sockmgr 0x7fa0b8b0a010: maximum number of FD events (64)
received
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1827923/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
