Closed classic-mcfly closed 9 months ago
Can you help confirm 1.80 or 1.84?
These errors occurred first on v1.80.0 but I have tested this on all versions after v1.80.0 including v1.84.0 which showed the same errors.
I just noticed that the immich CLI also exits with an error which seems to be related to the database columns:
response: {
status: 400,
statusText: 'Bad Request',
headers: [Object],
config: [Object],
request: [ClientRequest],
data: [Object]
},
isAxiosError: true,
toJSON: [Function: toJSON]
},
response: {
message: 'Error uploading file',
error: 'QueryFailedError: null value in column "localDateTime" of relation "assets" violates not-null co
nstraint',
statusCode: 400
}
}
Were you able to resolve the issue?
In the next release we have completely reworked how reverse geocoding will function. We are replacing the old library with our own implementation that uses postgres for doing the reverse geocoding. This should result in much lower memory usage overall, and also should eliminate the microservices container running out of memory. We believe this was happening due to some issue with the logic in the old geocoding implementation which was not written by us. If you still continue to experience these issues after the next release (1.89.0) please open a new issue describing the problem. Cheers!
Dears I still have this problem:
from Immich side: [Nest] 1158 - 12/17/2023, 11:40:27 AM ERROR [ExceptionHandler] relation "asset_faces" does not exist QueryFailedError: relation "asset_faces" does not exist at PostgresQueryRunner.query (/app/immich/server/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:211:19) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async UsePgVectors1700713871511.up (/app/immich/server/dist/infra/migrations/1700713871511-UsePgVectors.js:9:30) at async MigrationExecutor.executePendingMigrations (/app/immich/server/node_modules/typeorm/migration/MigrationExecutor.js:225:17) at async DataSource.runMigrations (/app/immich/server/node_modules/typeorm/data-source/DataSource.js:260:35) at async DataSource.initialize (/app/immich/server/node_modules/typeorm/data-source/DataSource.js:148:17)
from DB side:
2023-12-17 11:42:15.098 CET [162] ERROR: relation "asset_faces" does not exist at character 72
2023-12-17 11:42:15.098 CET [162] STATEMENT:
SELECT CARDINALITY(embedding::real[]) as dimsize
FROM asset_faces
LIMIT 1
How to solve it? Thanks
The bug
Hello,
I recently upgraded from 1.79.1 to 1.80.0. After upgrading and starting the migration job for the new folder structure the job is failing, even on higher versions.
I get the following errors after starting the server and after the failed migration:
and
and
These errors seem to have nothing to do with the migration because they appear even without triggering the migration job. But they seem to be caused by the version upgrade. While getting the errors the server is fully reachable from a browser. No assets are listed on the main page and there are three messages with "Internal server error (Immich Server Error)".
I could add the missing column to the database but I'm not sure if this will really fix the errors because the column will be empty. A rollback to v1.79.1 is working and triggering no error messages
The OS that Immich Server is running on
Alpine Linux 3.18.4
Version of Immich Server
1.80.0
Version of Immich Mobile App
1.80.0
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Additional information
The server has 16GB memory.