wrapper.conf:
set.AGENT_STARTUP_ARGS=-Dtoggle.agent.git.clean.keep.ignored.files=Y
2 replies
Hello, guys. We are using GoCD version 21.1.0 and when we checked the logs, we saw this error for each agent:
2021-04-22 07:41:43,409 WARN [qtp1740200769-58] AgentService:539 - Agent [Agent [ 0fdc505c-eda8-4d9c-a70b-f2cdf0dd7d99, null]] has no cookie set
2021-04-22 07:41:43,410 ERROR [qtp1740200769-58] BuildRepositoryRemoteImpl:59 - Error occurred in com.thoughtworks.go.server.service.AgentRuntimeInfo@767b3180[agentBootstrapperVersion=21.1.0-12439,agentVersion=21.1.0-0,buildingInfo=AgentBuildingInfo[, ],cookie=<null>,identifier=Agent [ 0fdc505c-eda8-4d9c-a70b-f2cdf0dd7d99],location=/var/lib/go-agent-3,operatingSystemName=CentOS Linux 7.9.2009 Core,runtimeStatus=Idle,usableSpace=21260271616] ping.
com.thoughtworks.go.server.service.AgentNoCookieSetException: Agent [Agent [0fdc505c-eda8-4d9c-a70b-f2cdf0dd7d99, null]] has no cookie set
This error appears only at restart, and in the end the cookie is assigned for each agent:
2021-04-22 07:41:44,788 INFO [qtp1740200769-211] BuildRepositoryRemoteImpl:127 - [Agent Cookie] Agent [Agent [0fdc505c-eda8-4d9c-a70b-f2cdf0dd7d99]] at location [/var/lib/go-agent-3] asked for a new cookie, assigned [33afe63e-2c18-41fa-97f5-8602e9f4c95a]
We have a lot of agents and logs are polluted with these errors. Do you have any idea how can I get rid of this error? Is any way to disable the log for com.thoughtworks.go.server.service.AgentRuntimeInfo/com.thoughtworks.go.server.service?
8 replies
4 replies
5 replies
4 replies
10 replies
1 reply
4 replies
Hello, GoCD newbie, i'm following the GoCD Kubernetes tutorial. https://docs.gocd.org/current/gocd_on_kubernetes/importing_a_sample_workflow.html
The Job is not running: it fails cos the gocd server url is http://gocd-server:8153/go but it needs to be https
[Mon May 03 21:47:02 GMT 2021] Starting process:
[Mon May 03 21:47:02 GMT 2021] Working directory : /go
[Mon May 03 21:47:02 GMT 2021] Application arguments: [-serverUrl, http://gocd-server:8153/go]
[Mon May 03 21:47:02 GMT 2021] GoCD Version: 18.3.0-6540
...
-serverUrl must be an HTTPS url and must begin with https://
Usage: java -jar agent-bootstrapper.jar [options]
Options:
-help
Print this help
-rootCertFile
The root certificate from the certificate chain of the GoCD server (in
PEM format)
- -serverUrl
The GoCD server URL. Must begin withhttps://, and end with/go
-sslVerificationMode
The SSL verification mode.
Default: NONE
Possible Values: [FULL, NONE, NO_VERIFY_HOST]
digging in, that value is coming from:- name: GO_SERVER_URL
value: 'http://gocd-server:8153/go'
Which is set by default in the helm template:- name: GO_SERVER_URL
{{- if .Values.agent.env.goServerUrl }}
value: {{ .Values.agent.env.goServerUrl }}
{{- else }}
value: "http://{{ template "gocd.fullname" . }}-server:{{ .Values.server.service.httpPort }}/go"
{{- end }}
http when the agent.jar does not accept it?
Looks like its been broken since gocd/gocd#7872 got shipped last year.
User created gocd/helm-chart#12
3 months ago but there's been no response.
is gocd still a thing?
Yes, GoCD is still a thing. In personally don’t have experience with the helm chart so I may be of limited help.
The team is spread across time zones so not everyone is online at a given time.
FWIW, the agent should work with http URL. We use that in development and no longer bake in TLS termination on the server and leave that up to the user to set up with a reverse proxy.
ok figured it out. the docker image for the agent in https://docs.gocd.org/current/gocd_on_kubernetes/importing_a_sample_workflow.htmlgocddemo/gocd-agent-dind:webinar is running an old version 18.3.0-6540 of the gocd-agent
The tutorial needs to be updated.
