Re: [go-cd] Re: One Agent conflicting with itself

Ketan, thanks for looking at this. For reference I managed to resolve this issue. As I said we use Amazon EC2 instances created on a daily basis from an AMI. When the machines come up the agent is stopped. The machines run a bootstrapping PowerShell script that set the correct agent resources,

Re: [go-cd] Re: One Agent conflicting with itself

I've looked at the code and I don't see this as a problem on the server end. It likely looks like you have multiple agents running on the agent VM. As Arvind mentions, could you run procexp on such agents as to eliminate if the issue

[go-cd] Re: One Agent conflicting with itself

This issue is now officially driving me crazy. Can someone please offer some help as to how to fix this issue. We seem to get this problem every day now. At least one, often more agents end up conflicting with themselves and pipelines will not run on the agent. Sometimes I can "fix" the issue b

[go-cd] Re: One Agent conflicting with itself

This error has happened every day this week now and it's becoming frustrating Looking through the logs it appears that Windows update is causing the servers to reboot when they are first starting and this is somehow causing errors with the agent registrations. For now, I am having to manually

[go-cd] Re: One Agent conflicting with itself

This problem troubles us on occasion, today being one of those occasions. We are seeing this error message: [Agent located at [WIN-KANQRBSIE3G, 10.132.44.244, C:\GoAgent]] has duplicate unique identifier which conflicts with [Agent located at [ Infrastructure - GO Build Server - WIN-KANQRBSIE3G,