group.of.nepali.translators team mailing list archive

[Christian Ehrhardt  <1833400@xxxxxxxxxxxxxxxxxx>]

Odd, I've seen really (I mean really) old reports with the same signature [1]
The attribute [2] seems to be DNS_DISPATCHATTR_NOLISTEN - anything in that regard in your configs?

Code seems to be this:
3685 void                                                                             
3686 dns_dispatch_importrecv(dns_dispatch_t *disp, isc_event_t *event) {              
3687 »···void *buf;                                                                   
3688 »···isc_socketevent_t *sevent, *newsevent;                                       
3689                                                                                  
3690 »···REQUIRE(VALID_DISPATCH(disp));                                               
3691 »···REQUIRE((disp->attributes & DNS_DISPATCHATTR_NOLISTEN) != 0);                
3692 »···REQUIRE(event != NULL);   


18.04 is quite different and less fatal for the same condition
3718 void                                                                             
3719 dns_dispatch_importrecv(dns_dispatch_t *disp, isc_event_t *event) {              
3720 »···void *buf;                                                                   
3721 »···isc_socketevent_t *sevent, *newsevent;                                       
3722                                                                                  
3723 »···REQUIRE(VALID_DISPATCH(disp));                                               
3724 »···REQUIRE(event != NULL);                                                      
3725                                                                                  
3726 »···if ((disp->attributes & DNS_DISPATCHATTR_NOLISTEN) == 0)                     
3727 »···»···return;


Thanks to git I was able to find changes [3][4] which seem to fix this issue.
This lead to the issue [5] which I can't read for permissions in their bug system :-/

Since the expected Fix is in Bionic (sine 9.10.6 [6] to be specific)
I'll mark only Xenial as affected for now.

I had hoped that the bug might have instructions to recreate the issue.

@Douglas / Heikki - do you have any means to trigger this bug so that we
could verify with a potential fix backport with a PPA ?

@Douglas / Heikki - it mentions that this is a race on shutdown, was
your server restarted around that time?

[1]: https://sourceforge.net/p/bind-dlz/mailman/message/6537634/
[2]: http://users.isc.org/~each/doxygen/bind9/dispatch_8h.html#73469a6ec10db29033bb0da2d8acb31c
[3]: https://gitlab.isc.org/isc-projects/bind9/commit/019132b70c368bc9abca0034d07b324bb7cb6eb2
[4]: https://gitlab.isc.org/isc-projects/bind9/commit/a94d68ce432b9e11c4ae91d48ee257b1675f86d7
[5]: https://bugs.isc.org/Public/Bug/Display.html?id=43822
[6]: https://abi-laboratory.pro/?view=changelog&l=bind&v=9.10.6

** Bug watch added: bugs.isc.org/Public/ #43822
   https://bugs.isc.org/Public/Ticket/Display.html?id=43822

** Also affects: bind9 (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: bind9 (Ubuntu)
       Status: Incomplete => Fix Released

** Changed in: bind9 (Ubuntu Xenial)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1833400

Title:
  named crashes on REQUIRE((disp->attributes assert

Status in bind9 package in Ubuntu:
  Fix Released
Status in bind9 source package in Xenial:
  Incomplete

Bug description:
  Ubuntu xenial 16.04, bind9 1:9.10.3.dfsg.P4-8ubuntu1.14

  Yesterday the named process started crashing frequently, 49 crashes so
  far on 49 different servers around the world (one crash each!). We did
  run OS upgrades yesterday, but bind9 packages were not updated at this
  time. This particular bind9 package version was mostly deployed out
  last month. Due to the sudden surge of crashes and the distribution
  I'm suspecting this might be triggered remotely by an incoming packet.

  Backtrace from the assert:

  2019-06-18T21:42:16.801421+00:00 hostname named[888]: general: critical: ../../../lib/dns/dispatch.c:3691: REQUIRE((disp->attributes & 0x00000020U) != 0) failed, back trace
  2019-06-18T21:42:16.801890+00:00 hostname named[888]: general: critical: #0 0x555c41aeeaf0 in ??
  2019-06-18T21:42:16.802118+00:00 hostname named[888]: general: critical: #1 0x7f475bd66eaa in ??
  2019-06-18T21:42:16.802315+00:00 hostname named[888]: general: critical: #2 0x7f475ca9f7da in ??
  2019-06-18T21:42:16.802496+00:00 hostname named[888]: general: critical: #3 0x555c41ae3195 in ??
  2019-06-18T21:42:16.802684+00:00 hostname named[888]: general: critical: #4 0x7f475bd8b420 in ??
  2019-06-18T21:42:16.802875+00:00 hostname named[888]: general: critical: #5 0x7f475b7346ba in ??
  2019-06-18T21:42:16.803056+00:00 hostname named[888]: general: critical: #6 0x7f475ae7e41d in ??
  2019-06-18T21:42:16.803245+00:00 hostname named[888]: general: critical: exiting (due to assertion failure)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1833400/+subscriptions