Open nh2 opened 2 years ago
journalctl -fu nix-daemon.service
shows:
Sep 28 17:18:29 t25 nix-daemon[328803]: accepted connection from pid 10271, user niklas (trusted)
And then no further output.
Doing Ctrl+C on the nix-copy-closure
results in daemon output:
Sep 28 17:20:57 t25 nix-daemon[10276]: 5 operations
Sep 28 17:20:57 t25 nix-daemon[10276]: unexpected Nix daemon error: writing to file: Broken pipe
systemctl restart nix-daemon.service
did not help.
Perhaps relevant:
# journalctl -eu nix-daemon.service
...
Sep 28 17:21:09 t25 systemd[1]: Stopping Nix Daemon...
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Succeeded.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Unit process 4173552 (nix-daemon) remains running after unit stopped.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Unit process 4173570 (ssh) remains running after unit stopped.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Unit process 4353 (nix-daemon) remains running after unit stopped.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Unit process 4364 (ssh) remains running after unit stopped.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Unit process 8841 (nix-daemon) remains running after unit stopped.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Unit process 8879 (ssh) remains running after unit stopped.
Sep 28 17:21:09 t25 systemd[1]: Stopped Nix Daemon.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Consumed 48.865s CPU time, no IO, received 970.3M IP traffic, sent 19.7M IP traffic.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Found left-over process 4173552 (nix-daemon) in control group while starting unit. Ignoring.
Sep 28 17:21:09 t25 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Found left-over process 4173570 (ssh) in control group while starting unit. Ignoring.
Sep 28 17:21:09 t25 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Found left-over process 4353 (nix-daemon) in control group while starting unit. Ignoring.
Sep 28 17:21:09 t25 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Found left-over process 4364 (ssh) in control group while starting unit. Ignoring.
Sep 28 17:21:09 t25 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Found left-over process 8841 (nix-daemon) in control group while starting unit. Ignoring.
Sep 28 17:21:09 t25 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Sep 28 17:21:09 t25 systemd[1]: nix-daemon.service: Found left-over process 8879 (ssh) in control group while starting unit. Ignoring.
Sep 28 17:21:09 t25 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Sep 28 17:21:09 t25 systemd[1]: Started Nix Daemon.
Rebooting the machine helped.
After doing that, nix works as normal:
locking path ...
lock acquired on ...
Thus I suspect something gets stuck in a way that systemd could not kill it.
I marked this as stale due to inactivity. → More info
possibly a duplicate of #3017
I just hit this on Nix 2.18.5. I had to manually delete the lock files in the Nix store.
After this, there is no further output, and
nix-copy-closure
hangs forever.Steps To Reproduce
Unsure, this is the first time I see it, but
Expected behavior
nix-env (Nix) 2.3.15
on NixOS 21.05