After upgrading my Mac to JDK 1.7, I noticed that CrashPlan stopped working. Given just how much trouble I got in a ways back when I lost a month's worth of pictures and videos of my son I'm now a belt and suspenders kind of backup guy ... the belt may be TimeMachine, but the suspenders are CrashPlan.
After working it out with their technical staff, it turns out CrashPlan is not compatible with JDK 1.7 on Mac which is rather unfortunate. And, having installed JDK 1.7, it was trying to use that version!
Getting it working is pretty easy however; most of the information is available in their recipe for starting and stopping the CrashPlan engine. The key part is that the com.crashplan.engine.plist file includes an entry where you can specify the path to the Java executable; with a bit of experimentation to find the right path, it appears to be working.
The only change I made to the file was to change the path; the first entry for the ProgramArguments key:
You will, of course, need to sudo to edit the file and to stop and relaunch the CrashPlan engine. Now, having set this up (and, coincidentally, renewed by annual subscription) my computer is happily chugging away, making the backups.
Not really the easiest solution for the common user, but I guess if someone is installing JDK on their Mac, they can handle this fix.
ReplyDeleteThanks for sharing!
Wouldn't it be nice if Crashplan exposed a public bug tracking system?
ReplyDeleteThanks, this fixed it for me. Didn't put things together right away that my install of Java 7 a few days ago was the issue. Saw this in Console.app: 11/19/12 10:03:55.658 PM CrashPlan menu bar[467]: CPConnectionNew Stream error occurred: Error code: 61
ReplyDeleteError description: The operation couldn’t be completed. Connection refused
They definitely need better logging around this issue if they're not going to fix it.
Thank you for this, it saved me a lot of time and headaches. You should add flattr or similar donation functionality on your blog, I would've sent you a little something. My CrashPlan works again now thanks to this blog post, thank you!
ReplyDelete