I managed to get the openjdk java to work on the box, installed crashplan and it starts up fine. However, as mentioned in the post above, crashplan is unable to backup because jna is not installed. If I try apt-get install libjna-java the package cannot be found.

Anybody has an idea how to install jna on the LS-CHLv2 with Lenny? Having Crashplan on the LS would be a reall blast

I have an LSPro (v1) and had Lenny on it until very recently (I now have a fresh Squeeze install).

I did try to install CrashPlan and did have JNA installed, but I can't remember where I got JNA for armel Lenny. In any event, I managed to get CrashPlan running with the Zero/Shark JVM, but even though I could browse for files to choose to backup (from another client), it would never actually back anything up. I documented the issue at https://crashplan.zendesk.com/entries/2 ... dexception.

Ultimately I gave up on CrashPlan on that platform, but I am going to try again with Squeeze.

Well I installed CrashPlan on Debian Squeeze on my LSPro V1 and it has successfully backed up some files, so it appears to be working although it is a bit slow and a bit of a memory hog. Let me know if you are interested in how I did it - not much hackery was involved.

in fact, I managed to install and run crashplan 3.0.3 following the informations from the previous link. My setup managed to backup some test files. More testing will follow but it looks working. Here the basic links:

I have successfully installed CrashPlan on a Duo LS-WXL. There is a lot of great information out there, but I did hit a snag I did not find documented for anywhere else.

My situation was CrashPlan would start, run for about 5 minutes, never bind to 4243, and shutdown. Looking at the logs, it didn't crash, rather shutdown gracefully. It was reporting that CPService was already running on 127.0.0.1:4243, but it was not. I did try switching from OpenJDK to Oracle SUN Java Embedded. That did get speed the process up. Instead of taking 5 minutes, it was up and down in under a minute.

I resolved that by changing the IP address in the Service Hosts configuration in the my.service.xml file from 127.0.0.1 to the IP address of the system. Downside, or plus side depending on how you look at it, is that CrashPlan is now accessible over the network. So you can manage it without port forwarding in an ssh tunnel.

Who is online

Users browsing this forum: No registered users and 4 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum