Crashplan stopped working
Crashplan stopped working and filled up the hard drive on Amahi 7 because it needed Java 1.7 (see attachment). I upgraded to Amahi 8 and installed Crashplan but I'm unable to start the Crashplan Desktop to configure the backup service (installer log is attached).
#2 Updated by bigfoot65 about 5 years ago
- Status changed from New to Feedback
- Assignee set to ceayuso
Have been looking at the Amahi 8 CrashPlan application and it appears to work. However, as mentioned only with Java 1.7.
In order to get it working again, you will need to remove any Java 1.8 packages installed. You can do the following as root user:
yum list "java-1.8*"
Then anything installed that is 1.8, remove it via:
yum erase "java-1.8*"
Once done, you will need to uninstall CrashPlan and then reinstall. Check /var/log/amahi-app-installer.log for errors.
If you did a new Amahi 8 install, this should work. If you did an upgrade from Amahi 7 to 8, there may be other issues.
Please report back your experience.
#4 Updated by ceayuso about 5 years ago
I did the update from 7 to 8. No errors in the log. The only possible issue is that Crashplan tried and failed to upgrade to a newer version when I started the desktop. It is set to try again in 1 hour. This is what filled up the hard drive when I was on Amahi 7 because Crashplan kept writing upgrade files to the hard drive until it was full. I'll keep an eye on it.
#6 Updated by bigfoot65 about 5 years ago
Did you install the application in Amahi 8 or was it left from the Amahi 7 to 8 upgrade?
Have you tried uninstalling the app, then reinstalling?
This is a very finicky application in Linux and hard to get working correctly. The version you see on the Amahi app is what it's supposed to upgrade to automatically.
Odd that it's not doing so.
#12 Updated by bigfoot65 about 5 years ago
What do you mean? The service appears to be running. What is the output of:
systemctl status crashplan
If it shows running, then the server is working as designed.
There are manual steps you will need to complete to setup the clients as noted in the wiki guidance: https://wiki.amahi.org/index.php/Crashplan#Amahi_8_.28Fedora_21.29
The guidance is somewhat different that it was for Amahi 7. I presume it's due to the newer version.
#13 Updated by ceayuso about 5 years ago
I use Crashplan Desktop to link to my account and configure the backups. It looks like the service is running.$ systemctl status -l crashplan
- crashplan.service - LSB: CrashPlan Engine
Loaded: loaded (/etc/rc.d/init.d/crashplan)
Active: active (exited) since Wed 2015-12-09 20:55:47 EST; 22h ago
Process: 24130 ExecStart=/etc/rc.d/init.d/crashplan start (code=exited, status=0/SUCCESS)
Dec 09 20:55:47 localhost.localdomain crashplan : CrashPlan is already running with pid 23931
I'll try the steps on the wiki to see if I can get the desktop running again. Thanks!
#16 Updated by bigfoot65 about 5 years ago
Great to hear it's working.
Can you update the wiki with the basic steps you followed for the client? I am sure what is on that link is more than what's needed.
Also please describe what you did to get the /var/lib/crashplan/.ui_info created. Was it just a stop and start?
#20 Updated by bigfoot65 about 5 years ago
No problem. Happy to assist. Appreciate your help as well. Without your efforts, we would not have the user testing it needed.
Once you have the wiki guidance updated, we will try to release this LIVE for Amahi 8.
Please let me know so I can test your steps and hopefully achieve the same result.
#21 Updated by ceayuso about 5 years ago
Having a new problem. The root drive filled up. I traced the problem to /var/hda/files/crashplan:
du -ch -d 1 | sort -hr
Although I told CrashPlan to use another drive for inbound backups, it seems to be trying to mirror the backups on the root drive. Here's the the location I specified for the inbound backups:
du -ch -d 1 | sort -hr
Is this something I need to ask Code42 about? I don't see anything in their UI that says to use /var/hda/files/crashplan for the backups.
#24 Updated by bigfoot65 about 5 years ago
/var/hda/files/crashplan is the default path for backup set on install. The app install script sets it as such.
Hopefully changing it on the client side will correct it. That is a good item to note in the wiki when you add the steps for post-install configuration.
Also available in: Atom