Recent upgrade of Ubuntu 22.04 Server updates bind9 but does not include libuv 1.43, hence bind9 can not start anymore

[Simon Hradecky]

After upgrading our Ubuntu Server 22.04.2 to the latest version (including kernel update to *72) named (bind9) didn't start anymore, the syslog contains following message:

May 28 11:54:16 lindev2 named[15965]: libuv version too old: running with libuv 1.37.1-dev when compiled with libuv 1.43.0 will lead to libuv failures because of unknown flags

It appears however, that libuv although required was not included in the recent upgrades.

I needed to download the library manually, compile it and then it started again and worked.

Breaking working functionality (bind9/named had worked flawlessly before the upgrade) makes me feel very uneasy about any further upgrade. What else is broken now even in this upgrade (due to absence the recent upgrade was 187 modules).

1:9.18.12-0ubuntu0.22.04.1

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bind9 1:9.18.12-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98
Uname: Linux 5.15.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sun May 28 12:17:04 2023
InstallationDate: Installed on 2023-02-19 (98 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
KernLog:

ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=linux
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
RelatedPackageVersions:
 bind9utils N/A
 apparmor 3.0.4-2ubuntu2.2
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.apparmor.d.usr.sbin.named: 2023-02-28T16:37:22
mtime.conffile..etc.bind.named.conf: 2023-04-09T12:22:34
mtime.conffile..etc.default.apport: 2023-03-12T18:23:17

[Bryce Harrington (bryce)]

Hi Simon, this does seem extremely atypical, bind9 should not fail like this on upgrade on a stock installation of Ubuntu. There doesn't appear to be other reports of this issue, so there may be something unique about your configuration.

I confirm from your logs that it seems to be failing due to the libuv version mismatch. What's odd is that I'm not spotting where Ubuntu has shipped a version of libuv numbered "1.37.1-dev". Could it be possible that you had installed that manually in the past (maybe from git, given the -dev in the version)? Or by chance was that installed to /usr/local?

It would be super helpful to see your /var/log/dpkg.log, /var/log/apt/history.log and /var/log/apt/term.log files. These may have rotated so we may also want to examine some of the *.log.N.gz files. Specifically, the one that shows when 1.37.1-dev was first installed and where it came from would be of interest, so we can look into if this error can be reproduced on our end.

[Launchpad Janitor (janitor)]

[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.]

[keith jolley (keithpjolley)]

also ran into this issue. i've been running "Ubuntu 22.04.3 LTS" for a while, keeping things up to date by running:
```
    for action in update upgrade dist-upgrade autoremove autoclean
    do
        DEBIAN_FRONTEND=noninteractive apt-get --yes --assume-yes -o DPkg::Options::="--force-confnew" "${action}"
        echo
    done
```
regularly. did that this morning. after a reboot i get this error:
```
❯ host ubuntu.com
netmgr/netmgr.c:231:isc__netmgr_create(): fatal error: libuv version too old: running with libuv 1.38.1 when compiled with libuv 1.43.0 will lead to libuv failures
[1] 9316 IOT instruction (core dumped) host ubuntu.com
```

dns is broken across the board. can still get to the interwebs via ip addresses.

[Athos Ribeiro (athos-ribeiro)]

Hi Keith. Bryce's comment in https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2021419/comments/2 also applies here.

I cannot see a 1.38.1 version of libuv ever being published in Ubuntu (https://launchpad.net/ubuntu/+source/libuv1/+publishinghistory).

Are there any chances you installed it manually or from a third party repository?

Showing the logs requested by Bryce in his comment would help us figure out what is going on there.