BartB

Other RMM tools, like LabTech deal with this issue by having a 2nd service that watches the 1st service ad makes sure it is running. Have you guys considered something like that with Pulseway?

Still having this issue on my Debian server: The server info: Description: Debian GNU/Linux unstable (sid) Release: unstable Codename: sid Linux albacore 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) x86_64 GNU/Linux Please let me know if more info is required. Thanks, Bart

I'm guessing that after all this time, there will be no exports posted. Too bad, it would make it much easier to get started, or to expand current functionality.

Sent! Thanks Mark.

OK, the XML tag was just an idea. Thanks for confirming it's not a problem, Paul. No, there are no errors relating to ping in the syslog. The only errors in syslog relating to pulseway involve SOAP and SSL: Apr 29 06:45:36 albacore pulseway: Error while registering computer:SOAP 1.1 fault: SOAP-ENV:Client[no subcode]#012"SSL_ERROR_SSL#012error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version"#012Detail: SSL_connect error in tcp_connect() Apr 29 06:46:56 albacore pulseway: Error while registering computer:Error 30 fault: SOAP-ENV:Client[no subcode]#012"SSL/TLS error"#012Detail: [no detail] I've posted about this issue in another topic, and I'm pretty sure it's not related to ping issues. Any other ideas why ping is not working?

This error is happening on my server constantly, with most recently just a little while ago, when I restarted the pulseway service on my Debian server. Apr 27 12:16:18 xxxxxxx pulseway[18797]: Error while registering online:SOAP 1.1 fault: SOAP-ENV:Client[no subcode] "SSL_ERROR_SSL error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version"...

I'm getting an error in the Ping status on my Linux server, running Debian 8 (Linux x86_64 3.16.0-4-amd64 according to the agent info) It says there is an error, but there are no details on what the error is. When I manually ping 8.8.8.8 from the Command Line, it works fine, both from the server itself and from the Webapp terminal. Here are the relevant lines from the config file: <!--Ping - Server: server IP address or hostname--> <Ping Server="8.8.8.8" Enabled="true"/> I checked the sample config file, which I copied and edited for my needs, and I noticed there is no </Ping> statement. Most other sections have a starting statement and a closing statement: i.e.: <MonitoredPorts> </MonitoredPorts> Could that be the problem? I also can see that there is a background process with the ping command: root@xxxxxxx ~ # ps aux | grep ping root 16329 0.0 0.0 8464 756 ? S 12:03 0:00 ping 8.8.8.8 So the system is at least trying to ping, but maybe the Pulseway agent is not capturing the output. Any ideas/suggestions/fixes?

Currently Rules only allow you to run a Scheduled Task on demand. It would be nice to just be able to run a script, like batch or powershell, instead of having to create a Sched Task that runs that script.

I would like to request that CrashPlan backup monitoring be added to Pulseway.