小萝卜 发表于 2024-12-15 01:37:33

升级umami出错了,大佬看看怎么解决?

[*]# docker compose up --force-recreate
[*][+] Running 2/2
[*] ✔ Container umami-umami-1Recreated                                                         0.1s
[*] ✔ Container umami-db-1   Recreated                                                         0.1s
[*]Attaching to db-1, umami-1
[*]db-1   |
[*]db-1   | PostgreSQL Database directory appears to contain a database; Skipping initialization
[*]db-1   |
[*]db-1   | 2024-12-14 17:35:35.818 UTC LOG:starting PostgreSQL 15.10 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
[*]db-1   | 2024-12-14 17:35:35.818 UTC LOG:listening on IPv4 address "0.0.0.0", port 5432
[*]db-1   | 2024-12-14 17:35:35.818 UTC LOG:listening on IPv6 address "::", port 5432
[*]db-1   | 2024-12-14 17:35:35.823 UTC LOG:listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[*]db-1   | 2024-12-14 17:35:35.829 UTC LOG:database system was shut down at 2024-12-14 17:26:40 UTC
[*]db-1   | 2024-12-14 17:35:35.836 UTC LOG:database system is ready to accept connections
[*]umami-1| yarn run v1.22.22
[*]umami-1| $ npm-run-all check-db update-tracker start-server
[*]umami-1| $ node scripts/check-db.js
[*]umami-1| ✓ DATABASE_URL is defined.
[*]umami-1| ✗ Unable to connect to the database: Prisma Client could not locate the Query Engine for runtime "linux-musl-arm64-openssl-3.0.x".
[*]umami-1|
[*]umami-1| This happened because Prisma Client was generated for "linux-musl-arm64-openssl-1.1.x", but the actual deployment required "linux-musl-arm64-openssl-3.0.x".
[*]umami-1| Add "linux-musl-arm64-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:
[*]umami-1|
[*]umami-1| generator client {
[*]umami-1|   provider      = "prisma-client-js"
[*]umami-1|   binaryTargets = ["native", "linux-musl-openssl-3.0.x", "linux-musl-arm64-openssl-3.0.x"]
[*]umami-1| }
[*]umami-1|
[*]umami-1| The following locations have been searched:
[*]umami-1|   /app/node_modules/.prisma/client
[*]umami-1|   /app/node_modules/@prisma/client
[*]umami-1|   /tmp/prisma-engines
[*]umami-1|   /app/prisma
[*]umami-1| error Command failed with exit code 1.
[*]umami-1| info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[*]umami-1| ERROR: "check-db" exited with 1.
[*]umami-1| error Command failed with exit code 1.
[*]umami-1| info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[*]umami-1 exited with code 0
[*]umami-1| yarn run v1.22.22
[*]umami-1| $ npm-run-all check-db update-tracker start-server
[*]umami-1| $ node scripts/check-db.js
[*]umami-1| ✓ DATABASE_URL is defined.
[*]umami-1| ✗ Unable to connect to the database: Prisma Client could not locate the Query Engine for runtime "linux-musl-arm64-openssl-3.0.x".
[*]umami-1|
[*]umami-1| This happened because Prisma Client was generated for "linux-musl-arm64-openssl-1.1.x", but the actual deployment required "linux-musl-arm64-openssl-3.0.x".
[*]umami-1| Add "linux-musl-arm64-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:
[*]umami-1|
[*]umami-1| generator client {
[*]umami-1|   provider      = "prisma-client-js"
[*]umami-1|   binaryTargets = ["native", "linux-musl-openssl-3.0.x", "linux-musl-arm64-openssl-3.0.x"]
[*]umami-1| }
[*]umami-1|
[*]umami-1| The following locations have been searched:
[*]umami-1|   /app/node_modules/.prisma/client
[*]umami-1|   /app/node_modules/@prisma/client
[*]umami-1|   /tmp/prisma-engines
[*]umami-1|   /app/prisma
[*]umami-1| error Command failed with exit code 1.
[*]umami-1| info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[*]umami-1| ERROR: "check-db" exited with 1.
[*]umami-1| error Command failed with exit code 1.
[*]umami-1| info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[*]umami-1 exited with code 1
[*]umami-1| yarn run v1.22.22
[*]umami-1| $ npm-run-all check-db update-tracker start-server
[*]Gracefully stopping... (press Ctrl+C again to force)
[*][+] Stopping 2/2
[*] ✔ Container umami-umami-1Stopped                                                         0.2s
[*] ✔ Container umami-db-1   Stopped                            复制代码


升级umami经常出错,这次更悲剧。

炒土豆丝 发表于 2024-12-15 02:30:25

我的自动更新挂了,回滚 2.14 版本,再也不升级了。
页: [1]
查看完整版本: 升级umami出错了,大佬看看怎么解决?