It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
When I attempt to connect the remote agent to the primary server, I'm getting the following error:
INFO | jvm 1 | 2012/07/20 08:13:03 | 2012-07-20 08:13:03,422 INFO WrapperSimpleAppMain AgentContext Requesting
fingerprint, url: http://bamboo/GetFingerprint.action?hostName=BAMBOO-BLD1&version
=3&agentUuid=63c717dc-3e9b-4ed7-bd05-f1d0d6a7d5d0
INFO | jvm 1 | 2012/07/20 08:13:03 | Exiting due to fatal exception.
INFO | jvm 1 | 2012/07/20 08:13:03 | com.atlassian.bamboo.agent.bootstrap.RemoteAgentHttpException: HTTP status code 500 received in response to fingerprint request.
In preparation for a support ticket, their first request is to run their network analyzer, which appears to check out:
C: bamboo bamboo-agent-home>java NetworkAnalyser http://bamboo
Testing connectivity to Bamboo Server: http://bamboo
Trying to establish connection with remote server: http://bamboo
Connection established!
Testing connectivity to Bamboo Server: http:?//bamboo:54663
Trying to establish connection with remote server: http:?//bamboo:54663
Connection established!
Further info - this is from the bamboo log:
2012-07-20 08:13:04,464 INFO http-80-3 AccessLogFilter GET http://bamboo/GetFingerprint.action?hostName=BAMBOO-BLD1&version=3&agentUuid=63c717dc-3e9b-4ed7-bd05-f1d0d6a7d5d0 60698kb
2012-07-20 08:13:04,480 ERROR http-80-3 DispatcherUtils Could not find action
There is no Action mapped for namespace / and action name GetFingerprint. Check if there is such an action name with such namespace defined in the xwork.xml and also if such an action class exists. Check also the log to see if the action class is successfully loaded. - unknown location
at com.opensymphony.xwork.DefaultActionProxy.<init>(DefaultActionProxy.java:75)
at com.opensymphony.xwork.DefaultActionProxyFactory.createActionProxy(DefaultActionProxyFactory.java:46)
at com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:265)
To fix this issue I had to do a few things.
1. Added -Dbamboo.home=C:\bamboo\bamboo-agent-home to the java statement on the build server when building the agent.
2. Changed the bamboo.cfg.xml to use the server IP address instead of the DNS name.
3. Opened port 54663 on the Windows firewall on both machines.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreBamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.