Closed jeremyjpj0916 closed 5 months ago
I notice there is a line:
listen 0.0.0.0:9443 ssl http2 deferred reuseport backlog=16384;
Since Nginx 1.25.1, the "http2" parameter of the "listen" directive is deprecated.
The message "failed to instantiate 'kong.worker_events' module" is reported by lua-resty-events library, Which needs a unix socket to run. We must define a server block like:
server {
charset UTF-8;
server_name kong_worker_events;
listen unix:${{PREFIX}}/worker_events.sock;
access_log off;
location / {
content_by_lua_block {
require("resty.events.compat").run()
}
}
}
Please refer to kong/templates/nginx_kong.lua
and nginx_kong_stream.lua
then edit our own template.
Ooooo @chronolaw ^ that is definitely the issue! My template lacks that it seems. As Kong grows the custom nginx template just keeps getting so big :/ . Wish there was a more elegant way to achieve running base kong + a kong runtime thats mtls geared with modsecurity like I do.
Testing out adding that new server block and I bet that closes and fixes this issue. Thanks bud!
lua-resty-events is a new library in kong gateway 3.x, this blog post may be helpful: https://konghq.com/blog/engineering/nginx-openresty-event-handling-strategy-for-cpu-efficiency
Yep, confirmed it fixed all my woes! Appreciate the quick support!
Is there an existing issue for this?
Kong version (
$ kong version
)3.7.0
Current Behavior
Upon startup some relevant logs likely causing me some runtime issues.
Expected Behavior
No critical errors with Kong's startup logs. Looking for ideas from Kong core devs as to what could cause this bit possibly:
Steps To Reproduce
Here is a custom nginx template that has all the latest updates for how I use Kong, really would like to get away from having to use this but its needed because of a separate kong runtime listening port for 9443 to do mtls verification against a custom CA chain vs the standard Kong server block plus waf execution. This always worked in the past for us on 2.8.x running two kong blocks:
Anything else?
No response