Aaron Trujillo

We recently noticed a problem with our Pulseway notifications, on one of our Linux servers that is running Cassandra. The Cassandra service had been put into the following state: Active: active (excited), unfortunately we never received notification about the excited state. I did some testing and when I manually stop the service, it shows Active: inactive (dead), I do get notifications. I am at a lose as to why I get notifications when inactive (dead) but not when it is Active (excited). This is the current configuration: <Service Name="cassandra" DisplayName="cassandra" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="true" /> If I change DaemonType to any other setting: NONE, SYSVINIT, or UPSTART, the service will not be recognized at all by Pulseway. So I am fairly confident that SYSTEMD is the correct parameter here. What is the correct way to set this up, so that I get notifications when its dead and/or excited? Thank you for your help.

Today i got a notification that read as the following: I am not sure how this was set up in our configuration. Is this an standard out of the box notification that is there regardless of set up or has it been set up to monitor disk space by someone on our end? If so can you tell me how that is so? Thanks.

Bottom line... can i change the computer identifier to something new? I am using a copy of a VM.vhdx to create a new secondary VM. However, the computer identifier is the same on both after setting them up. What do I need to do to create a new computer identifier? Deleting and reinstalling Pulseway is not enough, it still shows up with the same one. I assume somewhere deep in the registry I need to delete some things to stop this from happening. Thanks

So I copied a VM hard drive from one server to the next (lets say it was HDDx1), I just need to make a redundant VM (lets say it is HDDx2). I have done this successfully many times but never on VMs that are monitored by Pulseway. After I set up HDDx2, I did a system prep and reinstalled windows on it, gave it a new IP and name (I also renamed the copied VM HDD as well). Everything seems fine, except for Pulseway. It continues to send notifications that HDDx1 public IP has switched to HDDx2's IP and vice versa... What information can you provide to help me with this? I have tried uninstalling and reinstall Pulseway but it continues. I am not sure if I am fully uninstalling Pulseway though... any help would be appreciated.

Can I get some step-by-step instruction for getting notification emails? I have my email set in the account overview and the email notification tab checked... but i do not get any notifications by email... Thanks

UPDATE When Kamailio is manually stopped (service kamailio stop) Pulseway will send a notification to me and the status shows: ● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/lib/systemd/system/kamailio.service; enabled) Active: inactive (dead) since Thu 2016-11-17 10:48:43 MST; 5s ago But when i kill one of the child process (kill -9 15489) Pulseway does not send notification and the status shows: ● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/lib/systemd/system/kamailio.service; enabled) Active: failed (Result: exit-code) since Thu 2016-11-17 10:45:01 MST; 3s ago Apparently what is happening is one of the child processes is being killed and this sends a message to kill all the processes and this obviously stops or kamailio service from working correctly... So why am I not getting notification when it is in a failed state? Is there a way to fix it so that i do?

More information... So it appears that if i stop the service manually i do get notifications, but the two times that the Kamailio service stopped/crashed in the middle of the night, i did not get any notifications.

My Kamailio has gone down twice in the last two weeks and i have not been getting notifications through Pulseway. Above is the Kamailio service in a running state and below is my configuration set up, for that service to be monitored. Any guidance in fixing this problem would be greatly appreciated.

After installing some new software (not related to Pulseway) a reboot was required. As it happens, the server went down and no notifications were sent out. Looking at the Pulseway manager it looked like it was monitoring the server, however i got NO notifications about the downed server. When i ran a service pulseway restart... i quickly got a notification that the server was on-line. That seemed to resolve the problem. My question is why does Pulseway not automatically do a restart when the machine is rebooted? Is this something i need to do every time a server is rebooted? I use Jenkins when i need to run mass jobs on our servers. Should i create a job that restarts the Pulseway service daily to avoid this from happening again? The only downfall with that is i don't want daily notifications that the server us up and running like it would send with the restart. Any thoughts would be greatly appreciated.

When a specific service goes down, i am getting the appropriate notifications; however, when it comes back on-line i am not getting any notifications. I would like to know when the server goes down but also when it comes back up... any ideas?

I hope that this will be a simple question to resolve. I need to enable repeat notifications that are sent to my phone. If i miss a notification and i may never know it is there if i dont get follow up notifications. How do i set this up to allow repeat notifications that are sent to my phone app?

I am setting up the Ping Notification feature and need some insight into how it works. My understanding is that it pings the selected device every 5 seconds. Is this a consistent 5 seconds for as long as i have the device added to the ping feature? I don't know that i need it to ping every 5 seconds (can this be changed) 300ms for 1 minute, i dont understand this... how often is it checking the device? Any help would be appreciated, Thanks.

I am new to SNMP and I'm having a little trouble getting set up. I understand that SNMP works by trapping signals sent from the Agent and they are sent to the Master. I don't see any 'trapping" in the Pulseway set up. I have successfully discovered a test device and have been able to pull up the MIB/OID list. This list however makes very little sense to me as it doesn't explain what I am trying to monitor. Could somebody give me some depth in this subject. What is Pulseway monitoring exactly? How do i determine what the OID is? Is there any trapping actually going on? Any info would be greatly appreciated!!! Thanks, Aaron

Thanks Paul, That is what i figured i would have to do, i was just hoping maybe there was a simpler way. thanks,

I have MegaRaid controller cards in several of my servers. On my Windows servers I can use an app called MegaRaid Manager that logs errors and other info to the application event log that Pulseway monitors for me wonderfully. However, on my Linux servers the app different, it is called StorCLI. I can get plenty of information from this and even have a log generated but I don't know how to get Pulseway configured to monitor it. Any help would be appreciated, Thanks, Aaron