You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the update to 1.95.1, the postgres container tells this, and the app remains unreacheable :
immich_postgres | 2024-02-21 13:47:03.609 UTC [41] ERROR: pgvecto.rs: The index is not existing in the background worker.
immich_postgres | ADVICE: Drop or rebuild the index.
immich_postgres | 2024-02-21 13:47:03.609 UTC [41] STATEMENT:
immich_postgres | SELECT idx_status
immich_postgres | FROM pg_vector_index_stat
immich_postgres | WHERE indexname = $1
immich_postgres | 2024-02-21 13:47:03.798 UTC [41] ERROR: internal error: entered unreachable code
immich_postgres | 2024-02-21 13:47:03.798 UTC [41] STATEMENT: REINDEX INDEX face_index
Here is the complete log :
❯ dc up
[+] Running 6/6
✔ Network immich_internal Created 0.1s
✔ Container immich_postgres Created 0.1s
✔ Container immich_machine_learning Created 0.1s
✔ Container immich_redis Created 0.1s
✔ Container immich_microservices Created 0.0s
✔ Container immich_server Created 0.1s
Attaching to immich_machine_learning, immich_microservices, immich_postgres, immich_redis, immich_server
immich_redis | 1:C 21 Feb 2024 13:42:31.872 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
immich_redis | 1:C 21 Feb 2024 13:42:31.872 # Redis version=6.2.14, bits=64, commit=00000000, modified=0, pid=1, just started
immich_redis | 1:C 21 Feb 2024 13:42:31.872 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
immich_redis | 1:M 21 Feb 2024 13:42:31.873 * monotonic clock: POSIX clock_gettime
immich_redis | 1:M 21 Feb 2024 13:42:31.874 * Running mode=standalone, port=6379.
immich_redis | 1:M 21 Feb 2024 13:42:31.874 # Server initialized
immich_redis | 1:M 21 Feb 2024 13:42:31.874 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
immich_redis | 1:M 21 Feb 2024 13:42:31.874 * Ready to accept connections
immich_postgres |
immich_postgres | PostgreSQL Database directory appears to contain a database; Skipping initialization
immich_postgres |
immich_postgres | 2024-02-21 13:42:32.045 UTC [1] LOG: starting PostgreSQL 14.10 (Debian 14.10-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
immich_postgres | 2024-02-21 13:42:32.045 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
immich_postgres | 2024-02-21 13:42:32.045 UTC [1] LOG: listening on IPv6 address "::", port 5432
immich_postgres | 2024-02-21 13:42:32.051 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
immich_postgres | 2024-02-21 13:42:32.056 UTC [27] LOG: database system was shut down at 2024-02-21 13:42:24 UTC
immich_postgres | [2024-02-21T13:42:32Z INFO service::utils::clean] Delete outdated directory "pg_vectors/indexes/1125820".
immich_postgres | 2024-02-21 13:42:32.099 UTC [1] LOG: database system is ready to accept connections
immich_machine_learning | [02/21/24 13:42:33] INFO Starting gunicorn 21.2.0
immich_machine_learning | [02/21/24 13:42:33] INFO Listening at: http://0.0.0.0:3003 (9)
immich_machine_learning | [02/21/24 13:42:33] INFO Using worker: app.config.CustomUvicornWorker
immich_machine_learning | [02/21/24 13:42:33] INFO Booting worker with pid: 17
immich_microservices | [Nest] 7 - 02/21/2024, 1:42:34 PM LOG [CommunicationRepository] Initialized websocket server
immich_postgres | 2024-02-21 13:42:34.289 UTC [41] ERROR: pgvecto.rs: The index is not existing in the background worker.
immich_postgres | ADVICE: Drop or rebuild the index.
immich_postgres | 2024-02-21 13:42:34.289 UTC [41] STATEMENT:
immich_postgres | SELECT idx_status
immich_postgres | FROM pg_vector_index_stat
immich_postgres | WHERE indexname = $1
immich_postgres | 2024-02-21 13:42:34.302 UTC [41] ERROR: internal error: entered unreachable code
immich_postgres | 2024-02-21 13:42:34.302 UTC [41] STATEMENT: REINDEX INDEX clip_index
immich_microservices | [Nest] 7 - 02/21/2024, 1:42:34 PM WARN [DatabaseRepository] Could not reindex index clip_index. Attempting to auto-fix.
immich_server | [Nest] 7 - 02/21/2024, 1:42:34 PM LOG [CommunicationRepository] Initialized websocket server
immich_machine_learning | [02/21/24 13:42:36] INFO Started server process [17]
immich_machine_learning | [02/21/24 13:42:36] INFO Waiting for application startup.
immich_machine_learning | [02/21/24 13:42:36] INFO Created in-memory cache with unloading after 300s
immich_machine_learning | of inactivity.
immich_machine_learning | [02/21/24 13:42:36] INFO Initialized request thread pool with 8 threads.
immich_machine_learning | [02/21/24 13:42:36] INFO Application startup complete.
immich_postgres | 2024-02-21 13:47:03.609 UTC [41] ERROR: pgvecto.rs: The index is not existing in the background worker.
immich_postgres | ADVICE: Drop or rebuild the index.
immich_postgres | 2024-02-21 13:47:03.609 UTC [41] STATEMENT:
immich_postgres | SELECT idx_status
immich_postgres | FROM pg_vector_index_stat
immich_postgres | WHERE indexname = $1
immich_postgres | 2024-02-21 13:47:03.798 UTC [41] ERROR: internal error: entered unreachable code
immich_postgres | 2024-02-21 13:47:03.798 UTC [41] STATEMENT: REINDEX INDEX face_index
immich_microservices | [Nest] 7 - 02/21/2024, 1:47:03 PM WARN [DatabaseRepository] Could not reindex index face_index. Attempting to auto-fix.
The bug
After the update to 1.95.1, the postgres container tells this, and the app remains unreacheable :
Here is the complete log :
The OS that Immich Server is running on
Debia n12
Version of Immich Server
v1.95.1
Version of Immich Mobile App
no used
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Additional information
No response
The text was updated successfully, but these errors were encountered: