CrashPlan stopped backing up

[nolanid]

I'm running your CrashPlan backup docker container on a Synology DS918+. I set it up as new backup two weeks ago by following the instructions detailed in this video: https://www.youtube.com/watch?v=_8OMN08VQ6A. It was working fine, but then suddenly stopped. I've attached a photo of the CrashPlan dashboard. I've tried the following to fix it:

1. Increasing the memory limit of the container from 1GB to 2GB because my backup size is large (2TB)
2. Restarting the container,
3. Restarting the NAS and relogging into CrashPlan through the 192.168.124.1:xxxx where xxxx is the Local Port shown in docker. When I login through that IP address access, the Crash Plan login gives me two error messages on the login page (also attached).

I've also attached some of the log. Can you help me restart it? FYI: I'm not super technical, so appreciate the help.

Thank you

[jlesage]

For the inotify issue, see https://github.com/jlesage/docker-crashplan-pro#synology-1

What is the status of the backup as showed by the UI ? Looking at Tools->History may also provide some clue about what is happening.

[nolanid]

I got my the container to start again in September by increasing the memory, but now its stopped again and says” "CrashPlan exceeds inotify's max watch limit". I see some other comments about this in gitHub, but I don’t understand how to actually solve the problem. I’m not the most technical person in the world, but I can make things work with detailed instructions 😊 Do you have a link you can point me to? Thank you so much for your help with this. I love this solution. Just need to get it up and running again.

[nolanid]

Following up on my request above. I would greatly appreciate the help. Thank you so much

[jlesage]

You can get more details about the notify problem here: https://github.com/jlesage/docker-crashplan-pro#inotifys-watch-limit

However, this particular issue should not prevent the container from running.

[nolanid]

The Docker is still running, but no new data has been added to CrashPlan. I'm still trying to complete my initial backup. Its uploaded 845GB of 2.3TB selected. CrashPlan says that the last activity was 50 days ago. I ran the first command as indicated on the Code 42 site and your instructions (sudo nano /etc.defaults/sysctl.conf); however, it said that sudo: nano: command not found (see screen shot below). As mentioned above, I am not a coder, so I'm trying to figure this out with limited knowledge. :) You'll see in the image below that I tried a few other commands, none of which worked (they were guesses on my part). I used PuTTY for this. Do you have any suggestions? Thank you so much!

[nolanid]

Hello,

Any chance you can help with this? I'm stuck.

Thank you so much, Trevor

[jlesage]

nano is a text file editor that doesn't seem to be installed on your Synology. You probably need to use vi instead. I found this link, where it is explained how to use it: https://www.reddit.com/r/synology/comments/3jv6ov/changing_config_files_on_synology/

But again, I don't think the inotify issue is the cause of your backup not running. Did you have a look at Tools->History in CrashPlan ?

[nolanid]

Thank you so much for your response. I'd love to figure this out! I looked at History in CrashPlan, and it says "History log unavailable". I looked at the Log in Docker and it shows the inotify error and a recurring message about "Backtick: fatal: child process exited non-zero. Screen shots below. Any other thoughts?

[jlesage]

The history is accessible from the CrashPlan application UI itself (i.e. not from the https://www.crashplan.com website).

[nolanid]

I don’t have the CrashPlan application installed on the NAS (or on any PC) because I thought you couldn’t. Where would I access the UI if not through the website?

From: Jocelyn Le Sagemailto:notifications@github.com Sent: Monday, January 4, 2021 4:36 PM To: jlesage/docker-crashplan-promailto:docker-crashplan-pro@noreply.github.com Cc: nolanidmailto:nolanid@outlook.com; Authormailto:author@noreply.github.com Subject: Re: [jlesage/docker-crashplan-pro] CrashPlan stopped backing up (#264)

The history is accessible from the CrashPlan application UI itself (i.e. not from the https://www.crashplan.com website).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-crashplan-pro/issues/264#issuecomment-754079477, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ76A6NNQHRWRMCWW4EELADSYHU65ANCNFSM4RMF5WMA.

[jlesage]

Sorry, I'm probably not using the right words: the CrashPan app I'm talking about is the Docker container itself (the one you are running). This is the "CrashPlan UI".

You provided the following screenshot. This is where you need to go:

[nolanid]

Ok, that makes more sense :) I logged in and this is the first screen (its says its running, but when I look on www.crashplan.com, it says it hasnt run in 75 days. I also pasted the history below (it mentions that the upgrade failed. Could that be the issue? If so, how do I fix that?):

[jlesage]

Yes, having an up-to-date app would help. You need to update the Docker image. See https://github.com/jlesage/docker-crashplan-pro#docker-image-update

[nolanid]

I followed those steps and now the History says it was able to scan for files; however, it only found 2.4MB of files vs the 2.3TBs I have selected. Also, CrashPlan is now showing a second device on my account with the same name. I'm assuming that when I updated the docker, it created a new device on my account vs updating my existing backup. How can I merge these two (or remove the new one and get the old one to update)? Screen shots below. Thank you so much for your help. I feel like we're close to solving this.

[jlesage]

When you accessed the container after the update, were you asked for setup as a new device or adopt an existing one ?

If yes, then you probably don't have any mapping for /config. Without this, the CrashPlan config and states are not persistent.

[nolanid]

When I completed the steps you outlined (the last step was to restart the container), I thought I was done. I didnt go into the CrashPlan UI, so I wasnt asked to replace an existing device. Was I supposed to go into the CrashPlan UI after I restarted the container? I just went into the UI and it allowed me to do this. Hopefully it will work now. The History now says "Scanning for files to backup", so maybe it already is :)

[jlesage]

When you start from scratch, you do need to access the UI to start the adoption process.

So make sure you have configured a volume mapping for /config, else you will have to re-do the adoption process every time you update the container.

[nolanid]

Sorry to ask, but how do you configure a volume mapping? Also, how often do I need to update the container?

[jlesage]

The Synology interface has a "Volume" tab in the container settings. You probably already have touched this. For example:

CrashPlan provides updates to their app from time to time. The container image is updated accordingly. To ease your life, you can install the Watchtower docker container (https://github.com/containrrr/watchtower): this will automatically update your containers as soon as an image update is available.

[nolanid]

I found the Volume tab, but don't know how to create a volume mapping for /config. I tried to add a file and a folder, but I don't see config in any of my files or folders (see screen shots below)

Also, the only way I can get to the volume settings is by stopping the container and clicking Edit. I also don't see an Advanced Settings tab on mine. Is there a different way to access settings without stopping the container? See screen shot.

[jlesage]

The folder you select is a folder on your NAS. So you probably need to create a new one to store data of CrashPlan. Then, the associated "mount point" is the path inside the container. This one should be set to /config.

[nolanid]

Thanks again for your help. As you can tell (and I've already said), I'm sot super technical, so I'm trying to find my way through this. :) I setup a CrashPlan Data folder in the Docker folder in File Station (see image)
I then set this as the mount path for /config. Does it look correct? Do you need to see anything else to confirm? Here are my General Settings, in case that helps:

I also setup WatchTower, but had to run this line in PuTTY that I found on YouTube (I couldnt get it to work using the instructions in the link you sent): sudo docker run --name="watchtower" -d --restart=always -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower Hopefully its setup correctly.

[jlesage]

This looks good. You can disable executing container using high privilege, this is not needed.

watchtower setup should also be good.

[nolanid]

Great, thank you so much! Now I'll just wait and see if the backup starts running again. Just to be clear, now that I've enabled the watchtower container, I don't need to check for updates or do anything at all, correct? should just run on its own.

[jlesage]

Just make sure to open the CrashPlan UI to make sure everything is fine.

And yes, watchtower should take care of updating your containers.

[nolanid]

Hello again. I left the backup to run after we fixed the issues above; however, when I checked now, it shows that the backup set is 37MB, when it should be 2.2TB. When I go to Manage Files, it shows all of the correct files are selected. If I login to the crashplanpro website, it shows that the backup is complete with 0MB selected, though it still shows the 843MB that had backed-up previously (I pasted pictures below including the History) Do you have any idea why its not working properly? I'm at a loss. Thanks again for your support!

Here is the CrashPlan Pro interface and the history, which shows no activity since 13-Jan:

[nolanid]

Hello again. I wanted to follow-up on my note above. I'm hoping its a simple fix :)

[jlesage]

Looks like CrashPlan doesn't have the permission to read you files. In Manage Files, if you dig into your folders, are seeing the files ?

[nolanid]

Yes, it does show the files (see image below).

I also have an annoying issue where the UX times out after a minute or so and shows this:

[jlesage]

You last screenshot seems to indicate that CrashPlan is crashing.... Does the container's log show that the engine is restarting ?

[nolanid]

Here are two screen shots of today's log. Definitely looks like something is wrong, but I have no idea how to fix it.

[nolanid]

Do you have any suggestions on how to fix this issue? Thanks again for all of your help. I would be lost with it!

[jlesage]

Look at /config/log/service.log.0 inside the container. You should see recurring errors that might help determining what is the issue...

[nolanid]

Sorry for not being technical enough, but how do you look inside the container? I went into the container, terminal and then typed the command you pasted above, but nothing happened

[jlesage]

This is the path to the log file. If you prefer to examine this file outside the container, it is also accessible from your NAS under the directory you mapped to /config.

Else, from the terminal you opened, you can execute tail -f /config/log/service.log.0. Wait some time to see errors. Press ctrl+c to stop printing the content of the file.

[nolanid]

Hopefully I did this right. Does this help?

[jlesage]

Unfortunately no :( Can you access the file on the NAS instead? According to your previous screenshots, your should find it under docker/CrashPlan Data/log

[nolanid]

Do I access the files on the NAS through PuTTY? I tried and this is what it says:

Here are my terminal settings in Control Panel (not sure if that helps or not).

[PatGitMaster]

Add /volume1/ before that. All of the Synology shared folders are on your volume (whatever your volume name is).

[PatGitMaster]

[nolanid]

I tried this but it didnt work. I assume I missed something, but don't know what:

[PatGitMaster]

What jlesage is saying is the that file should be in this directory: /volume1/docker/CrashPlan Data/log

So try looking there: cd /volume1/docker/CrashPlan Data/log

In my system, where the directory name and casing is different from yours, this works:

[nolanid]

Thank you so much for the help, but its still not working for me. I'm not super technical, so I don't know if I'm doing what you said or not. I tried a few different ways:

[PatGitMaster]

Try changing directories a level at a time, such as: cd /volume1/docker ls -l

The cd to the right directory. Continue until you see "log". Then issue the tail command.

Note that my casing is different than what most folks choose.

[jlesage]

Maybe it could be easier to use the Synology File Station to download the file ?

[nolanid]

Tried this, but didnt work? How would I get it through File Station?

[nolanid]

I found this:

[jlesage]

Great, so you should be able to download service.log.0 to your PC and open it with a text editor. You can start from the bottom of the file and look for errors. The engine starts with STARTED Code42 Agent, so the problems causing the crash should appear prior to this message,

[nolanid]

Below is a screen shot of what the log shows. Does this help?

[jlesage]

Can you instead copy-paste the part of the log file into a new file and attach it to this issue ? I seem that a lot more more messages are needed.