# Job Errors on 2nd Run
**URL:** https://forum.duplicati.com/t/job-errors-on-2nd-run/15803
**Category:** Support
**Created:** [March 2, 2023, 9:44am UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803 "2023-03-02T09:44:54Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@acidtranslate](https://forum.duplicati.com/u/acidtranslate)
#### Post date: [March 2, 2023, 9:44am UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/1 "2023-03-02T09:44:54Z")
Deployed Duplicate on an Unraid server.
Created first backup job and re-ran until it completed successfully, uploading to a S3-compatible cloud storage provider. The job backs up my own data stored on this server, as well as the containers I have running on this Unraid server too, i.e. their configs and other.
The job is configured to run weekly, but this fails.
If I try to manually run it, it also errors.
I am mostly confused because it has run successfully the first time. So I am not sure why it is now erroring.
These are the entries from the log file, under the “Warnings” section (note, not the “Error” section):
> “Warnings”: [
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/live/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/live/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/archive/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/archive/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/keys/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/keys/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/accounts/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/accounts/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/docker\_config/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/docker\_config/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/bin/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/bin/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/compose/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/compose/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/tls/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/tls/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/certs/”,
> “2023-02-14 20:35:12 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/portainer-ce/certs/”,
> “2023-02-14 20:35:38 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.FileEntry-PathProcessingFailed]: Failed to process path: /source/appdata/rclone/rclone.conf”,
> “2023-02-14 20:36:26 +00 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /source/appdata/Nginx-Proxy-Manager-Official/letsencrypt/live/”
However, I do not want to go in a disrupt a container’s filesystem permissions. Particularly the containers in question, it is their SSL cert keys which typically have owner-only RW permissions only.
---
### Author:  [@Lerrissirrel](https://forum.duplicati.com/u/Lerrissirrel)
#### Post date: [March 2, 2023, 2:40pm UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/2 "2023-03-02T14:40:35Z")
Welcome to the forum @acidtranslate !
Have you tried looking at those paths (/source/appdata/…) from within the Duplicati container? (“ls -l”) That will at least tell you what Duplicati is seeing and give some clue to what’s going on and why Duplicati can’t access those things. From there, hopefully, we can come up with a solution.
---
### Author:  [@acidtranslate](https://forum.duplicati.com/u/acidtranslate)
#### Post date: [March 2, 2023, 8:32pm UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/3 "2023-03-02T20:32:48Z")
Thanks @Lerrissirrel - and I should have thought of that myself…
```plaintext
root@06eaf3e440c7:/# ls -l /
total 96
drwxr-xr-x 1 abc users 18 Feb 11 10:19 app
drwxrwxrwx 1 1001 users 65 Feb 15 12:26 backups
drwxrwxrwx 1 abc users 99 Feb 5 20:30 source
```
There are more directories from the container. These are the volumes that are the source of the Duplicati backup job.
Otherwise, this is the standard Unraid config for this container image.
---
### Author:  [@gpatel-fr](https://forum.duplicati.com/u/gpatel-fr)
#### Post date: [March 2, 2023, 9:13pm UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/4 "2023-03-02T21:13:13Z")
Hello
a quick remark: let’s encrypt files are root-only on a normal computer. I don’t know about the other files, but maybe it’s related also to your backup running on a normal user account ? I don’t know Docker so feel free to dismiss my advice as irrelevant.
---
### Author:  [@acidtranslate](https://forum.duplicati.com/u/acidtranslate)
#### Post date: [March 2, 2023, 9:33pm UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/5 "2023-03-02T21:33:05Z")
Yes - this was my understanding too. These permissions are by design.
But how do you back this up? Or is it not necessary to, and upon redeploying this container, new certs would be generated?
---
### Author:  [@acidtranslate](https://forum.duplicati.com/u/acidtranslate)
#### Post date: [March 2, 2023, 9:44pm UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/6 "2023-03-02T21:44:28Z")
Docker has its history with running as root, but is mostly running in user space these days. However, I am brand new to Unraid, and it’s own internal config of Docker… Some of these permissions look odd, but as you say, it is sometimes dictated / recommended.
---
### Author:  [@gpatel-fr](https://forum.duplicati.com/u/gpatel-fr)
#### Post date: [March 2, 2023, 10:32pm UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/7 "2023-03-02T22:32:29Z")
If the Docker container is running as an ordinary user, I don’t see how it will be able to backup root files directly. That’s a general problem for any backup software. On a more standard computer, you need to run Duplicati as a systemd service (as root) or a Windows service to backup files belonging to another user(s).
IIRC there are mentions of bind mount in posts concerning Docker, so maybe a work around can be found.
---
### Author:  [@Lerrissirrel](https://forum.duplicati.com/u/Lerrissirrel)
#### Post date: [March 3, 2023, 12:12am UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/8 "2023-03-03T00:12:22Z")
> [@acidtranslate](#):
>
> `root@06eaf3e440c7:/# ls -l /`
Actually I was thinking of the specific files you were having trouble backing up vs the /source directory itself. But as you and @gpatel-fr are already discussing, it’s almost certainly a root ownership related problem. With luck you’ll be able to find lots of discussions on the web about allowing Docket containers’ OS to access root owned files from outside the container.
---
### Author:  [@ts678](https://forum.duplicati.com/u/ts678)
#### Post date: [March 3, 2023, 12:33am UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/9 "2023-03-03T00:33:11Z")
> [@acidtranslate](#):
>
> So I am not sure why it is now erroring.
I don’t use Docker either, but generic way to see more about the specific complaint is to use logging.
About → Show log → Live → Warning and click on them, or use Advanced options to have a log file.
[Job log summary due to exception should also include exception summary #4843](https://github.com/duplicati/duplicati/issues/4843)
is my pitch to make the default logs more informative. Second line often contains the “why” of errors.
I suppose you could also look at About → System info and see what `UserName` line says Duplicati is.
I don’t know if the launch method on 2nd run might have been different, resulting in low permissions.
---
### Author:  [@acidtranslate](https://forum.duplicati.com/u/acidtranslate)
#### Post date: [March 3, 2023, 3:58pm UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/10 "2023-03-03T15:58:49Z")
These log entries appear under “Warning” not “Error”.
I have seen some people changing the PUID and GUID values, but also that [LinuxServer.io](http://LinuxServer.io) specifically state not to do so.
This would seem a standard requirement for this SPECIFIC container, given its function…
---
### Author:  [@ts678](https://forum.duplicati.com/u/ts678)
#### Post date: [March 3, 2023, 4:35pm UTC](https://forum.duplicati.com/t/job-errors-on-2nd-run/15803/11 "2023-03-03T16:35:51Z")
> [@acidtranslate](#):
>
> This would seem a standard requirement for this SPECIFIC container, given its function…
I suppose you could look for a place to ask, but this person didn’t get very far…
[Duplicati cannot access some files](https://discourse.linuxserver.io/t/duplicati-cannot-access-some-files/1305)
[Duplicati’s container](https://hub.docker.com/r/duplicati/duplicati) runs as root, which is cruder (and more dangerous) but gets files better.
[Runtime privilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities) is possibly a finer-grained way to get what’s needed.
[Linux kernel capabilities](https://docs.docker.com/engine/security/#linux-kernel-capabilities) explains the idea behind this, and links to a man page with specifics:
[capabilities(7) — Linux manual page](https://man7.org/linux/man-pages/man7/capabilities.7.html)
Maybe this can do the job?
```
CAP_DAC_OVERRIDE
Bypass file read, write, and execute permission checks.
(DAC is an abbreviation of "discretionary access
control".)
```
EDIT:
but I’m not sure what user files would restore as by default. Inside-outside mapping is complex.
Just to do backup, you might need less, e.g.
```
CAP_DAC_READ_SEARCH
* Bypass file read permission checks and directory read
and execute permission checks;
```
[How can I ensure my backup user has access to all files created by arbitrary processes with arbitrary UMASK, users, groups, and permissions?](https://unix.stackexchange.com/questions/712051/how-can-i-ensure-my-backup-user-has-access-to-all-files-created-by-arbitrary-pro)
gets into this and more, without a clear answer. If you like, continue web searches for solutions,
or if you can find the right place, ask the LinuxServer folks how they think you should be usng it.