Just like my earlier comment, this _fix_ *broke* a running system after it was automatically applied.
Start-Date: 2017-03-22 04:17:12 Commandline: /usr/bin/unattended-upgrade Upgrade: libc6:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), locales:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), libc-bin:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), multiarch-support:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7) End-Date: 2017-03-22 04:17:34
Immediately after that, the system is no longer able to resolve names. On my DNS server, I can see this is sending queries of TYPE62321 instead of A
22-Mar-2017 04:17:30.407 queries: info: client 172.16.x.x#63762 (host.interna.domain): query: host.interna.domain IN TYPE62321 + (172.16.1.10)
A reboot clears the issue, but the point is that applying the update is still a "critical" bug because it breaks [some] running systems. In this case, the system is running apache+php. It might be that it only effects certain things.
Just like my earlier comment, this _fix_ *broke* a running system after it was automatically applied.
Start-Date: 2017-03-22 04:17:12 unattended- upgrade support: amd64 (2.23-0ubuntu6, 2.23-0ubuntu7)
Commandline: /usr/bin/
Upgrade: libc6:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), locales:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), libc-bin:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), multiarch-
End-Date: 2017-03-22 04:17:34
Immediately after that, the system is no longer able to resolve names. On my DNS server, I can see this is sending queries of TYPE62321 instead of A
22-Mar-2017 04:17:30.407 queries: info: client 172.16.x.x#63762 (host.interna. domain) : query: host.interna.domain IN TYPE62321 + (172.16.1.10)
A reboot clears the issue, but the point is that applying the update is still a "critical" bug because it breaks [some] running systems. In this case, the system is running apache+php. It might be that it only effects certain things.