9.10.3.dfsg.P4-8ubuntu1.9 - keep on crashing on Ubuntu 16.04

Bug #1736943 reported by Jai on 2017-12-07
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bind9 (Ubuntu)
Undecided
Unassigned

Bug Description

Error logs:
Dec 7 11:51:47 dns01 named[1305]: ../../../lib/isc/netaddr.c:358: INSIST(0) failed, back trace
Dec 7 11:51:47 dns01 named[1305]: #0 0x561b704538b0 in ??
Dec 7 11:51:47 dns01 named[1305]: #1 0x7f75748c6e7a in ??
Dec 7 11:51:47 dns01 named[1305]: #2 0x7f75748de518 in ??
Dec 7 11:51:47 dns01 named[1305]: #3 0x7f75748e6832 in ??
Dec 7 11:51:47 dns01 named[1305]: #4 0x7f75748e698b in ??
Dec 7 11:51:47 dns01 named[1305]: #5 0x7f75756a3f12 in ??
Dec 7 11:51:47 dns01 named[1305]: #6 0x7f75756b0b6c in ??
Dec 7 11:51:47 dns01 named[1305]: #7 0x7f75748eb360 in ??
Dec 7 11:51:47 dns01 named[1305]: #8 0x7f75742946ba in ??
Dec 7 11:51:47 dns01 named[1305]: #9 0x7f75739de3dd in ??
Dec 7 11:51:47 dns01 named[1305]: exiting (due to assertion failure)
Dec 7 11:52:01 dns01 CRON[21203]: (root) CMD (/usr/local/bin/dnscheck > /dev/null 2>&1)
Dec 7 11:52:27 dns01 systemd[1]: bind9.service: Main process exited, code=killed, status=6/ABRT
Dec 7 11:52:27 dns01 rndc[21209]: rndc: connect failed: 127.0.0.1#953: connection refused
Dec 7 11:52:27 dns01 systemd[1]: bind9.service: Control process exited, code=exited status=1
Dec 7 11:52:27 dns01 systemd[1]: bind9.service: Unit entered failed state.
Dec 7 11:52:27 dns01 systemd[1]: bind9.service: Failed with result 'exit-code'.

Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

Bind9 version: 9.10.3.dfsg.P4-8ubuntu1.9

For Ubuntu16.04 that's the latest available version.
=========================
bind9 is already the newest version (1:9.10.3.dfsg.P4-8ubuntu1.9).
bind9-host is already the newest version (1:9.10.3.dfsg.P4-8ubuntu1.9).
bind9utils is already the newest version (1:9.10.3.dfsg.P4-8ubuntu1.9).
=========================

As per my check, it's almost related to this open bug: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1085593

If it so, please merge this with that one and add Xenial in that OS list then confirm it.

Andreas Hasenack (ahasenack) wrote :

Do you have a crash file in /var/crash about this?

Hello Andreas,

Thank you for your quick response.

Given below the crash file link.

<goog_1961136065>
http://81.91.12.28/_usr_sbin_named.108.crash.gz

Regards,
Jay

On Thu, Dec 7, 2017 at 6:28 PM, Andreas Hasenack <email address hidden>
wrote:

> Do you have a crash file in /var/crash about this?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1736943
>
> Title:
> 9.10.3.dfsg.P4-8ubuntu1.9 - keep on crashing on Ubuntu 16.04
>
> Status in bind9 package in Ubuntu:
> New
>
> Bug description:
> Error logs:
> Dec 7 11:51:47 dns01 named[1305]: ../../../lib/isc/netaddr.c:358:
> INSIST(0) failed, back trace
> Dec 7 11:51:47 dns01 named[1305]: #0 0x561b704538b0 in ??
> Dec 7 11:51:47 dns01 named[1305]: #1 0x7f75748c6e7a in ??
> Dec 7 11:51:47 dns01 named[1305]: #2 0x7f75748de518 in ??
> Dec 7 11:51:47 dns01 named[1305]: #3 0x7f75748e6832 in ??
> Dec 7 11:51:47 dns01 named[1305]: #4 0x7f75748e698b in ??
> Dec 7 11:51:47 dns01 named[1305]: #5 0x7f75756a3f12 in ??
> Dec 7 11:51:47 dns01 named[1305]: #6 0x7f75756b0b6c in ??
> Dec 7 11:51:47 dns01 named[1305]: #7 0x7f75748eb360 in ??
> Dec 7 11:51:47 dns01 named[1305]: #8 0x7f75742946ba in ??
> Dec 7 11:51:47 dns01 named[1305]: #9 0x7f75739de3dd in ??
> Dec 7 11:51:47 dns01 named[1305]: exiting (due to assertion failure)
> Dec 7 11:52:01 dns01 CRON[21203]: (root) CMD (/usr/local/bin/dnscheck >
> /dev/null 2>&1)
> Dec 7 11:52:27 dns01 systemd[1]: bind9.service: Main process exited,
> code=killed, status=6/ABRT
> Dec 7 11:52:27 dns01 rndc[21209]: rndc: connect failed: 127.0.0.1#953:
> connection refused
> Dec 7 11:52:27 dns01 systemd[1]: bind9.service: Control process exited,
> code=exited status=1
> Dec 7 11:52:27 dns01 systemd[1]: bind9.service: Unit entered failed
> state.
> Dec 7 11:52:27 dns01 systemd[1]: bind9.service: Failed with result
> 'exit-code'.
>
> Distributor ID: Ubuntu
> Description: Ubuntu 16.04.3 LTS
> Release: 16.04
> Codename: xenial
>
> Bind9 version: 9.10.3.dfsg.P4-8ubuntu1.9
>
> For Ubuntu16.04 that's the latest available version.
> =========================
> bind9 is already the newest version (1:9.10.3.dfsg.P4-8ubuntu1.9).
> bind9-host is already the newest version (1:9.10.3.dfsg.P4-8ubuntu1.9).
> bind9utils is already the newest version (1:9.10.3.dfsg.P4-8ubuntu1.9).
> =========================
>
> As per my check, it's almost related to this open bug:
> https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1085593
>
> If it so, please merge this with that one and add Xenial in that OS
> list then confirm it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/
> 1736943/+subscriptions
>

--
Carry a heart that never hates..!
Carry a smile that never fades..!
Carry a touch that never hurts..!
Carry a friendship that never fails..!

Regards,
JayaChandran Palanisamy
<email address hidden>
http://innovationframes.com/phpbb/

Andreas Hasenack (ahasenack) wrote :

Can you perhaps attach it to the bug instead? The download is taking a long time.

Andreas Hasenack (ahasenack) wrote :

I got the crash file.

Andreas Hasenack (ahasenack) wrote :

In order to reach that INSIST(0) code, type.sa.sa_family needs to be something other than AF_INET, AF_INET6 or AF_UNIX:
void
isc_netaddr_fromsockaddr(isc_netaddr_t *t, const isc_sockaddr_t *s) {
        int family = s->type.sa.sa_family;
        t->family = family;
        switch (family) {
        case AF_INET:
                t->type.in = s->type.sin.sin_addr;
                t->zone = 0;
                break;
        case AF_INET6:
                memmove(&t->type.in6, &s->type.sin6.sin6_addr, 16);
#ifdef ISC_PLATFORM_HAVESCOPEID
                t->zone = s->type.sin6.sin6_scope_id;
#else
                t->zone = 0;
#endif
                break;
#ifdef ISC_PLATFORM_HAVESYSUNH
        case AF_UNIX:
                memmove(t->type.un, s->type.sunix.sun_path, sizeof(t->type.un));
                t->zone = 0;
                break;
#endif
        default:
                INSIST(0);
        }
}

From the crash file:
(gdb) frame 4
#4 0x00007f2e236f1518 in isc_netaddr_fromsockaddr (t=t@entry=0x7f2e1dc06720, s=s@entry=0x7f2e0b046590) at ../../../lib/isc/netaddr.c:358
358 in ../../../lib/isc/netaddr.c
(gdb) p s->type.sa.sa_family
$9 = 57054
(gdb)

That's odd, that looks like the port number:
(gdb) p s->type.sin
$13 = {sin_family = 57054, sin_port = 57054, sin_addr = {s_addr = <redacted>}, sin_zero = "\336\336\336\336\336\336\336", <incomplete sequence \336>}

Andreas Hasenack (ahasenack) wrote :

Do you have more logs just before what you posted when filing this bug? Could you please attach them?

Jai (chandranjoy) wrote :

Hi Andreas,

I Hope you got the needed syslog from my colleague Fredrik.

Please let me know if you need further info.

Thank you very much for your quick responses.

/Jay

Jai (chandranjoy) wrote :

Also, noticed this in other server which got crashed with same logs.

Enclosed 1 minute log before crash.
http://81.91.12.28/_dns_crash_before_1min_.log.gz

======================================
Dec 7 11:51:47 dns2 named[1305]: no valid DS resolving 'bahnuaayklyzeofxzdde.gb.com/DS/IN': <unknown address, family 57054>
Dec 7 11:51:47 dns2 named[1305]: no valid DS resolving 'nqqfrjygddiijntpzdjd.gb.com/DS/IN': <unknown address, family 57054>
Dec 7 11:51:47 dns2 named[1305]: validating hu.com/SOA: got insecure response; parent indicates it should be secure Dec 7 11:51:47 dns2 named[1305]: no valid RRSIG resolving 'gekasappen.hu.com/DS/IN': 208.109.255.64#53
Dec 7 11:51:47 dns2 named[1305]: no valid DS resolving 'gekasappen.hu.com/NS/IN': 216.69.185.64#53
Dec 7 11:51:47 dns2 named[1305]: no valid DS resolving 'pndtdisenvjwiwplgyot.gb.com/DS/IN': 2600:1800:10::1#53
Dec 7 11:51:47 dns2 named[1305]: ../../../lib/isc/netaddr.c:358: INSIST(0) failed, back trace
Dec 7 11:51:47 dns2 named[1305]: #0 0x561b704538b0 in ??
Dec 7 11:51:47 dns2 named[1305]: #1 0x7f75748c6e7a in ??
Dec 7 11:51:47 dns2 named[1305]: #2 0x7f75748de518 in ??
Dec 7 11:51:47 dns2 named[1305]: #3 0x7f75748e6832 in ??
Dec 7 11:51:47 dns2 named[1305]: #4 0x7f75748e698b in ??
Dec 7 11:51:47 dns2 named[1305]: #5 0x7f75756a3f12 in ??
Dec 7 11:51:47 dns2 named[1305]: #6 0x7f75756b0b6c in ??
Dec 7 11:51:47 dns2 named[1305]: #7 0x7f75748eb360 in ??
Dec 7 11:51:47 dns2 named[1305]: #8 0x7f75742946ba in ??
Dec 7 11:51:47 dns2 named[1305]: #9 0x7f75739de3dd in ??
Dec 7 11:51:47 dns2 named[1305]: exiting (due to assertion failure)
======================================

Thanks

/Jay

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers