Jump to content

windracer

Members
  • Content Count

    40
  • Joined

  • Last visited

About windracer

  • Rank
    IT Sidekick

Profile Information

  • Location
    St. Pete, FL

Recent Profile Visitors

1582 profile views
  1. Here's the line I use: <Service Name="plexmediaserver" DisplayName="Plex Media Server" IsDaemon="true" DaemonType="SYSVINIT" Path="" StartParameters="" CanBeStopped="true" Enabled="true"/> This works for me on Ubuntu 20.10.
  2. Interesting. Using @ghodder's instructions from July last year, I was able to get the 6.0.1 agent running on my new Pi 3 B+! But the same instructions fail to work on my original Pi B+. I noticed that the old Pi is armv6 and the Pi 3 is armv7. Maybe that has something to do with it? Still waiting for that 6.1 agent on Linux!
  3. I got a new Raspberry Pi 3 B+ (running jessie 9.6) and this is apparently still a problem. Any idea on when I'll be able to run the pulseway agent on a RasPi again?
  4. Any idea on when 6.1 will be out for Linux?
  5. I had to re-apply my symlink changes after upgrading to Ubuntu 18.10. So I'm still using the 1.0.0 versions of libssl.so and libcrypto.so to get Pulseway to run. Seems odd that switching to v1.1 wouldn't be on the roadmap.
  6. I took yet another shot at this (since I got it to work by changing symlinks on my regular (Intel-based) Linux server) and it still doesn't work. I installed libssl1.0.0_1.0.1t-1+deb8u8_armhf.deb and then fixed the libssl.so and libcrypto.so symlinks so they point to the 1.0.0 versions of the files (also tried 1.0.2): 11:18:19 /usr/lib/arm-linux-gnueabihf:$ ls -la libssl* -rw-r--r-- 1 root root 490932 Mar 29 06:51 libssl.a lrwxrwxrwx 1 root root 15 Sep 14 11:18 libssl.so -> libssl.so.1.0.0 lrwxrwxrwx 1 root root 44 Jul 20 22:04 libssl.so.0.9.8 -> /usr/lib/arm-linux-gnuea
  7. 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.
  8. Pretty sure I already tried that, but did it again. Still nothing, same result. Jul 24 17:02:26 pidp8 systemd[1]: Starting LSB: Monitor and Control Everything IT from Any Smartphone or Tablet... Jul 24 17:02:26 pidp8 pulseway[1032]: /usr/sbin/pulsewayd: /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /usr/sbin/pulsewayd) Jul 24 17:02:26 pidp8 pulseway[1032]: /usr/sbin/pulsewayd: /usr/lib/arm-linux-gnueabihf/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /usr/sbin/pulsewayd) Jul 24 17:02:26 pidp8 systemd[1]: Started LSB
  9. Still no luck. Jul 20 22:00:53 pidp8 systemd[1]: Starting LSB: Monitor and Control Everything IT from Any Smartphone or Tablet... Jul 20 22:00:56 pidp8 pulseway[16522]: /usr/sbin/pulsewayd: /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /usr/sbin/pulsewayd) Jul 20 22:00:56 pidp8 pulseway[16522]: /usr/sbin/pulsewayd: /usr/lib/arm-linux-gnueabihf/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /usr/sbin/pulsewayd) Jul 20 22:00:56 pidp8 systemd[1]: Started LSB: Monitor and Control Everything IT from Any Smartphone or Tablet.
  10. Any chance on getting an updated version that works without all of these libssl hoops to jump through?
  11. That didn't work for me: Jul 18 20:01:25 pidp8 systemd[1]: Starting LSB: Monitor and Control Everything IT from Any Smartphone or Tablet... Jul 18 20:01:26 pidp8 pulseway[27509]: /usr/sbin/pulsewayd: /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /usr/sbin/pulsewayd) Jul 18 20:01:26 pidp8 pulseway[27509]: /usr/sbin/pulsewayd: /usr/lib/arm-linux-gnueabihf/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /usr/sbin/pulsewayd) Jul 18 20:01:26 pidp8 systemd[1]: Started LSB: Monitor and Control Everything IT from Any Smartphone or T
  12. 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
  13. 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.
  14. 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: CRY
×
×
  • Create New...