Registered Target Instance shows unhealthy in target groups
up vote
0
down vote
favorite
I have created a Application Load Balancer(ALB) and registered target groups with Ec2 instance and all the deployment is done in openshift (I have created routes for all registered instances in Openshift). Deployment works fine but the issue is in Target groups registered instances health shows unhealthy and throws message {Health checks failed with these codes: [503]}. How do i make health checks success.
PS: if i use NLB target group instances shows healthy.
what am i deploying?
grafana and it works fine only issue is registred instances shows unhealthy
amazon-web-services amazon-ec2 routes amazon-route53
asked Nov 9 at 15:18
Cena
255
add a comment |
up vote
0
down vote
favorite
I have created a Application Load Balancer(ALB) and registered target groups with Ec2 instance and all the deployment is done in openshift (I have created routes for all registered instances in Openshift). Deployment works fine but the issue is in Target groups registered instances health shows unhealthy and throws message {Health checks failed with these codes: [503]}. How do i make health checks success.
PS: if i use NLB target group instances shows healthy.
what am i deploying?
grafana and it works fine only issue is registred instances shows unhealthy
amazon-web-services amazon-ec2 routes amazon-route53
asked Nov 9 at 15:18
Cena
255
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have created a Application Load Balancer(ALB) and registered target groups with Ec2 instance and all the deployment is done in openshift (I have created routes for all registered instances in Openshift). Deployment works fine but the issue is in Target groups registered instances health shows unhealthy and throws message {Health checks failed with these codes: [503]}. How do i make health checks success.
PS: if i use NLB target group instances shows healthy.
what am i deploying?
grafana and it works fine only issue is registred instances shows unhealthy
amazon-web-services amazon-ec2 routes amazon-route53
asked Nov 9 at 15:18
Cena
255
I have created a Application Load Balancer(ALB) and registered target groups with Ec2 instance and all the deployment is done in openshift (I have created routes for all registered instances in Openshift). Deployment works fine but the issue is in Target groups registered instances health shows unhealthy and throws message {Health checks failed with these codes: [503]}. How do i make health checks success.
PS: if i use NLB target group instances shows healthy.
what am i deploying?
grafana and it works fine only issue is registred instances shows unhealthy
amazon-web-services amazon-ec2 routes amazon-route53
amazon-web-services amazon-ec2 routes amazon-route53
asked Nov 9 at 15:18
Cena
255
asked Nov 9 at 15:18
Cena
255
edited Nov 9 at 19:29
asked Nov 9 at 15:18
Cena
255
asked Nov 9 at 15:18
Cena
255
asked Nov 9 at 15:18
Cena
255
255
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
As far as I know, ALB is HTTP/HTTPS check (URL path), and NLB is TCP check (port).
So, you might be configured your ALB health check details for your OpenShift cluster after checking your health check details. Check the target URL of health check is valid.
- Application Load Balancer - health check
- Network Load Balancr - health check
I hope if help you. :^)
answered Nov 10 at 12:37
Daein Park
85527
How to configure ALB health check for open shift or any other cluster, I didn't configure any health check
– Cena
Nov 11 at 23:38
As far as I remember, Application Load Balancer is HTTP/HTTPS health check against "/" path, so it will respond503 statusfromOpenShift, how about change thehealth checktoTCP port check, if you can ? Unfortunately I'm not familiar with AWS configuration, so I can't help you aboutAWSdetails, but you would check the around health check details betweenALBandNLB, then you can find solution for this issue.
– Daein Park
Nov 12 at 0:58
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As far as I know, ALB is HTTP/HTTPS check (URL path), and NLB is TCP check (port).
So, you might be configured your ALB health check details for your OpenShift cluster after checking your health check details. Check the target URL of health check is valid.
- Application Load Balancer - health check
- Network Load Balancr - health check
I hope if help you. :^)
answered Nov 10 at 12:37
Daein Park
85527
How to configure ALB health check for open shift or any other cluster, I didn't configure any health check
– Cena
Nov 11 at 23:38
As far as I remember, Application Load Balancer is HTTP/HTTPS health check against "/" path, so it will respond503 statusfromOpenShift, how about change thehealth checktoTCP port check, if you can ? Unfortunately I'm not familiar with AWS configuration, so I can't help you aboutAWSdetails, but you would check the around health check details betweenALBandNLB, then you can find solution for this issue.
– Daein Park
Nov 12 at 0:58
add a comment |
up vote
0
down vote
As far as I know, ALB is HTTP/HTTPS check (URL path), and NLB is TCP check (port).
So, you might be configured your ALB health check details for your OpenShift cluster after checking your health check details. Check the target URL of health check is valid.
- Application Load Balancer - health check
- Network Load Balancr - health check
I hope if help you. :^)
answered Nov 10 at 12:37
Daein Park
85527
How to configure ALB health check for open shift or any other cluster, I didn't configure any health check
– Cena
Nov 11 at 23:38
As far as I remember, Application Load Balancer is HTTP/HTTPS health check against "/" path, so it will respond503 statusfromOpenShift, how about change thehealth checktoTCP port check, if you can ? Unfortunately I'm not familiar with AWS configuration, so I can't help you aboutAWSdetails, but you would check the around health check details betweenALBandNLB, then you can find solution for this issue.
– Daein Park
Nov 12 at 0:58
add a comment |
up vote
0
down vote
up vote
0
down vote
As far as I know, ALB is HTTP/HTTPS check (URL path), and NLB is TCP check (port).
So, you might be configured your ALB health check details for your OpenShift cluster after checking your health check details. Check the target URL of health check is valid.
- Application Load Balancer - health check
- Network Load Balancr - health check
I hope if help you. :^)
answered Nov 10 at 12:37
Daein Park
85527
As far as I know, ALB is HTTP/HTTPS check (URL path), and NLB is TCP check (port).
So, you might be configured your ALB health check details for your OpenShift cluster after checking your health check details. Check the target URL of health check is valid.
- Application Load Balancer - health check
- Network Load Balancr - health check
I hope if help you. :^)
answered Nov 10 at 12:37
Daein Park
85527
answered Nov 10 at 12:37
Daein Park
85527
answered Nov 10 at 12:37
Daein Park
85527
answered Nov 10 at 12:37
Daein Park
85527
85527
How to configure ALB health check for open shift or any other cluster, I didn't configure any health check
– Cena
Nov 11 at 23:38
As far as I remember, Application Load Balancer is HTTP/HTTPS health check against "/" path, so it will respond503 statusfromOpenShift, how about change thehealth checktoTCP port check, if you can ? Unfortunately I'm not familiar with AWS configuration, so I can't help you aboutAWSdetails, but you would check the around health check details betweenALBandNLB, then you can find solution for this issue.
– Daein Park
Nov 12 at 0:58
add a comment |
How to configure ALB health check for open shift or any other cluster, I didn't configure any health check
– Cena
Nov 11 at 23:38
As far as I remember, Application Load Balancer is HTTP/HTTPS health check against "/" path, so it will respond503 statusfromOpenShift, how about change thehealth checktoTCP port check, if you can ? Unfortunately I'm not familiar with AWS configuration, so I can't help you aboutAWSdetails, but you would check the around health check details betweenALBandNLB, then you can find solution for this issue.
– Daein Park
Nov 12 at 0:58
How to configure ALB health check for open shift or any other cluster, I didn't configure any health check
– Cena
Nov 11 at 23:38
How to configure ALB health check for open shift or any other cluster, I didn't configure any health check
– Cena
Nov 11 at 23:38
As far as I remember, Application Load Balancer is HTTP/HTTPS health check against "/" path, so it will respond
503 status from OpenShift, how about change the health check to TCP port check, if you can ? Unfortunately I'm not familiar with AWS configuration, so I can't help you about AWS details, but you would check the around health check details between ALB and NLB, then you can find solution for this issue.– Daein Park
Nov 12 at 0:58
As far as I remember, Application Load Balancer is HTTP/HTTPS health check against "/" path, so it will respond
503 status from OpenShift, how about change the health check to TCP port check, if you can ? Unfortunately I'm not familiar with AWS configuration, so I can't help you about AWS details, but you would check the around health check details between ALB and NLB, then you can find solution for this issue.– Daein Park
Nov 12 at 0:58
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228476%2fregistered-target-instance-shows-unhealthy-in-target-groups%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
