Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Bamboo Remote Agent Problem: URI has an authority component

Robin Gauß
Robin Gauß October 5, 2015

I have a problem with one of my remote agents. When starting the agent I see the following errors in the log file:

Exiting due to fatal exception.
java.lang.IllegalArgumentException: URI has an authority component
   at java.io.File.<init>(Unknown Source)
   at com.atlassian.bamboo.agent.bootstrap.BootstrapUpdater.ensureLatestBootstrap(BootstrapUpdater.java:36)
   at com.atlassian.bamboo.agent.bootstrap.AgentContext.updateBootstrapIfNecessary(AgentContext.java:203)
   at com.atlassian.bamboo.agent.bootstrap.AgentContext.initServerSession(AgentContext.java:104)
   at com.atlassian.bamboo.agent.bootstrap.AgentContext.run(AgentContext.java:94)
   at com.atlassian.bamboo.agent.bootstrap.AgentBootstrap.run(AgentBootstrap.java:95)
   at com.atlassian.bamboo.agent.bootstrap.AgentBootstrap.main(AgentBootstrap.java:41)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240)
   at java.lang.Thread.run(Unknown Source)
FATAL [WrapperSimpleAppMain] [AgentBootstrap] Exiting due to fatal exception.
java.lang.IllegalArgumentException: URI has an authority component
   at java.io.File.<init>(Unknown Source)
   at com.atlassian.bamboo.agent.bootstrap.BootstrapUpdater.ensureLatestBootstrap(BootstrapUpdater.java:36)
   at com.atlassian.bamboo.agent.bootstrap.AgentContext.updateBootstrapIfNecessary(AgentContext.java:203)
   at com.atlassian.bamboo.agent.bootstrap.AgentContext.initServerSession(AgentContext.java:104)
   at com.atlassian.bamboo.agent.bootstrap.AgentContext.run(AgentContext.java:94)
   at com.atlassian.bamboo.agent.bootstrap.AgentBootstrap.run(AgentBootstrap.java:95)
   at com.atlassian.bamboo.agent.bootstrap.AgentBootstrap.main(AgentBootstrap.java:41)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240)
   at java.lang.Thread.run(Unknown Source)
JVM exited while starting the application.

I checked the Java version and architecture, the config file for the wrapper and the agent and couldn't find any difference to the other Remote Agents that I use. The system Path variable looks good as well.

 

Remote Agent Infos:
OS: Windows 7 x64
Jdk: 1.8_60 x64 by Oracle
Wrapper / Remote Agent Version: Version 3.2.3-atlassian-1

Bamboo Version: 5.9.4

Any help is highly appreciated.
 

Answer
Watch
Like Be the first to like this
865 views

2 answers

1 accepted

0 votes
Answer accepted
Robin Gauß
Robin Gauß October 12, 2015

I found it out myself.

The problem was caused by a network share of the standard installation path. The path was shared before the bamboo agent got installed. Somehow the installation batch for the service used the UNC path for the call of the agent rather than the local path. It worked after removing the share of the folder and reinstalling the whole agent.
Make sure to check the "Path to executable" in the Windows service if you run into a similar problem.

Reply
0 votes
Przemek Bruski
Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 5, 2015

What is the full path of your atlassian-bamboo-agent-bootstrap.jar ?

View More Comments
Robin Gauß
Robin Gauß October 5, 2015

I guess you mean the bamboo-agent-bootstrap.jar Full path: C:\Users\[UserID]\bamboo-agent-home\lib\bamboo-agent-bootstrap.jar The UserID contains no blanks or special characters it's like abc123.

Like
rsperafico
rsperafico
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 6, 2015

Hello Robin, The file requested is "atlassian-bamboo-agent-bootstrap-5.9.4.jar": * under "<bamboo-install>/atlassian-bamboo/WEB-INF/lib" * under "<bamboo-agent-home>/classpath" — Kind regards, Rafael P. Sperafico Atlassian Support

Like
Robin Gauß
Robin Gauß October 6, 2015

Alright, the paths are: E:\Atlassian\Bamboo\atlassian-bamboo\WEB-INF\lib\atlassian-bamboo-agent-bootstrap-5.9.4.jar or \\[Hostname]\Atlassian\Bamboo\atlassian-bamboo\WEB-INF\lib\atlassian-bamboo-agent-bootstrap-5.9.4.jar and C:\Users\[UserID]\bamboo-agent-home\classpath\atlassian-bamboo-agent-core-5.9.4.jar

Like
Przemek Bruski
Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 8, 2015

How do you start your agent?

Like
Robin Gauß
Robin Gauß October 8, 2015

I used the included batches to create a Windows service. Something strange happened today. After reinstalling the whole agent, the process agent that got started by the installation process was working correct. The service that I installed afterwards failed again with the same error like before. So I guess it has something to do with the service. The service is set up to use the account of the main PC user which also has local admin rights on the machine and can write to the user directory where the builds are happening. Maybe this has something to do with it? This setup is also used on the other 3 remote agents that are working with no problem. But maybe I missed something.

Like
Przemek Bruski
Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 8, 2015

What I think happens is that for some reason the agent determines its location using an UNC path and that does not work.

Like
Reply

Suggest an answer

Log in or Sign up to answer
Bamboo
Bamboo
TAGS
AUG Leaders

Atlassian Community Events

    See all events