Installing Domoticz the "easy" way doesn't work?

[Timmiej93]

Following this guide, I tried installing Domoticz the "easy" way about 3 times. Each time it seems to run without issues, saying that i can access Domoticz at the ports I set, but trying to access these ports always results in "This site can't be reached". I'm positive that the IP is correct, since I'm using SSH to connect to the Pi in the first place. I tried hunting down the install log, but for some reason I couldn't find it. I've tried rebooting the Pi, but to no avail.

Is there anything I'm missing here, is it a known bug, or is there something else going on?

[mrf68]

Check if domoticz is running and if a firewall is not blocking the ports on the machine you can connect with the pi using ssh.

[Denny64]

Put an empty file called ssh into the boot partition of SD and it should solve the problem.

If not, try to install SSL 1.0.0 in this way:

1) sudo nano /etc/apt/sources.list
2) deb http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi
3) sudo apt-get update
4) sudo apt-get install libssl1.0.0
5) sudo reboot

I think you can solve.

[Timmiej93]

Check if domoticz is running and if a firewall is not blocking the ports on the machine you can connect with the pi using ssh.

Domoticz is indeed running (check with 'service domoticz status', resulting in 'active (exited)'), and I doubt a firewall would be the cause of this. I'm on the same LAN as the Pi is, and have been able to connect to another install of Domoticz before.

Put an empty file called ssh into the boot partition of SD and it should solve the problem.

If not, try to install SSL 1.0.0 in this way:

1) sudo nano /etc/apt/sources.list
2) deb http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi
3) sudo apt-get update
4) sudo apt-get install libssl1.0.0
5) sudo reboot

I think you can solve.

I think you may have misunderstood, I can actually use SSH to control the Pi, that's how I know that the IP address I'm connecting to is correct. I'm on Stretch by the way, not on Jessie.

[mrf68]

You can be on the same LAN and still have a local firewall (on the machine you try to reach the pi from) blocking the ports that you may use with your domoticz. But i cannot inspect your network.
The message from the browser “This site can’t be reached’ usually means that it can’t make a network connection. The browser probably gives more info that can be useful, like “ERR_NAME_NOT_RESOLVED”.

[Denny64]

Domoticz 'active (exited)' does not mean working. It is in a wrong state.

Check if libssl it's ok with this command in domoticz path: ldd domoticz .

If not, try to manually install libssl1.0.0:

1) wget http://ftp.nl.debian.org/debian/pool/ma ... _armhf.deb
2) sudo dpkg -i libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb
3) sudo reboot

[Timmiej93]

Hm, I was wondering about that 'exited' part.
I tried your suggestions of checking libssl:

Code: Select all

~ $ ldd domoticz
ldd: ./domoticz: not regular file

I'm assuming that's not the desired result?

Trying to get the file you suggested, I get a 404 error, both when trying to access the file on my PC, and when trying to access it on my RPi.

[Denny64]

You must be in the domoticz path.

1) cd domoticz
2) ldd domoticz

[Timmiej93]

My bad, I misunderstood your post.

Result:

Code: Select all

~/domoticz $ ldd domoticz
        linux-vdso.so.1 (0x7eff9000)
        /usr/lib/arm-linux-gnueabihf/libarmmem.so (0x76eeb000)
        libusb-0.1.so.4 => /lib/arm-linux-gnueabihf/libusb-0.1.so.4 (0x76ebf000)
        libssl.so.1.0.0 => not found
        libcrypto.so.1.0.0 => not found
        librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0x76ea8000)
        libresolv.so.2 => /lib/arm-linux-gnueabihf/libresolv.so.2 (0x76e83000)
        libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x76e5a000)
        libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0x76e33000)
        libcurl.so.4 => /usr/lib/arm-linux-gnueabihf/libcurl.so.4 (0x76db7000)
        libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0x76da4000)
        libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x76d25000)
        libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x76be6000)
        /lib/ld-linux-armhf.so.3 (0x76f01000)
        libnghttp2.so.14 => /usr/lib/arm-linux-gnueabihf/libnghttp2.so.14 (0x76bb8000)
        libidn2.so.0 => /usr/lib/arm-linux-gnueabihf/libidn2.so.0 (0x76b86000)
        librtmp.so.1 => /usr/lib/arm-linux-gnueabihf/librtmp.so.1 (0x76b5d000)
        libssh2.so.1 => /usr/lib/arm-linux-gnueabihf/libssh2.so.1 (0x76b28000)
        libpsl.so.5 => /usr/lib/arm-linux-gnueabihf/libpsl.so.5 (0x76b0b000)
        libssl.so.1.0.2 => /usr/lib/arm-linux-gnueabihf/libssl.so.1.0.2 (0x76aac000)
        libcrypto.so.1.0.2 => /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.2 (0x7692c000)
        libgssapi_krb5.so.2 => /usr/lib/arm-linux-gnueabihf/libgssapi_krb5.so.2 (0x768e3000)
        libkrb5.so.3 => /usr/lib/arm-linux-gnueabihf/libkrb5.so.3 (0x7682c000)
        libk5crypto.so.3 => /usr/lib/arm-linux-gnueabihf/libk5crypto.so.3 (0x767ed000)
        libcom_err.so.2 => /lib/arm-linux-gnueabihf/libcom_err.so.2 (0x767da000)
        liblber-2.4.so.2 => /usr/lib/arm-linux-gnueabihf/liblber-2.4.so.2 (0x767be000)
        libldap_r-2.4.so.2 => /usr/lib/arm-linux-gnueabihf/libldap_r-2.4.so.2 (0x76769000)
        libunistring.so.0 => /usr/lib/arm-linux-gnueabihf/libunistring.so.0 (0x7665a000)
        libgnutls.so.30 => /usr/lib/arm-linux-gnueabihf/libgnutls.so.30 (0x764cd000)
        libhogweed.so.4 => /usr/lib/arm-linux-gnueabihf/libhogweed.so.4 (0x76490000)
        libnettle.so.6 => /usr/lib/arm-linux-gnueabihf/libnettle.so.6 (0x76449000)
        libgmp.so.10 => /usr/lib/arm-linux-gnueabihf/libgmp.so.10 (0x763d6000)
        libgcrypt.so.20 => /lib/arm-linux-gnueabihf/libgcrypt.so.20 (0x76306000)
        libkrb5support.so.0 => /usr/lib/arm-linux-gnueabihf/libkrb5support.so.0 (0x762ed000)
        libkeyutils.so.1 => /lib/arm-linux-gnueabihf/libkeyutils.so.1 (0x762da000)
        libsasl2.so.2 => /usr/lib/arm-linux-gnueabihf/libsasl2.so.2 (0x762b3000)
        libp11-kit.so.0 => /usr/lib/arm-linux-gnueabihf/libp11-kit.so.0 (0x76255000)
        libidn.so.11 => /lib/arm-linux-gnueabihf/libidn.so.11 (0x76214000)
        libtasn1.so.6 => /usr/lib/arm-linux-gnueabihf/libtasn1.so.6 (0x761f4000)
        libgpg-error.so.0 => /lib/arm-linux-gnueabihf/libgpg-error.so.0 (0x761d4000)
        libffi.so.6 => /usr/lib/arm-linux-gnueabihf/libffi.so.6 (0x761bc000)
        libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x7618f000)

Seems like libssl isn't installed?

[Jem101]

The current version of Domoticz requires a specific ssl library which isn't available in the standard installation of Raspbian Stretch.

Although this is probably the reason it's not working, you can check first by making an SSH connection to your Pi, changing to the domoticz directory and then running sudo ./domoticz

which starts it in a sort of interactive mode and you can watch the startup sequence - I'm guessing that it'll bail out fairly soon with a message about the missing libssl1.0.0 library.

If it does then follow the instructions given earlier about installing this library from the Raspbian Jessie repository. Once done, I don't think you need to restart the Pi (although it never really hurts), just try restarting the service as shown above, and if it starts OK, kill it (CTRL-C) and then start it normally

sudo service domoticz.sh start

Give it a few seconds and then try the web interface. Should now work OK

Good luck

[Timmiej93]

Your suspicions are correct Jem. When I try to run domoticz manually, I indeed get an error about the libssl library.

Code: Select all

~ $ cd domoticz/
~/domoticz $ sudo ./domoticz
	./domoticz: error while loading shared libraries: libssl.so.1.0.0: cannot open s                                     hared object file: No such file or directory

I'd love to install the library, but the link provided gives me a 404 not found error. I have been looking around for the library myself, but I'm a bit too unfamiliar with this stuff to know what I'm looking for.
Would it be possible to link me to the correct version of libssl?

[Jan Jansen]

take a look at : https://www.domoticz.com/forum/viewtopi ... 80#p160364

[Jem101]

Yep trying to download packages directly can be a bit frustrating as paths change and stuff gets moved about, better to use the built-in tools to get packages.

What you need to do is

1) Edit the file which tells Raspbian where to get packages and updates from, thats the file called sources.list found in /etc/apt. So we want to use the nano editor

sudo nano /etc/apt/sources.list


2) Add a line which can tell the system to also look for Jessie distributions. If you know how to use nano you just want to add the following line (it doesn't really matter where in the file you add it

deb http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi

Save the file (CTRL-O) and then exit the nano editor (CTRL-X)

3) Issue the following command to make the Pi reload the list of sources

sudo apt-get update

Note, you'll probably get a lot of scary looking error messages about repositories being old and superseded but these can be safely ignored.

4) Now you can install the required library from the Jessie repository

sudo apt-get install libssl1.0.0

Let it do its stuff and you should be good to go. Otherwise if you do a bit of searching around this forum (and others) I'm sure there are more comprehensive instructions about getting this library. I remember going through the same thing about five months or so ago when I updated my Pi to Stretch and it suddenly broke for no obvious reason! There were whole threads about it on this forum at the times a quick search should turn something up.

[Timmiej93]

take a look at : https://www.domoticz.com/forum/viewtopi ... 80#p160364

I tried updating to the beta, as advised in the last post of that topic, that worked. Is there any harm in running the beta, stability wise?

Spoiler: show

Yep trying to download packages directly can be a bit frustrating as paths change and stuff gets moved about, better to use the built-in tools to get packages.

What you need to do is

1) Edit the file which tells Raspbian where to get packages and updates from, thats the file called sources.list found in /etc/apt. So we want to use the nano editor

sudo nano /etc/apt/sources.list


2) Add a line which can tell the system to also look for Jessie distributions. If you know how to use nano you just want to add the following line (it doesn't really matter where in the file you add it

deb http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi

Save the file (CTRL-O) and then exit the nano editor (CTRL-X)

3) Issue the following command to make the Pi reload the list of sources

sudo apt-get update

Note, you'll probably get a lot of scary looking error messages about repositories being old and superseded but these can be safely ignored.

4) Now you can install the required library from the Jessie repository

sudo apt-get install libssl1.0.0

Let it do its stuff and you should be good to go. Otherwise if you do a bit of searching around this forum (and others) I'm sure there are more comprehensive instructions about getting this library. I remember going through the same thing about five months or so ago when I updated my Pi to Stretch and it suddenly broke for no obvious reason! There were whole threads about it on this forum at the times a quick search should turn something up.

Thanks for the elaborate explanation, really appreciate it. Unfortunately, when starting domoticz manually, I get the following errors:

Code: Select all

2018-01-02 17:29:54.538 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)

This repeats 5 times, and domoticz doesn't start.
Like I mentioned above, I tried the beta as well, which worked. Is there any harm in running the beta?

[Denny64]

If you don't want a beta version, the only way is to install libssl1.0.0, and you can do it in this way:

1) sudo nano /etc/apt/sources.list
2) deb http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi
3) sudo apt-get update
4) sudo apt-get install libssl1.0.0
5) sudo reboot

It works with latest stretch.

[Jan Jansen]

Is there any harm in running the beta?

Personally, I prefer the stable version. But due to the hassle with libssl1.0.0 I am currently using the beta version. I only experience a problem with timers (sunrise / sunset search the forum if you need them).

[Timmiej93]

Thank you all for your help and advice, much appreciated.

[mahdenavabegh]

too,,,Thank you all for your help