Using USB external hard drive as backup devices and each drive can be recognized if manually added to the notifications/storage screen but I need to know if there is a way to set this to be automatic when the drive is replaced either daily or weekly. Also, where would this be set globally for are servers being monitored. Currently have 8.6.8.
Onsite IT Services
Hi, i want to know how i can monitor the dropbox daemon on linux, i'v tried things with workflow but when i stop the service manualy it won't send me a notification or try to restart the service, and that is bothering me becaus on our servers we need to have dropbox running all the time for our application, i know that dropbox is weird on linux, it won't show with systemctl, but it's still like a daemon.
I'm running debian buster machine all up to date with the last pulseway agent
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,
Hi. I have a CentOS machine that I've been trying to get pulseway working on. I could not find anyone having the same problem.
I have successfully installed pulseway, or at least the system thinks so. I edited the config file and removed the sample text from the name. However, when I attempt to start pulseway, the terminal gives me no indication of success or failure. However, when I check the systemctl logs, it claims that pulseway failed to start because of a missing file. I searched for the file, and it was indeed there. Can anyone help me with this?
Here's what it says:
"delta systemd: Failed at step EXEC spawning /usr/sbin/pulsewayd: No such file or directory"
***This problem has been solved, I was unaware that my server was x64 based***