CrashPlan install issue?

[PogoEnthu]

Hi all, I'm new to linux and trying to install CrashPlan from archlinux AUR with yaourt -S crashplan. It failed at cpio line with the error message "cpio: write error: No space left on device". df -h shows 400MB space available. It seems write permission might be missing. Any ideas? I appreciate any help or guidance here!!!

==> Validating source files with sha256sums...
CrashPlan_4.2.0_Linux.tgz ... Passed
crashplan.service ... Passed
install.vars ... Passed
sysctl-crashplan.conf ... Passed
==> Extracting sources...
-> Extracting CrashPlan_4.2.0_Linux.tgz with bsdtar
==> Starting build()...
==> Entering fakeroot environment...
==> Starting package()...
cpio: write error: No space left on device
==> ERROR: A failure occurred in package().
Aborting...
==> ERROR: Makepkg was unable to build crashplan.

[PogoEnthu]

Found the issue - have to increase the /tmp size to resolve the problem.

[PogoEnthu]

Ran into another issue in the later part of the installation. Anything thought there? I've have 147M space remaining in /tmp at this point.

==> Tidying install...
-> Purging unwanted files...
-> Removing libtool files...
-> Removing static library files...
-> Compressing man and info pages...
-> Stripping unneeded symbols from binaries and libraries...
strip: Unable to recognise the format of the input file `./opt/crashplan/libmd5.so'
strip:./opt/crashplan/libmd564.so: File format not recognized
strip: Unable to recognise the format of the input file `./opt/crashplan/libjniwrap.so'
strip:./opt/crashplan/libjtux64.so: File format not recognized
strip:./opt/crashplan/libjniwrap64.so: File format not recognized
strip: Unable to recognise the format of the input file `./opt/crashplan/libjtux.so'
==> Creating package "crashplan"...
-> Generating .PKGINFO file...
-> Adding install file...
-> Generating .MTREE file...
-> Compressing package...
/usr/bin/makepkg: line 2240: 11408 Killed ${COMPRESSXZ[@]:-xz -c -z -}
bsdtar: Write error
==> ERROR: Failed to create package file.
==> ERROR: Makepkg was unable to build crashplan.

[moonman]

Those are x86 prebuilt libs probably. There was a guide on the forum somewhere on installing for arm.

[PogoEnthu]

Thanks Moonman. Wished the guide was more obvious.

[PogoEnthu]

CrashPlan is now installed and running - Using my Win7 CrashPlan GUI to access Archlinux ARM Crashplan Engine.

Even though it is connected but no files are being back up!? Why? It doesn't make sense.

status crashplan -l
* crashplan.service - CrashPlan Backup Engine
Loaded: loaded (/usr/lib/systemd/system/crashplan.service; enabled; vendor preset: disabled)
Active: failed (Result: resources)

Jun 02 23:29:52 alarm systemd[1]: Failed to load environment files: No such file or directory
Jun 02 23:29:52 alarm systemd[1]: crashplan.service failed to run 'start' task: No such file or directory
Jun 02 23:29:52 alarm systemd[1]: Failed to start CrashPlan Backup Engine.
Jun 02 23:29:52 alarm systemd[1]: Unit crashplan.service entered failed state.
Jun 02 23:29:52 alarm systemd[1]: crashplan.service failed.
Jun 02 23:29:52 alarm systemd[1]: Starting CrashPlan Backup Engine...


crashplan.service
[Unit]
Description=CrashPlan Backup Engine
After=network-online.target
Wants=network-online.target

[Service]

Type=forking
PIDFile=/usr/local/crashplan/CrashPlanEngine.pid
EnvironmentFile=/usr/local/crashplan/bin/run.conf

WorkingDirectory=/opt/crashplan

ExecStart=/usr/local/crashplan/bin/CrashPlanEngine start
ExecStop=/usr/local/crashplan/bin/CrashPlanEngine stop

[Install]
WantedBy=multi-user.target

[moonman]

Because it is missing those architecture specific libraries?

[PogoEnthu]

Possibly. Have replaced installed x86 libjtux.so with Arm's. Are there any good, recent CrashPlan instruction out there? Most of what I've found are at least 2 years old and not sure if they are completely applicable to 4.2 (the latest)