Closed hwyzleo closed 2 years ago
Could you run the runner with -m dev
and see if it has received the RPC from the APISIX during the request?
Could you run the runner with
-m dev
and see if it has received the RPC from the APISIX during the request?
do you mean use running mode with that argument like this? cmd: ["/path/to/apisix-go-plugin-runner/go-runner", "run", "-m", "dev"] or use debugging mode? in order to confirm the issue, i used debugging mode locally with apisix docker and go-runner through /tmp/runner.sock file, after set the route and plugin, i found nothing in apisix log or go-runner log like 'register plugin say', and the plugin still did not trigger.
Could you run the runner with
-m dev
and see if it has received the RPC from the APISIX during the request?
by the go-runner log, i thought the handleConn function is not be called, but i didn't find any error in apisix log during the request, how to troubleshoot?
Any interesting log in the APISIX? You can add more logs to this function: https://github.com/apache/apisix/blob/b8daf65b3c0690138feccb2ce399fc58349ac7ee/apisix/plugins/ext-plugin/init.lua#L435.
My fault, because I set the route and plug-in through the apisix dashboard before, it did not have any error response after i set, so I did not think that the plugin did not take effect. Yesterday I tried to use REST API to set up, the console directly told me that ext-plugin-pre-req plugin did not work, I found the key reason. Please close the current issue.
I have got the go-runner and put it in the apisix container. when i restart the apisix, i can see the log in console like register plugin fault-injection register plugin limit-req register plugin say register plugin sign-verify (mine) and i try to set the route with mine plugin like
when i visit the route, upstream can response, but plugin sign-verify and say do not trigger. how it happen?