!DBFhtjpqmJNENpLDOv:nixos.org

NixOS systemd

607 Members
NixOS ❤️ systemd172 Servers

Load older messages


SenderMessageTime
20 Jan 2025
@elvishjerricco:matrix.orgElvishJerriccoalso, if you feel like trying something nifty, you can try using magic-wormhole to send me the log. Just a bit nicer than matrix uploads.19:42:44
@iridium:faui2k11.deiridiumRelevant timestamps (approximate!): "restarting systemd..." at roughly 20:41:06. "Error: Failed to reset failed units" at roughly 20:41:20 (plusminus...).19:45:06
@elvishjerricco:matrix.orgElvishJerricco Ok I think the lots of Closing set fd 657 style messages indicate I was right about my hunch of the file descriptor pool thingymajig 19:47:49
@elvishjerricco:matrix.orgElvishJerriccotrying to remember what systemd calls that correctly so I can actually look it up :P19:48:14
@elvishjerricco:matrix.orgElvishJerricco iridium: https://systemd.io/FILE_DESCRIPTOR_STORE/ 19:49:39
@elvishjerricco:matrix.orgElvishJerriccothis19:49:40
@elvishjerricco:matrix.orgElvishJerriccothe "protocol error" makes me think there's something up with this store19:50:07
@elvishjerricco:matrix.orgElvishJerriccoit could be that the expected state of this store changes between releases19:50:20
@elvishjerricco:matrix.orgElvishJerriccoit could be that there's a bug in restoring the state after reexec19:50:30
@elvishjerricco:matrix.orgElvishJerricconot sure19:50:33
@iridium:faui2k11.deiridiumhm... Not sure if relevant in any way, but both systems I experienced this on have a bcachefs filesystem mounted19:50:35
@elvishjerricco:matrix.orgElvishJerriccoabsolutely that's relevant :P19:50:46
@elvishjerricco:matrix.orgElvishJerriccothis is exactly the kind of obscure bug I expect from bcachefs19:50:56
@iridium:faui2k11.deiridiumSorry! 🙂19:51:13
@iridium:faui2k11.deiridium (for one of the machines, it's not the root FS) 19:51:28
@elvishjerricco:matrix.orgElvishJerriccoit's reasonably likely not to be bcachefs's fault19:51:44
@elvishjerricco:matrix.orgElvishJerriccobut it's something to keep in mind for sure19:51:49
@elvishjerricco:matrix.orgElvishJerriccocan you tell me the exact nixpkgs revisions you were switching between, and share as much of your configuration, including the NFS mount, as you can?19:52:04
@iridium:faui2k11.deiridiumI'll ping you some details via dm, give me a sec19:52:29
@iridium:faui2k11.deiridiumMight be worth retrying this without the NFS share mounted, now that I can reproduce reliably19:52:58
@elvishjerricco:matrix.orgElvishJerriccoactually I was going to suggest we make a nixpkgs issue to track all this info19:53:01
@iridium:faui2k11.deiridiumsample size 1: did not reproduce the issue without the NFS mount19:55:26
@iridium:faui2k11.deiridium(reproduced ~8 times in a row with NFS mounted, no other differences I'm aware of)19:55:43
@elvishjerricco:matrix.orgElvishJerricconfs is another thing that causes all kinds of obscure bugs19:57:07
@iridium:faui2k11.deiridium second attempt, upgrade succeeded again. I'd be reasonably confident it's somehow NFS-related 19:58:00
@elvishjerricco:matrix.orgElvishJerriccoyea19:58:11
@elvishjerricco:matrix.orgElvishJerricco it's probably more about how systemd tracks the NFS mount 19:58:21
@iridium:faui2k11.deiridiumhttps://github.com/NixOS/nixpkgs/issues/375376 This also has the flake lockfiles from before/after the upgrade. Everything else you should know already.20:14:41
@iridium:faui2k11.deiridiumAh, and details about the NFS mounts 🙂20:14:53
@elvishjerricco:matrix.orgElvishJerriccothanks!20:19:42

Show newer messages


Back to Room ListRoom Version: 6