`reboot` command stopped working but `systemctl reboot` still works

After creating a very large NixOS configuration for my server, after some time, the reboot command stopped working. However, the systemctl reboot command still works. Anyone got any idea what could cause this behavior? Tried googling for it but have not found any relevant results so far.

Some relevant logs?

sep 24 22:52:14 dominix sshd[3495]: Connection from 10.10.10.101 port 39426 on 10.10.10.12 port 22 rdomain ""
sep 24 22:52:14 dominix sshd[3495]: Accepted key ED25519 SHA256:GhfXWuCw1WjupJ61wD4PZkF8uIrx6NRvE3BUJBqddXQ found at /etc/ssh/authorized_keys.d/root:2
sep 24 22:52:14 dominix sshd[3495]: Postponed publickey for root from 10.10.10.101 port 39426 ssh2 [preauth]
sep 24 22:52:14 dominix sshd[3495]: Accepted key ED25519 SHA256:GhfXWuCw1WjupJ61wD4PZkF8uIrx6NRvE3BUJBqddXQ found at /etc/ssh/authorized_keys.d/root:2
sep 24 22:52:14 dominix sshd[3495]: Accepted publickey for root from 10.10.10.101 port 39426 ssh2: ED25519 SHA256:GhfXWuCw1WjupJ61wD4PZkF8uIrx6NRvE3BUJBqddXQ
sep 24 22:52:14 dominix sshd[3495]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
sep 24 22:52:14 dominix systemd-logind[1619]: New session 4 of user root.
sep 24 22:52:14 dominix systemd[1]: Started Session 4 of User root.
sep 24 22:52:14 dominix sshd[3495]: Starting session: command on pts/0 for root from 10.10.10.101 port 39426 id 0
sep 24 22:52:18 dominix postfix/smtpd[3215]: warning: unknown[46.148.40.84]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
sep 24 22:52:18 dominix postfix/smtpd[3215]: lost connection after AUTH from unknown[46.148.40.84]
sep 24 22:52:18 dominix postfix/smtpd[3215]: disconnect from unknown[46.148.40.84] ehlo=1 auth=0/1 rset=1 commands=2/3
sep 24 22:52:18 dominix rspamd[2548]: <da5256>; milter; rspamd_milter_process_command: got connection from 46.148.40.84:11776
sep 24 22:52:18 dominix rspamd[2548]: <da5256>; proxy; proxy_milter_finish_handler: finished milter connection
sep 24 22:52:18 dominix systemd[1]: Received SIGTERM from PID 3572 (reboot).
sep 24 22:52:18 dominix systemd[1]: Reexecuting.
sep 24 22:52:18 dominix systemd[1]: systemd 253.6 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)
sep 24 22:52:18 dominix systemd[1]: Detected architecture x86-64.
sep 24 22:52:18 dominix prometheus-backup-exporter-start[1810]: 127.0.0.1 - - [24/Sep/2023 22:52:18] "GET /metrics HTTP/1.1" 200 722
sep 24 22:52:19 dominix systemd[1]: bpf-lsm: LSM BPF program attached
sep 24 22:52:19 dominix systemd[1]: acme-radicale.grug.service: RuntimeMaxSec= has no effect in combination with Type=oneshot. Ignoring.
sep 24 22:52:19 dominix systemd[1]: acme-prometheus.grug.service: RuntimeMaxSec= has no effect in combination with Type=oneshot. Ignoring.
sep 24 22:52:19 dominix systemd[1]: acme-influxdb.grug.service: RuntimeMaxSec= has no effect in combination with Type=oneshot. Ignoring.
sep 24 22:52:19 dominix systemd[1]: acme-grafana.grug.service: RuntimeMaxSec= has no effect in combination with Type=oneshot. Ignoring.
sep 24 22:52:19 dominix systemd[1]: acme-gitea.grug.service: RuntimeMaxSec= has no effect in combination with Type=oneshot. Ignoring.
sep 24 22:52:19 dominix systemd[1]: acme-dominix.blocky.grug.service: RuntimeMaxSec= has no effect in combination with Type=oneshot. Ignoring.


1 Like

What do you mean it “stopped working”? What does it say when you try it?

It does not do anything at all. No stdout or anything. When I run systemctl reboot, the system immediately starts to shut down. I reinstalled my server yesterday and this behavior was still there on a clean installation. Therefore, I assume it must have something to do with my configuration.

Did you find a solution to this? I have the same problem with my system.

No. So far I have just been happily typing systemctl reboot and pretended as if it is raining. :slight_smile:

Do you have busybox installed? That was the culprit for me.

1 Like