Arch Linux User Repository

I'm going to be disowning this package soon. I'm moving away from crashplan and have no interest in maintaining this package, and dealing with usage issues, when I wont be using it.

I'll keep it up to date during the coming months as needed, but if no one else shows up, I plan to disown it at the end of October.

@gadicc, I added some pacman hooks to handle setting/unsetting the immutable flag:

Sets immutable flag after install/upgrade:

[Trigger]
Operation = Upgrade
Operation = Install
Type = Package
Target = crashplan-pro

[Action]
Description = Set immutability of Crashplan Pro upgrade directory
When = PostTransaction
Exec = /usr/bin/bash -c "rm -rf /opt/crashplan/upgrade/*; chattr +i /opt/crashplan/upgrade"`

Unsets immutable flag before upgrade/remove:

[Trigger]
Operation = Upgrade
Operation = Remove
Type = Package
Target = crashplan-pro

[Action]
Description = Undo immutability of Crashplan Pro upgrade directory
When = PreTransaction
Exec = /usr/bin/bash -c "chattr -i /opt/crashplan/upgrade"```

It seems CrashPlan is using the conf/tmp directory to download updates now that upgrade/ isn't writable, causing the same issues as before.

It looks like crashplan / Code42 might have changed their required packages / forgotten to put something in their java bundles.

I am currently seeing the engine fail a small time after startup, with:

ERROR main                                         ] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[01.20.22 14:54:08.642 ERROR main                                         ] SLF4J: Defaulting to no-operation (NOP) logger implementation
[01.20.22 14:54:08.643 ERROR main                                         ] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[01.20.22 14:54:08.648 ERROR main           com.backup42.service.CPService] Error starting up, java.lang.UnsatisfiedLinkError: 'int org.mozilla.jss.CryptoManager.getJSSMajorVersion()'
STACKTRACE:: java.lang.UnsatisfiedLinkError: 'int org.mozilla.jss.CryptoManager.getJSSMajorVersion()'

I will look into this later, but let me know if you also see this.

@gr211 and anyone else. Dont implement my comments from below, just use the AUR and read pinned comments by legodfrey/

@legodfrey, I reinstalled completely a couple of weeks back to enjoy your auto-upgrade units fresh.

Alas, today I see it is trying to update, but unsuccessful. I forced it clicking the link in the gui and watched the 'upgrade' directory in /opt/crashplan/upgrade/ but nothing came into existence there... what a drag.

Besides this, my crashplan kept trying to want to verify about half of my backup, cauing it to re-upload (verify) about 3tb every day.... bothersome.

I made the switch for now and gonna try the docker version of crashplan.

Good luck all, and maybe till later if I return.

Hi. Thx a lot for this pkg.

Could be just me, but thought I'd put it out there for others just in case.

On a fresh install of crashplan (ie no /opt/crashplan dir), the cmd

/usr/bin/chattr -i /opt/crashplan/conf/tmp

failed (as in directory did not exist yet).

Good catch, Merry Christmas! to you all.

Thanks a bunch for keeping this product alive for me on a linux VM.

Further more, updated the AUR. Will let you know the results at some point in the future when the disk is full again or if I notice there has been an update installed ... all by itself.

Will it not try to install the upgrade possibly without waiting for it to be fully downloaded? .. a well, what do i know.

Ha!

That's freakin' brilliant @legodfrey!

Thank you.

I'll give it a try and let you know how it goes with the next update.

I have added a second systemd unit, this is a path monitor, which if a file is detected in the upgrade directory will try to run an update. This might fail, or require a different glob. Please report any issues you have with this.

This should be enabled through:

systemctl enable crashplan-pro_upgrade.path
systemctl start crashplan-pro_upgrade.path

@muncrief and @p_wandelwall - Merry Christmas! I have adopted those changes while I look into fixing the auto update... I agree it is annoying, especially as it should still backup with the older version (or at least did on windoze).

@P_wandelwall, I'm not the maintainer of this package so I can't change it. I just chime in from time to time if there are easy changes that users can make to get them by until the package is updated.

The maintainer is @legodfrey, so hopefully he can adopt the changes so CrashPlan can self update. It certainly is annoying having to constantly check! :)

Comment to myself. My last post did not really work very well. Changed some things and this seems to work, even after reboot.

crashplan-pro.service
.....
ExecStartPre=/bin/bash /usr/local/sbin/crashplan.sh
ExecStart=/opt/crashplan/bin/CrashPlanEngine start
ExecStartPost=/bin/bash /usr/local/sbin/crashplan-i.sh
.....

crashplan.sh

#!/bin/bash
/usr/bin/chattr -i /opt/crashplan/conf/tmp

crashplan-i.sh

#!/bin/bash
sleep 30
/usr/bin/chattr +i /opt/crashplan/conf/tmp