`borg.timer` needs to be both enabled and started with systemctl about borg-cron-helper HOT 5 CLOSED

@rugk I am happy to make the change if you like; I am not sure how much control you want over the project.

from borg-cron-helper.

So you are saying you need to start the timer once (even after getting enabled), before it runs?

If this is really the case, then yes, feel free to adjust the wiki. However, IMHO that behavior makes no sense at all for systemd and I did not test it right now, but the blog you linked also does not explicitly state that this systemctl start was really required?

So I'd really prefer a better source for that. I mean, are you sure this was really the thing that was causing/fixing the issue?

from borg-cron-helper.

So you are saying you need to start the timer once (even after getting enabled), before it runs?

Yes, at least on ubuntu 18.04.

but the blog you linked also does not explicitly state that this systemctl start was really required?

Are you sure? The first line under "Execution" is

Activate at boot and start the backup timer to get your website backed up every day:

Note the "and start" and the lack of any "Optional"

If you want other sources, https://wiki.archlinux.org/index.php/Systemd/Timers says, under "Management" (emphasis mine)

To use a timer unit enable and start it like any other unit (remember to add the .timer suffix). To view all started timers, run:

And yes, if I stop it, it disappears from the list of active timers and returns only when I start it (see below).

# systemctl list-timers | grep borg
Tue 2019-01-01 01:41:45 PST  18h left      Mon 2018-12-31 01:04:38 PST  5h 57min ago borg.timer                   borg.service
# systemctl stop borg.timer
# systemctl list-timers | grep borg
# systemctl start borg.timer
# systemctl list-timers | grep borg
Tue 2019-01-01 00:13:35 PST  17h left      Mon 2018-12-31 01:04:38 PST  5h 57min ago borg.timer                   borg.service

from borg-cron-helper.

Fixed in https://github.com/rugk/borg-cron-helper/wiki/How-to-setup%3F/be2916db7f19ee52bef503f3623a387b721dee8f

from borg-cron-helper.

Ah, I thought that start would trigger the command immediately, but it seems it only "triggers" the timer, i.e. enables it.

I can imagine, however, that instead of starting it manually a restart of the server would also work, as the enable command does "[e]nable a unit to be started on bootup" (acc. to Arch wiki).
(Maybe that is why I did not notice it.)

Anyway, thanks for fixing this in the wiki. 😄

from borg-cron-helper.