Missing libgnutls.so.28 after files stem corrupted

Altiris · 08-14-2015, 08:20 PM

I know I have a hard drive issue, I thought I could bear with it but this is the second time it's borked the ext4 file system and I've had to run fsck and hit y/enter probably 30 times to get it back working.

Anyway, samba adnd libvirt are complaining thay there is no libgnutls.so.28 although it seems to be in /usr/lib/
What can I do about this? Could I reinstall all of the system libraries with slackpkg?

Didier Spaier · 08-14-2015, 09:19 PM

You can try but if the hard disk is dying that won't help. A best it would be as we say here "reculer pour mieux sauter".

Altiris · 08-15-2015, 09:04 AM

Quote:

Originally Posted by Didier Spaier

You can try but if the hard disk is dying that won't help. A best it would be as we say here "reculer pour mieux sauter".

Uh, how do I do this? I tried doing slackpkg install l but it just looked for a package instead.

Nvm found it in wiki..actually what's in the wiki doesn't work.

kingbeowulf · 08-15-2015, 12:37 PM

Altiris,
make sure slackpkg is set up properly, then

Code:

# slackpkg update
# slackpkg reinstall gnutls

or you can just download the package from a Slackware mirror and

Code:

upgradepkg reinstall gnutls-3.1.25-x86_64-1_slack14.1.txz

That should reset the missing symlinks. For example:

Code:

# ls -l /usr/lib64/libgnutls*
-rwxr-xr-x 1 root root    1111 Jun  5  2014 /usr/lib64/libgnutls-openssl.la*
lrwxrwxrwx 1 root root      27 Jun  9  2014 /usr/lib64/libgnutls-openssl.so -> libgnutls-openssl.so.27.0.2*
lrwxrwxrwx 1 root root      27 Jun  9  2014 /usr/lib64/libgnutls-openssl.so.27 -> libgnutls-openssl.so.27.0.2*
-rwxr-xr-x 1 root root  135320 Jun  5  2014 /usr/lib64/libgnutls-openssl.so.27.0.2*
-rwxr-xr-x 1 root root    1089 Jun  5  2014 /usr/lib64/libgnutls-xssl.la*
lrwxrwxrwx 1 root root      23 Jun  9  2014 /usr/lib64/libgnutls-xssl.so -> libgnutls-xssl.so.0.0.0*
lrwxrwxrwx 1 root root      23 Jun  9  2014 /usr/lib64/libgnutls-xssl.so.0 -> libgnutls-xssl.so.0.0.0*
-rwxr-xr-x 1 root root   83128 Jun  5  2014 /usr/lib64/libgnutls-xssl.so.0.0.0*
-rwxr-xr-x 1 root root    1041 Jun  5  2014 /usr/lib64/libgnutls.la*
lrwxrwxrwx 1 root root      20 Jun  9  2014 /usr/lib64/libgnutls.so -> libgnutls.so.28.21.5*
lrwxrwxrwx 1 root root      20 Jun  9  2014 /usr/lib64/libgnutls.so.28 -> libgnutls.so.28.21.5*
-rwxr-xr-x 1 root root 1164792 Jun  5  2014 /usr/lib64/libgnutls.so.28.21.5*
-rwxr-xr-x 1 root root    1108 Jun  5  2014 /usr/lib64/libgnutlsxx.la*
lrwxrwxrwx 1 root root      21 Jun  9  2014 /usr/lib64/libgnutlsxx.so -> libgnutlsxx.so.28.1.0*
lrwxrwxrwx 1 root root      21 Jun  9  2014 /usr/lib64/libgnutlsxx.so.28 -> libgnutlsxx.so.28.1.0*
-rwxr-xr-x 1 root root   63056 Jun  5  2014 /usr/lib64/libgnutlsxx.so.28.1.0*

But, really? Forcing a bit more life out of a dying hard drive? You are nuts. Back up your data and get thee a new one.

Altiris · 08-15-2015, 04:02 PM

Quote:

Originally Posted by kingbeowulf

Altiris,
make sure slackpkg is set up properly, then

Code:

# slackpkg update
# slackpkg reinstall gnutls

or you can just download the package from a Slackware mirror and

Code:

upgradepkg reinstall gnutls-3.1.25-x86_64-1_slack14.1.txz

That should reset the missing symlinks. For example:

Code:

# ls -l /usr/lib64/libgnutls*
-rwxr-xr-x 1 root root    1111 Jun  5  2014 /usr/lib64/libgnutls-openssl.la*
lrwxrwxrwx 1 root root      27 Jun  9  2014 /usr/lib64/libgnutls-openssl.so -> libgnutls-openssl.so.27.0.2*
lrwxrwxrwx 1 root root      27 Jun  9  2014 /usr/lib64/libgnutls-openssl.so.27 -> libgnutls-openssl.so.27.0.2*
-rwxr-xr-x 1 root root  135320 Jun  5  2014 /usr/lib64/libgnutls-openssl.so.27.0.2*
-rwxr-xr-x 1 root root    1089 Jun  5  2014 /usr/lib64/libgnutls-xssl.la*
lrwxrwxrwx 1 root root      23 Jun  9  2014 /usr/lib64/libgnutls-xssl.so -> libgnutls-xssl.so.0.0.0*
lrwxrwxrwx 1 root root      23 Jun  9  2014 /usr/lib64/libgnutls-xssl.so.0 -> libgnutls-xssl.so.0.0.0*
-rwxr-xr-x 1 root root   83128 Jun  5  2014 /usr/lib64/libgnutls-xssl.so.0.0.0*
-rwxr-xr-x 1 root root    1041 Jun  5  2014 /usr/lib64/libgnutls.la*
lrwxrwxrwx 1 root root      20 Jun  9  2014 /usr/lib64/libgnutls.so -> libgnutls.so.28.21.5*
lrwxrwxrwx 1 root root      20 Jun  9  2014 /usr/lib64/libgnutls.so.28 -> libgnutls.so.28.21.5*
-rwxr-xr-x 1 root root 1164792 Jun  5  2014 /usr/lib64/libgnutls.so.28.21.5*
-rwxr-xr-x 1 root root    1108 Jun  5  2014 /usr/lib64/libgnutlsxx.la*
lrwxrwxrwx 1 root root      21 Jun  9  2014 /usr/lib64/libgnutlsxx.so -> libgnutlsxx.so.28.1.0*
lrwxrwxrwx 1 root root      21 Jun  9  2014 /usr/lib64/libgnutlsxx.so.28 -> libgnutlsxx.so.28.1.0*
-rwxr-xr-x 1 root root   63056 Jun  5  2014 /usr/lib64/libgnutlsxx.so.28.1.0*

But, really? Forcing a bit more life out of a dying hard drive? You are nuts. Back up your data and get thee a new one.

Ayee nice that came in handy, I really needed to use Samba. Oh yeah I am nuts lol, problem was that this happened long ago in June when I was on CentOS and I dd'ed the disk to completely wipe it so I could send to manufacturer but once I did that, I thought, ill run another SMART scan. I did and it didnt show any errors, I was perplexed, took it up to the forums and people said it is still bad and I believed but considering I had just bought a new hard drive for my media files....I wanted to see how long this one would last. It definitely isn't going to last much longer and I am not putting up with it anymore, I'll be ordering a new one today.

Thanks again!