emielregis
emielregis
IImmich
Created by emielregis on 4/14/2025 in #help-desk-support
Postgres errors when restoring
I am testing my backups and am seeing a new error. The restore itself seems to be working, but I'm unsure what is leading to this error. Error message (appears twice as postgres is being restored):
ERROR: called `Result::unwrap()` on an `Err` value: Error { inner: Error { inner: TomlError { message: "invalid table header\nexpected newline, `#`", original: Some("[indexing.hnsw]\r\r\nm = 16\r\r\nef_construction = 300"), keys: [], span: Some(15..16) } } }
ERROR: called `Result::unwrap()` on an `Err` value: Error { inner: Error { inner: TomlError { message: "invalid table header\nexpected newline, `#`", original: Some("[indexing.hnsw]\r\r\nm = 16\r\r\nef_construction = 300"), keys: [], span: Some(15..16) } } }
Command used to backup: docker exec -t immich_postgres pg_dumpall -c -U postgres > /path/to/database-backup/immich-database.sql Command used to restore: cat /path/to/database-backup/immich-database.sql | sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" | docker exec -i immich_postgres psql --dbname=postgres --username=postgres Relevant history: - This installation has been up for a very long time - about two years. - It went through the pgvector to pgvecto.rs breaking change, etc. - I restored from a backup a few months back and re-initialized the db to use data checksums. There were no errors at the time. No changes have been made to the compose file since.
38 replies
IImmich
Created by emielregis on 9/12/2023 in #help-desk-support
Library folder permission set to 711 instead of 755
No description
8 replies
IImmich
Created by emielregis on 9/9/2023 in #help-desk-support
Connection timeout in microservices log
I saw a few failed face recognition jobs, so I checked the microservices log. I found many ETIMEDOUT errors. I'm on v 1.76.1, the version just before the release that had the machine learning timeout issue. My docker-compose and .env files are here: https://github.com/immich-app/immich/issues/4002 Error: connect ETIMEDOUT at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:628:28) at Socket.emit (node:events:514:28) at Socket._onTimeout (node:net:571:8) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } I'm surprised that the redis container seems to be timing out, if I'm understanding the logs correctly. I've included details about my hardware in the linked github issue. I suspect the culprit might be a relatively slow CPU, but I'd greatly appreciate it if someone can point me in the right direction on how to fix this. Thank you!
5 replies
IImmich
Created by emielregis on 9/6/2023 in #help-desk-support
Clarification regarding "Missing" option in Recognize Faces job
No description
2 replies