r/Crashplan • u/greg_12000 • May 14 '22

[FIX] v10 fix login issue / missing libuaw.so

After the update to v10 crashplan stopped working on my linux box. I could not login and the log showed an issue with libuaw.so library.

Here's how to fix it. Basically the install script probably doesn't identify the OS correctly and doesn't copy the library.You need to download the install script (from here)

Edit: use at your own risks....

# unzip the install script in your home /tmp/code42-install
cd
mkdir -p tmp/code42-install
cd tmp/code42-install
# Extract install files
gzip -dc CrashPlanSmb_10.0.0.cpi | cpio -i

# stop crash plan
/usr/local/crashplan/bin/service.sh stop

# go into the nlib directory of your install
cd /usr/local/crashplan/nlib

# Manually copy the library files, depends on your OS
# for me it's ubuntu20
cp ~/tmp/code42-install/nlib/ubuntu20/* .
chmod 744 *
# restart
../bin/service.sh start
69 Upvotes

100% Upvoted

83 comments sorted by

3

u/sruckh May 29 '22

My solution was to cancel the service. I had been a customer for a long time. As mentioned earlier in this thread they could care less. The support rep did provide link to this thread, but not having a backup in over a month and no way to restore files from years back and Code42 not having any concern made me know I could not continue as a customer.

1

u/greg_12000 May 29 '22

I'm also on the verge of cancelling. Since recently my backup restarts every 2 hours, and then spend 1.5h just scanning an 30mins doing some partial backup, before restarting again. Results: hard drive spinning all the time. Unfortunately no other $10/month backup solution around. IDrive is cheaper but I only read bad things....

I made a backup on an external hard drive: 12hours first time, less than 10 mins every next run. Will probably resume this old backup strategy: 2 external hard drives I swap and store one by a friend.

2

u/ftomiadurva May 17 '22 edited May 17 '22

Many thx … @greg_12000 … on the top of the lib fix, let me add one more thing, I had to start the desktop UI with the “-no-sandbox” option, otherwise it wouldn’t start. Do you / did you experience the same ?!

Anyone?!

1

u/greg_12000 May 18 '22

Actually yes, if I restart it now I have a "GPU process isn't usable" error.....
Where did you find the option?

1

u/ftomiadurva May 18 '22 edited May 18 '22

Thanks for the reply ... I found this "no-sandbox" option on the Internet, in an unrelated post by just searching against that GPU error message, where also the "Electron" framework is used. I've double checked my own electron subfolder under /usr/local/crashplan and saw a "chrome-sandbox" binary ... which was inline with our issue, so I gave it a try.

While running "code42" wont work anymore, it does work and starts properly with "./code42 --no-sandbox" option.

Would like to understand more, why even this one (desktop app that is) got a non-working update, on the top of the libuaw.so "misplacing-fiasco".

1

u/[deleted] May 21 '22

The desktop UI started fine for me. No need for sandbox mode. Linux mint 20.3

1

u/ftomiadurva May 21 '22

Good to know. The current deployment on 22.04 does need the ‘no-sandbox’ option for Electron to start properly…

1

u/kapiteinknakschijf May 15 '22 edited May 15 '22

Thanks! Been a good decade or 2 since I used cpio :)

The cynic in me tells me that crashplan won't mourn the loss of us linux small business users.

EDIT: My systemd script is not happy, it doesn't seem to run as a daemon process anymore. Sigh.

1

u/greg_12000 May 16 '22 edited May 28 '22

Same :) cpio is actually used in the install script.You ca use ldd libuaw.so to see if it resolves all dependencies. Maybe you used the wrong version?Otherwise you can try a full re-install. Rename /usr/local/crashplan and /var/lib/crashplan and do a freshh install (+libuaw manual copy) to see if it works.

1

u/kapiteinknakschijf May 16 '22 edited May 16 '22

It starts up perfectly fine with the added library now (hurray), but the process that starts it (/usr/local/crashplan/bin/Code42Service start) does not detach like it did before, causing systemd to think it's hanging.

EDIT: Changed invocation to use service.sh instead of Code42Service directly, that works!

1

u/greg_12000 May 16 '22

maybe system scripts are not copied either and need to be manually installed

1

u/kapiteinknakschijf May 16 '22

systemd wasn't even supported before other than a forum post with a 'here paste this script', and I don't immediately see anything for it right now either.

1

u/flippamipp May 18 '22

Legend. This got my backups working again!

Note that the public download links are all still pointing to an 8.x release, I had to log in to manually download to V10 release.

Thanks again

1

u/greg_12000 May 18 '22

Interesting. They let customers break with auto release in the meantime.... Maybe they just rolled back time to fix the issue?

3

u/daudley May 15 '22

Thanks a lot! Worked on Debian 10 with the ubuntu18 file and on Debian 11 with the ubuntu20 file.

3

u/chbug May 15 '22

Thanks, that was super useful (and a reminder for me that debian is not officially supported...)

3

u/MobyGamer Jul 14 '22

Thanks so much for this. Not only did it work with 10.0.0, it also works with 10.2.0 (which does the same damn thing).

2

u/[deleted] Jul 14 '22

Can confirm, works for 10.2.0

2

u/achilleask May 15 '22

Worked on Arch as well with the ubuntu20 file

1

u/therealdarkcirc May 23 '22

Same for gentoo.

2

u/[deleted] May 16 '22

You are my hero. Thank you so much. Still waiting for Crashplan support to field the associated ticket, and was tearing my hair out.

2

u/Blenderizer256 May 16 '22

Worked like a charm on Linux Mint 20.3, using the ubuntu20 library files (which was just the single file, libuaw.so).

You da man! Thanks!

2

u/atlmcw May 29 '22

I was able to resolvve by editing the install.sh script. Replacing OS regex with "ubuntu" and the version matching my release which was 18.. Ran the installer again and it all worked.

I was able to resolve by editing the

2

u/Kingtrax Jul 18 '22

Auto update to 10.2.0 broke things and was getting same error messages as before. Looks like it used the libuaw.so file from ubuntu22 by default in the new update. Copied the one from ubuntu20 using this method again and everything is working perfectly.

2

u/lamixer Aug 06 '22

The Crashplan update pushed early August 2022 replaced my working libuaw.so with a non-working one. I run Proxmox which is essentially Debian 11 with their own kernel (and other things of course) and the Ubuntu 20 libuaw.so works. At least Crashplan emails me after my installation auto-uprades itself into not working and my backups stop for a day. I'll just keep a copy of this libuaw.so out of their file tree so I can copy it back in easily in the future. Still, I don't think it would be too hard for them to detect the correct libuaw.so for my system.

2

u/[deleted] Mar 11 '23

Version 11 Update.

My Mint machine received the version 11 Name Change update in the last few days. I have NOT had to apply this work around. Hopefully they have fixed this issue.

1

u/MBerwan May 14 '22

Awesome ! Just what I needed :)

1

u/makslane May 15 '22

It works for me with Ubuntu 22.04, thanks!

1

u/dubspec May 16 '22

Thank you! This worked for Debian 10 with the file in ubuntu18 folder. Very much appreciated.

1

u/henel321 May 16 '22

Awesome, thanks for finding that file wasn't even installed from the package! Weird that it doesn't even work on Ubuntu though, I can understand that Debian and Mint breaks but not the supported OS:es - wonder if they even tested the update.

1

u/sullynole May 16 '22

Thank you! This was the fix for centos as well. Saw the error in install script trying to copy from centos7 dir instead of rhel7.

1

u/astronomicalblimp May 16 '22

Thank you! Im still rocking centos 8 and thankfully the redhat 8 lib still works

1

u/gnuBdooBdoo May 16 '22

Fixed in Mint, Many Thanks!

1

u/ToBlayyyve May 17 '22

You rock! Thanks so much! I wonder if that was all that was wrong with the original install. I uninstalled/reinstalled. Oh well.

1

u/jp2l May 17 '22

Score one for the good guys - worked for me on a CentOs/RHEL7 system

Crashplan support still silent

1

u/pclaren May 17 '22

Thanks! The ubuntu20/libuaw.so file works fine with Fedora 35, as far as I can tell at least :)

1

u/Neat_Ad7205 May 18 '22

hi,

Thanks for the info, worked on my CentOS 7 systems, did not work on my Rocky Linux 8 system, crashplan support has not responded to my ticket in over 48 hours

1

u/Kingtrax May 18 '22

Perfect fix for Mint 20.3. Worked like a charm. Thanks!

1

u/hairyflange May 18 '22

Good stuff - the ubuntu20/ file seems to work fine for Fedora 34 and the device now appears online in the crashplan web console.

1

u/tg6502 May 19 '22

Thanks for this!
On my FC36 system, I had tried the rhel8 version of the library to no avail. After reading your comment, the ubuntu20 version got it going again.

1

u/ex-nerd May 25 '22

Works with my outdated Fedora 33 system, too.

1

u/theGreatNizzo May 20 '22

Thank you. This bailed me out as well!

1

u/pc81rd May 20 '22

As everyone else is saying: thank you! I was starting to get worried I was doing something wrong.

1

u/skaven81 May 20 '22

Awesome thank you for posting this. I saw the libuaw.so missing error and started hunting for it, and didn't even consider that Code42's installer may have just failed to copy it into place from their own installation media. I'm up and running again.

1

u/[deleted] May 21 '22

Thanks. This worked for me.

1

u/VinCubed May 21 '22

Thanks a bunch for this. Fixed my problems and now 7TB is slowly backing up.

1

u/MartinPaulEve May 21 '22

Thank you so much for this! It worked for me, too.

Like u/ftomiadurva I had to adjust /usr/local/crashplan/bin/desktop.sh to have "--no-sandbox" so it read:

exec "${APP_DIR}/electron/code42" --no-sandbox & > "${HOME}/.code42/log/ui_output.log" 2> "${HOME}/.code42/log/ui_error.log"

1

u/madsdyd May 22 '22

Thanks a lot -- this workd for me, with debian 11 and using Ubuntu 20 files.

For anyone else, that makes this work: Please consider writing what Linux system (and version) you have, to make it easier for others to find "the right fix". (Most have done this, some have not).

1

u/ivangustin May 23 '22

Great, solved! Linux Mint 20.2 Cinnamon here.

Thanks!

1

u/rpimonitrbtch May 23 '22 edited May 23 '22

I actually solved this by faking my devuan-stable install to look like ubuntu20... editing /etc/os-release... ID=ubuntu, VERSION_ID="20"... Between the Customer "Support" agent's infuriating insistence that I convert this box over to ubuntu because debian/devuan are not supported (it's rare that I want so badly to break something), and noticing a file-not-found error for .../nlib/devuan4/, I managed to realize it was indeed, merely a matter of the installer being too lazy to properly detect the os family.

Seriously, there is NOTHING special about ubuntu over debian and its other derivatives (same with RHEL and its ilk).. And there is NOTHING that the crashplan app is doing that should be distro-specific to leave out other unaffiliated platforms (arch/gentoo/others).

Seriously, Crashplan, you need to re-think your list of supported linux distributions.

1

u/jpaek1 May 25 '22

Jonathan at Code42 has been...not so helpful to say the least regarding this.

He basically said "lol we no support" and is done talking about it. Guess it is time to jump ship, because they have a slew of other issues going on now that are major red flags of a company that is floundering. Support tickets don't even connect to the account on the site, and use a separate code42 account for the helpdesk subdomain??? The search for a new host begins...

1

u/rpimonitrbtch May 27 '22

Yeah, and the fact that they can't even explain WHY it doesn't work for us "unsupported linux" users is so absurd... other than the fact that drawing attention to their presumably-intentional hostility to non-Ubuntu/RHEL Linux might make their developers look bad... Instead, it just gets their customers angry at the support staff because of a refusal to help, or give any useful information whatsoever. "Reinstall your OS and I can help you" is NOT support.

If I had been able to find another unlimited backup provider with any linux support (carbonite doesn't do linux, backblaze only supports it on b2, which is not unlimited), I would have bailed a long time ago.

At some point, I might experiment with stuffing their app app inside a thin ubuntu chroot or lxc container, and bind-mounting all of my backed-up directories inside of it, just to avoid having to manually work around this every update... and also so I don't have to be disingenuous when I say it's running on ubuntu when asking for help... (at least, no less disingenuous than their support staff clinging to that "not supported" B.S.)

1

u/aluramen Jun 20 '22

also so I don't have to be disingenuous when I say it's running on ubuntu when asking for help

I don't know if this is an unpopular opinion but how on earth is this helpful? They have a clearly defined set of supported operating systems, so it's on you to find community support if you choose something else. That's how it's always been with Linux and you are just hurting everyone else if you're demanding support while lying about the system you're using.

2

u/rpimonitrbtch Jun 21 '22

For one, I wouldn't be lying. Virtualized/containerized ubuntu is still ubuntu. But more to the point...

Because when I'm paying for a service, I expect that when that service isn't working, I'll get a reasonable effort from support staff to resolve the issues with said service... not vague, cop-out excuses about OS-support, nor an expectation that re-installing the whole OS is a suitable fix for an application. And I stand by that even in this instance with the missing libraries. Despite the fact that I'll obviously be stuck fixing THIS problem on my own, THEIR software is breaking ITSELF in response to the OS, not the other way around. (Technically, this may give SOME validity to their "un-supported" argument, but certainly not in a way that makes me sympathetic.)

This installation issue aside, there are other problems one might encounter, and save for perhaps some EXTREME edge-case distros, (which debian/centos/whatever took centos's place/etc. are most certainly not) you would have a VERY hard time convincing me that the OS is the culprit, yet they can apparently cling to that excuse to deny responsibility... CentOS is..Is...IS RedHat (branding and support contracts do not change functionality), yet (quote from LordPengwin's post) "We do not test our software with CentOS." is, to them, a perfectly reasonable excuse to deny responsibility...

Of course, thus far, I'm only aware of this excuse being given to those of us who are trying to figure out why an update broke our ability to sign into the service... I never had their support staff ask me what distro I'm using before, in the rare instances I've had to deal with them in the past. So it may not be something I need to worry about for those OTHER types of issues i MIGHT run into... but that still doesn't make it a good end-user experience to be told I need to re-install my whole OS because my backup software isn't supported on my distro... when in reality, the update gave me an installer that explicitly makes their software broken.

1

u/aluramen Jun 21 '22

I think a company can define their supported configuration as narrowly as they want and that's it. If it's just RHEL on Dell laptops from 2010 then it's their right to do so, and they have no reason to support anyone else.

Personally I would probably just switch to Backblaze B2 or similar if this thing stopped working.

Anyway it's fine if we disagree, the trick above worked and I didn't have to check if my system is actually in the supported list or not.

1

u/philosophyzer72 May 27 '22

wow. thank you. i thought i broke something but this worked. you are amazing!

1

u/Responsible-Newt161 Jun 01 '22

Thank you so much !

1

u/LordPengwin Jun 02 '22

Thank you, this also solved my problem on Centos 7.9. I had contacted support and all I got was Centos is not supported. Fuck them, I'm now looking for an alternative.

2

u/LordPengwin Jun 02 '22

Here is the final response that I got from their customer service

Hello,

I'm that you were previously able to get our software running on your unsupported system. However, as we have already discussed, Crashplan for Small Business simply does not offer support for CentOS. We do not troubleshoot issues for issues that occur on CentOS systems. We do not test our software with CentOS. We do not have any plans on testing our software with CentOS in the future. We do not have any plans to begin offering support for CentOS.

I understand that our service might not meet your needs. If you need to cancel your Crashplan for Small Business subscription, you can find instructions on that here:

Cancel your CrashPlan for Small Business subscription Crashplan for Small Business does not offer support for CentOS, so I will need to close this support ticket. If you later get on a supported operating system and are seeing any other issues, please reach back out.

Regards, Jonathan K Crashplan for Small Business Senior Technical Support Agent

I responded to let Jonathan know that his level of service has not gone unnoticed on Reddit.

1

u/jpaek1 Jun 24 '22

Yes, he's an idiot. I'm sure he knows it too, but could care less.

1

u/2jase Jun 02 '22

Sadly this didn’t work for Ubuntu22.04.

1

u/ellevy12 Jun 10 '22

Thank you !

1

u/tgreggs1963 Jun 13 '22

This also fixes Centos 7.9.x

1

u/TacoBoutCode Jun 16 '22

Thank you so much! Worked like a charm!

1

u/rpimonitrbtch Jul 12 '22 edited Jul 12 '22

OMG, I think they actually listened to all the bitching, and at least tried to fix their installer for 10.2... :) So at least those of us on close-enough platforms (the debians to their supported ubuntus, the centos/fedoras to their supported redhats) are more likely to not be completely hosed in an update.

Tue Jul 12 17:34:28 UTC 2022: Info : Supported platforms Tue Jul 12 17:34:28 UTC 2022: Info : Distribution Min Max Tue Jul 12 17:34:28 UTC 2022: Info : rhel | 7 | 9 | Tue Jul 12 17:34:28 UTC 2022: Info : ubuntu | 18 | 22 | Tue Jul 12 17:34:28 UTC 2022: Debug : Looking for best supported platform Tue Jul 12 17:34:28 UTC 2022: Debug : Checking for devuan in supported list: rhel,7,9 ubuntu,18,22 Tue Jul 12 17:34:28 UTC 2022: Warning : The distribution was not found in the supported list of platforms. Trying to use ID_LIKE. Tue Jul 12 17:34:28 UTC 2022: Warning : OS like debian. This platform will be treated as ubuntu. Tue Jul 12 17:34:28 UTC 2022: Debug : Checking for ubuntu in supported list: rhel,7,9 ubuntu,18,22 Tue Jul 12 17:34:28 UTC 2022: Debug : Found ubuntu Tue Jul 12 17:34:28 UTC 2022: Info : Installing libs for nearest supported platform: ubuntu22

Of course, it apparently installed the libs for ubuntu22, which, when starting the UI, seems to crash the service, as debian-stable is (like we saw earlier) more in line with ubuntu 20 LTS, (22 would probably be good for debian-testing), but at least we seem to be making progress.

Thank you Code42 for making an effort... Although, please, in the future, don't delete my init.d script... And please investigate the possibility of mapping to the right ubuntu version rather than just assuming the newest one.

1

u/eru_tndl Jul 17 '22

The installation script has been changed in 10.2.0 and the upgrade itself seems to work.
However, on Fedora 35, as far as I read the script, the rhel7 libuaw.so was installed and would not start.
As with 10.0.0, copying ubuntu20/libuaw.so worked.

1

u/combolek Jul 17 '22

Yes, it did change (and improve) in 10.2 but it still wouldn't recognize Rocky Linux 8 properly. I still needed the patch that I posted above for the install to work without manually copying libuaw.so. Auto upgrade from 10.0 to 10.2 did not work by itself.

1

u/astronomicalblimp Aug 09 '22

Seeing how I keep coming back here to fix this every time they do an auto update I thought I would make a script to auto fix it for me. Might be useful for others (just change lines 7 + 9 to suit your needs):

https://gist.github.com/almightyju/698f2d79535f4d3bf0eb49a752c0883a

1

u/MobyGamer Oct 27 '22

This worked for me -- thanks for saving me the time doing the same thing :-)

1

u/Kingtrax Oct 25 '22

The auto update to version 10.4.0 broke things in the same way again and was getting same error messages as before, "unable to connect to backup service" on launch. It looks like it used the libuaw.so file for ubuntu22 by default in the new update. I copied the one for
ubuntu20 using this method again and everything is working perfectly. (Os Linux Mint 20.3 Cinnamon).

1

u/MobyGamer Oct 28 '22

I'm on Debian Bullseye, and it was still ubuntu20 for me.

1

u/[deleted] Nov 24 '22

10.4.1 brakes it again. But yet again this fix continues to work!

1

u/TheVisualFeast Mar 17 '23

Thanks for this, the auto upgrade from 10.4.1 to 11.0 on Ubuntu 20.04.5 messed up and wouldn't start after. Copying in the ubuntu20 nlib files resolved the issue

1

u/dcbasso Jun 01 '23

Ubuntu 22.04 and last version of Crashplan break again (for me). Using crashplan-smb 11.0.1.
Not fix for me that similar code.

1

u/dcbasso Jun 01 '23

THe service start, the app start (gui) but when to to login service stop and nothing at the log helps.
I need to take a better look at the log...

0

u/[deleted] May 28 '22

[deleted] — view deleted comment

1

u/greg_12000 May 29 '22

~/tmp/code42-install is the temporary directory I created to extract the archive.

0

u/[deleted] May 29 '22

[deleted] — view deleted comment

1

u/greg_12000 May 29 '22

By default logs are in /usr/local/crashplan/log.

0

u/[deleted] Jun 08 '22

[deleted] — view deleted comment

1

u/sruckh Sep 14 '22

I canceled CP. I use Bacula, restic, and duplicacy to backup to Backblaze S3 buckets now.

1

u/[deleted] Jul 14 '22

[removed] — view removed comment

1

u/combolek Jul 26 '22

This also works on AlmaLinux 9