Mark

Hi Norman, Please edit /etc/init.d/pulseway and change : # chkconfig: 98 98 03 with: # chkconfig: 35 98 03 Then run this: /sbin/chkconfig --add pulseway/sbin/chkconfig --level 35 pulseway on Regards, Mark

Hi Toby, Thank you for reporting this. Can you, please, run in Terminal: df -hRegards, Mark

Hi, Just tested now on CentOS 6 with : <Service Name="postfix" DisplayName="Postfix Service" IsDaemon="true" DaemonType="SYSVINIT" Path="" StartParameters="" CanBeStopped="true" Enabled="true"/> and works as expected. Please send an email to support@pulseway.com with your config file and output of the following: cat /proc/cpuinfo uname -a openssl -v ldd --version Regards, Mark

Hi, Can you, please, check the logs for anything related to Pulseway. Regards, Mark

Hi, Just remove pcmonitor from /opt folder. Old java agent was installed via unziping the binaries into /opt folder. Regards, Mark

Is it still an issue? Mark

You don't need to enable it via systemd. It's using SysV and will automatically start on boot. root@localhost ~]# chkconfig --list iprdump 0:off 1:off 2:on 3:on 4:on 5:on 6:off iprinit 0:off 1:off 2:on 3:on 4:on 5:on 6:off iprupdate 0:off 1:off 2:on 3:on 4:on 5:on 6:off netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off network 0:off 1:off 2:on 3:on 4:on 5:on 6:off pulseway 0:off 1:off 2:off 3:on 4:off 5:on 6:off Mark

Be sure that you don't mix 32bit with 64bit packages. If you have 32bit machine install pulseway_x86.rpm. If you have 64bit machine then pulseway_x64.rpm is what you need. Mark Update: I just reproduced your issue: Jan 23 09:58:49 localhost.localdomain pulseway[3869]: Starting pulseway daemon: /bin/bash: /usr/sbin/pulsewayd: /lib/ld-linux.so.2: bad ELF interpreter: No ...directory Jan 23 09:58:49 localhost.localdomain pulseway[3869]: [FAILED] Jan 23 09:58:49 localhost.localdomain systemd[1]: pulseway.service: control process exited, code=exited status=1 Jan 23 09:58:49 localhost.localdomain systemd[1]: Failed to start LSB: start and stop pulsewayd. Jan 23 09:58:49 localhost.localdomain systemd[1]: Unit pulseway.service entered failed state. On my 64bit machine I had installed the 32 bit rpm pulse way package. Again, be sure that you get the right package for your system.

Arch package contain precompiled binaries. You can install it via pacman -U pulseway_x64.pkg.tar.xz Mark

Hi, Can you, please sent us (support@pulseway.com) your config file (after remove all sensitive informations). As well can you please send the output of: uname -a; cat /etc/issue; openssl -v . Thanks! Regards, Mark

Hi, What distro (uname -a; cat /etc/issue; openssl version) are you using? Can you, please, PM your config file? (After removing your username and password) Thanks! Mark

Hi, Do you have any particular software that will change default core libs (glibc, gcc, kernel, OpenSSL) ? I'm asking this because I tested your config with a fresh distro install and works. I'm trying to isolate your issue. Mark

Hi, This is your replay from other thread after I tested your configure file with a vanilla FC16 installation: "Yes, it works. I can see two new machines - one offline and one online. So, what might cause the problem on my machine ? :(" We don't what you have installed on your machine, we don't know how your machine is configured. All our release we test then against fresh VANILLA distributions. And your config file WORKS with a fresh install of FC16. Mark

Hi, What is the version of Debian? (uname -a; cat /etc/debian_version; openssl version). Try to a rm -rf /usr/sbin/pulseway* get latest version from our website and give it a try. If still an issue send me more details about your distro along with config.xml (on PM) I'll try to set up an environment and try to replicate it. Regards, Mark

Hi, We'll have a solution with "Gentoo flavour" soon Pulseway outputs to system logs, /var/log/messages. Have a look there. Mark

So, your config against a vanilla FC16 works. Them must be something local then. Have you installed recently any software that changed core libs? Or any system updates? Mark

Works here using your config: [root@localhost pulseway]# /etc/init.d/pulseway status pulseway.service - LSB: start and stop pulsewayd Loaded: loaded (/etc/rc.d/init.d/pulseway) Active: active (running) since Tue, 14 Oct 2014 02:49:41 -0700; 7s ago Process: 1126 ExecStop=/etc/rc.d/init.d/pulseway stop (code=exited, status=0/SUCCESS) Process: 1146 ExecStart=/etc/rc.d/init.d/pulseway start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/pulseway.service 1152 /usr/sbin/pulsewayd I'll use credential from config.xml that you send it to me and I'll start my FC16 test machine and let me know if you can see it online.

I'll get a vanilla FC16 and try to replicate your issue. Can you, please PM you config.xml after you remove username/password. Thanks! Mark

Hi, Can you, please, download and install this version: https://www.dropbox.com/s/s9nhiiglttznlyu/pulseway-4.5.4-2.i386.rpm?dl=0 Let us know if that fix your issue. Regards, Mark

Hi, What version of Fedora are you using? (uname -a; cat /etc/issue; openssl version). Can you see any errors/crash in logs? (journalctl -f) Regards, Mark

Can you enable core dump on your machine? Will be great if we can analyse the crash. Mark.

Libidn is part of default installation on all distributions (at least the ones that we test pulseway on). We'll do more investigation but libidn it's a dependence for pulseway package (like openssl, wget and ca-certificates). Mark

Do you have any network issues? Looks like "curl_easy_perform() failed: Couldn't resolve host name" trigger the crash...and this point to a network issues. Mark

Great! Good to hear that is working again. Just bear in mind that config.xml from java linux client (old) is not 100% compatible with native linux client (new). Regards, Mark

"confix.xml" permision is 744 (part of install script) unless is manually changed.