adm122

I actually found the fix for it last night and corrected the issue. Crashplan has been working and running flawless ever since. Found 2 websites with some additional steps. One site says they fixed it on DSM 5.2 http://chrisnelson.ca/2015/05/12/fixing ... -2-update/ Seems to be the same steps as below Here are the steps that I followed from the comments section http://pcloadletter.co.uk/2012/01/30/cr ... /#comments This was a reply posted by someone named "Stephen" My Crashplan installation just stopped seemingly due to an update pushed out by Crashplan. I followed the steps that had previously been given when an update caused it to break but adjusted them for this release. I’ve copied them below incase anyone else experiences the same issue. You’ll need to be logged in as admin or sudo before the commands and in the final mv command you will need use the result from the ls command which will be a series of numbers: unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar *.jar -d /var/packages/CrashPlan/target/lib/ unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar run.conf -d /var/packages/CrashPlan/target/bin/ unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar lang/* -d /var/packages/CrashPlan/target/ ls -l /var/packages/CrashPlan/target/upgrade/1425276000420.* mv /var/packages/CrashPlan/target/upgrade/1425276000420.LS_RESULT/upgrade.sh /var/packages/CrashPlan/target/upgrade/1425276000420.LS_RESULT/upgrade.sh.old

Is anyone having a problem with there crashplan installation, it seems that crashplan has updated the GUI to v4.2. The package installed on DSM is v3.7 which goes into a stopped state and can't be restarted. Anyone else having this issue.