Hello! Can you please try this?
1. Stop the agent. 2. Remove or move /var/lib/go-agent/agent.jar and /var/lib/go-agent/agent-launcher.jar (if they exist). 3. Start the agent. Should be just a one-time process. We think it happens because the agent was upgraded before the server (so new agent connects to the old server and gets confused). This is not a problem in 16.6 or earlier. Just in 16.7, because the agent was changed in that version. The release notes and documentation will be updated to mention this. In 16.8 or probably 16.9, we will try to make it so that the agent will recognize this and fix itself. Sorry about the trouble. Thanks, Aravind On Thu, Aug 4, 2016 at 9:11 AM, Aravind SV <[email protected]> wrote: > On Thu, Aug 4, 2016 at 8:48 AM, Moritz Lenz <[email protected]> wrote: > >> Please try setting GO_SERVER and GO_SERVER_PORT, which are currently >> commented out in your agent configuration. >> > > For 16.7, GO_SERVER_URL should be ok. The other two should not be needed. > Ketan is looking at this and will respond soon. It looks like this has to > do with the order of upgrade between the server and the agent, since 16.7.0 > changed the agent bootstrapper a bit. There should be an easy workaround > for this, for now, while we look at whether the installer needs to be > changed. > > Meanwhile, Meghanand, do you remember the order you upgraded the agent and > server? > -- 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.
