GO Agents will not start due to corrupted profiles

[Jamfo Florida]

I am having an issue with the GO Agents on multiple independent servers that I have been struggling with for several months and am reaching out to see if anyone else has seen such an issue and, if so, if they've managed to find a fix.

I have an Active Directory service account that is used to run the GO Agents on multiple servers.  These servers are not clustered; each is a stand-along machine running a stand-alone instance of GO.  I am having an issue where something is going on where the user profile for that account is constantly getting corrupted and this prevents the GO Agents from starting.  My only solution is to change the service account for the GO Agents and disable them, reboot the server and delete the old profile for the service account.  At that point, I can re-assign that account as the service account for the GO Agents and they'll start right up.

As I had mentioned, this is occurring on multiple servers on different hardware, so it's nothing like a bad drive or bad hardware.  Each is running on a fully patched and updated Windows Server 2022 (again, all on separate hardware) and my Event Logs are absolutely clean.

If anyone has seen anything similar and has any hints, I would be happy to listen.  Thanks in advance for any assistance you can provide!

[Sriram Narayanan]

I’ve faced such a corruption when the RAM was bad. I moved the AD instances to ECC RAM based physical servers and the corruption ended. This was with Windows Server 2003. 

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/02408855-fbc8-4837-927b-389de1159638n%40googlegroups.com.

[Sriram Narayanan]

On Tue, 20 Aug 2024 at 12:14 AM, Sriram Narayanan <srir...@gmail.com> wrote:

On Mon, 19 Aug 2024 at 11:58 PM, Jamfo Florida <choochoo...@gmail.com> wrote:

I am having an issue with the GO Agents on multiple independent servers that I have been struggling with for several months and am reaching out to see if anyone else has seen such an issue and, if so, if they've managed to find a fix.

I have an Active Directory service account that is used to run the GO Agents on multiple servers.  These servers are not clustered; each is a stand-along machine running a stand-alone instance of GO.  I am having an issue where something is going on where the user profile for that account is constantly getting corrupted and this prevents the GO Agents from starting.  My only solution is to change the service account for the GO Agents and disable them, reboot the server and delete the old profile for the service account.  At that point, I can re-assign that account as the service account for the GO Agents and they'll start right up.

As I had mentioned, this is occurring on multiple servers on different hardware, so it's nothing like a bad drive or bad hardware.  Each is running on a fully patched and updated Windows Server 2022 (again, all on separate hardware) and my Event Logs are absolutely clean.

If anyone has seen anything similar and has any hints, I would be happy to listen.  Thanks in advance for any assistance you can provide!

I’ve faced such a corruption when the RAM was bad. I moved the AD instances to ECC RAM based physical servers and the corruption ended. This was with Windows Server 2003. 

Relating to myself to add:

The central AD was on that server with bad hardware.

In your case, you may want to review whether something like gpupdate fixes the profile. Looks like an AD issue for this particular service account. What if you create a fresh service account with a different SID together?