Release announcement - 19.6.0

80 views
Skip to first unread message

Saurabh Kishor Mistry

unread,
Jul 22, 2019, 3:52:35 AM7/22/19
to go-cd

Hello everyone,


A new version of GoCD (19.6.0) is out. 


To know more about the features and bug fixes in this release, see the release notes or head to the downloads page to try it. Feedback and ideas are always welcome.


Cheers,

GoCD Team

Shivani Shinde

unread,
Jul 25, 2019, 7:35:13 AM7/25/19
to go-cd
Hi!
I am running server on a remote server at http://<ip-address>:8153/go. And I am trying to point my agent at same ip-address with port 8153. But the agent doesn't seem to connect or does not appear on Agents tab in dashboard. I am using 19.6.0 version of GoCD. Can you help?

Ankit Srivastava

unread,
Jul 25, 2019, 2:33:21 PM7/25/19
to go...@googlegroups.com
Hi Shivani,

GoCD agent connects on port 8154. Can you try adding server URL as https://your_go_server:8154/go/.

Also, make sure agent is able to access server https://your_go_server:8154/go/ from agent machine. For further troubleshooting, you can refer this help link: https://docs.gocd.org/current/faq/fixing_common_issues.html



--
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/899befec-b69f-4e08-a906-8ee95ec21b42%40googlegroups.com.


--
Regards,
Ankit

Ankit Srivastava

unread,
Jul 25, 2019, 3:18:26 PM7/25/19
to go...@googlegroups.com
Hi Shivani,

Ignore my previous response, from 19.6 release of GoCD, agents can connect on port 8153.

Do you see any error in the go-agent-launcher.log or go-agent.log files? If yes, can you share it here? Thanks. 
--
Regards,
Ankit

Shivani Shinde

unread,
Jul 26, 2019, 1:21:26 AM7/26/19
to go...@googlegroups.com
Hi Ankit,
I configured the file by changing port number to 8153, still my agent won't connect to server.
Agent was working perfectly with 19.5.0 version of GoCD.
----------------------------------
The following are the log details in go-agent.log:

2019-07-26 10:42:34,046 ERROR [scheduler-1] AgentHTTPClientController:103 - Error occurred when agent tried to ping server:
org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [http://<my_ip_addr>:8153/go/remoting/remoteBuildRepository]; nested exception is org.apache.http.client.ClientProtocolException: The server returned status code 403. Possible reasons include:
   - This agent has been deleted from the configuration
   - This agent is pending approval
   - There is possibly a reverse proxy (or load balancer) that is terminating SSL. Hint: use port 8154 of the GoCD server. See https://docs.gocd.org/19.6.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details.
        at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:226)
        at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:153)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
        at com.sun.proxy.$Proxy10.ping(Unknown Source)
        at com.thoughtworks.go.agent.AgentHTTPClientController.ping(AgentHTTPClientController.java:98)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65)
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.apache.http.client.ClientProtocolException: The server returned status code 403. Possible reasons include:
   - This agent has been deleted from the configuration
   - This agent is pending approval
   - There is possibly a reverse proxy (or load balancer) that is terminating SSL. Hint: use port 8154 of the GoCD server. See https://docs.gocd.org/19.6.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details.
        at com.thoughtworks.go.agent.GoHttpClientHttpInvokerRequestExecutor.validateResponse(GoHttpClientHttpInvokerRequestExecutor.java:112)
        at com.thoughtworks.go.agent.GoHttpClientHttpInvokerRequestExecutor.doExecuteRequest(GoHttpClientHttpInvokerRequestExecutor.java:79)
        at org.springframework.remoting.httpinvoker.AbstractHttpInvokerRequestExecutor.executeRequest(AbstractHttpInvokerRequestExecutor.java:137)
        at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:202)
"/var/log/go-agent/go-agent.log" 1351L, 144803C              
------------------------------

Following are details of go-agent-launcher.log

2019-07-26 10:39:12,568 ERROR [WrapperJarAppMain] ServerBinaryDownloader:82 - Couldn't update admin/agent-launcher.jar. Sleeping for 1m. Error:
javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
        at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source)
        at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source)
        at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source)
        at java.base/sun.security.ssl.Alert$AlertConsumer.consume(Unknown Source)
        at java.base/sun.security.ssl.TransportContext.dispatch(Unknown Source)
        at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source)
        at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
        at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
        at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
        at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:396)
        at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355)
        at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:394)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
        at com.thoughtworks.go.agent.launcher.ServerBinaryDownloader.fetchUpdateCheckHeaders(ServerBinaryDownloader.java:98)
        at com.thoughtworks.go.agent.launcher.ServerBinaryDownloader.downloadIfNecessary(ServerBinaryDownloader.java:74)
                                                                                                                                                    514,1-8       93%
at com.thoughtworks.go.agent.launcher.AgentLauncherImpl.doLaunch(AgentLauncherImpl.java:90)
        at com.thoughtworks.go.agent.launcher.AgentLauncherImpl.lambda$launch$0(AgentLauncherImpl.java:68)
        at com.thoughtworks.go.logging.LogConfigurator.runWithLogger(LogConfigurator.java:62)
        at com.thoughtworks.go.agent.launcher.AgentLauncherImpl.launch(AgentLauncherImpl.java:68)
        at com.thoughtworks.go.agent.bootstrapper.AgentBootstrapper.go(AgentBootstrapper.java:78)
        at com.thoughtworks.go.agent.bootstrapper.AgentBootstrapper.lambda$main$0(AgentBootstrapper.java:59)
        at com.thoughtworks.go.logging.LogConfigurator.runWithLogger(LogConfigurator.java:53)
        at com.thoughtworks.go.agent.bootstrapper.AgentBootstrapper.main(AgentBootstrapper.java:59)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)
        at com.thoughtworks.gocd.Boot.run(Boot.java:89)
        at com.thoughtworks.gocd.Boot.main(Boot.java:55)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)
        at org.tanukisoftware.wrapper.WrapperJarApp.run(WrapperJarApp.java:451)
        at java.base/java.lang.Thread.run(Unknown Source)
2019-07-26 10:39:38,416 INFO  [TouchLoopThread-1] Lockfile:101 - Using lock file: /var/lib/go-agent/.agent-bootstrapper.running
2019-07-26 10:39:58,336 INFO  [WrapperJarAppMain] ServerBinaryDownloader:108 - Downloading agent.jar
2019-07-26 10:39:58,401 INFO  [WrapperJarAppMain] ServerBinaryDownloader:115 - Got server response
2019-07-26 10:40:02,475 INFO  [WrapperJarAppMain] ServerBinaryDownloader:123 - Piped the stream to admin/agent
2019-07-26 10:40:02,550 INFO  [WrapperJarAppMain] PerfTimer:52 - Performance: Downloading new admin/agent with md5 signature: f24d7111cfa5ddd517ae2a6601979868 took 4214ms
2019-07-26 10:40:03,899 INFO  [WrapperJarAppMain] AgentProcessParentImpl:51 - Agent is version: 19.6.0-9515
2019-07-26 10:40:06,200 INFO  [WrapperJarAppMain] ServerBinaryDownloader:108 - Downloading agent-plugins.zip
2019-07-26 10:40:06,227 INFO  [WrapperJarAppMain] ServerBinaryDownloader:115 - Got server response
2019-07-26 10:40:06,441 INFO  [WrapperJarAppMain] ServerBinaryDownloader:123 - Piped the stream to admin/agent-plugins.zip
2019-07-26 10:40:06,443 INFO  [WrapperJarAppMain] PerfTimer:52 - Performance: Downloading new admin/agent-plugins.zip with md5 signature: 9794977161dcf3a2a94dfd03ace222ef took 243ms
2019-07-26 10:40:26,830 INFO  [WrapperJarAppMain] ServerBinaryDownloader:108 - Downloading tfs-impl.jar
2019-07-26 10:40:26,850 INFO  [WrapperJarAppMain] ServerBinaryDownloader:115 - Got server response
2019-07-26 10:40:28,455 INFO  [WrapperJarAppMain] ServerBinaryDownloader:123 - Piped the stream to admin/tfs-impl.jar
2019-07-26 10:40:28,458 INFO  [WrapperJarAppMain] PerfTimer:52 - Performance: Downloading new admin/tfs-impl.jar with md5 signature: ae0785c73cbf398e7a9f0353cedd9c72 took 1628ms
2019-07-26 10:40:28,460 INFO  [WrapperJarAppMain] AgentProcessParentImpl:70 - Launching Agent with command: /usr/share/go-agent/jre/bin/java -Xms128m -Xmx256m -Dgocd.agent.log.dir=/var/log/go-agent -Dagent.plugins.md5=9794977161dcf3a2a94dfd03ace222ef -Dagent.binary.md5=f24d7111cfa5ddd517ae2a6601979868 -Dagent.launcher.md5=66ec93e59afaff1655c4ade7fd33e530 -Dagent.tfs.md5=ae0785c73cbf398e7a9f0353cedd9c72 -jar agent.jar -serverUrl http://<my-ip-addr>:8153/go -sslVerificationMode NONE
                                                                                                                                                    579,1         Bot
                                                                                                        



--
Shivani Shinde
AlefEdge

Shivani Shinde

unread,
Jul 29, 2019, 12:42:19 AM7/29/19
to go...@googlegroups.com
Hi,
Following up on the issue. My agent still won't connect to server. I have tried both ports and manipulated the url (http/https) like-wise. Yet I couldn't figure out what is the issue.
Can you help?

Thanks
--
Shivani Shinde
AlefEdge

Ketan Padegaonkar

unread,
Jul 29, 2019, 3:15:24 AM7/29/19
to go...@googlegroups.com
Could you please open an issue on GitHub with more details, logs, steps to reproduce etc?

Ankit Srivastava

unread,
Jul 29, 2019, 7:54:01 PM7/29/19
to go...@googlegroups.com
Hi Shivani,

Was the GoCD (19.5.0) server upgraded? Or you trying to point the same agent (earlier connected to 19.5.0 server) to different GoCD (19.6.0) instance? 

Looking at the go-agent-launcher.log, it looks like you are trying to connect to a different server. Can try deleting agent.jks and guid.txt file from agent config/ folder and restart the agent.

Let me know if this works. Otherwise, please open an issue on GitHub (https://github.com/gocd/gocd/issues) as suggested by Ketan.

Regards,
Ankit



--
Regards,
Ankit

Shivani Shinde

unread,
Jul 30, 2019, 2:05:32 AM7/30/19
to go...@googlegroups.com
Hi,
I re-intsalled go-agent and point it to my server at http://<my_ip_address>:8153 and it worked. I did the same before, by I don't know why it wasn't working.

Thank you for your response.



--
Shivani Shinde
AlefEdge

Kai Krupka

unread,
Aug 22, 2019, 7:12:50 AM8/22/19
to go-cd
Dear Ankit,

had the same issue as described and just for completeness: your fix worked. Deleting agent.jks and guid.txt file from agent config/ folder and restarting the agent solved the problem.

Kai

Am Dienstag, 30. Juli 2019 01:54:01 UTC+2 schrieb Ankit:
Hi Shivani,

Was the GoCD (19.5.0) server upgraded? Or you trying to point the same agent (earlier connected to 19.5.0 server) to different GoCD (19.6.0) instance? 

Looking at the go-agent-launcher.log, it looks like you are trying to connect to a different server. Can try deleting agent.jks and guid.txt file from agent config/ folder and restart the agent.

Let me know if this works. Otherwise, please open an issue on GitHub (https://github.com/gocd/gocd/issues) as suggested by Ketan.

Regards,
Ankit

On Mon, Jul 29, 2019 at 12:15 AM Ketan Padegaonkar <ketanpad...@gmail.com> wrote:
Could you please open an issue on GitHub with more details, logs, steps to reproduce etc?

On Mon, 29 Jul, 2019, 10:12 Shivani Shinde, <shivan...@alefedge.com> wrote:
Hi,
Following up on the issue. My agent still won't connect to server. I have tried both ports and manipulated the url (http/https) like-wise. Yet I couldn't figure out what is the issue.
Can you help?

Thanks

To unsubscribe from this group and stop receiving emails from it, send an email to go...@googlegroups.com.


--
Regards,
Ankit


--
Regards,
Ankit

--
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...@googlegroups.com.


--
Shivani Shinde
AlefEdge


--
Shivani Shinde
AlefEdge

--
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...@googlegroups.com.

--
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...@googlegroups.com.


--
Regards,
Ankit
Reply all
Reply to author
Forward
0 new messages