Missing plugin socket

[esatterwhite]

I'm not sure if this is the right place, But recently after updating to kong 3.2.2, I started seeing ciritical errors at start up

2023/05/18 15:33:19 [notice] 1206#0: *148 [kong] process.lua:252 Starting js, context: ngx.timer
2023/05/18 15:33:19 [crit] 1206#0: *149 connect() to unix:/usr/local/kong/js_pluginserver.sock failed (2: No such file or directory), context: ngx.timer
2023/05/18 15:33:19 [crit] 1206#0: *149 connect() to unix:/usr/local/kong/js_pluginserver.sock failed (2: No such file or directory), context: ngx.timer
2023/05/18 15:33:19 [crit] 1206#0: *149 connect() to unix:/usr/local/kong/js_pluginserver.sock failed (2: No such file or directory), context: ngx.timer
2023/05/18 15:33:19 [crit] 1206#0: *149 connect() to unix:/usr/local/kong/js_pluginserver.sock failed (2: No such file or directory), context: ngx.timer
2023/05/18 15:33:19 [crit] 1206#0: *149 connect() to unix:/usr/local/kong/js_pluginserver.sock failed (2: No such file or directory), context: ngx.timer
2023/05/18 15:33:19 [crit] 1206#0: *149 connect() to unix:/usr/local/kong/js_pluginserver.sock failed (2: No such file or directory), context: ngx.timer
2023/05/18 15:33:19 [crit] 1206#0: *149 connect() to unix:/usr/local/kong/js_pluginserver.sock failed (2: No such file or directory), context: ngx.timer

2023/05/18 15:33:28 [warn] 1206#0: *160 [kong] plugins.lua:125 /plugins/schema/:name endpoint is deprecated, please use /schemas/plugins/:name instead (deprecated after 1.2.0, scheduled for removal in 3.0.0), client: 127.0.0.1, server: kong_admin, request: "GET /plugins/schema/prometheus HTTP/1.1", host: "127.0.0.1:8444"

Things seem to have a real hard time connecting to kong when this happens.

Here are the env vars used to set this up

KONG_PLUGINSERVER_JS_QUERY_CMD=node /usr/local/bin/kong-js-pluginserver --plugins-directory /opt/plugins/js --dump-all-plugins
KONG_PLUGINSERVER_JS_SOCKET=/usr/local/kong/js_pluginserver.sock
KONG_PLUGINSERVER_JS_START_CMD=node /usr/local/bin/kong-js-pluginserver --plugins-directory /opt/plugins/js
KONG_PLUGINSERVER_NAMES=js

[esatterwhite]

I in fact had to patch the deployment in production to disable this plugin server because it looked like we were loosing connections

After I patched it and the error stop things normalized

[StarlightIbuki]

Hi. Have you checked if the plugin functions normally? I believe this is an expected behavior.

We introduced a check to prevent requests before the plugin server is ready. Due to the implementation limit, we have to check by trying to connect to the socket, which generates error messages and we cannot mute it.

We're considering removing this check logic as it does not really help when a plugin server is slow.

Reference:
Kong/kong#9507
openresty/lua-nginx-module#2138