Track Internet disconnections, provider outages with historical data, and automated speed testing.
For Windows, Linux, ARM64, ARMa7. Learn more by visiting www.outagesio.com
Notice: If you created an account on app.outagesio.com, simply use the same credentials to log in here.
Agents is running but not reporting
-
There is a problem with this link https://downloads.outagesio.com/otm/OtmWinClient.exe-V1.73.zip, it's a .2203 extension file inside.........
-
Yes, just rename the file to exactly what you see in the directory as mentioned above in the steps.
-
Just tried that, it doesn't work. The service get stuck on "Starting". I did that on a fresh install of Windows Server and Client v1.69. And I can't find any logs.
-
Maybe that's indicative of what ever is going on with your instances then because we can replicate this and it works every time.
Perhaps fully un-install the agent again, make sure the echo networks service and directory are removed then re-install.
Right after re-installing, stop the service, replace the file with the one shared here then re-start the service again.
Wish we could get remote access to one of these servers, it certainly would help us to help you quickly. Is that possible, even something like Anydesk while you're there monitoring?
-
I can look into it but I don't think I can provide that.
We are still testing the new version and working out bugs so maybe we'll have the new agent out in the next few weeks.It's taking longer than usual because this problem has been highly difficult to pinpoint.
Glad you're still willing to try so please hang in there and once we solve this, you should have something that will work well for you.
-
Hi again,
If you get the chance to try the latest version, it seems to be working properly now.
We've tested for weeks on most Windows versions including yours and the agent never stopped.
Hopefully, this will be your experience too.
If you try it, be sure to fully uninstall the old version and use the installer to re-install an agent.
-
@lp4y said in Agents is running but not reporting:
@SBK Ok I will test it
If you can, re-install completely on maybe a handful of servers making sure they are all running the latest and we can go from there.
-
Yes that's what I'm doing, I'm progressively deploying v1.76 on my servers.
-
@lp4y
Mainly there was a bug happening in a section of the logic that was generating a cascade effect.
So it appeared to be related to Windows Server version but it could have happened in other context too.
Thx for you patience that allowed the devs to debug it!We really need these kind of feedback
-
Happy that you stuck with us to this point.
Can you let us know how things go once you feel the agents are working as expected. As SBK mentioned, feedback is highly important to us and helps to improve where ever we can.
-
To give you more context, I work a for a non-profit and I have ~25 computer labs to supervise (one computer lab = 1 server + 15 to 25 thin clients). I install the agent on each server.
Your tool is useful for me to get an idea if
- the internet connection is stable or not (because I can see the last 50 outages and for how long they went)
- if problems are coming from the LAN or the WAN
and all of that for free, which is nice :)
-
Hello.
I have updated all my agents to v1.76 but today I noticed some agents are still not working. E.g. agent 129005 is reported disconnected from the portal :
but the agent is actually running on the server :
and ping from this agent to your server is also working :
I can't see any error in Windows logs.
Restarting the service brought the connection back with your portal.
I have this problem on couple of servers running Windows Server 2016 and also on a PC Running Windows 10 (21H2).
Any idea ?
-
I'll pass this on to our windows dev. It's sad to see this since we spent months trying to find the problem so this is a bit confusing.
Since you don't see anything in the logs, then we need to look at our end to see when the agent(s) stops communicating to see if there is a pattern. Can you provide all the agent IDs involved so we can do that.
The agent is supposed to auto restart every 24hrs so it's possible something is preventing it from doing that and maybe it ends up crashing in memory.
Maybe the solution is to auto restart the service daily. Is that something you could try?
We will look at our end to see if it's going offline around the time it's supposed to restart.
Question
We see 30 agents installed but most of those are always disconnected status.You mentioned these are all Windows 2016 servers so are some of those turned off at night or something or are they supposed to be running 24/7?
I ask because looking into this, we cannot know which servers are supposed to be (or are) left on 24/7.
-
I don't know which agents are involved and I guess it's happening on all of them.
The servers are only on during daytime as they are used for computer labs. They sometimes stay powered on during the night if the students forget to turn them off when they leave the training center.
There is no point of configuring a daily auto-restart as most of the servers are shutdown at night. And some agents which have been up for less than 24hours are reported disconnected.
E.g..at the time of writing this message (11:55am IST time), agent 129006 has been up for 21 hours and is reported disconnected.
-
I asked the Windows dev and he says it's not possible that the agent is not logging what it's doing. Perhaps you're not looking in the right place?
Also, you mention that most of the machines are offline but you said you guess it's happening to all of them.
The problem with that is that it makes it much harder for us to know where to search for problems :).
We absolutely want to see this working for you and right now, you've told us the new version may not be working after we've spent many months testing so this comment makes us quite nervous.
Is there any way you can confirm how many might be having problems? There should be something in the logs if you could take a deeper look. I think it would be in the application log.
