Lewnatick

I was sincerely hoping that someone would have some feedback on this issue. I would still love to hear some if it's out there.

I recently installed the latest version of Pulseway on my Ubuntu 17.04 server. The service appears to be starting, and I'm not seeing any errors. However, the machine never shows up in the Pulseway app. I feel like I'm missing something simple here. Any advice would be greatly appreciated.

I can vouch for what Chris said above. The support team did indeed get things working again, and I greatly appreciate their help.

The support team is still trying to figure out this issue. Nothing new to report.

Just a quick update for the other users in this thread: I spent some time in a shared session this morning with Pulseway support. They gathered a lot of information, and are doing some internal testing to try and reproduce this issue. Once more is understood about this issue, and more headway is made, I will update here.

The reply was an offer to investigate more thoroughly. I will do my best to relay any helpful details that I can once the investigation takes place. As of the writing of this post, there is no new information to share.

Are any updates available on this issue? My Linux box has been unmonitored by Pulseway for 70 days now due to this.

I've emailed in the requested information. Thank you in advance for the help, I really appreciate it.

Even with the latest version, this is still an issue. My Linux server is going unmonitored because of whatever this bug is. Frankly, I am quite tired of seeing "pulseway: Got exception signal: 4" in my logs. Is there any hope of a fix or work-around for this?

I want to echo what bbb was saying in that I too had the Linux agent stop working on October 13th. I received the same messages in the agent log (see below). Has a work-around for this issue been discovered or are the Pulseway devs working on a fix? I'd really like to get the agent running again. Thanks everyone.