I was in the process of configuring my Pulseway agent on a VPS running Ubuntu Server 20.04 and I ran in this interesting bug.
Even using the sample config provided by the agent, uncommenting the Ping Responses bloc throws this error in the log, and prevents the service from starting.
vps pulseway: Starting Pulseway Daemon version 6.5 (2019082205) vps pulseway: Configuration: Values for 'Milliseconds' attribute at 'PingResponse' node 10.6.0.53(1) should be between 1 and 1000 vps systemd: pulseway.service: Main process exited, code=exited, status=1/FAILURE
The PingResponse bloc in /etc/pulseway/config.xml looks like this:
<PingResponses> <PingResponse Address="10.6.0.53" Milliseconds="1500" Minutes="1" PriorityOnSlowResponse="1" PriorityOnNoResponse="1" Alias="vps DNS notif" Enabled="true"/> </PingResponses>
So then I tried many Milliseconds values between 1 and 1000 but the same exact error always comes back.
Is this a known issue or is there anything wrong with my setup?
Many thanks to anyone who can help,
By Canadian Dental Services
I recently did a clean upgrade to Windows 10 on 2 WKSTs previously running Windows 7 with Pulseway installed. I am now at a loss as to how to re-add these units to my Pulseway instance.
I see they are still showing up in the “Deployment Successful” tab under “Discovery & Deployment”.
Is there a way to re-add these units without manually installing the Pulseway app on these WKSTs?
Hello, I have a question about the Pulseway app. When the pc is on all of the commands work great and are perfect for managing the pc. But I am attempting to turn on my pc when I am away from my home and then be able to fully control it like I was there. The issue is how the wake up command from sleep or from powered down will not work even when on my home network. How can I fix this. Also a side question, is there a way I would be able to see a live view of the screen or does it only allow screenshots of the screen. Thanks
We reinstalled Pulseway on a re-imaged system and after the install we noticed issues. In the patch mgmt section, the status was "assign failed" in red. We rebooted the system and then the service was not starting. We checked the service, it was set to start automatically and in the event log it was generating this error: "Service cannot be started. The handle is invalid" We removed the system from Pulseway, uninstalled, and reinstalled. Service is starting normally, but still getting the same issue of the patch policy failing to assign. I tried moving the system to another group that did not have a patch policy at all and got the same result.