forked from cep21/healthcheck_nginx_upstreams
-
Notifications
You must be signed in to change notification settings - Fork 478
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
Segfault when compiling with nginx_upstream_check_module but not using it #3
Comments
Thanks for your bug report, nice catch. I have fix the problem in the new revision. This is a silly bug. I think I need a careful code review and a full test. |
Closed
rq0net
pushed a commit
to rq0net/nginx_upstream_check_module
that referenced
this issue
Dec 9, 2020
created check_1.11.1+.patch
ngarratt
pushed a commit
to ngarratt/nginx_upstream_check_module
that referenced
this issue
Jul 5, 2023
…healthchecks_cleanup OPENRESTY-71 SSL healthchecks cleanup
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the module is compiled in but not used, in ngx_http_upstream_check_init_shm()
(umcf->peers->peers.nelts > 0) is never true thus check_peers_ctx stays NULL.
This causes a segfault when then ngx_http_check_add_timers() is called
The text was updated successfully, but these errors were encountered: