Having an issue where when I rebuild all the .target operations fail to start and timeout? I see it says that it could be a network issue but I have tried various setups, tethering, vpn, changing dns settings etc and it still happens. I am unsure how to actually diagnose and reslove this issue. Would appreciate any help etc, with doing so.
Have also rebooted etc.
🕙 10:42:58 zsh ❯ sudo nixos-rebuild switch --flake .
warning: Git tree '/home/martin/.dotfiles' is dirty
building the system configuration...
warning: Git tree '/home/martin/.dotfiles' is dirty
evaluation warning: The option `services.xserver.displayManager.defaultSession' defined in `/nix/store/qwp1716v59yrqzfafr8p1vraikar3waq-source/nix/modules/x11.nix' has been renamed to `services.displayManager.defaultSession'.
activating the configuration...
reloading user units for martin...
restarting sysinit-reactivation.target
Failed to restart sysinit-reactivation.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
starting the following units: local-fs.target, remote-fs.target
Failed to start sockets.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start graphical.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start smartcard.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start cryptsetup.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start swap.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start multi-user.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start getty.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start sysinit.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start timers.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start tpm2.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start remote-fs.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start virt-guest-shutdown.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start paths.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start machines.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to start basic.target: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
the following new units were started: home-manager-martin.service, libvirtd.service, local-fs.target, NetworkManager-dispatcher.service, remote-fs.target, sysinit-reactivation.target, systemd-coredump@13-16638-0.service, systemd-tmpfiles-resetup.service, tailscale-autoconnect.service
warning: error(s) occurred while switching to the new configuration