Every time, I end up Googling around and referencing this thread and a few others. Recently, CrashPlan has started automatically upgrading itself every few weeks to months, which breaks my install.
I’ve been using a Raspberry Pi as a local backup destination for CrashPlan for a few years now. Works here, using ubuntu20 file(s) for debian 11.Bottom Line: My strategy for getting CrashPlan working on the Raspberry Pi (currently on Raspbian Jessie). The solution would be very similar to last time: - where we had to manually copy a "correct" version of libuaw into the nlib library if we were on an unsupported platform.
So, the code to handle installing a suitable set of compatible native libraries fails, and the native libraries from RedHat 7 is installed. Looking at the source code for the install.sh script for version 10.2, it would seem that it at some point wants to treat debian as ubuntu: function get_os_like_platform() /nlib/" " is followed by the install.sh script installing all the native libs from RedHat 7 (evident from the source code).
The line "Attempting to install ABI compatible libs. Attempting to install ABI compatible libs to allow application to run. Wed Jul 13 16:17:16 CEST 2022: Warning : Unsupported platform. However, it essentially does not succeed in treating debian "nicely" Wed Jul 13 16:17:16 CEST 2022: Warning : The distribution was not found in the supported list of platforms. Wed Jul 13 16:17:16 CEST 2022: Debug : Checking for debian in supported list: rhel,7,9 ubuntu,18,22 Wed Jul 13 16:17:16 CEST 2022: Debug : Detected platform: debian11 If you check the "upgrade.log" file, you can see that on Wednessday, when it updated it self, it sort of figured out that debian was in the mix: Wed Jul 13 16:17:12 CEST 2022: Info : Checking prerequisites for debian. Looking at my own nlib directory, the version of libuaw manually installed by my, has been overwritten, when crashplan upgraded itself. So, it is probably native lib errors again. And again, unsupported platforms are the issue. # If you would like to submit a bug report, please visit: # An error report file with more information is saved as: To enable core dumping, try "ulimit -c unlimited" before starting Java again # Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.12+7 (11.0.12+7, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# A fatal error has been detected by the Java Runtime Environment: Jvm_args: /usr/local/crashplan/conf/jvm_args WARNING: All illegal access operations will be denied in a future release WARNING: Use -illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: Please consider reporting this to the maintainers of .ec.EcCurveLookup WARNING: Illegal reflective access by .ec.EcCurveLookup (file:/usr/local/crashplan/lib/c42-crypto-impl-15.2.4.jar) to method .lookup() The only error I've found is on engine_error.log and engine_output.log.Įngine_error.log WARNING: An illegal reflective access operation has occurred The most recent service.log.0 last few lines shows it starting things but never gets to an error. Checking the logs though the issue isn't quite as obvious.
Sure enough there was an upgrade on the 13th. But I just got the email that my system hasn't backed up for three days so I thought I'd check. I had the UAW library issue from the last upgrade which I fixed from the info found here.
Looks like another update has broken crashplan for me.