misskey@2025.4.0 start (failed)

[spirillen]

💡 Summary

Apr 13 01:38:35 ns3109441 "matrix.rocks"[791294]: > misskey@2025.4.0 start
Apr 13 01:38:35 ns3109441 "matrix.rocks"[791294]: > pnpm check:connect && cd packages/backend && node ./built/boot/entry.js
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791306]: > misskey@2025.4.0 check:connect /home/misskey/misskey
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791306]: > cd packages/backend && pnpm check:connect
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791323]: > backend@ check:connect /home/misskey/misskey/packages/backend
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791323]: > node ./scripts/check_connect.js
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]: node:internal/modules/esm/resolve:283
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     throw new ERR_MODULE_NOT_FOUND(
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:           ^
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/misskey/misskey/packages/backend/built/config.js' imported from /home/misskey/misskey/packages/backend/scripts/check_connect.js
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     at finalizeResolution (node:internal/modules/esm/resolve:283:11)
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     at moduleResolve (node:internal/modules/esm/resolve:952:10)
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     at defaultResolve (node:internal/modules/esm/resolve:1188:11)
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25)
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38)
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38)
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:     at ModuleJob._link (node:internal/modules/esm/module_job:130:49) {
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:   code: 'ERR_MODULE_NOT_FOUND',
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]:   url: 'file:///home/misskey/misskey/packages/backend/built/config.js'
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]: }
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791339]: Node.js v20.19.0
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791323]:  ELIFECYCLE  Command failed with exit code 1.
Apr 13 01:38:36 ns3109441 "matrix.rocks"[791306]:  ELIFECYCLE  Command failed with exit code 1.
Apr 13 01:38:36 ns3109441 systemd[1]: matrix.rocks.service: Main process exited, code=exited, status=1/FAILURE
Apr 13 01:38:36 ns3109441 systemd[1]: matrix.rocks.service: Failed with result 'exit-code'.
Apr 13 01:38:36 ns3109441 systemd[1]: matrix.rocks.service: Consumed 1.113s CPU time.
Apr 13 01:38:37 ns3109441 systemd[1]: matrix.rocks.service: Scheduled restart job, restart counter is at 5.
Apr 13 01:38:37 ns3109441 systemd[1]: Stopped Misskey daemon.
Apr 13 01:38:37 ns3109441 systemd[1]: matrix.rocks.service: Consumed 1.113s CPU time.
Apr 13 01:38:37 ns3109441 systemd[1]: matrix.rocks.service: Start request repeated too quickly.
Apr 13 01:38:37 ns3109441 systemd[1]: matrix.rocks.service: Failed with result 'exit-code'.
Apr 13 01:38:37 ns3109441 systemd[1]: Failed to start Misskey daemon.

ll /home/misskey/misskey/packages/backend/built/config.js
ls: cannot access '/home/misskey/misskey/packages/backend/built/config.js': No such file or directory
:~# ll /home/misskey/misskey/packages/backend/built/
ls: cannot access '/home/misskey/misskey/packages/backend/built/': No such file or directory
:~# ll /home/misskey/misskey/packages/backend/

🥰 Expected Behavior

I wonder... a running misskey maybe..

🤬 Actual Behavior

📝 Steps to Reproduce

1. run update script (bash)

💻 Frontend Environment

* Model and OS of the device(s): ubuntu 20.04
* Browser: Firefox EXR
* Server URL: https://matrix.rocks/
* Misskey:2025.4.0

🛰 Backend Environment (for server admin)

* Installation Method or Hosting Service: Misskey install shell script
* Misskey: 2025.4.0
* Node: v20.19.0
* PostgreSQL: 15
* Redis: 7
* OS and Architecture: ubuntu 20.04

Do you want to address this bug yourself?

• Yes, I will patch the bug myself and send a pull request

[anatawa12]

ll /home/misskey/misskey/packages/backend/built/
ls: cannot access '/home/misskey/misskey/packages/backend/built/': No such file or directory

it might failed to build during installation process.
Could you show us the log when you ran install script to upgrade misskey to 2025.4.0?

[darekasann]

You should use Node v22.x.x , not v20.19.0 .

Since Misskey 2024.11.0, Node v20 is obsolete and v22 is reccomended.

[spirillen]

Super... have kept it back for so long because of misskey... Will upgrade straight away....

another Q, do you know about a way or script/command to move all existing contents from ./files/ to newly attached S3 bucket?

[darekasann]

I don’t know of any tool or script for that, but I can imagine what you are planning to do.

If you move your files to S3, you will also need rewrite the URIs directly in the database.
That will work on your local-timeline, but there is no way to reflect those changes to other servers.

[spirillen]

Hi @darekasann,

Thanks so much for getting back to me!

I wanted to mention that it seems like a bit of a limitation in Misskey that we can't reflect those changes to other servers. I've managed to do this on my PeerTube instance at https://tube.matrix.rocks/, and those changes are picked up by the network, including Misskey in most cases.

Do you think there might be any plans to change this in the future? Also, will there be a feature for editing messages (just editing, not deleting) coming to Misskey?

Cheers!