Package Details: crashplan 4.6.0-7

Git Clone URL: (read-only)
Package Base: crashplan
Description: An online/offsite backup solution
Upstream URL:
Licenses: custom
Submitter: billyburly
Maintainer: justin8
Last Packager: justin8
Votes: 116
Popularity: 5.358381
First Submitted: 2011-09-17 03:06
Last Updated: 2016-04-21 23:46

Latest Comments

whstrain commented on 2016-04-29 15:25

I found a bunch of log files under /opt/crashplan/log that people might want to clean out. rm -f upgrade.*.log. Also, the content of the upgrade log file may lend some information about the failing upgrade process.

Thu Apr 28 17:29:23 EDT 2016 : Ensuring the UpgradeUI is not running.
Thu Apr 28 17:29:23 EDT 2016 : UpgradeUI is shut down.
Thu Apr 28 17:29:23 EDT 2016 : JAVACOMMON is set: /usr/bin/java
Thu Apr 28 17:29:23 EDT 2016 : Current Java Version: 1.8
Thu Apr 28 17:29:23 EDT 2016: The Current java is not compatible. Embedding a compatible version.
Thu Apr 28 17:29:23 EDT 2016 : Download JVM from

whstrain commented on 2016-04-29 13:04

The file was approximately 1435813200460_403.jar.
The folder was approximately 1435813200460.#############. I have a feeling the ??? is the epoch time the .jar was expanded but not sure.

justin8 commented on 2016-04-29 12:24

Do you happen to know the name of the file that was left?

There is no file locking like that in Linux, it would remever the pointer on disk and not overwrite it or free the space until the last handle is closed, but it will happily let you delete and replace in-use files

whstrain commented on 2016-04-29 12:10

I must not have been clear. The install scripts removed many (more than 15) of the update folders but left one; and the update source .jar file was left behind. Perhaps the ones left behind were in use at the time and the service should be stopped at the beginning.

justin8 commented on 2016-04-29 05:03

The .sh files in there are fine, they are part of the upstream package installation.

The install scripts will remove the leftover failed update files if they exist.

whstrain commented on 2016-04-28 22:13

Just installed the 4.6.0-7. Many decompressed update folders were removed but one was left, and the update source .jar file was left behind. Also there are now many .sh files in the upgrade folder. I had to chattr -i /opt/crashplan/upgrade/ and rm -rf * at the end. Works as good as ever.

whstrain commented on 2016-04-28 21:38

What build version is in 4.6.0-7? I still show 4.6.0 build 382.

UglyBob commented on 2016-04-28 17:30

Could be, but it restarts like every 30 seconds (repeated over and over) and I don't think I ever get my new files backed up. I see that there is a new version, so I will try to upgrade and see what happens...

tmoore commented on 2016-04-28 14:18

I see the same kill error, but I think it's benign.. It's basically seeing a leftover pid file and tries to kill a non-existing crashplan process before it restarts.

justin8 commented on 2016-04-28 08:48

What version of the package are you running? I haven't had any issues since the last couple updates.

All comments