-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upstream status not correct #258
Comments
@FrancisAston Hi, Thanks reporting!! nginx-module-vts/src/ngx_http_vhost_traffic_status_display_json.c Lines 603 to 616 in 5b3812e
I still don’t make sense obviously whether it is bug or not but it worth for diving deeply for this. I’m willing to investigate that. |
the 127.0.0.1:8540 is down , response json data: "down": false |
@FrancisAston |
@FrancisAston
c.f. http://nginx.org/en/docs/http/ngx_http_upstream_module.html#zone if the directive is inactive, the upstream alive status check which I referred the comment in #258 (comment) can't pass for the goto is exist before. nginx-module-vts/src/ngx_http_vhost_traffic_status_display_json.c Lines 573 to 575 in 5b3812e
As a test we activate the zone directive, the status result
gdb info:
|
http { add zone backend 64k; and reload nginx. |
nginx version: openresty/1.19.9.1
nginx-module-vts-0.2.1/
server alread down,but the status page still up
nginx_upstream_check_module page
![image](https://user-images.githubusercontent.com/34341863/212256182-085cdcdf-b97f-4a89-bb57-be9714842197.png)
nginx-module-vts status page
![image](https://user-images.githubusercontent.com/34341863/212256440-9792ff92-ca47-4261-8b2b-249b2d364ffc.png)
The text was updated successfully, but these errors were encountered: