New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd: 247.1 -> 247.2 #107067
systemd: 247.1 -> 247.2 #107067
Conversation
Contains the following fixes: - 937118a5b2 journalctl: don't skip the entries that have the same seqnum - e017ac6a26 sd-bus: use SOCK_CLOEXEC on one more socket - db31432861 resolved: create stub-resolv.conf symlink with correct security label - f2ec15e2e5 efi: Only use arm flags if supported - cd43eee770 core: detect_container() may return negative errno - 04be042a1f meson: Fix reallocarray check - 5e906f483b network: do not assume address ready callback is always set to static addresses - 2ad7a2a96a network: drop assertions to check link state in netlink callback handlers - f375c8cbb5 network: do not reconfigure interface when the link gains carrier but udev not initialized it yet - 5d4909decf veritysetup: also place udev socket dep - 57ddb74245 cryptsetup: Fix crypto device missing issue after bootup - d3c224d441 network: fix SIGABRT related to unreachable route with DHCP6 - c91648cc83 network: revert previous changes to address_compare_func() - d8b5d8c8c3 udev: Fix sound.target dependency - 669107ae68 meson: specify correct libqrencode version in meson dep - c07dc6cedc udev: link_update() should fail if the entry in symlink dir couldn't have been created - 367006c806 man: document that automount units are privileged - 5129808141 logind: fix closing of button input devices - 37f06c91ef Update logind-button.c - 9e9fda0a2d async: add trivial cleanup wrapper for asynchronous_close() - 4a2ca1ca4a Silence cgroups v1 read-only filesystem warning - ed1f8f4ba2 manager: Fix HW watchdog when systemd starts before driver loaded - 383a747164 cgroup: Also set blkio.bfq.weight - 48d41091ac nss-resolve: varlink_call() set error_id only when r >= 0 - 56daba2deb missing: Define several syscall numbers for Alpha arch - f2a4b96276 Don't assume /run/systemd exists when creating unit-root - 553530fdc7 mkosi: Add findutils to Fedora config - e42990dfe3 mkosi: Add rpm to Fedora BuildPackages as it's needed by pkg-config - 6bacd1d971 mkosi: Replace iptables-dev with libiptc-dev in debian config - f1fc515c21 dissect: don't declare unused variables on archs that have no GPT discovery - 30d0c3f58c resolved: synthesize NODATA instead of NXDOMAIN if gateway exists, but of other protocol - 538ebbd7f3 local-addresses: make returning accumulated list optional - 228a22bb63 resolved: improve log message when we use TCP a bit - aa31dd9128 network: ignore broadcast address for /31 or /32 addresses - 85607cc094 network: fix verification for broadcast address - dc6ad6482a network: do not set broadcast if prefixlen is 31 or 32 - 39ee319c75 stub: don't ever respond to datagrams coming in on non-localhost addreses, on the stub - cbea0e5a83 resolved: never allow _gateway lookups to go to the network - c4df66816b resolved: lower SERVFAIL cache timeout from 30s to 10s - b5e39c20d9 dns-domain: try IDN2003 rules if IDN2008 doesn't work - 2c354cedd2 virt: Properly detect nested UML inside another hypervisor - 10f2cfb715 resolved: properly check per-link NTA list - a8437c07e4 meson: use '_' as separator in fuzz test names - 81ef7623c8 man: mention that --key= is about *secret* keys - 4ef70ecefc meson: check that cxx variable is set before using it
I've updated all my systems and didn't encounter any issues. |
This appears to have broken systemd-resolved. |
In what sense? Do you have logs?
…On 18 December 2020 17:58:31 CET, TredwellGit ***@***.***> wrote:
This appears to have broken systemd-resolved.
--
You are receiving this because your review was requested.
Reply to this email directly or view it on GitHub:
#107067 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
DNS does not resolve via systemd-resolved. The logs are no different from when it worked. |
@TredwellGit can you get a bit more specific? What outputs do you get? How did you do the lookup? |
resolved likes to be broken. From my experience it's sometimes due to misconfigurations and dhcp, as it has a per interface dns server. |
Since there were changes related to resolved in 247.2 I would not dismiss it that quickly, but I can not reproduce the problem with a VM: vm.nix:
Test with 247.1:
Result: Test with 247.2:
Result: As you can see both versions worked. I tried deleting the state (nixos.qcow2) in between, or upgrading the state from 247.1 to 247.2 without changes to the result. Only once when I closed the qemu window very quickly after starting the VM, resolved failed to start on the next boot (as in the service failed and a big red status entry was shown at startup), but after another restart it worked again. |
|
Can you try dig via the resolved stub resolver? There might be some transient, dnssec-downgrade-related failure - but not sure how that regressed from 247.1...
|
127.0.0.53 should be the stub resolver. Or what do you mean? |
Yes, as in, how does dig @127.0.0.53 nixos.org behave, and what does resolved log while doing so.
|
The dig in my screenshot was already using 127.0.0.53 as server since it's in /etc/resolv.conf. So 127.0.0.53 does respond, but the glibc calls do not correctly resolve things. |
@TredwellGit was that patch reverted by Archlinux for now? |
Hm, Archlinux cherry-picked this before 247.2 was released, to fix a firefox crash? archlinux/svntogit-packages@8a4be64#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a |
@flokli No, it was cherry picked before, but the cherry pick got removed, because it got merged upstream. |
@MartinX3 considering the comment in systemd/systemd#18025 (comment), this seems to be only happening when systemd-resolved is enabled, and DNSOverTLS= is enabled too. Both aren't enabled by default in NixOS, so I'm not sure if it's too much of a regression for now. @petabyteboy could you reproduce the bug without setting |
from this config
DNSOverTLS should have been not set. So guess it was without TLS. |
|
I also have this issue now after the recent staging merge / systemd update. |
Please report in the upstream issue - this is not a NixOS-specific problem, and if this isn't only related to On the NixOS side of things, we could stop automatically enabling resolved when networkd is enabled to work this around (or figure out if certain resolved options migitate this), but upstream is where this should be fixed. I'm also not sure if reverting this single commit is a good idea, given it seems to fix a firefox crash: #107067 (comment) Really, the best way seems to be sorting this out upstream. |
Might be the upstream issue. I took a second look at the debug output of |
Does it only fail on a punycode domain?
|
Nope, also on ordinary domains. |
@xaverdh systemd changed some of their dependencies to become This is tracked in #107537. |
Contains the following fixes:
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)