-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kong can not find custom_plugins #1817
Comments
can you try |
Sure! admin api: {"enabled_plugins":["syslog","ldap-auth","rate-limiting","correlation-id","jwt","runscope","tcp-log","http-log","hmac-auth","response-transformer","basic-auth","key-auth","request-transformer","acl","oauth2","galileo","udp-log","cors","file-log","ip-restriction","request-size-limiting","ssl","datadog","loggly","statsd","response-ratelimiting","bot-detection"]} Thanks |
anything in the logs? |
so this is your custom plugin;
|
Yes, |
That is all the logs using |
@HenryChelsea do you still see this behavior in 0.10.x releases? |
Closing as stale with no response. Please feel free to re-open if there are still pending questions. Thanks! |
Summary
In branch 'next'(0.9.5), when I added my custom plugins. Kong does not find them. But when I checkouted to branch 'master'(0.9.5), kong works well and find my custom plugins. Could anybody gives me some advice? Thanks.
Steps To Reproduce
Additional Details & Logs
Kong version (
0.9.5(next)
)start verbose logs:
2016/11/11 14:49:17 [verbose] Kong: 0.9.5
2016/11/11 14:49:17 [verbose] reading config file at /etc/kong/kong.conf
2016/11/11 14:49:17 [verbose] prefix in use: /home/token/kong
2016/11/11 14:49:17 [verbose] preparing nginx prefix directory at /home/token/kong
2016/11/11 14:49:17 [verbose] saving serf identifier to /home/token/kong/serf/serf.id
2016/11/11 14:49:17 [verbose] saving serf shell script handler to /home/token/kong/serf/serf_event.sh
2016/11/11 14:49:17 [verbose] SSL enabled, no custom certificate set: using default certificate
2016/11/11 14:49:17 [verbose] default SSL certificate found at /home/token/kong/ssl/kong-default.crt
2016/11/11 14:49:17 [verbose] Admin SSL enabled, no custom certificate set: using default certificate
2016/11/11 14:49:17 [verbose] admin SSL certificate found at /home/token/kong/ssl/admin-kong-default.crt
2016/11/11 14:49:17 [warn] ulimit is currently set to "1024". For better performance set it to at least "4096" using "ulimit -n"
2016/11/11 14:49:17 [verbose] running datastore migrations
2016/11/11 14:49:17 [verbose] migrations up to date
2016/11/11 14:49:17 [verbose] serf agent not running, deleting /home/token/kong/pids/serf.pid
2016/11/11 14:49:17 [verbose] waiting for serf agent to be running
2016/11/11 14:49:18 [verbose] serf agent started
2016/11/11 14:49:18 [verbose] auto-joining serf cluster
2016/11/11 14:49:18 [verbose] no other nodes found in the cluster
2016/11/11 14:49:18 [verbose] registering serf node in datastore
2016/11/11 14:49:18 [verbose] cluster joined and node registered in datastore
2016/11/11 14:49:18 [info] Kong started
Kong configuration (registered APIs/Plugins & configuration file)
custom_plugins = auth-key-check
curl http://localhost:8001/plugins/enabled
{"enabled_plugins":["syslog","ldap-auth","rate-limiting","correlation-id","jwt","runscope","tcp-log","http-log","hmac-auth","response-transformer","basic-auth","key-auth","request-transformer","acl","oauth2","galileo","udp-log","cors","file-log","ip-restriction","request-size-limiting","ssl","datadog","loggly","statsd","response-ratelimiting","bot-detection"]}
centos 7.0
The text was updated successfully, but these errors were encountered: