Elastic agent status stuck in Pending - AmazonHttpClient Unable to execute HTTP request: connect timed out

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

問題

After creating a custom AMI, Bamboo is able to start the EC2 agent and from the AWS console it is identified as running however, it never progresses past the "Pending" state. The following log data is captured on the agent in bamboo-elastic-agent.out:

Syncing Elastic Bamboo Agent files...
2016-08-24 21:15:41,794 INFO [main] [S3Sync] Syncing from: bamboo-agent-release-us-e1/5.12.2.1/7d847bfc46abc598ec795eacdb0ebf959084237678a2a0353b189525b42b108c/ to /opt/bamboo-elastic-agent
2016-08-24 21:15:51,039 INFO [main] [S3Synchroniser] Syncing s3://bamboo-agent-release-us-e1/5.12.2.1/7d847bfc46abc598ec795eacdb0ebf959084237678a2a0353b189525b42b108c/ to /opt/bamboo-elastic-agent
2016-08-24 21:15:51,039 INFO [main] [AmazonClients] Detecting bucket location for [bamboo-agent-release-us-e1]
2016-08-24 21:16:21,724 INFO [main] [AmazonHttpClient] Unable to execute HTTP request: connect timed out
java.net.SocketTimeoutException: connect timed out
...

診断

The two default security groups that Bamboo creates enable all outbound HTTP traffic – "ControlledByBamboo" and "elasticbamboo".

原因

Amazon Virtual Private Cloud (VPC) doesn't automatically permit outbound traffic.

ソリューション

If you've set up a VPC you must define an Amazon Simple Storage Service (S3) endpoint from your VPC:

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-endpoints.html

 

最終更新日 2016 年 9 月 14 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.