Comment 34 for bug 1674532

Agreed on this one, we're also experiencing production failures, but they happen every night around 1am and simply restarting apache clears it up.

From our logs

Start-Date: 2017-03-21 03:22:40
Commandline: /usr/bin/unattended-upgrade
Upgrade: libc6-dev:amd64 (2.23-0ubuntu3, 2.23-0ubuntu6), libc6:amd64 (2.23-0ubuntu3, 2.23-0ubuntu6), locales:amd64 (2.23-0ubuntu3, 2.23-0ubuntu6), libc-bin:amd64 (2.23-0ubuntu3, 2.23-0ubuntu6), libc-dev-bin:amd64 (2.23-0ubuntu3, 2.23-0ubuntu6), multiarch-support:amd64 (2.23-0ubuntu3, 2.23-0ubuntu6)
End-Date: 2017-03-21 03:22:46

Start-Date: 2017-03-22 00:27:23
Commandline: /usr/bin/unattended-upgrade
Upgrade: libc6-dev:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), 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), libc-dev-bin:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), multiarch-support:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7)
End-Date: 2017-03-22 00:27:29

We believe that the unattended upgrade updated and killed us RIGHT around the same time, thus needing the apache restart. 2 nights in a row we found these failures, and 2 libc upgrades at the same time.