Error on Debian 9.1 Stretch

[shadow00caster]

I have Pulseway installed on a fresh Debian 9.1 box and receive the below error:

pulseway[24336]: /usr/sbin/pulsewayd: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
 

Any advice?

[Chris]

Hi,

Currently we do not support openssl1.1, therefore you will need to install openssl 0.9.8

[dpmurphy]

My Linux skills are rusty, but I have two questions.  How did you determine this was your error?  I installed Pulseway on a new Raspberry Pi with Debian Stretch.  Pulseway will not start.  SystemCtrl Status says Pulseway exited, but when I look at the config.xml file, the password has not yet been encrypted.  I have another raspberry pi that was upgraded from Jessie, and that is running fine with Pulseway.

I was able to confirm that openssl 1.1 is installed via the openssl version command, but how does one get the old version installed?  I couldn't find an older version to download. I think it's because there was a security flaw.  Will Pulseway be updating their agent so that it works with 1.1?

 

[Chris]

Hi,

I have installed the Debian GNU/Linux 9.0 (stratch) on one of mine VM's and the issue was with libssl1.0.1.

As soon as I installed libssl0.9.8 the Pulseway service was started without any errors.

wget http://snapshot.debian.org/archive/debian/20110406T213352Z/pool/main/o/openssl098/libssl0.9.8_0.9.8o-7_amd64.deb

Please check this article.

Quote

According to solidot April 7 report, OpenSSL has released a 1.0.1g repair bug, Debian distribution in half an hour to repair bug, Fedora issued a correction scheme of an expedient. The bug was introduced in 2011 in OpenSSL, Use the OpenSSL 0.9.8 found that version is not affected, But Debian Wheezy, Ubuntu 12.04.4, CentOS 6.5, Fedora 18, SUSE 12.2, OpenBSD 5.4, FreeBSD 8.4 and NetBSD 5.0.2 version are affected. If the system allows you as concentrated, recommended patches to 1.0.1g or above.

 

[windracer]

Having the same problem on a fresh install of Raspbian Strech Lite on my Raspberry Pi:

Sep  7 22:21:21 pidp8 pulseway[11554]: /usr/sbin/pulsewayd: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

Is there a way to fix this other than downgrading libssl?
 

 

[ChrystalSolutions]

30 minutes ago, windracer said:

Having the same problem on a fresh install of Raspbian Strech Lite on my Raspberry Pi:

Sep  7 22:21:21 pidp8 pulseway[11554]: /usr/sbin/pulsewayd: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

Is there a way to fix this other than downgrading libssl?
 

 

This is exactly what I'm working with.  I deployed a Pi on a client site and I want to monitor it.

On ‎9‎/‎4‎/‎2017 at 7:22 AM, Chris said:

Hi,

I have installed the Debian GNU/Linux 9.0 (stratch) on one of mine VM's and the issue was with libssl1.0.1.

As soon as I installed libssl0.9.8 the Pulseway service was started without any errors.

wget http://snapshot.debian.org/archive/debian/20110406T213352Z/pool/main/o/openssl098/libssl0.9.8_0.9.8o-7_amd64.deb

Please check this article.

 

Thank you for this Chris.  Do you know where we can get the ARMHF version of this package in version 0.9.8?
I searched on the page https://www.debian.org/distrib/packages  and came up empty.

I also tried:  sudo apt-get install libssl0.9.8 but the response was:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libssl0.9.8 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'libssl0.9.8' has no installation candidate

It would be really great if Pulseway would accept the latest version of openSSL.  Is that possible?

[windracer]

Compiling from source would probably work ... but we'd need a source package.

[Chris]

Hi all,

Last week on Thursday we released a new version of the Linux agent. This version supports up to openssl 1.0.2

[ChrystalSolutions]

On ‎9‎/‎11‎/‎2017 at 6:58 AM, Chris said:

Hi all,

Last week on Thursday we released a new version of the Linux agent. This version supports up to openssl 1.0.2

Awesome, thank you.  Is that version 5.3?

[Chris]

Yes, the latest version for the Linux agent is 5.3.

[windracer]

5.3 still isn't working for me:

Sep 15 18:17:46 pidp8 systemd[1]: Starting LSB: Monitor and Control Everything IT from Any Smartphone or Tablet...
Sep 15 18:17:47 pidp8 pulseway[1119]: Illegal instruction
Sep 15 18:17:47 pidp8 systemd[1]: Started LSB: Monitor and Control Everything IT from Any Smartphone or Tablet.

So it thinks it's started, but it's not. 
 

 

[windracer]

Oh, I see why. I misread the note about the 5.3 agent. It only supports OpenSSL 1.0.2 and my Pi is running 1.1.0f. That's probably the cause still of the illegal instruction. But I do have libssl1.0.2l-2 installed on my Pi. Shouldn't that allow the agent to work? I'd rather not have to go back and rebuild this Pi using Jessie just to get back to an older OpenSSL build just to run the Pulseway agent.

Edited September 17, 2017 by windracer

[Chris]

Hi,

Please send an email to support@pulseway.com and add the output of this command: grep -i pulseway /var/log/syslog

Also, double-check if the config.xml file is not broken.

[windracer]

Thanks, Chris. config.xml is fine. I sent in an e-mail to support. The only result of the grep command is what I posted previously:

Sep 15 18:17:47 pidp8 pulseway[1119]: Illegal instruction

 

[fthl]

Hello,

is there any update on the "Illegal Instruction" issue?

I am running on Raspian 9, latest Pulseway client, I even installed libssl1.0.2 on the system.

Still pulseway will not actually start.

I have this vague idea that for some reason it is still using ssl 1.1, but I can't very well uninstall that ...

Any help or ideas would be appreciated.

[Paul]

Hi guys,

We are still investigating the "Illegal instruction" issue. We appreciate your patience on this matter.

-Paul

[windracer]

Thanks, Paul! I've just stopped using Pulseway on my RPIs for now until this is resolved ...

[fthl]

Is there any update on the illegal instruction issue?

[Mark]

Hi,

As a workaround in Debian Stretch you can install libssl package from Jessie:

https://packages.debian.org/jessie/armhf/libssl1.0.0/download

root@raspberrypi:~# uname -a
Linux raspberrypi 4.14.18-v7+ #1093 SMP Fri Feb 9 15:33:07 GMT 2018 armv7l GNU/Linux

root@raspberrypi:~# cat /etc/issue
Raspbian GNU/Linux 9 \n \l

root@raspberrypi:~# /etc/init.d/pulseway status
● pulseway.service - LSB: Monitor and Control Everything IT from Any Smartphone or Tablet
   Loaded: loaded (/etc/init.d/pulseway; generated; vendor preset: enabled)
   Active: active (running) since Tue 2018-02-13 12:57:24 UTC; 29min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3424 ExecStop=/etc/init.d/pulseway stop (code=exited, status=0/SUCCESS)
  Process: 3462 ExecStart=/etc/init.d/pulseway start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/pulseway.service
           └─3469 /usr/sbin/pulsewayd

 

Mark

[windracer]

I tried installing that package, but it didn't fix the problem for me:

08:42:21 $ sudo /etc/init.d/pulseway status
â— pulseway.service - LSB: Monitor and Control Everything IT from Any Smartphone or Tablet
   Loaded: loaded (/etc/init.d/pulseway; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2018-02-13 08:41:21 EST; 2min 6s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 4862 ExecStart=/etc/init.d/pulseway start (code=exited, status=0/SUCCESS)

Feb 13 08:41:21 pidp8 systemd[1]: Starting LSB: Monitor and Control Everything IT from Any Smartphone or Tablet...
Feb 13 08:41:21 pidp8 pulseway[4862]: Illegal instruction
Feb 13 08:41:21 pidp8 systemd[1]: Started LSB: Monitor and Control Everything IT from Any Smartphone or Tablet.
08:43:28 $

I suspect because I still have the other libssl packages installed:

08:36:24 $ dpkg -l |grep libssl
ii  libssl-dev:armhf                1.1.0f-3+deb9u1              armhf        Secure Sockets Layer toolkit - development files
ii  libssl-doc                      1.1.0f-3+deb9u1              all          Secure Sockets Layer toolkit - development documentation
ii  libssl1.0.0:armhf               1.0.1t-1+deb8u7              armhf        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.0.2:armhf               1.0.2l-2+deb9u2              armhf        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.1:armhf                 1.1.0f-3+deb9u1              armhf        Secure Sockets Layer toolkit - shared libraries

 

[Mark]

Can you try on a brand vanilla environment? (it's what I did here)

1. Download Raspbian from https://downloads.raspberrypi.org/raspbian_latest

2. Install libssl from https://packages.debian.org/jessie/armhf/libssl1.0.0/download

root@raspberrypi:~# dpkg -l |grep libssl
ii  libssl1.0.0:armhf                     1.0.1t-1+deb8u7                      armhf        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.0.2:armhf                     1.0.2l-2+deb9u1                      armhf        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.1:armhf                       1.1.0f-3+deb9u1                      armhf        Secure Sockets Layer toolkit - shared libraries

3. Download and install Pulseway

4. Edit config.xml file

5. Start pulseway via /etc/init.d/pulseway start

 

Mark

 

[windracer]

I don't have an extra RPi to try this on and am not really in a position to rebuild my existing environment from scratch, sorry. Hopefully someone else can confirm the fix ...

[fthl]

Didnt do the trick for me either, and I'm not gonna reinstall the system for this I am afraid.

[Chris]

Hi,

Please try to use this repository to get the appropriate library. http://ftp.nl.debian.org/debian/pool/main/o/openssl/

[windracer]

I tried libssl1.0.0_1.0.1e-2+deb7u20_armhf.deb and libssl1.0.0_1.0.1t-1+deb8u7_armhf.deb from that site. No luck with either. Same illegal instruction error.