Information and Support

And now we see it Inactive. It it stays this way for 29+ minutes, it will then change to Disconnected status. Last communicated on 2023-02-09 13:02:30.

You're welcome. I forgot to allow you for posting, you're all set now without our having to moderate.

They don't include any when we order them either. We used to provide them but most people have dozens of old USB power supplies laying around. Any 5v 1amp will do. Example; USB wall plug from ebay Probably bags of them at the local Goodwill :).

@shahinfard Hi, Please double check that all the settings are now associated to the HW agent.

Hi, When you order hardware from the main site, it doesn't show in the app site because the app site doesn't have the same paypal coding. The hardware agent is a one time purchase and can be used with either the free Community reports or Extended. If it's ordered as a bundle, the hardware and the reports are sold as a package deal from the main site. The hardware is manually prepared, shipped and then bundle time is then added to the agent ID. Once you activate the agent, the Extended reports will start. I'm not sure if this is helping to explain but if not, please add more information and we'll try to further explain.

@markl Hi Mark, I recall during the tests we made that if the agent was connected to one network the speed tests were coming in correctly while connected on the other one they didnt. Is this the situation?

@SBK No matter if it's the primary WAN is up or not, 192.168.0.1 always remains up even during the failover or failback process. I verified this in my first post. That's why I said the agent reports something incorrect, because it reports that 192.168.0.1 is down when actually 192.168.1.1 is down.

Trashing us publicly for trying to help you doesn't make any sense. You told us you have had up to 30 agents running and said it was great that it's free. As an admin yourself, surely you can appreciate the complexity of this problem. Even as a free member, we are still committed to helping because we want to find and solve the problem. The problem is not widespread. If it was, we would be hearing about it a lot but we aren't. You are running 2016 servers and it's quite the task to have a single software that runs across all Windows versions. Losing track is easy because it's a very long thread, and we've made other updates in some of the releases. The dev told me it was fixed in 1.75 but the log you sent us was 1.77 so clearly there is simply something that got out of sync. If the agent is not working for you, we do not know why. I can tell you that the Windows dev has been working on yet another release to try and improve the fixes recently made but I don't know if that will solve why only some of your agents are not working right. I'll reach out again to try and find out what he meant by pointing out 1.75 as being fixed.

@OutagesIO_Support Never mind. I searched for that command you suggested, "ps cax | grep otm_binary", in the forums and saw it mentioned to run the script, "sudo ./starter.sh". And now I'm back up and running! Thanks! Clay

@claytonbcollins said in Can't delete Agent: 129098 and switch the Extended service to 129112, Done Please confirm all is ok and let me know if you could change the address

@SBK Unfortunately, my extended subscription has expired, so I can no longer check it. Will renew again and let you know.

@OutagesIO_Support Excellent! Thank you so much for your help and I'm glad I was able to get you more data to analyze for the bugfix. Let me know if there is anything else you need from me, otherwise I'll be looking forward to the firmware update. Thanks again!

@OutagesIO_Support OK. So let's close this thread. I have reverted to windows everything is working and data is being processed. I will attempt the Linux on again but will purchase another mini pc at some point. Would be nice if there was an installer for Linux as there is for windows, so there must be a reason that this has not been done, I do not know or understand. Thanks to all who have offered assistance and provided comment, I need to familiarise myself with the Linux system before trying again. Anyway now on windows 10 pro, windows 10S did not work to many restrictions and hoops to jump through. Thanks All

Hi, Our agents run on Windows, Linux, Raspberry and other devices. We don't have an agent for Android. We tested quite a bit and it was pretty much impossible to do it so that folks could get quick alerts and it used up the battery very quickly since it's constantly using the network and consequently, data. However, you can install the agent on a PC/Laptop that you'll keep on at the location you'd like to monitor and can log into the control panel to view your reports using any mobile. Hope this helps.

@outagesio-greenwich-k12-ct-us Hi, Definitely a bug introduced in a recent commit: thank you for highlighting. The fix has already been applied: please test it ASAP to confirm all is fine now.

Hi, Thanks for posting your question. Here is what I see and with more information maybe we can figure out what is going on. [image: 1630945903297-new-agents-become-inactive-2-still-active-4-total.png] First, we need to eliminate 128292 because it isn't properly installed. From what I can see it looks like it was working, then you re-installed it and that installation never completed. What ever machine you installed this one on, you will need to make sure there aren't two agents installed on that same machine because we have seen cases where this can happen. If you have two, just remove both from the PC then use the re-install function in the agent's dashboard to re-install it. Next, I notice that all of these agents are in the Philippines which is fine but I see them all at the same address, all using the same provider. Is it safe for me to assume that you are trying to use OutagesIO to not only monitor the Internet service but also different LAN segments? Meaning, perhaps you have an agent installed on different floors and each as its our routing switch. Next, I need to understand what you mean by 'active' agents. Agents only go into another status based on if they can reach the OutagesIO network or not. As long as the agent software is running on the PC, does have the correct firewall rules, then it should be able to run normally. As you mention, those things are fine on the PC but it sounds like there is something else on the network that might be preventing some of the agents from communicating correctly. If you search for 'statuses' or 'inactive' on this support site, you'll find several explanations of what the different statuses mean. In the most basic sense, Inactive means the agent wasn't able to reach the OutagesIO network for around 20 seconds or more. If you see Disconnected, this means it's been at least a half hour. If all of these agents are on the same network, then you'll see different things potentially. Until I know more about how you are using all four and why they are in the same building, I'll have to wait to continue.