Can't SSH - libncurses cannot open shared object file

Rappelle · 2015-10-17 22:56:52

Crap!

While trying to install erlang and elixir on my remote server, I started receiving this error when trying to sudo -i:

bash: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory

Tried reinstalling from pacman, and it said the xz file was corrupted, do I want to remove it? Ok.
Went around in circles trying to install from pacman and yaourt for 5 minutes, and then came back to it after disconnecting, and now I can't even SSH into my server as I get the error above. WELP.

Not sure what to do if I can't even SSH in!?

WorMzy · 2015-10-17 23:12:24

Short answer: don't do partial updates.

If you have another way into the system (e.g. web-based KVM), try using that; you'll probably need to boot into a liveCD environment to fix your mess though. Otherwise, you're going to have to restore from a backup, or get whoever has physical access to the remote system to do this for you.

Rappelle · 2015-10-17 23:47:12

Say I have access to the file system via a rescue live cd (non-arch), how would I go about fixing this up?

Trilby · 2015-10-17 23:54:36

There are probably a few ways - but the shortest would be to downgrade any packages you upgraded in the partial upgrade (using the approach here) then do a proper system upgrade, just as I recently described in another thread.

Arch Linux

#1 2015-10-17 22:56:52

Can't SSH - libncurses cannot open shared object file

#2 2015-10-17 23:12:24

Re: Can't SSH - libncurses cannot open shared object file

#3 2015-10-17 23:47:12

Re: Can't SSH - libncurses cannot open shared object file

#4 2015-10-17 23:54:36

Re: Can't SSH - libncurses cannot open shared object file

Board footer