socket failed: No such file or directory about go-pdk

[StarlightIbuki]

Could you share the config of Kong for the plugin server?

[wangcong791510428]

the same question

[StarlightIbuki]

The critical message is emitted when Kong tries to test if the plugin server is ready (the socket is accessible) so it's expected. It cannot be silenced due to the limitation of OpenResty. You may try the latest version, which removes the detection logic.

The same question

@wangcong791510428 Are you using the same versions as @Kurosawa?

[wangcong791510428]

docker run --restart=always --network=kong-net -d --name kong --log-opt max-size=50m --log-opt max-file=3 --log-driver json-file
-e "KONG_DATABASE=postgres"
-e "KONG_PG_HOST=kong-database"
-e "KONG_PG_USER=kong"
-e "KONG_PG_DATABASE=kong"
-e "KONG_PG_PASSWORD=****"
-e "KONG_PROXY_ACCESS_LOG=/dev/stdout"
-e "KONG_ADMIN_ACCESS_LOG=/dev/stdout"
-e "KONG_PROXY_ERROR_LOG=/dev/stderr"
-e "KONG_ADMIN_ERROR_LOG=/dev/stderr"
-e "KONG_PLUGINS=bundled,ubm-auth-go"
-e "KONG_PLUGINSERVER_NAMES=ubm-auth-go"
-e "KONG_PLUGINSERVER_UBM_AUTH_GO_START_CMD=/usr/local/bin/ubm-auth-go"
-e "KONG_PLUGINSERVER_UBM_AUTH_GO_QUERY_CMD=/usr/local/bin/ubm-auth-go -dump"
-e "KONG_PLUGINSERVER_UBM_AUTH_GO_SOCK=/usr/local/kong/ubm-auth-go.sock"
-e "KONG_ADMIN_LISTEN=0.0.0.0:8002, 0.0.0.0:8444 ssl"
-v "/data/bigmodel/kong/make-image/kong-ratelimit-go/ubm-auth-go:/usr/local/bin/ubm-auth-go"
-p 8000:8000
-p 5001:8443
-p 8002:8002
-p 8444:8444 kong:3.4

the complete docker commond but i use kong:2.7 work ok

[wangcong791510428]

when i use kong:3.4 the result the same question kurosawa93

[StarlightIbuki]

@wangcong791510428 Could you confirm if that socket file exists?
The auto-generated socket should be named with postfix ".socket":

go-pdk/server/os.go

Line 44 in 231514d

pth = path.Join(*kongPrefix, name+".socket")

[alt-dima]

We have same issue with custom go-plugin

│ 2024/02/04 12:23:24 [crit] 1262#0: *302 connect() to unix:/usr/local/kong/okta-token-verifier-multi-auth.socket failed (2: No such file or directory), context: ngx.timer                                                                       │
│ 2024/02/04 12:23:25 [notice] 1262#0: *157 [lua] warmup.lua:70: finished warming up DNS entries' into the cache (in 897ms), context: ngx.timer                                                                                                   │
│ 2024/02/04 13:16:40 [warn] 1262#0: *5114 [kong] mp_rpc.lua:157 [okta-token-verifier-multi-auth] [OTV-GO-PLUGIN] 

checked file

kong-app-v2-5f947879dc-mkjwb:/usr/local/opt/lua-plugins$ cd /usr/local/kong/
kong-app-v2-5f947879dc-mkjwb:/usr/local/kong$ ls -la | grep okta
srwxr-xr-x    1 kong     nogroup          0 Feb  4 12:23 okta-token-verifier-multi-auth.socket

Seems kong checks, tries to connect to socket before plugin started

[StarlightIbuki]

We have same issue with custom go-plugin

│ 2024/02/04 12:23:24 [crit] 1262#0: *302 connect() to unix:/usr/local/kong/okta-token-verifier-multi-auth.socket failed (2: No such file or directory), context: ngx.timer                                                                       │
│ 2024/02/04 12:23:25 [notice] 1262#0: *157 [lua] warmup.lua:70: finished warming up DNS entries' into the cache (in 897ms), context: ngx.timer                                                                                                   │
│ 2024/02/04 13:16:40 [warn] 1262#0: *5114 [kong] mp_rpc.lua:157 [okta-token-verifier-multi-auth] [OTV-GO-PLUGIN] 

checked file

kong-app-v2-5f947879dc-mkjwb:/usr/local/opt/lua-plugins$ cd /usr/local/kong/
kong-app-v2-5f947879dc-mkjwb:/usr/local/kong$ ls -la | grep okta
srwxr-xr-x    1 kong     nogroup          0 Feb  4 12:23 okta-token-verifier-multi-auth.socket

Seems kong checks, tries to connect to socket before plugin started

It's expected for Kong to print error messages when starting plugin servers. As soon as the plugin server is started it should work.

[gszr]

As explained by @StarlightIbuki, notice that the errors stop after the plugin with its server is started. Closing this issue for now; if you encounter issues in more recent Kong versions, please open a new ticket, with logs, reproduction steps, Kong version, and configuration