curl: error while loading shared libraries

Having issues with your DietPi installation or found a bug? Post it here.
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by Joulinar »

issue is with your installation. it seems to inkonsistent now. Can you try to rerun the restore? I will ask @MichaIng to have a look
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
User avatar
novitibo
Posts: 133
Joined: Mon Feb 29, 2016 5:11 pm

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by novitibo »

what is possibillity that backup>restore can fail? :?
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by Joulinar »

Honestly I'm not sure but your system is looking for libhogweed.so.6. And if I'm not mistaken this is a library available on Bullseye.

https://packages.debian.org/search?suit ... libhogweed
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
User avatar
MichaIng
Site Admin
Posts: 3216
Joined: Sat Nov 18, 2017 6:21 pm

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by MichaIng »

If backup or restore fails, then rsync itself failed and you see an error prompt, so it shouldn't be possible that e.g. the libraries are reverted to Buster while the curl binary is not. If there was not error message, than it must have been a low level error with the drive or filesystem cache which rsync did not receive, not how such can happen. Also strange that it is curl only while obviously the remaining system works well :?.

Please try to reinstall curl. If it still fails, check which package version from where is installed:

Code: Select all

apt install --reinstall curl
curl -I https://dietpi.com/
# if it still fails
apt policy curl
User avatar
novitibo
Posts: 133
Joined: Mon Feb 29, 2016 5:11 pm

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by novitibo »

Code: Select all

root@DietPi:/home/tibo# apt install --reinstall curl
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 49 not upgraded.
Need to get 254 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.arnes.si/mirrors/raspbian/raspbian buster/main armhf curl armhf 7.64.0-4+deb10u2 [254 kB]
Fetched 254 kB in 0s (551 kB/s)
(Reading database ... 128449 files and directories currently installed.)
Preparing to unpack .../curl_7.64.0-4+deb10u2_armhf.deb ...
Unpacking curl (7.64.0-4+deb10u2) over (7.64.0-4+deb10u2) ...
Setting up curl (7.64.0-4+deb10u2) ...
root@DietPi:/home/tibo# curl -I https://dietpi.com/
curl: error while loading shared libraries: libhogweed.so.6: cannot open shared object file: No such file or directory
root@DietPi:/home/tibo# apt policy curl
curl:
  Installed: 7.64.0-4+deb10u2
  Candidate: 7.64.0-4+deb10u2
  Version table:
 *** 7.64.0-4+deb10u2 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        100 /var/lib/dpkg/status
:?
User avatar
novitibo
Posts: 133
Joined: Mon Feb 29, 2016 5:11 pm

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by novitibo »

is possible to add missing libhogweed.so.6 manually?

or

is bullseye upgrade the only option?
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by Joulinar »

give some time to @MichaIng to come back on this. We all have a day job and sometimes it might take a while.

on the other hand, if you have time, why not trying to update again. Probably we could have a look to your issues. As of know you are the only one reporting such issues after the upgrade. Would be interesting to see what issue is. :)
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
User avatar
MichaIng
Site Admin
Posts: 3216
Joined: Sat Nov 18, 2017 6:21 pm

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by MichaIng »

Very strange. You did a reboot in between, didn't you? I'll try to replicate on a Buster RPi system, just to rule out an issue with the Raspbian repo.

But wait, one more idea I have. Please run and paste the output of the following commands:

Code: Select all

which -a curl
ls -l {,/usr{,/local}}/bin/curl
User avatar
novitibo
Posts: 133
Joined: Mon Feb 29, 2016 5:11 pm

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by novitibo »

Code: Select all

root@DietPi:/home/tibo# which -a curl
/usr/bin/curl
root@DietPi:/home/tibo# ls -l {,/usr{,/local}}/bin/curl
ls: cannot access '/bin/curl': No such file or directory
ls: cannot access '/usr/local/bin/curl': No such file or directory
-rwxr-xr-x 1 root root 185812 Mar 30 22:56 /usr/bin/curl
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: curl not working after unsuccessful buster>bullseye upgrade

Post by Joulinar »

out of curiosity, could you run the restore again and watch the output closely for error messages?
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply