Hello! I'm running 22.3 and I keep having agents go offline. For example, on a particular server (mirror setup to other environments) I have several agents running side-by-side on an admin server and then an agent on various individual servers. At the moment for this particular example, I have 12 of 15 agents that are running perfectly fine. They all enabled and took their configs originally but now the two that are offline are just looping the below message. Generally I can go to each server, stop the agent, delete the contents of the config folder and restart and it may after 1 or more tries create a new entry. The new entry now is missing all the resource tags so we have to note all the tags from the abandoned agent registration and add it to the new one.
We have a significant number of agents around in multiple environments but this happens to maybe 10-20% of them. All agents were provisioned in the same way, started and registered in the same way. Sometimes they have a token, and guid file but sometimes there is only a guid while the error message loops. In this particular agent case, I have two that just went offline from a clean install. Both showed up initially and enabled but are now showing offline. They are on the same server but each has a different name "Go Agent 01" "Go Agent 02" etc.: 2023-04-03 18:46:28,930 INFO [scheduler-3] SslInfrastructureService:78 - [Agent Registration] Starting to register agent. 2023-04-03 18:46:28,930 INFO [scheduler-3] SslInfrastructureService:88 - [Agent Registration] Fetching token from server. 2023-04-03 18:46:28,932 ERROR [scheduler-3] TokenRequester:59 - Received status code from server 409 2023-04-03 18:46:28,933 ERROR [scheduler-3] TokenRequester:60 - Reason for failure A token has already been issued for this agent. 2023-04-03 18:46:28,933 ERROR [scheduler-3] SslInfrastructureService:106 - [Agent Registration] There was a problem registering with the GoCD server. java.lang.RuntimeException: A token has already been issued for this agent. I have tried to see if I could recreate the token and guid files but I can't seem to get them to be accepted when I think their values are correct. If there is a way to recreate the guid and token from the PostgreSQL server I can do that but I haven't found anything so far that seems to work for recreating those. Is there any reason that the agent would register and then lose its registration that we can try to avoid? Over the last month or two we've lost registration and set agents back up roughly 50-80 times across all areas. Thanks in advance for any assistance! -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/b5b7ee4f-d21a-41a5-8162-3c883ae01542n%40googlegroups.com.
