Hi Aravind,
Thanks for the reply.
In our case the GO server is on Linux (Debian). We have upgraded that from
17.2 -> 17.4.
The majority of the agents are Windows based and it is these I am talking
about regarding the version.
After stopping the agent, cleaning the log files and then restarting it,
the bootstrapper log file "C:\Program Files (x86)\Go
Agent\go-agent-bootstrapper.log" it never seems to show anything other than
this:
STATUS | wrapper | 2017/05/04 21:32:05 | --> Wrapper Started as Service
STATUS | wrapper | 2017/05/04 21:32:05 | Java Service Wrapper Standard
Edition 3.3.3
STATUS | wrapper | 2017/05/04 21:32:05 | Copyright (C) 1999-2009 Tanuki
Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2017/05/04 21:32:05 | http:
//wrapper.tanukisoftware.org
STATUS | wrapper | 2017/05/04 21:32:05 | Licensed to ThoughtWorks for
Cruise Agent
STATUS | wrapper | 2017/05/04 21:32:05 |
STATUS | wrapper | 2017/05/04 21:32:06 | Launching a JVM...
INFO | jvm 1 | 2017/05/04 21:32:07 | WrapperManager: Initializing...
INFO | jvm 1 | 2017/05/04 21:32:08 | logFile Environment Variable= null
INFO | jvm 1 | 2017/05/04 21:32:08 | Logging to go-agent-bootstrapper.
log
2017-05-04 21:32:08,884 [WrapperSimpleAppMain] INFO agent.common.util.
JarUtil:68 - Attempting to load Go-Agent-Launcher-Class from d24b462e-51e4-
4288-a494-30078909b2b1agent-launcher.jar File:
2017-05-04 21:32:08,946 [WrapperSimpleAppMain] INFO agent.common.util.
JarUtil:77 - manifestLibDirKey: Go-Agent-Launcher-Lib-Dir: libs
2017-05-04 21:32:09,259 [WrapperSimpleAppMain] INFO agent.common.util.
JarUtil:83 - manifestClassKey: Go-Agent-Launcher-Class: com.thoughtworks.go.
agent.launcher.AgentLauncherImpl
2017-05-04 21:32:09,274 [WrapperSimpleAppMain] INFO agent.common.util.
ParentClassAccessFilteringClassloader:43 - Loading com.thoughtworks.cruise.
agent.common.launcher.AgentLauncher using com.simontuffs.onejar.
JarClassLoader
2017-05-04 21:32:09,305 [WrapperSimpleAppMain] INFO go.agent.bootstrapper.
AgentBootstrapper:72 - Attempting create and start launcher...
INFO | jvm 1 | 2017/05/04 21:32:09 | Could not find file
`config\agent-launcher-log4j.properties'.
Attempting to load from classpath.
INFO | jvm 1 | 2017/05/04 21:32:09 | Using classpath resource `config/
agent-launcher-log4j.properties'.
2017-05-04 21:32:09,524 [WrapperSimpleAppMain] INFO
agent.common.util.ParentClassAccessFilteringClassloader:43 - Loading
com.thoughtworks.cruise.agent.common.launcher.AgentLaunchDescriptor using
com.simontuffs.onejar.JarClassLoader
There is no reference to the agent version from what I can see.
Is there somewhere else that shows the version?
Also, when I meant monitoring from the server, I meant via log files rather
than through the GUI - what should we see in the logs and which log file to
show that the agent has updated?
Thanks
Carl
On Thursday, 4 May 2017 21:14:01 UTC+1, Aravind SV wrote:
>
> Hey Carl,
>
> Agents can only pick up a job after they are upgraded to the version of
> the server (shown in the footer of every page). So, as soon as an agent
> finishes upgrading it becomes available ("idle"). It won't be able to pick
> up anything till that happens.
>
> The agent bootstrapper is the thing you actually installed (using a Debian
> package, etc). It is a small component that is responsible for upgrading
> the agent components (launcher and agent), which do the actual work. The
> agent bootstrapper log should be in /var/log/go-agent/. The
> agent-launcher.log (in the same location, on the agent machine) should have
> some lines similar to this:
>
> INFO thoughtworks.go.util.PerfTimer:53 - Performance: Downloading new
> admin/agent-launcher.jar with md5 signature: WZuIEwnR+Rkpjvs4/86f4Q== took
> 101ms
> INFO go.agent.launcher.ServerBinaryDownloader:108 - Downloading agent.jar
> INFO go.agent.launcher.ServerBinaryDownloader:115 - Got server response
> INFO go.agent.launcher.ServerBinaryDownloader:123 - Piped the stream to
> admin/agent
> INFO thoughtworks.go.util.PerfTimer:53 - Performance: Downloading new
> admin/agent with md5 signature: 7b6hZAvr2LJpmMyFZqoZoA== took 214ms
> INFO agent.common.util.JarUtil:68 - Attempting to load
> Go-Agent-Bootstrap-Class from agent.jar File:
> INFO agent.common.util.JarUtil:83 - manifestClassKey:
> Go-Agent-Bootstrap-Class: com.thoughtworks.go.agent.AgentProcessParentImpl
> INFO thoughtworks.go.agent.AgentProcessParentImpl:52 -
>
> *Agent is version: 17.4.0-23620*
> I don't believe the server shows the status of an agent as "Downloading"
> or anything like that in the agents page.
>
> Cheers,
> Aravind
>
> On Thu, May 4, 2017 at 3:45 PM, Carl Reid <[email protected]
> <javascript:>> wrote:
>
>> We have just updated from 17.2 to 17.4.
>>
>> I believe that the Go Agents upgrade automatically after the server is
>> updated to a new version however I cannot see anything in the Go server log
>> /var/log/go-server/go-server.log about this upgrade.
>>
>> From the server, how do you monitor the upgrade process and determine
>> which agents have updated?
>> From the agent, how do you show the current version of the agent?
>>
>> I saw another post that said you should look in the
>> "go-agent-bootstrapper.log" however from the agents I have looked at this
>> does not seem to get populated.
>>
>>
>> thanks
>>
>> Carl
>>
>> --
>> 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 [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
