-
Notifications
You must be signed in to change notification settings - Fork 21
go plugins are not called occasionally #21
Comments
I have seen this also, and I was able to reproduce. AFAIK problem seems related to networks names resolution problem (DNS misconfiguration) leading to go plugin not being called. |
my go-hello plugin was added without saying anything,how can I resolve it.thanks |
You may have a look at kong error.log, and change log level if needed (in that case restart kong). |
I have changed log level to debug.the log display go-hello is loaded.and go-pluginserver is started.no any errors. I have used 'go build -buildmode=plugin go-hello.go' to compiled plugin on centos7.and added it to kong. kong config set like this: plugins = bundled,go-hello the error.log like this: 2020/04/16 16:02:20 [debug] 21460#0: [lua] globalpatches.lua:10: installing the globalpatches |
and I use go-hello plugin like this: curl -i -X POST --url http://127.0.0.1:8001/services/ --data 'name=test-service' --data 'url=http://www.baidu.com' |
Good to know that the plugin is successfullly loaded. Could you try to install it globally ? |
hello,I install it as globally plugin,but it also can't work.my server have two ip address.the public address is 47.108.92.129,the private is 172.24.130.247.do I need some setup at dns in kong.conf? |
I think that this pr: Kong/kong#5586 and this Kong/kong#5597 fix indirectly this issue... |
Thanks for linking the issues, @ealogar! Both PRs are merged by now, so closing this. |
I already reported this at kong main repo:
Kong/kong#5586
But I think that the problem is at pluginserver side as the plugin iterator are being executed (i have added myself a trace on function Kong.access() in init.lua and I can say that the go plugin is being returned (as first) but afterwards the Access method is not called.
No errors appear it's just that the kong event is being lost and without saying anything.
This issue makes gopluginserver unusable for production
Can you have a look at it?
The text was updated successfully, but these errors were encountered: