Closed xpoveda closed 5 years ago
Hi everybody,
I have added the KONGA_HOOK_TIMEOUT environment variable but not works...;__(
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
I tried on Postgresql 9.6 -> link and .env file
PORT=1337
NODE_ENV=production
KONGA_HOOK_TIMEOUT=120000
DB_ADAPTER=postgres
DB_URI=postgresql://dbuser:dbpassword@localhost:5432/kongadb
DB_USER=dbuser
DB_PORT=5432
DB_DATABASE=kongadb
DB_PASSWORD=dbpassword
KONGA_LOG_LEVEL=warn
TOKEN_SECRET=your-token
https://github.com/balderdashy/sails/issues/6957 issue is with sailsjs and the solution to @pantsel are here: https://github.com/balderdashy/sails/issues/6957#issuecomment-591954307
For those that they have the possibility to use MySQL, I've tested with the latest"current" version 8.0.29 and it works fine.
@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.
@pantsel, any update of supporting the latest postgres or any plan in the near future?
:eyes:
I am facing the same issue when using mongo Atlas. Any idea?
Same here :/
Hi,
R u using normal connection string or mongo srv connection string?
Thanks, Sudhanshu Dev
On Thu, Dec 1, 2022 at 5:07 AM Salão Na Mão Engenharia < @.***> wrote:
I am facing the same issue when using mongo Atlas. Any idea?
Same here :/
— Reply to this email directly, view it on GitHub https://github.com/pantsel/konga/issues/462#issuecomment-1332892563, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPO62RLPVCRKWOPHX25HKLWK7QJZANCNFSM4I6EVVCA . You are receiving this because you commented.Message ID: @.***>
Hi,
take a look on this https://github.com/pantsel/konga/issues/487.
I describe a solution for postgres 14.
Regards.
Hi, somedays ago konga is installed perfect but now returns this error always (swarm and not swarm mode)
Thanks so much in advance.
Kind regards!!
Xavier.