vyos@vyos:~$ reboot at 04:00 Unit systemd-shutdownd.service could not be found. Shutdown is not scheduled
Description
Description
Details
Details
- Difficulty level
- Unknown (require assessment)
- Version
- 1.3-rolling-201912021432
- Why the issue appeared?
- Will be filled on close
- Is it a breaking change?
- Unspecified (possibly destroys the router)
- Issue type
- Bug (incorrect behavior)
Related Objects
Related Objects
Event Timeline
Comment Actions
[email protected]:~$ sh version Version: VyOS 1.3-rolling-201912040242 [email protected]:~$ reboot at 04:00 Shutdown scheduled for Thu 2019-12-05 04:00:00 UTC [email protected]:~$
Maybe we need to use "systemd-reboot" and "systemd-poweroff.service"?
root@1:/# systemctl status systemd-shutdownd.service Unit systemd-shutdownd.service could not be found. root@1:/# systemctl status systemd-reboot.service โ systemd-reboot.service - Reboot Loaded: loaded (/lib/systemd/system/systemd-reboot.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-halt.service(8) root@1:/# systemctl status systemd-poweroff.service โ systemd-poweroff.service - Power-Off Loaded: loaded (/lib/systemd/system/systemd-poweroff.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-halt.service(8)
Comment Actions
I agree. If it works in a way that is consistent with what the command promises, let's use it.
Comment Actions
In this case we can use /run/systemd/shutdown/scheduled file for detecting powertrl scheduler
PR for this task https://github.com/vyos/vyos-1x/pull/201
Comment Actions
All works, but seems we need works with timezone for correct converting USEC to "date time" format
vyos@GW1:~$ date Fri 10 Jan 2020 11:25:57 AM EET vyos@GW1:~$ reboot at 12:00 Reboot is scheduled 2020-01-10 10:00:00 vyos@GW1:~$ show reboot Reboot is scheduled 2020-01-10 10:00:00