Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,623
Community Members
 
Community Events
168
Community Groups

Unable to get bucket location for [bamboo-agent-release-us-e1]

I'm attempting to get Elastic Bamboo configured. Instances are successfully being spawned based on configured rules for when I'd need them, but the elastic instances fail to fully startup. The bamboo-elastic-agent.out has the following error info:

Syncing Elastic Bamboo Agent files...
2019-02-05 23:43:26,658 INFO [main] [S3Sync] Syncing from: bamboo-agent-release-us-e1/6.7.2/a7bfbd2f18ee00d80b6f43b636e3f4619fc097d099355a3643f8ae58607
fae87/ to /opt/bamboo-elastic-agent
2019-02-05 23:43:27,835 INFO [main] [AmazonClients] Detected current region us-east-1, using it for S3 access
2019-02-05 23:43:27,836 INFO [main] [S3Synchroniser] Syncing s3://bamboo-agent-release-us-e1/6.7.2/a7bfbd2f18ee00d80b6f43b636e3f4619fc097d099355a3643f8
ae58607fae87/ to /opt/bamboo-elastic-agent
2019-02-05 23:43:27,838 INFO [main] [AmazonClients] Detecting bucket location for [bamboo-agent-release-us-e1] via us-east-1
2019-02-05 23:46:28,894 WARN [main] [AmazonClients] Unable to get bucket location for [bamboo-agent-release-us-e1], using default. Error: com.amazonaws
.SdkClientException: Unable to execute HTTP request: Connect to bamboo-agent-release-us-e1.s3.amazonaws.com:443 [bamboo-agent-release-us-e1.s3.amazonaw
s.com/52.216.17.80] failed: connect timed out
2019-02-05 23:46:28,894 INFO [main] [S3Synchroniser] Fetching the list of remote objects...
Exception in thread "main" com.amazonaws.SdkClientException: Unable to execute HTTP request: Connect to bamboo-agent-release-us-e1.s3.amazonaws.com:443
[bamboo-agent-release-us-e1.s3.amazonaws.com/52.216.105.131] failed: connect timed out
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1116)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1066)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667)
at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4365)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4312)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4306)
at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:840)
at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:815)
at com.atlassian.aws.s3.S3Synchroniser.getObjectNamesAndHashes(S3Synchroniser.java:340)
at com.atlassian.aws.s3.S3Synchroniser.sync(S3Synchroniser.java:162)
at com.atlassian.bamboo.agent.elastic.S3Sync.sync(S3Sync.java:62)
at com.atlassian.bamboo.agent.elastic.installer.ElasticAgentInstaller.install(ElasticAgentInstaller.java:68)
at com.atlassian.bamboo.agent.elastic.installer.ElasticAgentInstaller.main(ElasticAgentInstaller.java:168)
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to bamboo-agent-release-us-e1.s3.amazonaws.com:443 [bamboo-agent-release-us-e1.s3.amazonaws.com/52.216.105.131] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.amazonaws.http.conn.ClientConnectionManagerFactory$Handler.invoke(ClientConnectionManagerFactory.java:76)
at com.amazonaws.http.conn.$Proxy4.connect(Unknown Source)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at com.amazonaws.http.apache.client.impl.SdkHttpClient.execute(SdkHttpClient.java:72)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1238)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1058)
... 16 more
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:339)
at com.amazonaws.http.conn.ssl.SdkTLSSocketFactory.connectSocket(SdkTLSSocketFactory.java:132)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
... 32 more

1 answer

0 votes

Hi! 

Have you checked the connectivity by 

telnet bamboo-agent-release-us-e1.s3.amazonaws.com 443

from source place. Looks like firewall issue :)

Because it works well,

 

Cheers,

Gonchik Tsymzhitov

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events