error while loading shared libraries: libssl so 1 1

[PeterRozenveld]

Raspbian 64 bit lite ( Shift key RAspberryPi 4 ; Image loader)
Geekworm powerbutton and Geekworm powerfan scripts installed.

I Build a geekworm, now twice , the first runs smoothly, now thiss second device : I can't access the webside because this error:

./domoticz:
error while loading shared libraries: lib ssl so 1 1: cannot open shared object file: No such file or directory

pi@lightHCC:~/domoticz $

It's telling me that the library lib ssl so1 1 is missing?
Wat went wrong ?

First thought that I had to make a user pi , ( i first did it with user "Peter")
did update domoticz and apt.

[FireWizard]

Hi @PeterRozenveld

Search for libssl.so.1.1 on this forum and you will get more than 200 results.

Check these posts first.

Regards

[PeterRozenveld]

Ok, thx, but searching for a solution is not easy!

[gizmocuz]

You probably use bookwork? Because many users are using the previous debian release our builds are still using version 1.1
This will change in the near feature to 3.0
If you are using raspbian, install the legacy version or use Domoticz in combination with docker-compose

[PeterRozenveld]

Yes, I Did installed a Legacy, but how I prevent Domoticz from upgrade !
Stil not running...
Thanks anyway

[bo2be]

These commands solved my issues, but I am too beginner to well understand them.
Raspberry Pi 4
Raspberry Pi OS (LEGACY) LITE Bullseye

Code: Select all

sudo apt update && sudo apt upgrade -y && sudo reboot 

Install Domoticz

Code: Select all

sudo service domoticz status 

Then you can see the error:

Code: Select all

start-stop-daemon: unable to start /home/dranreb/domoticz/domoticz (No such file or directory)

close and edit the file /boot/config (.txt)


Add at the end of file:

Code: Select all

arm_64bit=0

Save

Code: Select all

sudo reboot
cd domoticz
sudo ./updaterelease
service domoticz status

Normaly you should see the running status:

Code: Select all

     Active: active ([b]running[/b]) since Sat 2023-10-21 20:38:01 CEST; 9s ago

Then remove

arm_64bit=0

in the config text file.

Save and reboot

Code: Select all

sudo service domoticz status

You should still see:

Code: Select all

     Active: active ([b]running[/b]) since Sat 2023-10-21 20:40:41 CEST; 6s ago

Done!

[bo2be]

I have also solutions for
Raspberry Pi 4
With Raspberry Pi OS LITE (32-BIT) Bookworm

Orange Pi 0 Armbian Bookworm

Orange Pi 0 plus (h5) Bookworm

but I am not yet allowed to publish the wget commands (perhaps due to the fact that I am new on this forum)

I get always this message :
You can’t post image, email or url links that are external to this domain.

Perhaps later..

[JuanUil]

maybe someone else?
quite anoying

[PeterRozenveld]

THX bob3be its working, that arm64=0 !

[bo2be]

I still have the publishing limitations but I will try to explain anyway

(some "." are replaced with ' ')

If you try for :
Raspberry Pi 4
With
Raspberry Pi OS LITE (32-BIT) Bookworm

All former steps lead to the error:
error while loading shared libraries: lib ssl' 'so' '1' '1: cannot open shared object file: ...
So do the following commands:
In the next 2 lines replace ' ' by a point character.

Code: Select all

wget http://security' 'debian' 'org/debian-security/pool/updates/main/o/openssl/libssl1' '1_1' '1' '1n-0+deb11u5_armhf' 'deb
sudo dpkg -i libssl1' '1_1' '1' '1n-0+deb11u5_armhf' 'deb

sudo reboot
service domoticz status

Active: active (running) since Sat 2023-10-21 21:05:01 CEST; 1min 5s ago

Done !

[bo2be]

For
Orange Pi 0
Armbian_23.8.3_Orangepizero_bookworm_current_6.1.53

Code: Select all

sudo apt update && sudo apt upgrade -y && sudo reboot

Code: Select all

wget http://security' 'debian' 'org/debian-security/pool/updates/main/o/openssl/libssl1.1_1.1.1n-0+deb11u5_armhf' 'deb
sudo dpkg -i libssl1.1_1.1.1n-0+deb11u5_armhf.deb

Code: Select all

sudo reboot
Install Domoticz and reboot
service domoticz status

Active: active (running) since Sat 2023-10-21 21:05:01 CEST; 1min 5s ago

Done !


FOR
Orange Pi 0 plus (h5)
Armbian 23.8.1 Bookworm with Linux 6.1.47-current-sunxi64

Code: Select all

sudo apt update && sudo apt install armbian-config && sudo reboot
sudo apt update && sudo apt install && sudo reboot

Note that arm64 replace armhf

Code: Select all

wget http://security.debian.org/debian-security/pool/updates/main/o/openssl/libssl1.1_1.1.1n-0+deb11u5_arm64.deb
sudo dpkg -i libssl1' '1_1' '1' '1n-0+deb11u5_arm64' 'deb
sudo reboot

Install Domoticz and reboot

Code: Select all

service domoticz status

Active: active (running) since Sun 2023-10-22 13:34:04 CEST; 24s ago

[lost]

I still have the publishing limitations but I will try to explain anyway

Good to know this works, but IMO for those that follows the usual Debian (& derivatives) upgrade path from CLI (by modifying /etc/apt/source.list etc) this may not be needed as old libraries from previous Bullseye/Debian 11 should remain after upgrade to Bookworm/Debian 12. This'll not be the case for a brand new install.

Did not upgrade my raspberry PI3B hosting Domoticz for now, but for a few PC's I still have previous libssl1.1 if I look what's present a file location for an x86-64 PC for instance:

https://packages.debian.org/bullseye/libssl1.1

=> File list for x86-64 shows Bullseye libssl1.1 are supposed to be & if I check on a PC that got upgraded, tadam...

Code: Select all

$ ls -alrt /usr/lib/x86_64-linux-gnu/libssl*
-rw-r--r-- 1 root root 417144 15 févr.  2023 /usr/lib/x86_64-linux-gnu/libssl3.so
-rw-r--r-- 1 root root 597792 13 sept. 21:21 /usr/lib/x86_64-linux-gnu/libssl.so.1.1
-rw-r--r-- 1 root root 696352 26 sept. 21:08 /usr/lib/x86_64-linux-gnu/libssl.so.3

libssl.so.1.1 is still there along with new libssl.so.3 !
Tried to extract/start a stable Linux x86 domoticz supposed to be compiled towards libssl1.1 & no issue observed (https included).

From a new install (not upgraded), we can see no libssl1.1 is available in Bookworm repo:
https://packages.debian.org/search?keywords=libssl

=> So the need to install it manually (& hope no other dependency issue shows-up, looks that was the case for you) using .deb file from previous version for the machine architecture (armhf/arm64 depending on raspbian 32 or 64 bits installed).

Some distros like Alpine Linux provide a libsslcompat that makes a compatibility bridge between libssl1.1 and libssl3 to ease transition but looks Debian do not provide this, unfortunately.

[bo2be]

Thanks for the explanations, it-s now more clear for me.

[JuanUil]

THNX bo2be working like charm!