Bamboo agent stuck at pending with 30 minute timeout starting tunnel server
Asked by Lee Myring:

Atlassian OnDemand

Custom Amazon AMI based on Standard Atlassian AMI just copied to EU region

Starting Bamboo Agent and the tail of /home/bamboo/bamboo-elastic-agent.out shows that it gets stuck with the tunnel server. After 30 mins you get a fatal exception which terminates the instance. There are no changes from when the bamboo agent was last running successfully. The box can be contacted from the outside world via PING and via a telnet command to 26224 which indicates the box is running and accessible.

Is this related to another question I raised?

<https://answers.atlassian.com/questions/273550>

**Stacktrace of the log output**

2014-12-08 09:51:26,780 INFO \[main\] \[S3Utils\] Syncing s3://bamboo-agent-release-eu-w1/5.7-OD-06-010/f689e3f51bd0f52bd24bf2b7a1ca9bfdb6db1573/ to /opt/bamboo-elastic-agent

2014-12-08 09:51:26,781 INFO \[main\] \[S3Utils\] Fetching the list of remote objects...

2014-12-08 09:51:27,988 INFO \[main\] \[S3Utils\] Found 0 files in s3://bamboo-agent-release-eu-w1/5.7-OD-06-010/f689e3f51bd0f52bd24bf2b7a1ca9bfdb6db1573/

2014-12-08 09:51:28,017 INFO \[main\] \[S3Utils\] Found 388 files in /opt/bamboo-elastic-agent

2014-12-08 09:51:28,017 INFO \[main\] \[S3Utils\] Generating the list of files to fetch from S3...

2014-12-08 09:51:28,017 INFO \[main\] \[S3Utils\] Generating the list of files to remove...

2014-12-08 09:51:28,018 INFO \[main\] \[S3Utils\] Removing 0 files from /opt/bamboo-elastic-agent

2014-12-08 09:51:28,018 INFO \[main\] \[S3Utils\] Fetching 0 files to /opt/bamboo-elastic-agent

2014-12-08 09:51:28,018 INFO \[main\] \[S3Utils\] Fetched 0 MB from S3

2014-12-08 09:51:28,022 INFO \[main\] \[ElasticAgentInstaller\] Starting \[java, -server, -Xms32m, -Xmx256m, -XX:MaxPermSize=128m, -XX:+HeapDumpOnOutOfMemoryError, -Dimagefiles.version=3.0, -Dbamboo.agent.installDir=/opt/bamboo-elastic-agent, -cp, /opt/bamboo-elastic-agent/boot/commons-io-2.4.[jar:/opt/bamboo-elastic-agent/boot/bcprov-jdk15on-1.48.jar:/opt/bamboo-elastic-agent/boot/atlassian-annotations-0.4.jar:/opt/bamboo-elastic-agent/boot/commons-logging-1.0.4.jar:/opt/bamboo-elastic-agent/boot/bcpkix-jdk15on-1.48.jar:/opt/bamboo-elastic-agent/boot/gson-2.2.2-atlassian-1.jar:/opt/bamboo-elastic-agent/boot/joda-time-2.3.jar:/opt/bamboo-elastic-agent/boot/atlassian-bamboo-agent-elastic-5.5-OD-04-0004.jar:/opt/bamboo-elastic-agent/boot/atlassian-bamboo-core-agent-bootstrap-5.5-OD-04-0...](http://jar/opt/bamboo-elastic-agent/boot/bcprov-jdk15on-1.48.jar:/opt/bamboo-elastic-agent/boot/atlassian-annotations-0.4.jar:/opt/bamboo-elastic-agent/boot/commons-logging-1.0.4.jar:/opt/bamboo-elastic-agent/boot/bcpkix-jdk15on-1.48.jar:/opt/bamboo-elastic-agent/boot/gson-2.2.2-atlassian-1.jar:/opt/bamboo-elastic-agent/boot/joda-time-2.3.jar:/opt/bamboo-elastic-agent/boot/atlassian-bamboo-agent-elastic-5.5-OD-04-0004.jar:/opt/bamboo-elastic-agent/boot/atlassian-bamboo-core-agent-bootstrap-5.5-OD-04-0004.jar:/opt/bamboo-elastic-agent/boot/commons-codec-1.4.jar:/opt/bamboo-elastic-agent/boot/aws-java-sdk-1.7.1.jar:/opt/bamboo-elastic-agent/boot/jackson-core-2.1.1.jar:/opt/bamboo-elastic-agent/boot/atlassian-util-concurrent-2.4.1.jar:/opt/bamboo-elastic-agent/boot/annotations-13.0.jar:/opt/bamboo-elastic-agent/boot/atlassian-bamboo-agent-bootstrap-5.5-OD-04-0004.jar:/opt/bamboo-elastic-agent/boot/httpcore-4.2.5.jar:/opt/bamboo-elastic-agent/boot/httpclient-4.2.5.jar:/opt/bamboo-elastic-agent/boot/jsr305-1.3.9.jar:/opt/bamboo-elastic-agent/boot/atlassian-tunnel-0.20.jar:/opt/bamboo-elastic-agent/boot/atlassian-bamboo-api-agent-bootstrap-5.5-OD-04-0004.jar:/opt/bamboo-elastic-agent/boot/guava-10.0.1.jar:/opt/bamboo-elastic-agent/boot/commons-lang-2.6.jar:/opt/bamboo-elastic-agent/boot/commons-httpclient-3.0.1.jar:/opt/bamboo-elastic-agent/boot/jackson-annotations-2.1.1.jar:/opt/bamboo-elastic-agent/boot/stax-api-1.0-2.jar:/opt/bamboo-elastic-agent/boot/fugue-1.1.jar:/opt/bamboo-elastic-agent/boot/jackson-databind-2.1.1.jar:/opt/bamboo-elastic-agent/boot/atlassian-bamboo-agent-elastic-shared-5.5-OD-04-0004.jar:/opt/bamboo-elastic-agent/boot/atlassian-aws-1.0.59.jar:/opt/bamboo-elastic-agent/boot/log4j-1.2.15.jar):, com.atlassian.bamboo.agent.elastic.client.ElasticAgentBootstrap\]

2014-12-08 09:51:29,375 INFO \[main\] \[ElasticAgentBootstrap\] Starting Agent Bootstrap using Java 1.6.0_45 from Sun Microsystems Inc.

2014-12-08 09:51:29,526 INFO \[main\] \[ElasticAgentBootstrap\] No tunnelling. Using standard protocol handlers.

2014-12-08 09:51:29,535 INFO \[main\] \[ElasticAgentBootstrap\] Starting tunnel server


Answers:
author: Hayk Avetisyan
body: hi all

I got following this morning (yesterday it was ok)

FATAL \[main\] \[ElasticAgentInstaller\] No jars found in /opt/bamboo-elastic-agent/boot - it probably means that the assembly has not been propagated to this region. Contact Atlassian support.

can anyone help? thanks


author: Lee Myring
body: What was the problem please?

I have updated the agent version on my machine to 3.4 as instructed to do so via a support ticket so now I don't know if it's that or your problem resolution that has solved the issue? Please advise

comments: author: Przemek Bruski
body: Both. You normally shouldn't need to update the bootstrap manually, so your change fixed that. But the correction we've made should let you continue using your old image.


author: Przemek Bruski
body: The problem was resolved about an hour ago.


Tags: cloud