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.
- SUSEConnect –product sle-module-legacy/15/x86_64
- zypper in libopenssl1_0_0
- 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
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
- zypper in https://www.pulseway.com/download/pulseway_x64.rpm
(ignore if it complains about unsigned)
- cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xml
- 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.
Description=Pulseway server daemon
At this point you can:
- systemctl daemon-reload
- systemctl enable pulsewayd
- 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.