21 Mar 2024 08:11 AM - last edited on 28 Aug 2024 09:55 AM by MaciejNeumann
Hi,
My client encountered an unusual behaviour of OneAgent after upgrading to version 1.283.154.20240215-231351. The problem was that after reboots the custom services part was not detected again and an additional reboot was required.
Have any of you encountered this situation? I suspect it's a matter of some correlation on the environment, but it wouldn't hurt to ask either;)
Radek
23 Mar 2024 09:18 AM
Hello!
If oneagentctl --healthcheck - SUCCESS - I would think this is a network connectivity issue.
.NET or Java?
I had similar issues with versions(200+) previously, but in most cases it was network connectivity issue / or unavaliable - 15 seconds-30 seconds.
And yes, restart helps.
You can check the logs yourself, without it we can only guess😊
Regards,
Alex Romanenkov
25 Mar 2024 12:07 PM
From what I've established with the client it's a problem with the app getting up faster than OA. This behaviour fully explains the error.