Comments (10)
@samugi, I think he is hitting this:
https://github.com/Kong/lua-resty-openssl/blob/master/lib/resty/openssl/auxiliary/nginx.lua#L43-L90
from kong.
Hello @LukeMccon ,
thank you for reporting this.
I was unable to reproduce the problem you described, here's what I tried:
- configured postgres to use ssl, setting the
ssl = on
,ssl_cert_file
andssl_key_file
configuration options - ran
kong migrations bootstrap
usingKONG_ROLE=control_plane
fromkong:3.5-ubuntu
with appropriate pg_ssl and lua_ssl configuration as described in our docs - ran
kong migrations --v up
usingKONG_ROLE=control_plane
fromkong:3.6-ubuntu
(migrations completed successfully) - started
kong:3.6-ubuntu
successfully
Could you share additional details to help us reproduce the problem, i.e. if you have any scripts, docker-compose, etc. that would be very helpful. Thank you!
from kong.
Hi @LukeMccon could you share your kong.conf content, the postgres server version (is it higher than 11 and using scram auth?) and if there's any custom plugin that you are using?
And if possible, also the full stack trace for the error you mentioned.
from kong.
Same issue here. We have this problem in the waiting-for-db container.
Installed with helm chart without including any custom plugin.
│ Error: │
│ resty.openssl.auxiliary.nginx doesn't support Nginx version 1025003 │
│ stack traceback: │
│ [C]: in function 'error' │
│ /usr/local/share/lua/5.1/resty/openssl/auxiliary/nginx.lua:89: in main chunk │
│ [C]: in function 'require' │
│ /usr/local/share/lua/5.1/resty/openssl/ssl.lua:8: in main chunk │
│ [C]: in function 'require' │
│ /usr/local/share/lua/5.1/pgmoon/init.lua:397: in function 'auth' │
│ /usr/local/share/lua/5.1/pgmoon/init.lua:268: in function 'connect' │
│ .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:215: in function 'connect' │
│ .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:546: in function 'query' │
│ .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:296: in function 'init' │
│ /usr/local/share/lua/5.1/kong/db/init.lua:144: in function 'init_connector' │
│ /usr/local/share/lua/5.1/kong/cmd/start.lua:68: in function 'cmd_exec' │
│ /usr/local/share/lua/5.1/kong/cmd/init.lua:31: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:31> │
│ [C]: in function 'xpcall' │
│ /usr/local/share/lua/5.1/kong/cmd/init.lua:31: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:15> │
│ (command line -e):7: in function 'inline_gen' │
│ init_worker_by_lua(nginx.conf:204):44: in function <init_worker_by_lua(nginx.conf:204):43> │
│ [C]: in function 'xpcall' │
│ init_worker_by_lua(nginx.conf:204):52: in function <init_worker_by_lua(nginx.conf:204):50> ```
from kong.
I got the same issue when upgrade from Kong OSS 3.5.0 to 3.6.0 when run migration db process
kong migrations up --vv
Error: resty.openssl.auxiliary.nginx doesn't support Nginx version 1025003 stack traceback: [C]: in function 'error' /usr/local/share/lua/5.1/resty/openssl/auxiliary/nginx.lua:89: in main chunk [C]: in function 'require' /usr/local/share/lua/5.1/resty/openssl/ssl.lua:8: in main chunk [C]: in function 'require' /usr/local/share/lua/5.1/pgmoon/init.lua:397: in function 'auth' /usr/local/share/lua/5.1/pgmoon/init.lua:268: in function 'connect' .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:215: in function 'connect' .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:546: in function 'query' .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:296: in function 'init' /usr/local/share/lua/5.1/kong/db/init.lua:144: in function 'init_connector' /usr/local/share/lua/5.1/kong/cmd/migrations.lua:101: in function 'cmd_exec' /usr/local/share/lua/5.1/kong/cmd/init.lua:31: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:31> [C]: in function 'xpcall' /usr/local/share/lua/5.1/kong/cmd/init.lua:31: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:15> (command line -e):7: in function 'inline_gen' init_worker_by_lua(nginx.conf:132):44: in function <init_worker_by_lua(nginx.conf:132):43> [C]: in function 'xpcall' init_worker_by_lua(nginx.conf:132):52: in function <init_worker_by_lua(nginx.conf:132):50>
from kong.
Hi @LukeMccon , I think that we have fixed this issue in #12665, could you try it again? thanks.
from kong.
This issue is marked as stale because it has been open for 14 days with no activity.
from kong.
Dear contributor,
We are automatically closing this issue because it has not seen any activity for three weeks.
We're sorry that your issue could not be resolved. If any new information comes up that could
help resolving it, please feel free to reopen it.
Your contribution is greatly appreciated!
Please have a look
our pledge to the community
for more information.
Sincerely,
Your Kong Gateway team
from kong.
@LukeMccon This issue has been fixed in #12905 and will be released in the next version.
from kong.
Thank you @Water-Melon @chronolaw and team, confirmed that this issue is fixed in OSS 3.6.1
from kong.
Related Issues (20)
- Admissionwebhook misses faulty regex HOT 1
- Exceptions while trying to store secrets using environment variables option HOT 8
- kong lua-resty-lock lock timeout 500 error {"message":"An unexpected error occurred"} HOT 2
- custom proxy_access_log still not working in 3.4.* HOT 3
- Kong prometheus plugin does not record 404 response codes from proxy HOT 2
- Timeout when running migrations from 3.5 to 3.6 leading to corrupted data (migration ran twice) HOT 3
- Admin API address in "New Connnection" form only support IP, not DNS. HOT 2
- Upsert target is not an upsert HOT 4
- failed to set X-Kong-Upstream-Status header while sending to client HOT 2
- [PostgreSQL error] failed to retrieve PostgreSQL server_version_num: connection refused HOT 2
- DNS resolution failed: dns server error: 3 name error HOT 14
- Optional capture groups are broken with the request-transformer plugin and traditional_compatible router HOT 4
- Error in logs: failed to run timer HOT 2
- Database migration failed while using helm chart HOT 2
- JWT Plugin bypasses validation process occasionally on frequent requests HOT 3
- TLS SNI Route not work HOT 6
- Kong info, notice, inspect logs are all getting logged as error in GCP(google cloud platform) HOT 1
- Cannot use kong.db
- http-log plugin: Host header not including port
- Every time request localhost:8001/metrics, kong-cp-kong-pod will prompt a license-related error
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kong.