go-cd agent.sh (installation by zip folder doesnot work)

215 views
Skip to first unread message

pankaj singh

unread,
Aug 13, 2018, 4:11:16 AM8/13/18
to go-cd
Have anyone tried installing go-cd agent installation via zip format..There seems to be an issue in running the agent..
either configurations are missing or page on go-cd is not updated.

Thoughtworks team kindly look into it.

gane...@thoughtworks.com

unread,
Aug 13, 2018, 4:16:33 AM8/13/18
to go-cd
Hello Pankaj,

What version of GoCD version you are trying to install? Which platform?
Can you provide the entire agent.log or error you are seeing when you are trying to install GoCD agent?

Thanks,
Ganesh

pankaj singh

unread,
Aug 13, 2018, 6:38:39 AM8/13/18
to go...@googlegroups.com
It's the latest version available on site.
You can simply follow the instructions of zip command i.e. unzip the agent and run agent.sh.. it fails with an output 9f how to use it.. with options..

I checked the codebase of launching go cd via services everything looks same..

You can just follow the instructions of zip command. Will take less than 2-3 mons to replicate 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+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ganesh Patil

unread,
Aug 13, 2018, 6:51:28 AM8/13/18
to go...@googlegroups.com
Hey Pankaj,

That's strange, could you help us with a screenshot of the command line where you see this error? The script in general doesn't require any parameters while you launch an agent. You could also attach the said script here for us to further help you troubleshoot this.

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

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "go-cd" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/go-cd/shDrK6d5ziY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to go-cd+unsubscribe@googlegroups.com.

pankaj singh

unread,
Aug 13, 2018, 10:08:33 PM8/13/18
to go...@googlegroups.com
Updating the previous threads. Managed to pass the previous thread as i were passing the url in http: ...
I installed the agent and server both on different unix box. Server was up and running fine. 

Agent I used the command to start the agent.

java -jar agent-bootstrapper.jar -serverUrl https://192.168.1.35:8154/go 

(not sure why need to pass the URL as https.. it should be http though)


go agent log:

[Tue Aug 14 10:02:10 MYT 2018] Starting process: 

[Tue Aug 14 10:02:10 MYT 2018]   Working directory    : /media/amaris/datalake/gocd/agent/go-agent-18.7.0

[Tue Aug 14 10:02:10 MYT 2018]   Application arguments: [-serverUrl, https://192.168.1.35:8154/go]

[Tue Aug 14 10:02:10 MYT 2018]            GoCD Version: 18.7.0-7121

Could not find file `config/agent-bootstrapper-logback.xml'. Attempting to load from classpath.

Using classpath resource `jar:onejar:lib/agent-bootstrapper-18.7.0-7121-classes.jar!/config/agent-bootstrapper-logback.xml'.

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in [jar:onejar:lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: Found binding in [jar:file:/media/amaris/datalake/gocd/agent/go-agent-18.7.0/data/deps-ff963a73c3528303-agent-launcher.jar/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

Could not find file `config/agent-launcher-logback.xml'. Attempting to load from classpath.

Using classpath resource `jar:file:/media/amaris/datalake/gocd/agent/go-agent-18.7.0/data/deps-ff963a73c3528303-agent-launcher.jar/agent-launcher-18.7.0-7121-classes.jar!/config/agent-launcher-logback.xml'.



PFA screenshot. go agent status is stuck in pending stage. not sure why..




Thanks,
Pankaj K Singh
Contact No: +65-91882013(Singapore)
Screen Shot 2018-08-14 at 10.06.16 AM.png

Ashwanth Kumar

unread,
Aug 14, 2018, 12:17:57 AM8/14/18
to go...@googlegroups.com
Hello Pankaj,

The reason for server agent communication being https is for security. Imagine where you've a username and password credentials for a particular material. When the server sends these information to the agent for building a pipeline, you don't want anyone in the middle to eves drop that isn't? That's also the reason the web-ui is on 8153 and agent talks to server on 8154 ports respectively.

Now why is the agent not registered and enabled by default is also for a similar reason. If I happen know a GoCD server address I shouldn't be able to start a rougue agent say on my local machine and connect to it. That way I can get copies of your source and other artifacts.  That's the reason an admin should enable an agent on the page where you've shared the screenshot from.

Click on the agent that's pending and click on the Enable button on the top right corner.

If you're looking for a way to auto register your remote agents you can find more details on https://docs.gocd.org/current/advanced_usage/agent_auto_register.html


Text by Ashwanth, typos by Lumia

From: pankaj singh
Sent: ‎14-‎08-‎2018 07:38
To: go...@googlegroups.com
Subject: Re: [go-cd] Re: go-cd agent.sh (installation by zip folder doesnotwork)

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

pankaj singh

unread,
Aug 14, 2018, 12:32:19 AM8/14/18
to go...@googlegroups.com
Thanks for highlighting the concern. 
I guess many software stack have an option to run on https and http both by default. I am slightly curious to understand whats happening "https" if there is not certificate installed..

Aravind SV

unread,
Aug 14, 2018, 3:24:25 AM8/14/18
to go...@googlegroups.com
Hello Pankaj,
Yes, that's a good question. In the default case, it'll accept all certs provided by the endpoint and can possibly be mitm-ed. However, GoCD agents have the ability to verify certificates fully and provide end-to-end transport security, if you provide a cert file. Here are the details:

https://docs.gocd.org/current/installation/ssl_tls/end_to_end_transport_security.html

Cheers,
Aravind
Reply all
Reply to author
Forward
0 new messages