Jump to content
Akits

Not running under Ubuntu 18.04

Recommended Posts

Hi

I can't get pulseway to connect to the android app when it's running on my ubuntu 18.04 server. It worked just fine until I updated to U 18.04.
Has this occured to any one else? Is there an solution?

Share this post


Link to post
Share on other sites

Hi there,

Can you check the syslog to see if there's anything logged that's relevant to the Pulseway daemon?

-Paul

Share this post


Link to post
Share on other sites

I'm having a similar problem after upgrading to Bionic Beaver (18.04) ... pulsewayd won't start. At first, after the upgrade, I was seeing this in the syslog:

Apr 26 19:38:34 nucleus pulseway[1006]: /usr/sbin/pulsewayd: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory

So I downloaded the latest .deb and installed it over my existing install. pulsewayd still wouldn't start and now I'm seeing this:

Apr 26 21:19:52 nucleus pulseway[16794]: /usr/sbin/pulsewayd: symbol lookup error: /usr/sbin/pulsewayd: undefined symbol: CRYPTO_num_locks

But now when I try to start it nothing happens and nothing appears in the syslog.

 

Share this post


Link to post
Share on other sites

Hi,

Currently the Pulseway agent doesn't support the libssl version 1.1. You will need to do the following:

  1. Uninstall the Pulseway agent.
  2. Replace libssl 1.1 with libssl 1.0.2 or older versions of libssl.
  3. And finally, re-install the Pulseway agent.

Share this post


Link to post
Share on other sites

Any plans on supporting the newer libssl? This seems like the same problem that prevents Pulseway from running on my Raspberry Pi as well (link). That's been a problem since September last year and it still doesn't work. Very disappointing.

Share this post


Link to post
Share on other sites

I do have libssl 1.0.2 installed, by the way:

15:23:52 /usr/lib:$ dpkg -l |grep libssl
ii  libssl-dev:amd64                      1.1.0g-2ubuntu4                     amd64        Secure Sockets Layer toolkit - development files
ii  libssl1.0.0:amd64                     1.0.2n-1ubuntu5                     amd64        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.1:amd64                       1.1.0g-2ubuntu4                     amd64        Secure Sockets Layer toolkit - shared libraries
15:28:58 /usr/lib/x86_64-linux-gnu:$ ls -la libssl*
-rw-r--r-- 1 root root 328128 Feb  5 05:36 libssl3.so
-rw-r--r-- 1 root root 740092 Apr 25 13:03 libssl.a
lrwxrwxrwx 1 root root     13 Apr 25 13:03 libssl.so -> libssl.so.1.1
-rw-r--r-- 1 root root 426232 Mar 27 13:48 libssl.so.1.0.0
-rw-r--r-- 1 root root 433760 Apr 25 13:03 libssl.so.1.1
15:30:23 /usr/lib/x86_64-linux-gnu:$ ls -la libcrypto*
-rw-r--r-- 1 root root 4832196 Apr 25 13:03 libcrypto.a
lrwxrwxrwx 1 root root      16 Apr 25 13:03 libcrypto.so -> libcrypto.so.1.1
-rw-r--r-- 1 root root 2357760 Mar 27 13:48 libcrypto.so.1.0.0
-rw-r--r-- 1 root root 2575848 Apr 25 13:03 libcrypto.so.1.1

 

Share this post


Link to post
Share on other sites

Hi there,

You need to change the symbolic link to point to the 1.0.0 versions instead of the 1.1 versions.

-Paul

Share this post


Link to post
Share on other sites
On 5/15/2018 at 11:18 PM, Paul said:

Hi there,

You need to change the symbolic link to point to the 1.0.0 versions instead of the 1.1 versions.

-Paul

Any instructions on where to do this? Cant find any pointers on this...

Share this post


Link to post
Share on other sites

Simply rename the old symbolic link using the:

Quote

mv oldFileName newFileName

command then create a new symbolic link using this command:

Quote

ln -s /path/to/file /path/to/symlink

-Paul

Share this post


Link to post
Share on other sites

Hi @windracer

Thank you for your suggestions. Unfortunately this is not on our immediate roadmap, therefore I don't have any ETA for this. 

Share this post


Link to post
Share on other sites

I have two machines running bionic. On one the libraries keep re-St linking back to the 1.1 versions. Would appreciate knowledge no how to stop that happening.

Thanks

Share this post


Link to post
Share on other sites

Hi Ubuggeru,

Thank you for contacting us. Please try to blacklist the package so it is not getting updated.

Share this post


Link to post
Share on other sites

I finally got around to changing the libssl.so and libcrypto.ssl symlinks (to point to 1.0.0 versions of the files instead of 1.1) and the pulseway service started. It concerns me that maybe this could cause other security issues since I'm linking to older versions of the libraries, but I'll continue to monitor (heh) and see what happens.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Hax4dayz
      Ok so the other day i got informed about pulseway by linus tech tips and it seemed a good idea for me to install it on my raspberry pi vpn server for monitoring. But a few days after that my sd card died and i decided to start from scratch and make a new vpn + install pulseway again. But now i cant get the pi to show up at all.
      I installed everything as this post described but cant get it to show up. I did try to search the problem on google but nothing i tired helped.
      My raspberry pi model is the 3b
       
    • By frooky
      I would very much like to see some Arch Linux scripts added or at least include Arch compatibility in the existing Linux scripts. Updating my Arch systems from my phone with a single click would be pretty slick.
    • By remotenerd
      I have installed Pulseway on my unraid server and it has ben working great. I can monitor everything and shutdown/restart the machine. However,  wake on lan is not working at all. I have enabled it in the BIOS and in the OS. I can wake the machine using my router, but not with the Pulseway app. In the config.xml file I have WoWAN set to true and the port to 9 (also tried 50000) and it still doesn't work. Is there something I am missing?
      P.S. I also have a Windows machine that has WOW working perfectly.
      Thank you for your help.
    • By malvarez
      I have a Linux Server that reports as up-to-date version 5.4.
      Is this correct? Because I can't move it in Pulseway 6.0 to another Organization or Site. I get an error message that the agent requires an update.
    • By Rave-Net Computers
      If you need to install on SLES15 or openSUSE LEAP 15 and are fighting with ssl1.0 and systemV script limitations from pulseway 5.4, I wrote a how-to over at Novell's Coolsolutions
       
      https://bit.ly/2PP1OuI
×