-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Peertube fails to start on query error #6599
Comments
Please drop and re-create your database, then start peertube and paste the logs output |
I already tried that with the same result; |
Please paste the entiere application output |
|
Please see this as it might work for you too. |
Thanks, mine is a brand new installation, Shail I try it as well? |
Are you on 6.2.1 or 6.3.0 with the brand new installation? |
6.2.1 |
@patit72 Logs you pasted is not the first start of PeerTube on a fresh database. Can you retry to delete and recreate your database and run PeerTube? |
@patit72 I also had that error but with 6.3.0. Next time I tried again it was gone. That time I used 6.3.1 and there also was an update for nodejs so it might be that one of those did fix the problem (I guess it was not the update of Peertube because of what I read in the release notes). |
It happened to me today when running develop branch on a pure new docker container (without any previous data). I removed the container and started again, then it worked. |
Closing this issue without @patit72 answer to #6599 (comment) Don't hesitate to comment even if the issue is closed, we can reopen it :) @cintek & @kontrollanten In most cases, this problem occurs because the database was not created correctly the first time PeerTube was started. Subsequent starts will cause PeerTube to crash. It's the reason why pasting the first output start is important. If you notice interesting things in your logs, please create a dedicated issue so we can fix it |
Describe the problem
when I run NODE_ENV=production NODE_CONFIG_DIR=/var/www/peertube/config node dist/server manually server fails to start with error
error: Cannot start application. { "err": { "stack": "Error\n at Query.run (/var/www/peertube/versions/peertube-v6.2.1/node_modules/sequelize/lib/dialects/postgres/query.js:50:25)\n at /var/www/peertube/versions/peertube-v6.2.1/node_modules/sequelize/lib/sequelize.js:315:28\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async migrate (file:///var/www/peertube/versions/peertube-v6.2.1/dist/core/initializers/migrator.js:23:9)", "message": "null value in column \"nodeVersion\" of relation \"application\" violates not-null constraint", "name": "SequelizeDatabaseError", "parent": { "stack": "error: null value in column \"nodeVersion\" of relation \"application\" violates not-null constraint\n at Parser.parseErrorMessage (/var/www/peertube/versions/peertube-v6.2.1/node_modules/pg-protocol/dist/parser.js:283:98)\n at Parser.handlePacket (/var/www/peertube/versions/peertube-v6.2.1/node_modules/pg-protocol/dist/parser.js:122:29)\n at Parser.parse (/var/www/peertube/versions/peertube-v6.2.1/node_modules/pg-protocol/dist/parser.js:35:38)\n at Socket.<anonymous> (/var/www/peertube/versions/peertube-v6.2.1/node_modules/pg-protocol/dist/index.js:11:42)\n at Socket.emit (node:events:520:28)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)\n at Readable.push (node:internal/streams/readable:390:5)\n at TCP.onStreamRead (node:internal/stream_base_commons:191:23)", "message": "null value in column \"nodeVersion\" of relation \"application\" violates not-null constraint", "length": 236, "name": "error", "severity": "ERROR", "code": "23502", "detail": "Failing row contains (510, 0, null, null, null).", "schema": "public", "table": "application", "column": "nodeVersion", "file": "execMain.c", "line": "1883", "routine": "ExecConstraints", "sql": "INSERT INTO \"application\" (\"migrationVersion\") VALUES (0)" }, "sql": "INSERT INTO \"application\" (\"migrationVersion\") VALUES (0)", "parameters": {} } }
Additional information
The text was updated successfully, but these errors were encountered: