volume1/docker/appdata/crashplan-pro10/log/service.log.0 <<< Doesn’t appear to have been used since CrashPlan was originally installed, appears to be legacy/old <<< NEW files (time/date for last night prior to <<< NEW files (time/date for last am working on the assumption that the ‘NEW’ files noted above should actually be in the ‘/volume1/docker/appdata/crashplan-pro10/…. After countless cycles of Crashplan breaking and finding new ways to repair it on two different NASes over several years, Ive moved completely over to a Docker-based installation.

Once stopped click on Edit then check Enable auto restart then OK and START the Crashplan container again. I did a search for the log files as I am seeing issues with permissions, and found the config folders find / -name service.log.0 -print Go back to the Synology interface and go to: Docker > Container > Crashplan > Details > Terminal > Create > Bash and type the following: cat /var/lib/crashplan/.uiinfo Next, go to Docker > Container > Crashplan and STOP the container. This appears to have got everything running again, however, I think you are correct regarding the mapping of /config. I ran through the notes on the CrashPlan site - specifically section 3.

Yes, I have done some checking and it looks like there is no mapping for /config.

Crashplan synology 2020