sudo numa terminates with error #45

New Issue

2026-04-08T23:30:48+08:00

xplosionmind commented

2026-04-08 23:30:48 +08:00

(Migrated from github.com)

Before running sudo numa install I wanted to test the software, but it it not working. This is what I get when I run sudo numa:

sudo numa
[2026-04-08T13:35:07.338Z INFO  numa::config] config not found, using defaults (create /home/tommi/.config/numa/numa.toml)
[2026-04-08T13:35:07.359Z INFO  numa::system_dns] forwarding .hro.nl to 145.24.129.201
[2026-04-08T13:35:07.359Z INFO  numa::system_dns] forwarding .hr.nl to 145.24.129.201
[2026-04-08T13:35:07.359Z INFO  numa::system_dns] detected 2 search domain forwarding rules
[2026-04-08T13:35:07.359Z INFO  numa] could not detect system DNS, falling back to Quad9 DoH
[2026-04-08T13:35:07.360Z INFO  numa::tls] generated CA at "/usr/local/var/numa/ca.pem"
[2026-04-08T13:35:07.361Z INFO  numa::tls] generated TLS cert for: numa.numa
[2026-04-08T13:35:07.361Z INFO  numa::tls] TLS configured for 1 .numa domains
Error: Os { code: 98, kind: AddrInUse, message: "Address in use" }

Before running `sudo numa install` I wanted to test the software, but it it not working. This is what I get when I run `sudo numa`: ``` sudo numa [2026-04-08T13:35:07.338Z INFO numa::config] config not found, using defaults (create /home/tommi/.config/numa/numa.toml) [2026-04-08T13:35:07.359Z INFO numa::system_dns] forwarding .hro.nl to 145.24.129.201 [2026-04-08T13:35:07.359Z INFO numa::system_dns] forwarding .hr.nl to 145.24.129.201 [2026-04-08T13:35:07.359Z INFO numa::system_dns] detected 2 search domain forwarding rules [2026-04-08T13:35:07.359Z INFO numa] could not detect system DNS, falling back to Quad9 DoH [2026-04-08T13:35:07.360Z INFO numa::tls] generated CA at "/usr/local/var/numa/ca.pem" [2026-04-08T13:35:07.361Z INFO numa::tls] generated TLS cert for: numa.numa [2026-04-08T13:35:07.361Z INFO numa::tls] TLS configured for 1 .numa domains Error: Os { code: 98, kind: AddrInUse, message: "Address in use" } ```

razvandimescu commented

2026-04-08 23:55:16 +08:00

(Migrated from github.com)

Hi @xplosionmind thanks for reporting this!
Your systemd-resolved probably holds port 53 and the current tests mostly ran on other ports to dodge the sudo nudges

You could use this workaround for avoiding sudo until i come back with a proper fix

mkdir -p ~/.config/numa
cat > ~/.config/numa/numa.toml <<EOF
[server]
bind_addr = "127.0.0.1:5354"
api_port = 5380
EOF

numa

And in another terminal

dig @127.0.0.1 -p 5354 google.com
open

I'll post the pr here once it's ready

Hi @xplosionmind thanks for reporting this! Your systemd-resolved probably holds port 53 and the current tests mostly ran on other ports to dodge the sudo nudges You could use this workaround for avoiding sudo until i come back with a proper fix ``` mkdir -p ~/.config/numa cat > ~/.config/numa/numa.toml <<EOF [server] bind_addr = "127.0.0.1:5354" api_port = 5380 EOF numa ``` And in another terminal ```sh dig @127.0.0.1 -p 5354 google.com open ``` I'll post the pr here once it's ready

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dearsky/numa#45

sudo numa terminates with error #45

`sudo numa` terminates with error #45