Crashplan/Systemd issues

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Crashplan/Systemd issues

Postby marbletravis » Thu Feb 21, 2013 4:57 am

Using this tutorial, I was able to get crashplan running just over a year ago on a dockstar box.

http://www.opticality.com/blog/2011/07/ ... oplug-pro/

I am trying to do the same thing now with a pogoplug v4 and am running into some issues that may be related to the latest version and systemd.

After following the tutorial, I can launch the crashplan service, but it just uses 100% cpu and is not responsive.

I ran into some issues installing/running java, which I fixed with this post viewtopic.php?f=18&t=3343

then I noticed rc.conf and rc.local were empty, which prompted me to isntall initscripts.

I am wondering if its an issue with the setup of crapshplan. Crashplan asks for the directories to the init scripts (SYSV), which used to be /etc/rc.d. I am not familiar with systemd, but does the init scripts directory change with systemd?

Also is there a way to get a version of arch linux for arm prior to systemd?

Thanks,
Travis
marbletravis
 
Posts: 15
Joined: Thu Feb 21, 2013 4:50 am

Re: Crashplan/Systemd issues

Postby moonman » Thu Feb 21, 2013 6:42 am

https://aur.archlinux.org/packages/crashplan/ which includes systemd service.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Crashplan/Systemd issues

Postby marbletravis » Fri Feb 22, 2013 4:30 am

Excellent. I am in the process of building the package for ARM using the instructions here:

http://archlinuxarm.org/developers/building-packages

I am trying to makepkg and am getting an error, any thoughts?

-> Stripping unneeded symbols from binaries and libraries...
strip: Unable to recognise the format of the input file `./opt/crashplan/libjniwrap.so'

Thanks,
Travis
marbletravis
 
Posts: 15
Joined: Thu Feb 21, 2013 4:50 am

Re: Crashplan/Systemd issues

Postby WarheadsSE » Fri Feb 22, 2013 5:12 am

More than likely, that is an x86 binary file.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Crashplan/Systemd issues

Postby moonman » Fri Feb 22, 2013 11:45 am

Then you can take .service file from the tarball. Wonder why crashplan supplies precompiled libs.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Crashplan/Systemd issues

Postby marbletravis » Sun Feb 24, 2013 2:59 pm

I got it. Thanks!

I ended up getting makepkg to work by having it strip all of the .so files, as far as I can tell the .so files are all x86/64 binaries. Then I added back in a arm version of libjtux.so, which I believe is all is needed for the service.

I am going to talk to the original tutorial creator and hopefully get the tutorial updated.

Thanks for your help.
marbletravis
 
Posts: 15
Joined: Thu Feb 21, 2013 4:50 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 13 guests