Hi, somedays ago konga is installed perfect but now returns this error always (swarm and not swarm mode)
ubuntu@pre@:~/misproyectos/entorno-ci-herramientas/src/aws/kong(master)$ docker run -p 1337:1337 --network demo_net -e "DB_ADAPTER=postgres" -e "DB_HOST=postgresdemo" -e "DB_PORT=5432" -e "DB_USER=kong" -e "DB_PASSWORD=kong" -e "DB_DATABASE=kong" --name konga pantsel/konga
Using postgres DB Adapter.
Database exists. Continue...
error: A hook (`orm`) failed to load!
error: error: column r.consrc does not exist
at Connection.parseE (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:539:11)
at Connection.parseMessage (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:366:17)
at Socket.<anonymous> (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:105:22)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at TCP.onread (net.js:601:20)
/app/node_modules/sails-postgresql/lib/adapter.js:158
var collection = connectionObject.collections[table];
^
TypeError: Cannot read property 'collections' of undefined
at __DESCRIBE__ (/app/node_modules/sails-postgresql/lib/adapter.js:158:43)
at after (/app/node_modules/sails-postgresql/lib/adapter.js:1292:7)
at /app/node_modules/sails-postgresql/lib/adapter.js:1181:7
at /app/node_modules/sails-postgresql/node_modules/pg/lib/pool.js:84:11
at dispense (/app/node_modules/sails-postgresql/node_modules/pg/node_modules/generic-pool/lib/generic-pool.js:250:16)
at Object.me.release (/app/node_modules/sails-postgresql/node_modules/pg/node_modules/generic-pool/lib/generic-pool.js:349:5)
at /app/node_modules/sails-postgresql/node_modules/pg/lib/pool.js:88:20
at /app/node_modules/sails-postgresql/lib/adapter.js:1295:9
at Query.callback (/app/node_modules/sails-postgresql/lib/adapter.js:195:26)
at Query.handleError (/app/node_modules/sails-postgresql/node_modules/pg/lib/query.js:106:17)
at Connection.<anonymous> (/app/node_modules/sails-postgresql/node_modules/pg/lib/client.js:171:26)
at emitOne (events.js:116:13)
at Connection.emit (events.js:211:7)
at Socket.<anonymous> (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:109:12)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at TCP.onread (net.js:601:20)
Thanks so much in advance.
Kind regards!!
Xavier.
Hi everybody,
I have added the KONGA_HOOK_TIMEOUT environment variable but not works...;__(
```version: '3.0'
services:
konga:
image: pantsel/konga
networks:
- demo_net
ports:
- 80:1337
environment:
- DB_ADAPTER=postgres
- DB_HOST=postgresdemo
- DB_USER=kong
- DB_PASSWORD=kong
- DB_DATABASE=kong
- NODE_ENV=development
- KONGA_HOOK_TIMEOUT=120000
deploy:
replicas: 1
networks:
demo_net:
external: true
```
Issue solved, the problem was with the version of postgres.
Working with containers with postgres:alpine don't work, with postgres:9.6 konga works perfectly.
Thanks so much!!
Xavier.
i am having this issue with postgres 12 its simply not supported?
Hi,when I have this issue simply is this, with postgres 9.6 works perfect.
Xavier.
El dom., 24 may. 2020 12:11, luka dodelia notifications@github.com
escribió:
i am having this issue with postgres 12 its simply not supported?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/pantsel/konga/issues/462#issuecomment-633208292, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADF4XF2B2OFOXWIJYS7DYYLRTDXDHANCNFSM4I6EVVCA
.
i really need this to work on postgres12 :( @pantsel any idea how i can make it ?
@lukasa1993 , unfortunatelly pg 12 is not supported by the underlying driver. It all comes down to the sails framework used by Konga. An update to the most recent version requires a whole rewrite of the project. On the upside, a second generation of Konga is in the works but it will take some time for it to be publicly available.
If you have no alternatives, I would suggest that you use the build-in filesystem db, provided that you can mount a volume to konga-data folder. I've done it with no problems on production environments.
filesystem-db works in production mode ? and what would be docker mount point for it ?
If I understand you question correctly it would be something in the line of /host/path:/konga-data
so it works in production mode… what is latest version of postgres that it works ?
Yes, it works in production. I think 9.6, the adapter is quite old.
/app/kongadata isn't this path for docker container ? /konga-data is empty…
Yup, sorry.
ty, looking forward new konga hit me up for testing when its ready
Ofcourse, there will also be an announcement on gitter
Could be helpful adding a note regarding Postgres 12+ incompatibility to the docs, thanks for the clarification though.
confirm Postgres 13 also have this error
sudo docker run --rm pantsel/konga:latest -c prepare -a postgres -u postgresql://konga:meowmeowmeow@my_ip:5432/konga
debug: Preparing database...
Using postgres DB Adapter.
Database exists. Continue...
error: A hook (`orm`) failed to load!
error: Failed to prepare database: error: column r.consrc does not exist
at Connection.parseE (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:539:11)
at Connection.parseMessage (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:366:17)
at Socket.<anonymous> (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:105:22)
at Socket.emit (events.js:310:20)
at Socket.EventEmitter.emit (domain.js:482:12)
at addChunk (_stream_readable.js:286:12)
at readableAddChunk (_stream_readable.js:268:9)
at Socket.Readable.push (_stream_readable.js:209:10)
at TCP.onStreamRead (internal/stream_base_commons.js:186:23)
I am facing the same issue when using mongo Atlas. Any idea?
@pantsel - Do we have the latest version of Konga that connects to postgres 12 or later?
@pantsel this issue was happened one years age,why don't you fix it? up you lib ,it may be works
Most helpful comment
Issue solved, the problem was with the version of postgres.
Working with containers with postgres:alpine don't work, with postgres:9.6 konga works perfectly.
Thanks so much!!
Xavier.