AWS：无实例的发送数据 [英] AWS: None of the Instances are sending data

问题描述

我试图建立一个弹性魔豆申请用Amazon Web Services但是我收到错误的负载信息无实例的发送数据 。我试着删除弹性魔豆应用和EC2实例多次使用示例应用程序，并再次尝试，但我得到了同样的错误。

I'm trying to set up an Elastic Beanstalk application with Amazon Web Services however I'm receiving a load of errors with the message None of the instances are sending data. I've tried deleting the Elastic Beanstalk Application and the EC2 instance several times with the sample application and trying again but I get the same error.

我也试过上载与AWS弹性魔豆的命令行工具，烧瓶中的应用，但后来我收到以下错误：

I also tried uploading a flask application with AWS Elastic Beanstalk command line tools but then I received the error below:

Environment health has transitioned from Pending to Severe. 100.0 % of the requests to the ELB are failing with HTTP 5xx. Insufficient request rate (0.5 requests/min) to determine application health (7 minutes ago). ELB health is failing or not available for all instances. None of the instances are sending data

为什么我得到这个错误，我该如何解决？谢谢你。

Why do I get this error and how do I fix it? Thanks.

推荐答案

正在使用<一个href="https://aws.amazon.com/blogs/aws/elastic-beanstalk-update-enhanced-application-health-monitoring/">Enhanced健康监测。 具有增强健康监测的<一个href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/health-enhanced.html#health-enhanced-agent">agent安装在您的EC2实例监控重要的系统和应用水平的健康指标，并直接将它们发送到弹性青苗。

You are using Enhanced Health Monitoring. With enhanced health monitoring an agent installed on your EC2 instance monitors vital system and application level health metrics and sends them directly to Elastic Beanstalk.

当你看到像没有一个实例发送数据的错误信息，这意味着无论是在实例中的代理崩溃或无法将数据发布到弹性魔豆因网络错误或其他错误。

When you see an error message like "None of the instances are sending data", it means either the agent on the instance has crashed or it is unable to post data to Elastic Beanstalk due to networking error or some other error.

有关调试此，我建议从AWS控制台下载完整日志。您可以按照指示获取日志中的部分下载包日志由弹性魔豆控制台的此处。 如果您无法下载使用控制台以任何理由日志，也可以ssh到实例，并期待在日志中 /无功/日志。

For debugging this, I would recommend downloading "Full logs" from the AWS console. You can follow the instructions for getting logs in the section "Downloading Bundle Logs from Elastic Beanstalk Console" here. If you are unable to download logs using the console for any reason you can also ssh to the instance and look at the logs in /var/log.

您会发现在 /var/log/healthd/daemon.log 日志的健康代理。 其他日志这种情况下有用的是 /var/log/cfn-init.log ， /var/log/eb-cfn-init.log 和 /var/log/eb-activity.log 。你可以看一下日志，给你看到这些错误的更多细节？ 这应该希望给你更多的细节就没有一个实例发送数据的错误。

You will find logs for the health agent in /var/log/healthd/daemon.log. Additional logs useful for this situation are /var/log/cfn-init.log, /var/log/eb-cfn-init.log and /var/log/eb-activity.log. Can you look at the logs and give more details of the errors you see? This should hopefully give you more details regarding the error "None of the instances are sending data".

对于其他健康原因你们看到的：

Regarding other health "causes" you are seeing:

• 环境健康已经从待定过渡到重度 - 这是因为最初的环境健康状况的待定的。如果情况不走宽限期的健康状态转变中的健康的的严重的。你的情况，因为没有一个实例是健康/发送数据，健康转变为严重。

• Environment health has transitioned from Pending to Severe - This is because initially your environment health status is Pending. If the instances do not go healthy within grace period health status transitions to Severe. In your case since none of the instances is healthy / sending data, the health transitioned to Severe.

的请求到ELB的100.0％，是没有用的HTTP 5XX。没有足够的请求率（0.5请求/分钟）来确定应用程序运行状况（7分钟前）。 使用增强的健康监测，当弹性魔豆监控其他资源，除了您的EC2实例。例如，它监视CloudWatch的指标中的一种ELB。此错误意味着发送到您的环境CNAME /负载均衡器所有的请求都没有用HTTP 5XX错误。同时请求率非常低，每分钟只有0.5的要求，所以这表明，即使所有请求失败，请求速率为pretty的低。 5分钟前是指有关ELB度量信息稍微老了。由于弹性魔豆监控CloudWatch的指标，每隔几分钟，这样数据可以稍微陈旧。这是相对于我们从EC2实例是近实时获得直接的健康数据。你的情况，因为实例不发送数据对健康的唯一可用的源是被延迟了约7分钟ELB指标。

100.0 % of the requests to the ELB are failing with HTTP 5xx. Insufficient request rate (0.5 requests/min) to determine application health (7 minutes ago). Elastic Beanstalk monitors other resources in addition to your EC2 instances when using enhanced health monitoring. For example, it monitors cloudwatch metrics for your ELB. This error means that all requests sent to your environment CNAME/load balancer are failing with HTTP 5xx errors. At the same time the request rate is very low only 0.5 requests per minute, so this indicates that even though all requests are failing, the request rate is pretty low. "7 minutes ago" means that information about ELB metrics is slightly old. Because Elastic Beanstalk monitors cloudwatch metrics every few minutes, so the data can be slightly stale. This is as opposed to health data we get directly from the EC2 instances which is "near real time". In your case since the instances are not sending data the only available source for health is ELB metrics which is delayed by about 7 minutes.

ELB健康失败或不适用于所有的实例 弹性魔豆是看你的ELB的运行状况，也就是说，它是检查有多少实例背后ELB服务。在你的情况下，或者后面ELB所有实例都停止工作或健康是不适合某些其他原因。你应该仔细检查你的服务的角色配置是否正确。你可以阅读如何配置服务的角色正确这里还是在的documentation 。这可能是你的应用程序未能启动。

ELB health is failing or not available for all instances Elastic Beanstalk is looking at the health of your ELB, i.e. it is checking how many instances are in service behind ELB. In your case either all instances behind ELB are out of service or the health is not available for some other reason. You should double check that your service role is correctly configured. You can read how to configure service role correctly here or in the documentation. It is possible that your application failed to start.

在你的情况我建议集中在第一个错误无的情况下被发送数据。为此，你需要看日志，如上文所述。让我知道你在日志中看到的。该代理在启动实例上的引导过程相当早。所以，如果你看到类似无实例的发送数据的错误，这很可能是自举失败或代理无法启动的某些原因。日志应该告诉你更多。

In your case I would suggest focusing on the first error "None of the instances are sending data". For this you need to look at the logs as outlined above. Let me know what you see in the logs. The agent is started fairly early in the bootstrap process on the instance. So if you see an error like "None of the instances are sending data", it is very likely that bootstrap failed or the agent failed to start for some reason. The logs should tell you more.

另外，还要确保您使用与您的环境的实例配置文件。实例配置文件，可在您的EC2实例上运行的卫生剂弹性青苗进行身份验证。如果实例配置文件不与您的环境相关联，然后代理将无法将数据发送到弹性魔豆。了解更多关于实例概要文件与弹性魔豆<一href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts-roles.html#concepts-roles-instance">here.

Also make sure you are using an instance profile with your environment. Instance profile allows the health agent running on your EC2 instance to authenticate with Elastic Beanstalk. If instance profile is not associated with your environment then the agent will not be able to send data to Elastic Beanstalk. Read more about Instance Profiles with Elastic Beanstalk here.

这篇关于AWS：无实例的发送数据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！