Bad HTTP status received 503
Information
| Summary: |
A new virtual service was created, however, the real server is not passing health checks. |
| Environment: |
Product: LoadMaster Version: 7.2.56 Platform: VMware Application: IIS |
| Question/Problem Description: |
I created a new virtual service and the real server is showing as down. |
| Steps to Reproduce: | |
| Error Message: | Bad HTTP status received |
| Defect Number: | |
| Enhancement Number: | |
| Cause: |
The health check tries to access the root page URL by default to determine if the machine is available. Checks were failing since the root page is not an available service and has no content. |
| Resolution: |
The real server was failing due to Bad HTTP Status 503 which would mean the server is unavailable at the root page since this is checked by default. Navigating to the real server directly returned a 503 status code. Since there was no service available within the root page, an available directory needed to be specified within the health check parameters. Once a URL was configured within the health checking parameters the virtual service began passing health checks. To specify the URL, navigate to Virtual Services > View/Modify Services > Modify > Real Servers > URL. |
| Workaround: |
Health check status codes can be set to override default functionality when the 503 status code is specified within the health check parameters. Changing the status code would also work, however, if the site becomes unavailable the LoadMaster may not detect it since the root page is not actually available. It may be best to check on an active URL rather than specifying the status code that the root page is returning. Virtual Services > View/Modify Services > Modify > Real Servers > Status Codes. |
| Notes: |
https://support.kemptechnologies.com/hc/en-us/articles/211215546-Health-Checking Acceptable status codes would be anything between 200-299, 301, 302, or 401 |