UTMStack stops collecting

[KevCar69]

I have 1 server (windows), who disconnects about 1 hour after connecting. If I go and look at the winlogbeat logs I can see that the logs are no longer collecting. These are the NDJSON files that create a new file once they hit 10,000KB. Everything just seems to stop although all the services are running. In order to get it working again I have to stop the agent service and restart it. The other 4 servers are working just fine.

[c3s4rfred]

Hi, @KevCar69 we need more information to help you: all you can about the environment, network, virtualization system (if any), UTMStack version, but, overall things, compare the other 4 servers with the one with the issue, its configuration, etc. Seems to be something related to that, check the integration guide to check the installation and configuration steps.

Best regards

[KevCar69]

Thanks for replying. I have investigated the differences between the 2 and there is not much. But, its does have a different AV on it but I removed it and still having the same issues. Both servers are DC's but this one is also a print server. One thing I have noticed is a problem installing. I have uninstalled it and removed the folders, rebooted. When I try to install it I get an error that states, error installing the UTMStackagent service. When I check the log this is what its saying.
"/agent/main.go 64 failed to register agent: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake"

[c3s4rfred]

That agent error is because we released a new version of the platform which only uses secure protocol to exchange information with agents. You need to update your instance before trying to install new agents.

Best regards

[KevCar69]

Thanks. After upgrading, uninstalling the older version, deleting the left-over folders, rebooting, the agent installed.
But after updating the other servers are now disconnected. I would expect the updater service to update to the latest version but that does not seem to be happening. I don't see any docs on the agents updating. Restarting the updater service give me this in the logs
/update.go 18 enviroment: release

[KevCar69]

Ended up just uninstalling and reinstalling the agent. The good new is that the problem child is working now and not stopping. Thanks for the help.