Jump to content

Not running under Ubuntu 18.04

Recommended Posts

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.


Link to post
Share on other sites
  • Staff


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.
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


Link to post
Share on other sites
  • 2 weeks later...
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.


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

Link to post
Share on other sites
  • Administrators

Simply rename the old symbolic link using the:


mv oldFileName newFileName

command then create a new symbolic link using this command:


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


Link to post
Share on other sites
  • 1 month later...
  • 4 weeks later...
  • 5 weeks later...

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.

Link to post
Share on other sites
  • 1 month later...
  • 2 months later...
  • 3 weeks later...
  • 1 month later...
  • 1 month later...
  • 9 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By TheTechNerd
      Hi. I have a CentOS machine that I've been trying to get pulseway working on. I could not find anyone having the same problem.
      I have successfully installed pulseway, or at least the system thinks so. I edited the config file and removed the sample text from the name. However, when I attempt to start pulseway, the terminal gives me no indication of success or failure. However, when I check the systemctl logs, it claims that pulseway failed to start because of a missing file. I searched for the file, and it was indeed there. Can anyone help me with this?
      Here's what it says:
      "delta systemd[11600]: Failed at step EXEC spawning /usr/sbin/pulsewayd: No such file or directory"
      ***This problem has been solved, I was unaware that my server was x64 based***
    • By Brayden
      Is there a way I could Ping google.com for example and if below x milliseconds then create error sending notification to my Pulseway devices?
    • By alfred44
      does pulseway agent work on raspberry pi 4 (using debian buster arm64) ? thanks.
    • By Louwrens
      Please expand the list of programs on 3rd Party Patch management.
      Some suggestions:
      Adobe Flash
      Amazon Corretto (Since Oracle Java is not free anymore)
      Google Gsync (GSuite)
      K-lite Codec
      WhatsApp Desktop Client
    • By XxLilBoPeepsxX
      I am attempting to install pulseway on my raspberry pi 3b+, and have downloaded and installed the correct file from the pulseway website, and made sure that my openssl libraries are up to date and correctly setup. I followed through with the given installation instructions and repeatedly the pulseway service is unable to be started. When executing the command sudo systemctl start pulseway, the command works and presents no errors. Upon checking the app or the list of all services, however, pulseway is not shown as a service and there is no devices connected to the app. See the attached images for the output of sudo systemctl status pulseway

  • Create New...