Closed dayongi closed 5 years ago
I now know that the problem is that I wrote the wrong phase
@dayongi Yes, such error message is usually a clear indicator for the wrong execution context. Look at the documentation of this library for the correct usage.
@agentzh I was really careless. Thank you for your reply
ok I have seen
Yichun Zhang notifications@github.com 于2019年3月4日周一 上午2:28写道:
Closed #60 https://github.com/openresty/lua-resty-upstream-healthcheck/issues/60.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openresty/lua-resty-upstream-healthcheck/issues/60#event-2176430701, or mute the thread https://github.com/notifications/unsubscribe-auth/An2hdMYgNuvnfPvRvVmDE3VoVGBr3b1rks5vTBRGgaJpZM4bayBw .
-- tel: 18336032131 email:tianxiaoyongcs@gmail.com address: 上海
I used the openresty version 1.13.62, and I installed two openresty machines to do the test work. I followed the same test code in lua-resty-upstream-healthcheck, but the following error occurred, please help to answer, the first time I came into contact with openresty, thanks!
problem:
this is what I wrote in the init by lua block phase:
nginx.conf