cron and run-parts system #206

New Issue

Closed

opened 2019-08-19 15:43:31 +00:00 by Asaln · 3 comments

Asaln commented 2019-08-19 15:43:31 +00:00

Copy Link

Can we create a cron job for the system and not for the root user. If I run a task with the root crontab, including using run-parts it goes well. But if I do exactly the same thing in /etc/cron.xxx with run-parts I have as a result:

---

/etc/cron.hourly/borgmatic:
Traceback (most recent call last):
File "/ root / bin / borgmatic", line 6, in
from borgmatic.commands.borgmatic import main
ModuleNotFoundError: No module named 'borgmatic'
run-parts: /etc/cron.hourly/borgmatic exited with return code 1

---

Running run-parts in a terminal with root works:

---

run-parts /etc/cron.hourly/.
/etc/borgmatic/config.yaml: Running command for pre-backup hook
Starting a backup job.
/ mnt / save / TEST: Pruning archives
.....

---

In two words it works with the root user but not for the system ...

Other notes / implementation ideas

Environment

borgmatic version: [version here]
Version: 1.3.14

borgmatic installation method: [e.g., Debian package, Docker container, etc.]
pip3 as official guide
Borg version: [version here]
borgbackup-1.2.0-0.a4.1.mga7

Python version: [version here]

Use python --version
Python 2.7.16

operating system and version: [OS here]
Mageia release 7 (Official) for x86_64

Can we create a cron job for the system and not for the root user. If I run a task with the root crontab, including using run-parts it goes well. But if I do exactly the same thing in /etc/cron.xxx with run-parts I have as a result: ****** /etc/cron.hourly/borgmatic: Traceback (most recent call last): File "/ root / bin / borgmatic", line 6, in <module> from borgmatic.commands.borgmatic import main ModuleNotFoundError: No module named 'borgmatic' run-parts: /etc/cron.hourly/borgmatic exited with return code 1 ******** Running run-parts in a terminal with root works: ******** run-parts /etc/cron.hourly/. /etc/borgmatic/config.yaml: Running command for pre-backup hook Starting a backup job. / mnt / save / TEST: Pruning archives ..... ********* In two words it works with the root user but not for the system ... #### Other notes / implementation ideas #### Environment **borgmatic version:** [version here] Version: 1.3.14 **borgmatic installation method:** [e.g., Debian package, Docker container, etc.] pip3 as official guide **Borg version:** [version here] borgbackup-1.2.0-0.a4.1.mga7 **Python version:** [version here] Use `python --version` Python 2.7.16 **operating system and version:** [OS here] Mageia release 7 (Official) for x86_64

witten commented 2019-08-19 16:50:12 +00:00

Owner

Copy Link

Thanks for filing the ticket! This might be a Python path issue. Try adding PYTHONPATH=/root/.local/lib/python3.7/site-packages or similar (your version of Python may vary) to your cron job. See this example for how to insert environment variables like that in your cron job command invocation: https://projects.torsion.org/witten/borgmatic/src/branch/master/sample/cron/borgmatic

Note that Python 2.x is unsupported. So the version of Python that borgmatic is using (if you installed with pip3) can most likely be found by running: python3 --version.

Let me know if that helps!

Thanks for filing the ticket! This might be a Python path issue. Try adding `PYTHONPATH=/root/.local/lib/python3.7/site-packages` or similar (your version of Python may vary) to your cron job. See this example for how to insert environment variables like that in your cron job command invocation: https://projects.torsion.org/witten/borgmatic/src/branch/master/sample/cron/borgmatic Note that Python 2.x is unsupported. So the version of Python that borgmatic is using (if you installed with pip3) can most likely be found by running: `python3 --version`. Let me know if that helps!

Asaln commented 2019-08-19 21:32:44 +00:00

Author

Copy Link

Thanks for the solution.
With run-parts and cron.daily etc. folders it is the same.
the PYTHONPATH variable can be added to a script in /etc/cron.daily (or other /etc/cron.xxx) in the same way. For example, for a default configuration:

PYTHONPATH=/root/.local/lib/python3.7/site-packages borgmatic --stats 2>&1

Thanks for the solution. With run-parts and cron.daily etc. folders it is the same. the PYTHONPATH variable can be added to a script in /etc/cron.daily (or other /etc/cron.xxx) in the same way. For example, for a default configuration: PYTHONPATH=/root/.local/lib/python3.7/site-packages borgmatic --stats 2>&1

Asaln closed this issue 2019-08-19 21:32:44 +00:00

witten added the

question / support

label 2019-08-19 22:02:10 +00:00

witten commented 2019-08-19 22:02:19 +00:00

Owner

Copy Link

Glad that worked out for you!

Glad that worked out for you!

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

2 Participants

Notifications

Subscribe

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#206

No description provided.