borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 54 Pull Requests 1 Actions Packages Releases 121 Activity

systemd service from repo broken #275

New Issue
Closed
opened 2020-01-01 13:57:21 +00:00 by tilllt · 5 comments
tilllt commented 2020-01-01 13:57:21 +00:00
Copy Link

What I'm trying to do and why

install system service and timer

Steps to reproduce (if a bug)

follow documentation on borgmatic website

Include (sanitized) borgmatic configuration files if applicable.

Actual behavior (if a bug)

[/etc/systemd/system/borgmatic.service:18] Unknown lvalue 'LogRateLimitIntervalSec' in section 'Service'

Jan 01 14:48:39 systemd[1]: [/etc/systemd/system/borgmatic.service:21] Executable path is not absolute, ignoring: sleep 1m

Jan 01 14:48:39 systemd[1]: [/etc/systemd/system/borgmatic.service:22] Executable path is not absolute, ignoring: systemd-inhibit --who=

Jan 01 14:48:39 systemd[1]: borgmatic.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.

Expected behavior (if a bug)

service and timer should work

#### What I'm trying to do and why install system service and timer #### Steps to reproduce (if a bug) follow documentation on borgmatic website Include (sanitized) borgmatic configuration files if applicable. #### Actual behavior (if a bug) [/etc/systemd/system/borgmatic.service:18] Unknown lvalue 'LogRateLimitIntervalSec' in section 'Service' Jan 01 14:48:39 systemd[1]: [/etc/systemd/system/borgmatic.service:21] Executable path is not absolute, ignoring: sleep 1m Jan 01 14:48:39 systemd[1]: [/etc/systemd/system/borgmatic.service:22] Executable path is not absolute, ignoring: systemd-inhibit --who= Jan 01 14:48:39 systemd[1]: borgmatic.service: Service lacks both ExecStart= and ExecStop= setting. Refusing. #### Expected behavior (if a bug) service and timer should work
witten commented 2020-01-02 01:18:45 +00:00
Owner
Copy Link

Thank you for reporting this. Do you know what version of systemd/journald you're using? It appears that the LogRateLimitIntervalSec option at the Service level was added back in 2018, and possibly released in systemd version 240. You can check your systemd version with journalctl like this:

journalctl --version

If you have an old version of systemd, that could explain why the LogRateLimitIntervalSec option isn't working. You could just omit the option, or set it globally (but then it would affect more than just borgmatic). Or, if possible, upgrade systemd.

Let me know if that's it!

As for the other two errors, I've just switched the sample systemd configuration file to use absolute paths.

Thank you for reporting this. Do you know what version of systemd/journald you're using? It appears that the `LogRateLimitIntervalSec` option at the `Service` level was [added back in 2018](https://github.com/systemd/systemd/pull/10308), and possibly released in [systemd version 240](https://github.com/systemd/systemd/releases?after=v242-rc1). You can check your systemd version with journalctl like this: ```bash journalctl --version ``` If you have an old version of systemd, that could explain why the `LogRateLimitIntervalSec` option isn't working. You could just omit the option, or set it globally (but then it would affect more than just borgmatic). Or, if possible, upgrade systemd. Let me know if that's it! As for the other two errors, I've just switched the sample systemd configuration file to use absolute paths.
tilllt commented 2020-01-02 08:48:31 +00:00
Author
Copy Link

Didnt have time to investigate further, just a quick update on the SystemD version:
systemd 232 (this is a regular Debian Stretch install)

Didnt have time to investigate further, just a quick update on the SystemD version: systemd 232 (this is a regular Debian Stretch install)
witten commented 2020-01-02 18:09:57 +00:00
Owner
Copy Link

Look like that version's from March 2017. What I did was add a comment to the sample borgmatic systemd recommend that the option can be removed with older versions of systemd. (However, systemd may rate-limit borgmatic logs without the option.)

Hope that helps! Thanks again for filing this.

Look like that version's from March 2017. What I did was add a comment to the sample borgmatic systemd recommend that the option can be removed with older versions of systemd. (However, systemd may rate-limit borgmatic logs without the option.) Hope that helps! Thanks again for filing this.
alexzorin commented 2020-01-22 00:02:51 +00:00
Copy Link

The change to absolute paths (24e1516ec5) causes borgmatic.service to no longer work on Debian-based distros, where both sleep and systemd-inhibit are found in /bin rather than /usr/bin.

Can anybody think of a way to make this more cross-platform with Environment= or something? Or /usr/bin/env sleep 1m?

The change to absolute paths (https://projects.torsion.org/witten/borgmatic/commit/24e1516ec50b73df7612862f95f4bff956268445) causes `borgmatic.service` to no longer work on Debian-based distros, where both `sleep` and `systemd-inhibit` are found in `/bin` rather than `/usr/bin`. Can anybody think of a way to make this more cross-platform with `Environment=` or something? Or `/usr/bin/env sleep 1m`?
witten commented 2020-01-22 00:10:26 +00:00
Owner
Copy Link

I've just reverted that changeset. According to the systemd docs, absolute paths are not required. So let's not use them if they're causing cross-distro problems!

I appreciate you mentioning this.

I've just reverted that changeset. According to the [systemd docs](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Command%20lines), absolute paths are not required. So let's not use them if they're causing cross-distro problems! I appreciate you mentioning this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
spot-check
1.8.10
1.8.9
1.8.8
1.8.7
1.8.6
1.8.5
1.8.4
1.8.3
1.8.2
1.8.1
1.8.0
1.7.15
1.7.14
1.7.13
1.7.12
1.7.11
1.7.10
1.7.9
1.7.8
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.6
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.24
1.5.23
1.5.22
1.5.21
1.5.20
1.5.19
1.5.18
1.5.17
1.5.16
1.5.15
1.5.14
1.5.13
1.5.12
1.5.11
1.5.10
1.5.9
1.5.8
1.5.7
1.5.7.dev0
1.5.6
1.5.5
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.22
1.4.21
1.4.20
1.4.19
1.4.18
1.4.17
1.4.16
1.4.15
1.4.14
1.4.13
1.4.12
1.4.11
1.4.10
1.4.9
1.4.8
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.26
1.3.25
1.3.24
1.3.23
1.3.22
1.3.21
1.3.20
1.3.19
1.3.18
1.3.17
1.3.16
1.3.15
1.3.14
1.3.13
1.3.12
1.3.11
1.3.10
1.3.9
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
1.2.18
1.2.17
1.2.16
1.2.15
1.2.14
1.2.13
1.2.12
1.2.11
1.2.10
1.2.9
1.2.8
1.2.7
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.15
1.1.14
1.1.13
1.1.12
1.1.11
1.1.10
1.1.9
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.3
1.0.2
1.0.1
1.0.0
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.0.7
0.0.6
0.0.5
0.0.4
0.0.3
0.0.2
Labels
Clear labels   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#275
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?