Closed liquidsanek closed 2 years ago
The problem with errors during the build process is known and getting rid of all the errors is currently the 1st roadmap entry. Misskey should still run despite these build errors.
The query you posted does not strike me as anything out of the ordinary, or even anything that should take a long time to complete. I assume there is no further output after that? Maybe you can check if the PostgreSQL server logs have any more information.
even anything that should take a long time to complete.
I've left it going for at least 20 minutes, and as you said, seeing the query, it really shouldn't take that long, which is why it seems odd to me.
I assume there is no further output after that?
Nothing. It just gets stuck on this query and all I can do is either wait indefinitely or interrupt the migration process.
Maybe you can check if the PostgreSQL server logs have any more information.
I checked and nothing related to said migration queries are showing up, only Misskey failing to do certain queries since the migration scripts are not fully executed yet, which was before I stopped Misskey's process. I can't find any relevant log about this issue.
ใใใงๆญขใพใฃใฆใใใฟใใใงใใญใ https://github.com/misskey-dev/misskey/blob/a29ff7b1fa45e01bc7c097e8d770a4c4eedf2a8f/packages/backend/migration/1644010796173-convert-hard-mutes.js#L56-L62
ใกใใใจ่ชฟในใฆใใชใใฎใงใใ 12.98.0 ใใ 12.110.1 ใพใงไธๆฐใซ migrate ใใใจใใใใญใใฏใใฆ UPDATE ใงใใฆใใชใใใใชๆฐใใใพใใ
ไธๆฆ 12.105.0 ใซใขใใใใผใใใฆใใ 12.110.1 ใซใขใใใใผใใใใฐๆๅใใใใงใใ
12.105.0 ใฏใใซใใซๅคฑๆใใใฎใงใใกใงใใใ
12.110.1 ใฎใพใพใงใใใฉใณใถใฏใทใงใณใ็กๅนใซใใใใจใง migrate ใงใใพใใใ
yarn migrate
ใฎไปฃใใใซไธใฎใณใใณใใๅฎ่กใใพใใ
cd packages/backend
npx typeorm migration:run -d ormconfig.js -t false
cd ../..
ไธๅฟใใผใฟใใผในใฎใใใฏใขใใใๅใฃใฆใใๅฎ่กใใๆนใ่ฏใใใใ
It worked! The instance started successfully, and no errors are appearing in the logs. Thanks for the help @xianonn ! :)
Closing the issue since it's solved now
It worked! The instance started successfully, and no errors are appearing in the logs. Thanks for the help @xianonn ! :)
Closing the issue since it's solved now
๐ก Summary
Hello, as I tried to update my instance from version 12.98.0 to the latest version (12.110.1), the migration scripts hang constantly on the same query.
๐ฅฐ Expected Behavior
The project is built correctly, and the migration scripts are all executed.
๐คฌ Actual Behavior
There are errors during the build process:
I could post the full build logs if needed, I haven't yet because of how lengthy it is.
And the command
yarn migrate
hangs on the query:๐ Steps to Reproduce
๐ Environment
Misskey version: Update from 12.98.0 to 12.110.1 Your OS: Debian 10 Your browser: / NodeJS's version: Tried with 16.8, then 16.15 and finally 18.x after being told to update Node
Thanks!