Hi. A few times I’ve gotten the email that my node wasn’t connected. Exery time, I find I +can+ connect to the mgw310 and it seems pretty healthy….. BUT… when I go into Graphs, I can SEE it’s not reporting back to the website. Every time, a reboot conducted manually through the mgw310’s web interface has fixed the problem.
I could script a want to disable and enable the power TO the mgw310, based on receiving the email message — I don’t think it’s smart to do this with linux systems — even embedded linux.
YOU on the web side are not receiving anything from my node — there is nothing beyond the email that you can do.
My idea is to create a linux function to gracefully reboot the mgw310 (it exists behind that button in the UI)!!! They give the node operator a frame to send TO the node that will reboot it….. like a ping frame to an odd port number…. something like that.
Then, when we receive the “not responding” email, we can script an odd ping to automate the reboot!!! and maintain a high uptime.
THANK YOU,
Tom Miller
Please authenticate to join the conversation.
In Review
💡 Suggestions
10 months ago

tmillerj
Get notified by email when there are changes.
In Review
💡 Suggestions
10 months ago

tmillerj
Get notified by email when there are changes.