Oracle Cloud Ubuntu `systemd-resolved` DBus connection failure

[leeaash]

What is the issue?

Many logs show dns issue as following:

2023/07/10 06:26:47 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory 2023/07/10 06:36:36 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory 2023/07/10 06:37:55 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory 2023/07/10 06:35:33 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory 2023/07/10 06:24:45 magicsock: closing connection to derp-900 (idle), age 1m0s 2023/07/10 06:25:51 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory 2023/07/10 06:31:42 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory 2023/07/10 06:24:45 magicsock: 1 active derp conns: derp-911=cr9m0s,wr9m0s

Health check results when running tailscale status:

Health check: - dns-os: resolved DBus does not have a connection - dns: resolved DBus does not have a connection

Steps to reproduce

No response

Are there any recent changes that introduced the issue?

No response

OS

Linux

OS version

Ubuntu 22.04.2 LTS

Tailscale version

1.44.0 docker

Other software

No response

Bug report

No response

[DentonGentry]

Can you confirm that the Oracle Cloud instance is using systemd-resolved? tailscaled thinks that it is, but may just have gotten that wrong.

[leeaash]

Can you confirm that the Oracle Cloud instance is using systemd-resolved? tailscaled thinks that it is, but may just have gotten that wrong.

Yes

[davidemyers]

FWIW, I don't have issues on Oracle Cloud with Ubuntu Server 22.04.3 on either AMD or ARM, but I'm running 1.48.1 directly, not with Docker.

[danielcbit]

I'm currently with the same issue after updating to Ubuntu 22.04 in a ARM VM in Oracle Cloud. But I'm running in a Docker Container.

2024/03/03 02:39:21 dns: failed to configure resolved: resolved DBus does not have a connection
2024/03/03 02:39:21 health("dns-os"): error: resolved DBus does not have a connection
2024/03/03 02:39:21 health("dns"): error: resolved DBus does not have a connection
2024/03/03 02:39:21 peerapi: serving on http://100.71.18.78:56851
2024/03/03 02:39:21 peerapi: serving on http://[fd7a:115c:a1e0::f6c7:124e]:50579
2024/03/03 02:39:22 magicsock: home is now derp-11 (sao)
2024/03/03 02:39:22 magicsock: endpoints changed: x.x.x.x:58752 (stun), 10.0.0.177:58752 (local), 172.x.x.1:58752 (local)
2024/03/03 02:39:22 control: NetInfo: NetInfo{varies=false hairpin=false ipv6=false ipv6os=true udp=true icmpv4=false derp=#11 portmap= link="" firewallmode="ipt-default"}
2024/03/03 02:39:22 magicsock: adding connection to derp-11 for home-keep-alive
2024/03/03 02:39:22 magicsock: 1 active derp conns: derp-11=cr0s,wr0s
2024/03/03 02:39:22 Switching ipn state Starting -> Running (WantRunning=true, nm=true)
2024/03/03 02:39:22 derphttp.Client.Connect: connecting to derp-11 (sao)
Some peers are advertising routes but --accept-routes is false
boot: 2024/03/03 02:39:22 Startup complete, waiting for shutdown signal
2024/03/03 02:39:22 magicsock: derp-11 connected; connGen=1
2024/03/03 02:39:29 [RATELIMIT] format("dns: dbus connection error: %v") (10 dropped)
2024/03/03 02:39:29 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:39:31 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:39:31 [RATELIMIT] format("dns: dbus connection error: %v")
2024/03/03 02:39:41 [RATELIMIT] format("dns: dbus connection error: %v") (2 dropped)
2024/03/03 02:39:41 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:39:46 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:39:51 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:39:55 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:40:01 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:40:06 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:40:11 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:40:18 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:40:27 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:40:34 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2024/03/03 02:40:40 dns: dbus connection error: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory

[cubimol]

This additional parameter fixes the error for me when I create the tailscale container:

... -v /var/run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket:ro ...