Can't access snapshot folder (because of permission problems?) on headiess server

Hi, this is the first time I try to configure and run BIT (v1.5.2 from git repo) on a headless server. I get the errors like that in the debug output: DEBUG: [common/snapshots.py:851 backup] Cannot start snapshot yet: target directory not accessible. Waiting 1s. INFO: [common/snapshots.py:861 Snapshots.backup] Waited 29 seconds for target directory to be available WARNING: [common/snapshots.py:866 Snapshots.backup] Can't find snapshots folder! I am assuming that my BIT config is correct, but I am not sure. I am assuming that my permissions are not correct. But they do look OK for me and I can create files and folders in it. backup@OLAF:/mnt$ ls -ld /mnt/Nerys drwxrwxr-x 4 admin backup 4096 18. Aug 13:26 /mnt/Nerys backup@OLAF:/mnt$ ls -l /mnt/Nerys insgesamt 20 drwx------ 2 root root 16384 17. Aug 17:23 lost+found backup@OLAF:/mnt$ touch /mnt/Nerys/foo backup@OLAF:/mnt$ mkdir /mnt/Nerys/bar backup@OLAF:/mnt$ ls -l /mnt/Nerys insgesamt 20 drwxr-xr-x 2 backup backup 4096 18. Aug 13:26 bar -rw-r--r-- 1 backup backup 0 18. Aug 13:32 foo drwx------ 2 root root 16384 17. Aug 17:23 lost+found Any ideas? Best Christian

That message appears to based on the result from Config.canBackup, which has a few conditions that can cause it to return False. Maybe putting some logging from within that can show which of those is causing it or why. Derek On Sunday, August 18th, 2024 at 4:33 AM, c.buhtz@posteo.jp <c.buhtz@posteo.jp> wrote:

Hello Derek, thank you for your reply. Am 18.08.2024 19:16 schrieb Derek via Bit-dev:
That message appears to based on the result from Config.canBackup, which has a few conditions that can cause it to return False.
I will take a look into it. I am assuming I didn't used the correct format for the "include" values. Just have an new PR about it in the making... ;) Best, Christian

Hello Derek, thank you for that tip. The problem was that the snapshot folder (hostname, username, profile nr) did not exist. When configuring BIT via GUI the GUI does create that folder structure. When editing the config file by yourself this does not happen. You have to run "backintime check-config --profile YOURS" once. Then it works. Anyway, I slightly modified the log output to make it more clear for the next user. Best Christian On 2024-08-18 17:16 Derek via Bit-dev <bit-dev@python.org> wrote:

That message appears to based on the result from Config.canBackup, which has a few conditions that can cause it to return False. Maybe putting some logging from within that can show which of those is causing it or why. Derek On Sunday, August 18th, 2024 at 4:33 AM, c.buhtz@posteo.jp <c.buhtz@posteo.jp> wrote:

Hello Derek, thank you for your reply. Am 18.08.2024 19:16 schrieb Derek via Bit-dev:
That message appears to based on the result from Config.canBackup, which has a few conditions that can cause it to return False.
I will take a look into it. I am assuming I didn't used the correct format for the "include" values. Just have an new PR about it in the making... ;) Best, Christian

Hello Derek, thank you for that tip. The problem was that the snapshot folder (hostname, username, profile nr) did not exist. When configuring BIT via GUI the GUI does create that folder structure. When editing the config file by yourself this does not happen. You have to run "backintime check-config --profile YOURS" once. Then it works. Anyway, I slightly modified the log output to make it more clear for the next user. Best Christian On 2024-08-18 17:16 Derek via Bit-dev <bit-dev@python.org> wrote:
participants (2)
-
c.buhtz@posteo.jp
-
Derek