run under Windows #82

New Issue

Closed

opened 2018-07-28 20:49:55 +00:00 by henfri · 5 comments

henfri commented 2018-07-28 20:49:55 +00:00

Copy Link

Hello,

I am running borgmatic under Windows successfully on one machine.

on the other machine I get:

stoffers@StoffersPC:~$ sudo borgmatic -v 2
Ensuring legacy configuration is upgraded
/etc/borgmatic/config.yaml: Parsing configuration file
Since version 1.1.16, if you provide archive_name_format, you should also specify consistency.prefix.
/etc/borgmatic/config.yaml: No commands to run for pre-backup hook
/mnt/c/test: Pruning archives
borg prune /mnt/c/test --keep-within 3H --keep-hourly 24 --keep-daily 7 --keep-weekly 4 --keep-monthly 24 --keep-yearly 100 --prefix LaptopHen --remote-path borg --umask 77 --debug --stats --list
/etc/borgmatic/config.yaml: No commands to run for on-error hook
[Errno 13] Permission denied

As I am using -v 2 already:
how can I determine, what file cannot be accessed?

Regards,
Hendrik

Hello, I am running borgmatic under Windows successfully on one machine. on the other machine I get: >stoffers@StoffersPC:~$ sudo borgmatic -v 2 Ensuring legacy configuration is upgraded /etc/borgmatic/config.yaml: Parsing configuration file Since version 1.1.16, if you provide `archive_name_format`, you should also specify `consistency.prefix`. /etc/borgmatic/config.yaml: No commands to run for pre-backup hook /mnt/c/test: Pruning archives borg prune /mnt/c/test --keep-within 3H --keep-hourly 24 --keep-daily 7 --keep-weekly 4 --keep-monthly 24 --keep-yearly 100 --prefix LaptopHen --remote-path borg --umask 77 --debug --stats --list /etc/borgmatic/config.yaml: No commands to run for on-error hook [Errno 13] Permission denied As I am using -v 2 already: how can I determine, what file cannot be accessed? Regards, Hendrik

henfri commented 2018-07-28 20:51:29 +00:00

Author

Copy Link

Ubuntu under windows in fact:
https://www.microsoft.com/en-us/p/ubuntu/9nblggh4msv6?activetab=pivot%3aoverviewtab

Ubuntu under windows in fact: https://www.microsoft.com/en-us/p/ubuntu/9nblggh4msv6?activetab=pivot%3aoverviewtab

henfri closed this issue 2018-07-28 20:51:29 +00:00

henfri commented 2018-07-28 20:52:01 +00:00

Author

Copy Link

Sorry, I did not want to close this issue.

Sorry, I did not want to close this issue.

henfri reopened this issue 2018-07-28 20:52:04 +00:00

witten added the

question / support

label 2018-07-28 21:05:28 +00:00

witten commented 2018-07-28 21:11:26 +00:00

Owner

Copy Link

Based on your output, it appears that the borg prune command is failing with a permission error, an "on error" hook is skipped (because there isn't one), and then borgmatic exits. So a couple of ideas for debugging:

• Run the prune command manually in the same console you're running borgmatic in: borg prune /mnt/c/test --keep-within 3H --keep-hourly 24 --keep-daily 7 --keep-weekly 4 --keep-monthly 24 --keep-yearly 100 --prefix LaptopHen --remote-path borg --umask 77 --debug --stats --list .. And then see if the borg command alone gives a more useful error.
• Make sure your user has permissions to read /mnt/c/test.

Hope that helps.

Based on your output, it appears that the `borg prune` command is failing with a permission error, an "on error" hook is skipped (because there isn't one), and then borgmatic exits. So a couple of ideas for debugging: * Run the prune command manually in the same console you're running borgmatic in: `borg prune /mnt/c/test --keep-within 3H --keep-hourly 24 --keep-daily 7 --keep-weekly 4 --keep-monthly 24 --keep-yearly 100 --prefix LaptopHen --remote-path borg --umask 77 --debug --stats --list` .. And then see if the `borg` command alone gives a more useful error. * Make sure your user has permissions to read `/mnt/c/test`. Hope that helps.

henfri commented 2018-07-29 17:25:35 +00:00

Author

Copy Link

Hello,

thanks for your hints.
I will try that. I currently have no access to the machine, but I will try again in a week.

Regards,
Hendrik

Hello, thanks for your hints. I will try that. I currently have no access to the machine, but I will try again in a week. Regards, Hendrik

witten commented 2018-08-12 20:53:06 +00:00

Owner

Copy Link

Any luck with this?

Any luck with this?

witten closed this issue 2018-09-09 18:19:08 +00:00

witten referenced this issue from a commit 2024-03-04 21:51:15 +00:00

Support for NO_COLOR environment variable (#835).

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

No description provided.