Yichun Zhang

@frozenminds You don't have to remove `ngx_ssi` from your nginx build. You just need to avoid mixing `ngx_ssi`'s configurations with `ngx_lua`'s in the same main request. What do you have...

@frozenminds Thank you for the info! I have several suggestions for you: 1. Please try creating a _minimal_ but still _complete_ example that can reproduce the issue. It'll be trivial...

@frozenminds No, I don't mind. Please send me details privately to my email address, agentzh at gmail dot com :)

@KunkkaCoco The NGINX SSI module is complicated and error prone. Better use ngx_lua to do the content templating instead. For example, with Lemplate: https://github.com/openresty/lemplate

@sayap You're welcome to submit patches to this module :) But I'd suggest you take a look at the `lua-resty-mysql` library instead which does what you want: https://github.com/openresty/lua-resty-mysql#readme

@RyouZhang Please, no Chinese here. This place is considered English only. If you really want to use Chinese, please join the openresty (Chinese) mailing list instead. Please see https://openresty.org/#Community for...

@RyouZhang Then your `set_keepalive` method call may always return a failure. Have you checked its return values?

@RyouZhang You can get the string describing the error in the second return value (when the first one is nil). Let's stop guessing :)

@RyouZhang Okay, so your redis connection is already closed right before calling `set_keepalive` (like due to an earlier explicit `close` call or some previous method calls triggering a fatal error,...

@RyouZhang Maybe you are just using a too small value for your timeout threshold of the redis connections?