#Crashplan upgrade failed Patch
#Crashplan upgrade failed upgrade

Now let's start the package again and the 'Failed to run the package service' will be shown. 2 minutes the log should show one last message 'Service stopped normally'

#Crashplan upgrade failed upgrade

Waiting 60 seconds for upgrade script to shutdown service. HISTORY:: Upgrade installed - version 1436674800482 Upgrade process has been started successfully, cmd=/bin/bash upgrade.sh, milliseconds=3 SystemCommandRunner run as async so handles have leaked. Upgrade running command, cmd=/bin/bash upgrade.shĮXEC:: executeCommand(). HISTORY:: Installing upgrade - version 1436674800482

#Crashplan upgrade failed Patch

MD5 checksum matches, continuing with patch HISTORY:: Download of upgrade complete - version 1436674800482. HISTORY:: Downloading a new version of CrashPlan.ĭOWNLOAD:: Transferring patch at /linux/upgrade/crashplan/1436674800482_4.jar DownloadManager, patchProblem = false]įT::Client-tid=794090999109596468, guid=42 START. Now running 4.8.2, synchronising to CP Central and my laptop is backing up to the NAS.īased on the additional comments on the mentioned blog-post and my own experience I followed the following steps to get it back to business again.

I 05/06/17 10:16AM Synology extracting upgrade from /var/packages/CrashPlan/target/upgrade/1436674800482_4.jarĪccording to the discussion on the package owners blog post, this seems to be an issue with a missing cpio. I 05/02/17 04:58PM CrashPlan stopped, version 4.8.0, GUID XXXXXXXXXXXXXXXXX I 05/02/17 04:30PM Downloading a new version of CrashPlan.