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
-
Ok thank you.
Checking this morning, many servers are reported disconnected from outages.io meaning updating to .NET 4.7.2 did not solve the issue.
-
Hi,
If you re-install yet again, you'll get the same version but with the cert fixed. Here is the answer to your question about the various services.
OtmWinClient is the actual client app. This is the same app as on the other platforms and is build from the same source code.
OtmService is a windows service that launches and kills OtmWinClient. This is accessible via the windows service control and starts otm when windows boots.
OtmServiceApplication is the app that shows the tray icon and allows to start/stop the service via a popup menu. This is maybe badly named and would be better named as OtmTrayApplication.
The rest, we are still working on and are building servers so we can test here as well.
-
Thanks for the clarifications.
Are you building Windows servers to test ? Should I wait for your instructions before testing any further ?
-
Yes, Windows servers for testing. I'm not sure which yet but one is a very old 2003 server. I don't seem to have a 2016 version otherwise I would give that a try too.
You can try the most recent version just to see if the cert problem is gone which it should be otherwise, it's just a matter of time for us to do some testing, coding, testing.
Here is what I know so far.
The current and previous versions of the installer is already installing for “all users”.
It will probably work on most server editions as long as it’s 64 bit.
On server, each user gets a copy of the tray icon app.
That tray icon app just starts and stops the service.
There is only one instance of the agent running but multiple instances of the tray app. That should not be a problem. It should be possible to restrict that to administrators so I will check that.
I know we touched on this but you could try what we talked about. Make sure all instances are removed then re-install just one as full admin using the new version and see what happens.
The new version pulls everything down needed so maybe it would pull something down that got missed before.
-
It's a lot of effort to update all the servers as I need to do it manually. I there a way to do an unattended installation so I can script it ?
You can download Windows Server Evaluation (180 days trial) here : https://www.microsoft.com/en-us/evalcenter/download-windows-server-2016
-
Thanks, I'll give it a try.
Which version are you using, standard or datacenter?
I'll try standard first since you mentioned a number of people can log into this server. -
No luck. I'm not a Windows person so cannot get 2016 running right. Just trying to get RDP access to it and cannot.
I'll have to find someone that knows MS.
-
@OutagesIO_Support we use standard edition. You may need to allow RDP in the Windows firewall.
-
Yes, I just can't move around. I built it as a vm and the mouse doesn't work. It didn't work using 2003 either so maybe those are too old to fully funtion on vmware 6.7. I'll give it one more try on proxmox.
BTW, did you try the current version? It's got a change in it that may pull down something missing. I think the dev is waiting to get some feedback from you to know what to look for because we aren't sure why the service might stop on 2016.
-
The current version is deployed on a server but I don't know if it's working properly or not. I need to deploy it to all the servers to notice if there's a problem or not.
Is it possible to make an unattended installation ? It is too time consuming to upgrade all the servers manually.
-
We have no unattended version because each agent has to be assigned to the correct report/owner which happens at installation time, those codes you use. The codes are what create the association.
I would just pick one server and see if we can get that one going. You said all of the servers should be identical so if one works, the rest should.
Can you expand on why you're not sure if it's working or not. Can you share the ID and I'll take a look.
-
The agent ID 128994 was updated to the latest version.
I am not sure if it is working because I don't know if the OtmWinClient.exe process has stopped or not since I updated it (my servers are not always on, we shut them down at night).
I just realized I can set a monitor on this process. It will log an alert on Itarian (my remote management tool) when OtmWinClient.exe has stopped. I also configured an auto remediation action that will restart the OtmService. It might solve my problem.
Would it be possible to update existing installations without needing to re-enter the keys ? Because I can't update manually 22 servers every time there is a new release.
-
No, nothing is coming in from that agent, it is not communicating at all.
It's not possible to update agents without the keys. As I mentioned, it's because those keys are what are used to assign the software side that you install to the reports on OutagesIO.
That would be a nice idea for the Enterprise side of our service but I'm not sure how it could be done. The software still has to know which reports/member owns it.
Once we have a solid agent, it usually doesn't change much unless MS changed something that forces us to have to update.
I'll bring it up as a topic however.
-
The server was shutdown yesterday so it is normal there was no communication from that agent.
My fix seem to work (restart OtmService if OtmWinClient.exe is not running) and all the agents are now up. It's a bit of a dirty solution but it was at least simple to implement.
For other softwares like Itarian or Teamviewer agents, it is possible to embed the authentication keys in the installer and the agents update automatically. When I deploy the Itarian agent, I just double click on the installer and the agent will be automatically configured with my account and reporting to the management portal.
-
We're going to try testing on a 2016 here as well.
If the same key could be used, that would work but right now, I don't see how agents can be installed without a unique key as they would not know which reports to write to.
I've got it in my notes as something to bring up.
However, something like this would only be available in our Enterprise level service as the lower levels aren't really built to handle so many agents.
-
The agent 128994 which is under the latest release has already stopped 9 times this morning, see below the logs.
(ON means the monitor is triggered because the agent is not running, OFF means the monitor is not triggered because the agent is running).
2022/06/28 12:33:18 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:33:14 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running 2022/06/28 12:31:37 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:31:33 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running 2022/06/28 12:30:01 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:29:57 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running 2022/06/28 12:26:52 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:26:48 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running 2022/06/28 12:25:14 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:25:10 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running 2022/06/28 12:08:28 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:08:24 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running 2022/06/28 12:06:21 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:06:17 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running 2022/06/28 12:05:09 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:05:05 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running 2022/06/28 12:01:28 PM OFF Process Monitor : Condition: OtmWinClient.exe is not running - Status is running 2022/06/28 12:01:22 PM ON Process Monitor : Condition: OtmWinClient.exe is not running - Status is not running -
That's great, thanks. Any more logs or information you might see that can be shared?
-
Why don't you change the apps to admin in the properties box (compatibility tab \ run as administrator) and see if that helps.
-
Only the top-most entry is shown. So it would be interesting to see if the others have the same “fault offset”
