Re: [go-cd] git clone failures in gocd pipelines after sonoma upgrade
Hi Chad, Thank you for responding to my issue. Just wanted to give some basic info on the GoCD version. We are using GoCD 23.1.0 aarch version, all of our servers are Mac OS M1 servers(for both GoCD and agents) - What are the specific clone errors you are getting? *we get the below error when the job tried to clone more the repositories, at first we thorught the git server is closing the connection, the gitlab team took the logs from ec2 instance where it says the source ip which is go-agent is requesting the disconnection.pipelines logs:STDERR: Cloning into '/Users//go-agent-23.1.0/pipelines/Git_Clone/daf-mock-server'...STDERR: kex_exchange_identification: Connection closed by remote hostSTDERR: Connection closed by 10.112.205.90 port 22STDERR: fatal: Could not read from remote repository.STDERR: STDERR: Please make sure you have the correct access rightsSTDERR: and the repository exists.Failed to run git clone command* *Logs from Git server: the Ip in the logs is go-agent ip.Mar 5 23:30:23 ip-10-112-205-125 sshd[3315655]: pam_unix(sshd:session): session closed for user git Mar 5 23:30:23 ip-10-112-205-125 sshd[3315640]: Received disconnect from 10.254.56.146 port 63239:11: disconnected by user* - Have you tried running clones manually to see if you can replicate the problem? That way you can enable git debugging flags to debug the issue. (e.g GIT_CURL_VERBOSE=1) *I have not done this part, I can try this on the agent.* - Which exact git version are you using? A Mac pre-installed one, or something from Brew or MacPorts? *Before this issue, we used pre-installed git version on all go-agents. In order to resolve this issue, I have installed git with brew on the go-agents and started using it. the version is 2.44.0. But the issue still exists. on the GoCD, we are still using pre-installed git, do I need install git with brew on the GoCD as well.* - Are the errors always on agents or always on the server, or both? *This error is occurring on the agents when the job starts cloning the repos mentioned in the materials.* - What's the filesystem path that GoCD is cloning into when there are failures? *The failures are happening on the agents. the agent path is /Users//go-agent-23.1.0/* *We installed GoCD in /Applications/.* *The artifacts path is /Volumes/Artifacts.* Please let me know if you need more information. Thank you. On Saturday, March 16, 2024 at 9:37:21 AM UTC-4 Chad Wilson wrote: > GoCD doesn't do anything special with Git - it just uses whatever git > version you have available to the agent/server on the path. If something > has changed after the Sonoma upgrade, it is probably affecting all Git > usage on the machine. > >- What are the specific clone errors you are getting? >- Have you tried running clones manually to see if you can replicate >the problem? That way you can enable git debugging flags to debug the >issue. (e.g GIT_CURL_VERBOSE=1) >- Which exact git version are you using? A Mac pre-installed one, or >something from Brew or MacPorts? >- Are the errors always on agents or always on the server, or both? >- What's the filesystem path that GoCD is cloning into when there are > failures? > > -Chad > > On Sat, Mar 16, 2024 at 2:51 AM SATYA R wrote: > >> Hi Team, >> >> Recently, we upgraded all of our go-agents to macos Sonoma from ventura. >> GoCD also runs on Sonoma version. >> After the upgrade, we are seeing intermittent git clone failures in the >> pipelines. >> Each pipeline has 3 or more repos to clone, when multiple pipelines >> around 20 pipelines try to clone the 3 or more repositories from git, we >> are facing this git clone issue. >> sometimes the pipeline are able to clone all the repos but sometimes they >> fail. >> >> is there anything that we need to particularly look into in gocd and >> go-agents configuration due to sonoma upgrade. do we need to make any >> changes in go-agent service in order to support the sonoma version? >> >> Kindly help us. >> >> Thank you. >> >> -- >> 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/63efcffd-c537-4855-8039-9de9eafb885en%40googlegroups.com >> >> <https://groups.google.com/d/msgid/go-cd/63efcffd-c537-4855-8039-9de9eafb885en%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/f725ced6-703d-480d-a801-049fc13f474fn%40googlegroups.com.
[go-cd] git clone failures in gocd pipelines after sonoma upgrade
Hi Team, Recently, we upgraded all of our go-agents to macos Sonoma from ventura. GoCD also runs on Sonoma version. After the upgrade, we are seeing intermittent git clone failures in the pipelines. Each pipeline has 3 or more repos to clone, when multiple pipelines around 20 pipelines try to clone the 3 or more repositories from git, we are facing this git clone issue. sometimes the pipeline are able to clone all the repos but sometimes they fail. is there anything that we need to particularly look into in gocd and go-agents configuration due to sonoma upgrade. do we need to make any changes in go-agent service in order to support the sonoma version? Kindly help us. Thank you. -- 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/63efcffd-c537-4855-8039-9de9eafb885en%40googlegroups.com.
[go-cd] Kill running tasks api is not resolving the "building(cancelled)" state
Hi team, We are using GoCD 22.3.0 the latest version and we always have the issue of "building(cancelled)" state on agents. We usually restart the go agent service by logging into the agents when this issue happens. And now we are trying to resolve this issue using "Kill running tasks" api, but the below command is not resolving the issue and not giving any response. Any suggestion/solution on this would be really helpful for us. *curl 'https://ci.example.com/go/api/agents/adb9540a-b954-4571-9d9b-2f330739d4da/kill_running_tasks' \ -u 'username:password' \ -H 'Accept: application/vnd.go.cd.v7+json' -H 'X-GoCD-Confirm: true' \ -X POST* Thanks, Srikala Rekapalli. DevOps. -- 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/16290d5e-87a5-48b6-985b-1977c62f9018n%40googlegroups.com.
[go-cd] SSO login is not working between GitLaB and GOCD
Hi Team, I am trying enable to SSO between GitLan and GoCD. GoCD version: 22.3.0 In GoCD, I configured the plugin with ApplicationId, ClientSecret and AccessToken and the check connection is also successful. In GitLab, I have provided the GoCD url in Applications. But the SSO still not working, am getting the below error. Kindly help me identify the issue. Thanks, Srikala Rekapalli. DevOps. -- 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/993b395a-8929-4240-b11d-3ce8df89756an%40googlegroups.com.
Re: [go-cd] Need help in resolving few issues with GoCD 20.4
Hi Ashwanth, Thanks alot for the quick response. Here is what i found from the server.log *2022-11-02 08:43:20,092 WARN [131@MessageListener for MaterialUpdateListener] MaterialDatabaseUpdater:127 - [Material Update] Modification check failed for material: URL: gitit.l\tcom:flsndfydta/flydtadhgyplayfgheagit, Branch: master* *java.lang.RuntimeException: Working directory: pipelines/flyweight/1d3077c5-8571-4a73-a87c-cecf44e5c5fe* *STDERR: kex_exchange_identification: read: Connection reset by peer* *STDERR: fatal: Could not read from remote repository.* *STDERR: * *STDERR: Please make sure you have the correct access rights* *STDERR: and the repository exists.* Is the error occurring because of this flyweight? Regrading the GoConfig changes: The old server was configured by some other person who is now not in the project. Usually do we create a custom cron job to push GoConfig changes to gitlab? if yes, can you please let us know to which path we should set up the cron? Thanks in advance. On Wednesday, November 2, 2022 at 6:10:17 AM UTC-4 ashwant...@gmail.com wrote: > From the attached screenshot the error seems like something to do with a > network configuration. > > > kex_exchange_identification: read: Connection reset by peer > > First answer on SO <https://stackoverflow.com/a/69398009> also says the > same. Also if you can check the go-server.log, it might have additional > details which might be useful to debug as well. See if you can share those > after masking any sensitive details. > > From the GoCD Docs > <https://docs.gocd.org/current/advanced_usage/config_repo.html>, the > config.git is not pushed by GoCD to a remote. We usually have a cron that > runs on the server machine that periodically does a `git push`. Do you know > how you were doing this with v18.x series earlier? > > Thanks, > > > On Wed, 2 Nov 2022 at 15:30, SATYA R wrote: > >> Hi Everyone, >> >> Recently our GoCD 18.8 server got destroyed and we installed new version >> of GoCD 20.4 in new mac server and restored the backup of 18.8. >> We are able to get all the pipelines back and running. But we are facing >> few issues with the new server. >> >> 1. The pipelines Auto-trigger is not happening immediately, it is taking >> lot of time to get auto-triggered. And whenever we do test connection in >> materials it always fails with an error. PFA after many refreshes we get >> "OK" connection message. >> 2. Sometimes even when we try to trigger the pipelines manually, they >> don't run, after so many refreshes they run, we have to hit run button >> multiple times to make them run. >> 3. After our old GoCD18.8 is crashed, the config.xml changes are not >> getting committed to GoConfig.git repo in GitLab. >> >> Kindly help us resolving the above issues. >> >> Thanks, >> Srikala Rekapalli. >> DevOps. >> >> -- >> 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/0f7f723b-23bd-416c-a9e1-ec585dcb7a38n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/go-cd/0f7f723b-23bd-416c-a9e1-ec585dcb7a38n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > > Ashwanth Kumar / ashwanthkumar.in > > -- 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/0d437f59-4e9b-463f-9dda-328eefacc612n%40googlegroups.com.
[go-cd] Need help in resolving few issues with GoCD 20.4
Hi Everyone, Recently our GoCD 18.8 server got destroyed and we installed new version of GoCD 20.4 in new mac server and restored the backup of 18.8. We are able to get all the pipelines back and running. But we are facing few issues with the new server. 1. The pipelines Auto-trigger is not happening immediately, it is taking lot of time to get auto-triggered. And whenever we do test connection in materials it always fails with an error. PFA after many refreshes we get "OK" connection message. 2. Sometimes even when we try to trigger the pipelines manually, they don't run, after so many refreshes they run, we have to hit run button multiple times to make them run. 3. After our old GoCD18.8 is crashed, the config.xml changes are not getting committed to GoConfig.git repo in GitLab. Kindly help us resolving the above issues. Thanks, Srikala Rekapalli. DevOps. -- 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/0f7f723b-23bd-416c-a9e1-ec585dcb7a38n%40googlegroups.com.
Re: [go-cd] error launching the go-agent
Hi Team, We are trying to launch the Go Agent.app file but the popup window is not showing to enter the go cd server url and it is connecting to localhost by default. we are seeing the below error in log file. Please let us know if there is any specific file to change the go cd server address and port. Could not find file `config/agent-bootstrapper-logback.xml'. Attempting to load from classpath. Using classpath resource `jar:onejar:lib/agent-bootstrapper-18.8.0-7433-classes.jar!/config/agent-bootstrapper-logback.xml'. SLF4J: Class path contains multiple SLF4J bindings. Thanks in advance. On Monday, September 26, 2016 at 3:24:46 PM UTC+5:30 sala...@thecirqus.com wrote: > Hi Ketan, > > Thanks for the help. > Changing the port number and restarting the go-agent solved it. > -- 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/91aabefa-1226-494a-9341-95491cae3239n%40googlegroups.com.
