unbound-anchor not found in Ubuntu 24.04

[necrevistonnezr]

Is it just me or is unbound-anchor not installed per default in Ubuntu 24.04?

I had a problem installing a new app after upgrading to Cloudron 8.0.5 as I received the error queryNs ETIMEOUT

After a forum search, I ran cloudron-support --troubleshoot as per https://forum.cloudron.io/topic/12145/setup-error-queryns-etimeout

The result was

unbound is down. updating root anchor to see if it fixes it
/usr/bin/cloudron-support: line 251: unbound-anchor: command not found

After manually installing unbound-anchor, I re-ran cloudron-support --troubleshoot - now unbound is running.

--> So I wonder if it's just me or if the package is missing in vanilla Ubuntu Server 24.04 (the OS on my server)? Maybe the troubleshoot utility should check for this package?

[nebulon]

Indeed, it seems the unbound-anchor binary has moved to its own package in Ubuntu 24

We actually install unbound-anchor already with Cloudron, so maybe it got removed manually or did you update from some very old ubuntu version?

[nebulon]

To be clear, it is not installed on vanilla Ubuntu as such and also not as a default dependency of the unbound package. If you install Cloudron, it will install it as a Cloudron dependency though.

[necrevistonnezr]

Yep, it's a very old install And I only ever updated, both Ubuntu and Cloudron, never re-installed

[nebulon]

That then probably explains it.

[imc67]

@nebulon said in unbound-anchor not found in Ubuntu 24.04:

That then probably explains it.

Explains what? If one only updates Cloudron and Ubuntu for years does it mean one has to do this manually or is/will it be part of the post-Ubuntu upgrade check/install?

Don't know what to do know? I have 2 Cloudron servers candidate for upgrade to 22.04 and then 24.04.

[necrevistonnezr]

@imc67 said in unbound-anchor not found in Ubuntu 24.04:

Don't know what to do know? I have 2 Cloudron servers candidate for upgrade to 22.04 and then 24.04.

sudo apt install unbound-anchor

(@nebulon Maybe add this to https://docs.cloudron.io/guides/upgrade-ubuntu-24/ ?)
And it only seems relevant for troubleshooting, not in running unbound per se.

[NCKNE]

Same happened to one of my installations as well. Also causing problems with email delivery:

Die Zustellung von E-Mail ist fehlgeschlagen. Wird in Sekunden erneut versucht.. DNS lookup failure: Error: queryMx ESERVFAIL xyz.de

After fixing the problem and a reboot, the outgoing mail queue is empty. Will there still be attempts to resend the outgoing mails that were not yet send because of the unbound-anchor problem?

[girish]

@NCKNE Did you also upgrade from Ubuntu 22 to 24?

[NCKNE]

@girish Yes, I did. A while ago. The problem just came up after upgrading to 8.0.5 a few days ago. 8.0.4 was running fine.

[girish]

@NCKNE I have fixed the upgrade guide now. unbound-anchor package must be installed after the upgrade.

[nichu42]

Ah, thanks! I was already running 8.0.5, but the upgrade to 8.0.6 got stuck. /home/yellowtent/box/setup/start.sh came up with an unbound error. I was able to start box manually and start all apps, but the backup volume did not mount. After installing unbound-anchor, I was able to run /home/yellowtent/box/setup/start.sh without errors, and now the backup is working again.