Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.

Running Pulseway RMM on OpenSUSE LEAP / SLES 15

Running Pulseway RMM on OpenSUSE LEAP / SLES 15

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.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments
Apologies, I modified the 1st step to properly enable the Legacy module using SUSEConnect command.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2018-08-28 22:16
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.