| 20 Jan 2025 |
 iridium | that specific stacktrace couldn't be less interesting tbh | 19:07:16 |
 @elvishjerricco:matrix.org | if it does, it'd be good to try booting the old generation, but adding systemd.log_level=debug to the kernel params from your boot menu, and then doing the upgrade | 19:07:39 |
| @elvishjerricco:matrix.org | those journal logs could be much more useful | 19:07:46 |
| iridium | Anything I should do with the machine right now, in case I don't manage to get it into exactly the same state again afterwards? | 19:08:11 |
| @elvishjerricco:matrix.org | not that I can think of unfortunately. | 19:08:33 |
| @elvishjerricco:matrix.org | iridium: last time you said you could reproduce it if you had an NFS and/or an SSHFS mounted. Was that the case this time? | 19:11:00 |
| iridium | NFS yes, sshfs no | 19:11:09 |
| iridium | NFS over wireguard, to be specific | 19:11:16 |
| @elvishjerricco:matrix.org | where is the NFS mounted? | 19:11:58 |
| iridium | Some folder in /mnt | 19:13:05 |
| iridium | reproduced it, let me skim the logs | 19:18:01 |
| iridium | I sent you the complete journal dump in private. I'm slightly confused by the fact that it no longer shows the "protocol error" message in the journal, but otherwise, the symptoms are pretty much similar | 19:22:21 |
| iridium | This is the output from nixos-switch: https://pastebin.com/raw/usHgRPJL | 19:23:26 |
| iridium | "restarting systemd" should be at ~20:15:40 in that log | 19:29:05 |
| @elvishjerricco:matrix.org | iridium: This log is not showing the same symptom | 19:31:53 |
| @elvishjerricco:matrix.org | The key line should be "Freezing execution" | 19:32:06 |
| @elvishjerricco:matrix.org | and it's not in there | 19:32:09 |
| @elvishjerricco:matrix.org | "Freezing execution" is how you know systemd is down and causes all the "no reply" things | 19:32:38 |
| @elvishjerricco:matrix.org | * "Freezing execution" is how you know systemd is down and causes all the "Did not receive a reply" things | 19:32:54 |
| iridium | Hmm, yes | 19:36:40 |
| iridium | Ah! I think that's because "Freezing execution" shows up quite a bit later | 19:37:38 |
| @elvishjerricco:matrix.org | it does? I grep'd the file and didn't see it | 19:37:53 |
| iridium | That's because I grabbed the log at the time when rebuild failed. Give me some time, I'll rebuild with debug again... | 19:38:51 |
| iridium | (I just retried without debugging enabled. "Freezing execution" happened 2min after the failed restart) | 19:39:23 |
| @elvishjerricco:matrix.org | oh really? | 19:39:29 |
| @elvishjerricco:matrix.org | that's very surprising | 19:39:31 |
| @elvishjerricco:matrix.org | iridium: This time, try to get the journal with -t systemd | 19:39:40 |
| @elvishjerricco:matrix.org | just to avoid the logspam | 19:39:44 |
| @elvishjerricco:matrix.org | we shouldn't need any other logs than systemd's | 19:39:53 |
| iridium | ack | 19:40:02 |
