Domoticz

Posted: **Tuesday 14 May 2019 22:39**

After the migration to a new version of Domoticz recently (I use the development branch), I start getting a problem with Domoticz that crashes. A detailed description of the problem can be found in https://github.com/domoticz/domoticz/issues/3208.

However, the bug report is closed with the conclusion of a problem with the libcrypto. Domoticz would require version 1.0 instead of 1.1. I suppose the conclusion comes from the crash report that states:

Thread 35 (Thread 0x62eff430 (LWP 951)):
#0 0x76db34cc in __waitpid (pid=952, stat_loc=0x62efd5c8, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
#1 0x0010c6a0 in dumpstack_gdb(bool) ()
#2 0x0010cc8c in signal_handler(int, siginfo_t*, void*) ()
#3 <signal handler called>
#4 raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:51
#5 <signal handler called>
#6 0x69e73794 in RSA_verify () from /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1
#7 0x69e7206c in ?? () from /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

However when investigating on my RPI, I find that libcrypto1.0 is installed aside libcrypto1.1. See below. So I don't see the issue.

pi@MyRaspberrypi:/usr/lib/arm-linux-gnueabihf $ ls -al libcrypt*
-rw-r--r-- 1 root root 41292 jan 14 2018 libcrypt.a
-rw-r--r-- 1 root root 1123644 nov 2 2017 libcrypto.so.1.0.0
-rw-r--r-- 1 root root 1497376 mrt 29 2018 libcrypto.so.1.0.2
-rw-r--r-- 1 root root 1827956 mrt 29 2018 libcrypto.so.1.1
lrwxrwxrwx 1 root root 38 jan 14 2018 libcrypt.so -> /lib/arm-linux-gnueabihf/libcrypt.so.1

Don't know how I could force Domoticz using the version 1.0... Of course, I would prefer that my loging, HTTPS, ... keeps on working. After a bit of searching in the forum, I saw that the absence of the libcrypto generates such kind of problems.

The plugin that generates the problem is to detect chromecast devices on my network. The plugin itself is also published in the bug report, together with the crash report.

Thanks for your help!

Filip

Posted: **Friday 07 June 2019 21:08**

Anyone a silimar problem? Get not out of the problem...

Posted: **Friday 07 June 2019 21:46**

Filip wrote: ↑Friday 07 June 2019 21:08 Anyone a silimar problem? Get not out of the problem...

If I do the same ls as you, I see a second symbolic link. Have to admit that I cannot remember when / how it was set but maybe worth a try ?

Code: Select all

/usr/lib/arm-linux-gnueabihf:#ls -al libcrypt*
-rw-r--r-- 1 root root   41292 Feb  6 22:17 libcrypt.a
lrwxrwxrwx 1 root root      38 Feb  6 22:17 libcrypt.so -> /lib/arm-linux-gnueabihf/libcrypt.so.1
-rw-r--r-- 1 root root 3169152 Nov 28  2018 libcrypto.a
lrwxrwxrwx 1 root root      16 Nov 28  2018 libcrypto.so -> libcrypto.so.1.1
-rw-r--r-- 1 root root 1501512 Feb 27 21:58 libcrypto.so.1.0.2
-rw-r--r-- 1 root root 1848612 Nov 28  2018 libcrypto.so.1.1

Posted: **Saturday 08 June 2019 8:14**

I will give it a try however it is strange.. Domoticz would require version 1.0 of the libcrypto while the simbolic link you mention is really pointing to the libcrypto 1.1..

Posted: **Saturday 08 June 2019 8:39**

Problem solved!
I noticed there was a new version of the library pyChromecast.
Upgraded to the new version and problem solved.
Thanks for triggering thinking me further.
F

Domoticz

[SOLVED] Problem libcrypto?

[SOLVED] Problem libcrypto?

Re: Problem libcrypto?

Re: Problem libcrypto?

Re: Problem libcrypto?

Re: Problem libcrypto?