blocks|key|3090208|text|ALB+healthcheck将通过web界面访问您的healthcheck.php，并且不知道文件在文件系统中的位置。该值必须是主机名之后的URI路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3090209|将运行状况检查配置为/var/www/html/generic/website.com/healthcheck.php相当于告诉亚马逊网络服务检查http://website.com//var/www/html/generic/website.com/healthcheck.php，这可能不是您的本意。|offset|length|style|CODE|3090210|假设您想要检查的实际路径更像http://website.com/healthcheck.php，将您的健康检查路径更新为简单的/healthcheck.php，这对您来说应该是可行的。|3090211|entityMap^0|0|A|1D|21|1W|0|E|Y|1S|G|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|K|$]]

The ALB healthcheck is going to be accessing your healthcheck.php via the web interface and has no concept of where the files exist on the file system. This value needs to be the URI path after the hostname.
Configuring the healthcheck to be <code>/var/www/html/generic/website.com/healthcheck.php</code> is equivalent to telling AWS to check <code>http://website.com//var/www/html/generic/website.com/healthcheck.php</code> which is probably not your intention.
Assuming the actual path you want to check is more like <code>http://website.com/healthcheck.php</code>, update your healthcheck path to simply be <code>/healthcheck.php</code> and this should hopefully work for you.

blocks|key|383622|text|因为您在nginx中有多个命名主机。您可以尝试在/上设置状态码为200OK的运行状况检查。它应该返回默认的nginx页面，状态代码为200OK。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|383623|另一种方法是，您可以添加不存在的健康检查url，如/my-health-page，并在健康检查配置中将预期的健康检查状态代码设置为404。因此，我们在这里假设的是，如果nginx正在检查url并返回404+NOT+FOUND，则Nginx正在工作。但是这个方法不会检查比这更多的东西。|383624|优点：|383625|383626|ALB能够检测您的实例是否正在运行|unordered-list-item|383627|ALB可以检查nginx是否正在运行|383628|383629|缺点:运行状况检查不能识别情况，例如php不工作或应用程序无法访问mysql服务器等。|383630|entityMap^0|O|1|0|P|F|2R|D|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|13|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|14|8|@]|D|@]|E|$]]|$1|N|3|O|5|M|7|15|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|16|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|17|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|T|$]]

Since you have multiple named hosts in nginx. What you could try is setting the healthcheck on the <code>/</code> with 200 OK as the status code. it should return the default nginx page with status code 200 OK.
Another method is, you can add healthcheck url that doesn't exist such as <code>/my-health-page</code> and in the health check configuration set the expected health check status code to be 404. So what we are assuming here is, if the nginx is inspecting url and return <code>404 NOT FOUND</code>,the Nginx is working. But this method wont be checking anything more than that.
Pros:
<ul>
<li>ALB is able to whether your instance is running</li>
<li>ALB can check whether nginx is running</li>
</ul>
Cons:
The health check wont identify the cases for example php not working or mysql server is not reachable from the application etc

blocks|key|4516621|text|似乎您不能使用基于名称的vhost进行健康检查。因此，我在我的vhost文件中添加了以下代码。它所做的是，如果有人直接访问你的ip，它会给他们一个404，但如果他们访问你的ip/healthcheck，那么它将显示200，这正是ALB所需要的。然后在你的路径中放入/healthcheck。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4516622|<VirtualHost+*:80>
++ServerName+default
++RewriteRule+"/healthcheck"+-+[R=200]
++Redirect+404+/
</VirtualHost>
<VirtualHost+_default_:80>
++RewriteRule+"/healthcheck"+-+[R=200]
++Redirect+404+/
</VirtualHost>|code-block|syntax|javascript|4516623|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Seems you can't use a namebased vhost for a healthcheck. So in my vhost file I added the following code. What it does is if someone goes straight to your ip it will give them a 404 but if they go to your ip/healthcheck then it will show a 200 which is what ALB needs. Then in your path just put /healthcheck.
<pre><code>&lt;VirtualHost *:80&gt;
 ServerName default
 RewriteRule &quot;/healthcheck&quot; - [R=200]
 Redirect 404 /
&lt;/VirtualHost&gt;
&lt;VirtualHost _default_:80&gt;
 RewriteRule &quot;/healthcheck&quot; - [R=200]
 Redirect 404 /
&lt;/VirtualHost&gt;
</code></pre>

I have an ALB with 2 targets in the target group. However my health check aren't working properly. Both are showing
<pre><code>&quot;Health checks failed with these codes: [404]&quot;
</code></pre>
My settings for the health check path are:
<pre><code>/var/www/html/generic/website.com/healthcheck.php
</code></pre>
and if I do a <code>nano /var/www/html/generic/website.com/healthcheck.php</code> on the ec2 instance it shows this which should be all the health check needs I think.
<pre><code>&lt;?php
header(&quot;Status: 200&quot;);
?&gt;
</code></pre>
I double checked the AZ and the ALB is in the same one and subnets as the 2 instances.
Also when I check my apache logs this is what I see:
<pre><code>&quot;GET /var/www/html/generic/website.com/healthcheck.php HTTP/1.1&quot; 404 196 &quot;-&quot; &quot;ELB-HealthChecker/2.0&quot;
</code></pre>
What am I doing wrong that is making the healthcheck fail?

AWS ALB Health Check 404

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我有一个ALB，目标组中有2个目标。然而，我的健康检查不能正常工作。两个都在显示"Health checks failed with these codes: [404]"我对运行状况检查路径的设置是：/var/www/html/generic/website.com/healthcheck.php如果我在ec2实例上...

问AWS ALB运行状况检查404
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问AWS ALB运行状况检查404EN