Cool Solutions

Running Pulseway RMM on OpenSUSE LEAP / SLES 15

Rodney Wilder

By:

August 28, 2018 2:16 pm

Reads:676

Comments:1

Score:Unrated

Print/PDF

Pulseway is a relatively popular RMM solution that thankfully supports many Linux distros including SUSE up to SLES12, and even has a 2 device free account to let you test with.  Unfortunately there are a few hurdles to get over currently with their 5.4 release in SLES15 thanks to Pulseway not currently supporting openssl 1.1 yet, or having a proper systemd start script and their systemV init script apparently having some strange init.d function requirement settings.

First we need to enable ssl 1.0.2 libraries from the Legacy release repository / Module.  Note this will leave your openssl 1.1 intact.

  1. SUSEConnect –product sle-module-legacy/15/x86_64
  2. zypper in libopenssl1_0_0
  3. create the libssl.so and libcrypto.so softlinks pointing to the legacy openssl1.0.2 libraries
    ln -s /usr/lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so
    and
    ln -s /usr/lib64/libssl.so.1.0.0 /usr/lib64/libssl.so

Now that libssl1.0.2 is ready, we can install and the pulseway rpm

  1. zypper in https://www.pulseway.com/download/pulseway_x64.rpm
    (ignore if it complains about unsigned)
  2. cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xml
  3. edit your /etc/pulseway/config.xml as appropriate with your account and various settings

Note that the init.d script won’t run as it is looking for various systemV functions under /etc/rc.d/init.d/functions that SLES15 doesn’t have.

Instead, create a basic systemd script named pulsewayd.service under /usr/lib/systemd/system/ with the below, though do note this is a very basic systemd script that can simply handle starting and stopping the pulseway server.  I may provide updates as I learn to tweak this further, or should someone else provide a more functional script.

*move the pre-existing /etc/init.d/pulseway script into another directory so you don’t accidentaly try running it and get confused when it complains about functions missing.

———-

[Unit]
Description=Pulseway server daemon
After=network.target
Wants=network.target
ConditionPathExists=/etc/pulseway/config.xml

[Service]
Type=forking
ExecStart=/usr/sbin/pulsewayd $OPTIONS
KillMode=process
Restart=on-failure

[Install]
WantedBy=multi-user.target

———

At this point you can:

  1. systemctl daemon-reload
  2. systemctl enable pulsewayd
  3. systemctl start pulsewayd

Note: I’m not affiliated with Pulseway, and as such am not responsible for errors, issues or data loss from these modifications should this blow up on you.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...

Tags: , ,
Categories: End-user How-to, File Services and Management, IT Operations Management, Open Enterprise Server, Technical

1

Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

1 Comment

  1. Apologies, I modified the 1st step to properly enable the Legacy module using SUSEConnect command.

Comment

RSS