[Errno 2] No such file or directory: 'borg' #114

New Issue

Closed

opened 2018-12-02 07:19:35 +00:00 by breyer · 6 comments

breyer commented 2018-12-02 07:19:35 +00:00

Copy Link

I've been struggling for a few days with the following error message when i start borgmatic via cron.

"[Errno 2] No such file or directory: 'borg'"

I can't figure out where the error is coming from. If I start borgmatic without cron, i don't get an error message.

I also use borgmatic on another server with the same configuration. Since the error does not occur there, i would assume that the problem has to do with the backup job.

Is there a way to narrow this down further?

Thank you
Mark

I've been struggling for a few days with the following error message when i start borgmatic via cron. "[Errno 2] No such file or directory: 'borg'" I can't figure out where the error is coming from. If I start borgmatic without cron, i don't get an error message. I also use borgmatic on another server with the same configuration. Since the error does not occur there, i would assume that the problem has to do with the backup job. Is there a way to narrow this down further? Thank you Mark

witten commented 2018-12-02 22:48:23 +00:00

Owner

Copy Link

Hi Mark,

I'm guessing that this problem is due to cron running by default without setting the PATH, or perhaps with an incorrect path, meaning that the Borg binary can't be found. My recommendation is to modify your borgmatic invocation via cron to include the appropriate system PATH, thereby allowing borgmatic to find Borg. Here's an example: https://projects.torsion.org/witten/borgmatic/src/branch/master/sample/cron/borgmatic

Your particular Borg binary location may be different than /usr/local/bin though. You can find it by running: which borg

Let me know if that works!

Hi Mark, I'm guessing that this problem is due to cron running by default without setting the PATH, or perhaps with an incorrect path, meaning that the Borg binary can't be found. My recommendation is to modify your borgmatic invocation via cron to include the appropriate system PATH, thereby allowing borgmatic to find Borg. Here's an example: https://projects.torsion.org/witten/borgmatic/src/branch/master/sample/cron/borgmatic Your particular Borg binary location may be different than `/usr/local/bin` though. You can find it by running: `which borg` Let me know if that works!

👍 1

witten added the

question / support

label 2018-12-02 22:48:29 +00:00

breyer commented 2018-12-02 22:52:12 +00:00

Author

Copy Link

bull's eye! The working server knowns the path to borg, the other not.
Thank you for your hint!

bull's eye! The working server knowns the path to borg, the other not. Thank you for your hint!

breyer closed this issue 2018-12-02 22:52:27 +00:00

witten commented 2018-12-02 22:52:47 +00:00

Owner

Copy Link

Cool, glad to hear that worked out!

Cool, glad to hear that worked out!

breyer reopened this issue 2018-12-02 22:53:13 +00:00

breyer commented 2018-12-02 22:54:23 +00:00

Author

Copy Link

Ahhrg. Sorry, tested this on the wrong server.
My problem server also knowns the path to the borg binary. But i will try your hint with the path variable in the cron job. I'll come back to you.

Ahhrg. Sorry, tested this on the wrong server. My problem server also knowns the path to the borg binary. But i will try your hint with the path variable in the cron job. I'll come back to you.

breyer commented 2018-12-03 00:23:32 +00:00

Author

Copy Link

Your mentioned hint with the PATH in the cronjob fixed my issue.
And again something learned.

Your mentioned hint with the PATH in the cronjob fixed my issue. And again something learned.

breyer closed this issue 2018-12-03 00:23:32 +00:00

witten commented 2018-12-03 03:02:20 +00:00

Owner

Copy Link

Great!

Great!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

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

No description provided.