2017-02-17 75 views
0

我正在創建一個雲信息模板,該模板創建一些資源,如EC2實例autoscaling grouplaunchConfiguration。 通過launchConfiguration資源的userData財產,我試圖安裝Cloudwatch agent如下:無法通過Amazon ECS優化的AMI上的雲信息安裝cloudwatch代理

"UserData":{ "Fn::Base64" : { 
      "Fn::Join" : ["", [ 
       "#!/bin/bash -xe\n", 
       "yum -y install aws-cfn-bootstrap\n", 
       "/opt/aws/bin/cfn-init -v", 
       "   --stack ", { "Ref": "AWS::StackName" }, 
       "   --resource LaunchCongig", 
       "   --region ", { "Ref" : "AWS::Region" },"\n", 
       "yum -y install wget\n", 
       "# Get the CloudWatch Logs agent\n", 
       "wget https://s3.amazonaws.com/aws-cloudwatch/downloads/latest/awslogs-agent-setup.py\n", 
       "# Install the CloudWatch Logs agent\n", 
       "python ./awslogs-agent-setup.py -n -r ", { "Ref" : "AWS::Region" }, " -c /etc/cwlogs.cfg || error_exit 'Failed to run CloudWatch Logs agent setup'\n", 
       "service awslogs start" 
      ]]} 

SSH連接實例後,我檢查了文件/var/log/cloud-init-output.log,看看是否一切都很好,但這裏是我得到了什麼:

+ wget https://s3.amazonaws.com/aws-cloudwatch/downloads/latest/awslogs-agent-setup.py 
--2017-02-17 14:36:10-- https://s3.amazonaws.com/aws-cloudwatch/downloads/latest/awslogs-agent-setup.py 
Resolving s3.amazonaws.com (s3.amazonaws.com)... 52.216.226.59 
Connecting to s3.amazonaws.com (s3.amazonaws.com)|52.216.226.59|:443... connected. 
HTTP request sent, awaiting response... 200 OK 
Length: 47998 (47K) [text/x-python] 
Saving to: ‘awslogs-agent-setup.py’ 

    0K .......... .......... .......... .......... ...... 100% 196K=0.2s 

2017-02-17 14:36:10 (196 KB/s) - ‘awslogs-agent-setup.py’ saved [47998/47998] 

+ python ./awslogs-agent-setup.py -n -r eu-west-1 -c /etc/cwlogs.cfg 

Step 1 of 5: Installing pip ...Traceback (most recent call last): 
    File "./awslogs-agent-setup.py", line 1144, in <module> 
    main() 
    File "./awslogs-agent-setup.py", line 1140, in main 
    setup.setup_artifacts() 
    File "./awslogs-agent-setup.py", line 693, in setup_artifacts 
    self.install_pip() 
    File "./awslogs-agent-setup.py", line 600, in install_pip 
    fail("Could not install pip. Please try again or see " + AGENT_SETUP_LOG_FILE + " for more details") 
TypeError: fail() takes exactly 2 arguments (1 given) 
+ error_exit 'Failed to run CloudWatch Logs agent setup' 
/var/lib/cloud/instance/scripts/part-001: line 8: error_exit: command not found 
Feb 17 14:36:12 cloud-init[2798]: util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-001 [127] 
Feb 17 14:36:12 cloud-init[2798]: cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts) 
Feb 17 14:36:12 cloud-init[2798]: util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_scripts_user.pyc'>) failed 
Cloud-init v. 0.7.6 finished at Fri, 17 Feb 2017 14:36:12 +0000. Datasource DataSourceEc2. Up 85.78 seconds 

這個腳本有什麼問題?有沒有其他的方法來安裝代理? 謝謝。

編輯:

我想通了,是因爲也許python-pip包沒有得到安裝,所以我說這個給userData

"yum -y install python-pip\n", 

之後,我再次打出了模板,奇怪我得到了同樣的錯誤。

我usinh的Amazon ECS-optimized AMI

回答

1

我通過yum awslogs直接安裝代理解決了這個問題:

 "UserData":{ "Fn::Base64" : { 
     "Fn::Join" : ["", [ 
      "#!/bin/bash -xe\n", 
      "yum -y install aws-cfn-bootstrap\n", 
      "/opt/aws/bin/cfn-init -v", 
      "   --stack ", { "Ref": "AWS::StackName" }, 
      "   --resource launchConfig", 
      "   --region ", { "Ref" : "AWS::Region" },"\n", 
      "yum -y install awslogs\n", 
      "service awslogs start" 
     ]]} 

下面是從日誌文件中的輸出:

Installed: 
    awslogs.noarch 0:1.1.2-1.10.amzn1            

Dependency Installed: 
    aws-cli.noarch 0:1.11.29-1.45.amzn1           
    aws-cli-plugin-cloudwatch-logs.noarch 0:1.3.3-1.15.amzn1      
    freetype.x86_64 0:2.3.11-15.14.amzn1           
    libjpeg-turbo.x86_64 0:1.2.90-5.14.amzn1          
    mailcap.noarch 0:2.1.31-2.7.amzn1            
    python27-botocore.noarch 0:1.4.86-1.62.amzn1         
    python27-colorama.noarch 0:0.2.5-1.7.amzn1          
    python27-dateutil.noarch 0:2.1-1.3.amzn1          
    python27-docutils.noarch 0:0.11-1.15.amzn1          
    python27-futures.noarch 0:3.0.3-1.3.amzn1          
    python27-imaging.x86_64 0:1.1.6-19.9.amzn1          
    python27-jmespath.noarch 0:0.9.0-1.11.amzn1         
    python27-ply.noarch 0:3.4-3.12.amzn1           
    python27-pyasn1.noarch 0:0.1.7-2.9.amzn1          
    python27-rsa.noarch 0:3.4.1-1.8.amzn1           

Complete! 
+ service awslogs start 
Starting awslogs: [ OK ] 
Cloud-init v. 0.7.6 finished at Fri, 17 Feb 2017 15:33:42 +0000. Datasource DataSourceEc2. Up 83.47 seconds 

一切正常這樣好。希望有一天能幫助別人!

2

有關ECS的具體信息,請參閱EC2容器服務文檔中的Using CloudWatch Logs with Container Instances,以獲取有關配置CloudWatch Logs的詳細信息。文檔建議使用yum install -y awslogs而不是Python安裝腳本。

該文檔在Configuring CloudWatch Logs at Launch with User Data部分提供了完整的示例。

在你的情況,因爲你已經在管理使用cfn-init和CloudFormation CloudFormation::Init元數據的配置文件,你不需要的配置文件的任何複雜的分析在用戶數據的腳本,但你仍然可以使用腳本作爲參考。值得添加到用戶數據腳本的一件事是運行chkconfig awslogs on以確保服務在重新啓動後繼續在實例上運行。

+0

在CloudFormation :: Init中;我這樣做了: '{「Ref」:「ClusterName」},「/」,{「Ref」:「ContainerInstances」}'我還沒有測試,但這是一樣的做userData? – Somar

+0

你能告訴我如何把這個腳本放在UserData中嗎? – Somar

+0

由於您使用的是CloudFormation,我認爲使用'CloudFormation :: Init'來引用這些字段可能是更好的選擇,並且更易於管理。如果您直接從控制檯啓動實例,則該文檔中的示例僅用於完全從用戶數據進行配置。我會堅持已有的內容,只是使用文檔中的細節作爲參考進行比較 - 可能會添加'chkconfig awslogs on'以確保服務始終在實例重新啓動後始終啓動。 – wjordan