Skip to content

Misskey 2023.10.2 is running abnormally #12104

Closed
Closed
Misskey 2023.10.2 is running abnormally#12104
Labels
⚠️bug?This might be a bug

Description

@MomentQYC
MomentQYC
opened on Oct 21, 2023

💡 Summary

Numerous errors were reported and the timeline was not working

🥰 Expected Behavior

Normal use after upgrade

🤬 Actual Behavior

A large number of errors are reported, examples of which are as follows

misskey-web-1  | WARN 1 [queue inbox]   failed(UnrecoverableError: skip: failed to resolve user) id=797327 attempts=1/8 age=8ms activity=https://(Post)
misskey-web-1  | WARN 2 [queue inbox]   failed(UnrecoverableError: skip: failed to resolve user) id=797328 attempts=1/8 age=7ms activity=https://(Post)
misskey-web-1  | WARN 1 [queue inbox]   failed(UnrecoverableError: skip: failed to resolve user) id=797329 attempts=1/8 age=7ms activity=https://(Post)
misskey-web-1  | INFO 2 [queue check-expired-mutings]   Checking expired mutings...
misskey-web-1  | WARN 2 [queue system]  failed(QueryFailedError: column muting.createdAt does not exist) id=repeat:e456d804f4cee04d9f14f9d6867a8dcf:1697883900000
misskey-web-1  | WARN 1 [queue inbox]   failed(QueryFailedError: column MiUser.createdAt does not exist) id=797146 attempts=3/8 age=4m activity=https://(Post)

📝 Steps to Reproduce

  1. docker compose up -d --build
  2. Not working properly

📌 Environment

💻 Frontend

  • Model and OS of the device(s):
  • Browser:
  • Server URL:
  • Misskey:
    13.x.x

🛰 Backend (for server admin)

  • Installation Method or Hosting Service:
  • Misskey: 2023.10.2
  • Node: 20.8.1
  • PostgreSQL: 16
  • Redis: 7.0.11
  • OS and Architecture: Ubuntu 22.04.3 amd64

Activity

  1. MomentQYC
    added
    ⚠️bug?This might be a bug
    on Oct 21, 2023

  2. MomentQYC commented on Oct 21, 2023

    @MomentQYC
    MomentQYC
    on Oct 21, 2023
    ContributorAuthor

    Accessing /queue gives the following error

    {"error":"Internal server error","message":"column MiUser.createdAt does not exist","details":"QueryFailedError: column MiUser.createdAt does not exist\n
    at PostgresQueryRunner.query (/misskey/node_modules/.pnpm/typeorm@0.3.17_ioredis@5.3.2_pg@8.11.3/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:211:19)\n
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n
    at async SelectQueryBuilder.loadRawResults (/misskey/node_modules/.pnpm/typeorm@0.3.17_ioredis@5.3.2_pg@8.11.3/node_modules/typeorm/query-builder/SelectQueryBuilder.js:2183:25)\n
    at async SelectQueryBuilder.executeEntitiesAndRawResults (/misskey/node_modules/.pnpm/typeorm@0.3.17_ioredis@5.3.2_pg@8.11.3/node_modules/typeorm/query-builder/SelectQueryBuilder.js:2034:26)\n
    at async SelectQueryBuilder.getRawAndEntities (/misskey/node_modules/.pnpm/typeorm@0.3.17_ioredis@5.3.2_pg@8.11.3/node_modules/typeorm/query-builder/SelectQueryBuilder.js:684:29)\n
    at async SelectQueryBuilder.getOne (/misskey/node_modules/.pnpm/typeorm@0.3.17_ioredis@5.3.2_pg@8.11.3/node_modules/typeorm/query-builder/SelectQueryBuilder.js:711:25)\n
    at async Object.<anonymous> (file:///misskey/packages/backend/built/server/web/ClientServerService.js:200:30)"}

  3. Candinya commented on Oct 21, 2023

    @Candinya
    Candinya
    on Oct 21, 2023 · Hidden as outdated

  4. MomentQYC commented on Oct 21, 2023

    @MomentQYC
    MomentQYC
    on Oct 21, 2023
    ContributorAuthor

    This problem was solved by running npm start manually for me, so if you're using Docker as well, check out my solution to this problem.

  5. Candinya commented on Oct 22, 2023

    @Candinya
    Candinya
    on Oct 22, 2023
    Contributor

    Not reproduced on NyaOne (running on Docker), might be an occasional error?

  6. sasagar commented on Nov 11, 2023

    @sasagar
    sasagar
    on Nov 11, 2023
    Contributor

    I'm facing this issue now, updating from 2023.9.3 to 2023.11.0.

  7. hikalium commented on Dec 24, 2023

    @hikalium
    hikalium
    on Dec 24, 2023
    Sponsor

    Here is another instance affected by this issue 🙌 (In my case, it happened when updating misskey from 2023.9.0 to 2023.12.0)

    And I think I found a workaround 😉 - TL; DR

    # cd /path/to/misskey
rm -rf packages/backend/built
sudo docker-compose stop
sudo docker-compose rm
sudo docker-compose build --no-cache --force-rm
sudo docker-compose run --rm web pnpm run init
sudo docker-compose up -d

    It looks like the issue happens when the backend server is not built from the updated source since there are cached artifacts in packages/backend/built (I think this cache is generated when I tried building the Misskey server without Docker before switching to the Docker-based workflow). So removing them and rebuilding the container images cleanly with docker-compose fixes the problem.

    Although I'm not sure if it is the right way, I hope it helps!

  8. samunohito
    added this to [実験中] 管理用on Dec 12, 2024
  9. github-project-automation
    moved this to Todo in [実験中] 管理用on Dec 12, 2024
  10. misskey-dev
    locked and limited conversation to collaborators on Oct 30, 2026
  11. kakkokari-gtyih
    converted this issue into a discussion #18080 on Oct 30, 2026
  12. github-project-automation
    moved this from Todo to Done in [実験中] 管理用on Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ⚠️bug?This might be a bug

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions