run under Windows #82

New Issue

henfri · 2018-07-28T20:49:55Z

henfri commented

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

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

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

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

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

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

Any luck with this?

witten closed this issue

2018-09-09 18:19:08 +00:00

witten referenced this issue from a commit