Re: [go-cd] Config Repositories has always in fetch status

Thanks so much for sharing back! This does make sense. I have also experienced issues with EFS related to things like this. I would have suggested checking disk performance if I had realised a GoCD server replacement+upgrade was part of what had changed :-) While it has some challenges in terms

Re: [go-cd] Config Repositories has always in fetch status

Hello Chad, Thank you for your suggestion. Just for your infomation. I had fixed this issue since last week. This root cause issue related to our EFS throughput for stored flyweight, /home/go, artifacts, This issue solved by I changed EFS throughput mode from bursting to elastic

Re: [go-cd] Config Repositories has always in fetch status

Hmm, given your description and the basic metrics you shared, the behaviour sounds strange. To step back slightly and confirm the issue, please look inside the container at the process tree (via ps, top etc) and see whether there are a large number of forked git processes. If there *are*, we want

Re: [go-cd] Config Repositories has always in fetch status

Hello Chad, What did you change around the time this behaviour started happening? -GoCD = no -Gitlab = upgrade from 16.2.0 to 16.2.3 Which container image for the server are you using? (only gocd-server-centos-9 is built for ARM64 - if you

Re: [go-cd] Config Repositories has always in fetch status

If you are getting logs like that, it sounds like the container is experiencing CPU starvation. - What did you change around the time this behaviour started happening? - Which container image for the server are you using? (only gocd-server-centos-9

Re: [go-cd] Config Repositories has always in fetch status

Hello Chad, Thank you for your advice. I tried run git clone with debug environment variables command in gocd server pod. So the command run successfully and there is no any abnormal log. And CPU and memory are not high usage. We tried restart gocd server pods many time but it is not help.