Skip to content

geodata_places missing causing restart loop after upgrade from v2.7.5 to v3 #29609

Closed
Closed
geodata_places missing causing restart loop after upgrade from v2.7.5 to v3#29609

Description

@Tom62719
Tom62719
opened on Jul 5, 2026

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

  • Yes

The bug

Hi there.

I just tried upgrading immich from version 2.7.5 to v3 after reading the release notes. but i'm getting the following error now.

[Nest] 7 - 07/05/2026, 11:45:21 PM ERROR [Microservices:MetadataService] Unable to initialize reverse geocoding: PostgresError: relation "geodata_places" does not exist

I already tried some troubleshooting but with no success. i reverted back with a backup to the previous version.
i would love to hear your response in resolving this issue.

Below is the full log output.

The OS that Immich Server is running on

Ubuntu 24.04.4 LTS

Version of Immich Server

2.7.5 to 3.0.0

Version of Immich Mobile App

2.7.5

Platform with the issue

  • Server
  • Web
  • Mobile

Device make and model

No response

Your docker-compose.yml content

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.transcoding.yml
    #   service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    volumes:
      # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file
      - ${UPLOAD_LOCATION}:/data
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - '2283:2283'
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false

  immich-machine-learning:
    container_name: immich_machine_learning
    # For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag.
    # Example tag: ${IMMICH_VERSION:-release}-cuda
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
    #   file: hwaccel.ml.yml
    #   service: cpu # set to one of [armnn, cuda, openvino, openvino-wsl] for accelerated inference - use the `-wsl` version for WSL2 where applicable
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false

  redis:
    container_name: immich_redis
    image: docker.io/redis:6.2-alpine@sha256:148bb5411c184abd288d9aaed139c98123eeb8824c5d3fce03cf721db58066d8
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
     # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
     # DB_STORAGE_TYPE: 'HDD'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
    shm_size: 128mb
    restart: always

volumes:
  model-cache:

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=./library
# The location where your database files are stored
DB_DATA_LOCATION=./postgres

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time_z>TZ=Europe/Amsterdam

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=v3.0.0

#immich host
IMMICH_HOST=0.0.0.0

# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=*********

# The values below this line do not need to be changed
###################################################################################
DB_USERNAME=*****
DB_DATABASE_NAME=****

Reproduction steps

1 have immich running on version 2.7.5, database already migrated to VectorChord
2. change version in the .env file to v3 or v3.0.0
3. run docker compose pull && docker compose up -d
4. restart loop occurs with the geodata error as shown in the logs above.
...

Relevant log output

Initializing Immich v3.0.0
Detected CPU Cores: 6
(node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Starting api worker
Starting microservices worker
(node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:27) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[Nest] 7  - 07/05/2026, 11:45:20 PM     LOG [Microservices:WebsocketRepository] Initialized websocket server
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for clip_index of 1296 rows
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for face_index of 649 rows
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:DatabaseRepository] Running migrations
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:DatabaseRepository] Finished running migrations
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:DatabaseService] Checking for schema drift
[Nest] 7  - 07/05/2026, 11:45:21 PM    WARN [Microservices:DatabaseService] Detected schema drift. For more information, see https://docs.immich.app/errors#schema-drift or run `immich-admin schema-check`
[Nest] 7  - 07/05/2026, 11:45:21 PM    WARN [Microservices:DatabaseService]   - The table "geodata_places" is missing and needs to be created
[Nest] 7  - 07/05/2026, 11:45:21 PM    WARN [Microservices:DatabaseService]   - The index "geodata_places"."IDX_geodata_gist_earthcoord" is missing and needs to be created
[Nest] 7  - 07/05/2026, 11:45:21 PM    WARN [Microservices:DatabaseService]   - The index "geodata_places"."idx_geodata_places_name" is missing and needs to be created
[Nest] 7  - 07/05/2026, 11:45:21 PM    WARN [Microservices:DatabaseService]   - The index "geodata_places"."idx_geodata_places_admin2_name" is missing and needs to be created
[Nest] 7  - 07/05/2026, 11:45:21 PM    WARN [Microservices:DatabaseService]   - The index "geodata_places"."idx_geodata_places_admin1_name" is missing and needs to be created
[Nest] 7  - 07/05/2026, 11:45:21 PM    WARN [Microservices:DatabaseService]   - The index "geodata_places"."idx_geodata_places_alternate_names" is missing and needs to be created
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:StorageService] Successfully verified system mount folder checks
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:MetadataService] Bootstrapping metadata service
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:MetadataService] Initializing metadata service
[Nest] 7  - 07/05/2026, 11:45:21 PM     LOG [Microservices:MapRepository] Initializing metadata repository
[Nest] 27  - 07/05/2026, 11:45:21 PM     LOG [Api:WebsocketRepository] Initialized websocket server
[Nest] 27  - 07/05/2026, 11:45:21 PM     LOG [Api:DatabaseRepository] targetLists=1, current=1 for clip_index of 1296 rows
[Nest] 27  - 07/05/2026, 11:45:21 PM     LOG [Api:DatabaseRepository] targetLists=1, current=1 for face_index of 649 rows
[Nest] 27  - 07/05/2026, 11:45:21 PM     LOG [Api:DatabaseRepository] Running migrations
[Nest] 27  - 07/05/2026, 11:45:21 PM     LOG [Api:DatabaseRepository] Finished running migrations
[Nest] 27  - 07/05/2026, 11:45:21 PM     LOG [Api:DatabaseService] Checking for schema drift
Query failed : {
  durationMs: 2.3832910000000993,
  error: PostgresError: relation "geodata_places" does not exist
      at ErrorResponse (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:815:30)
      at handle (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:489:6)
      at Socket.data (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:324:9)
      at Socket.emit (node:events:508:28)
      at addChunk (node:internal/streams/readable:563:12)
      at readableAddChunkPushByteMode (node:internal/streams/readable:514:3)
      at Readable.push (node:internal/streams/readable:394:5)
      at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
    severity_local: 'ERROR',
    severity: 'ERROR',
    code: '42P01',
    position: '74',
    file: 'namespace.c',
    line: '433',
    routine: 'RangeVarGetRelidExtended'
  },
  sql: 'CREATE TABLE geodata_places_tmp\n' +
    '                (\n' +
    '                  LIKE geodata_places INCLUDING ALL EXCLUDING INDEXES\n' +
    '                )',
  params: []
}
[Nest] 7  - 07/05/2026, 11:45:21 PM   ERROR [Microservices:MetadataService] Unable to initialize reverse geocoding: PostgresError: relation "geodata_places" does not exist
PostgresError: relation "geodata_places" does not exist
    at ErrorResponse (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:815:30)
    at handle (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:489:6)
    at Socket.data (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:324:9)
    at Socket.emit (node:events:508:28)
    at addChunk (node:internal/streams/readable:563:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:514:3)
    at Readable.push (node:internal/streams/readable:394:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
Error: Metadata service init failed
    at MetadataService.init (/usr/src/app/server/dist/services/metadata.service.js:125:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async MetadataService.onBootstrap (/usr/src/app/server/dist/services/metadata.service.js:104:9)
    at async EventRepository.onEvent (/usr/src/app/server/dist/repositories/event.repository.js:91:13)
    at async MicroservicesModule.onModuleInit (/usr/src/app/server/dist/app.module.js:100:9)
    at async callModuleInitHook (/usr/src/app/server/node_modules/.pnpm/@nestjs+core@11.1.27_@nestjs+common@11.1.27_reflect-metadata@0.2.2_rxjs@7.8.2__@nestjs+_0784543a664f2ceb9cb9587477b059cf/node_modules/@nestjs/core/hooks/on-module-init.hook.js:51:9)
    at async NestApplication.callInitHook (/usr/src/app/server/node_modules/.pnpm/@nestjs+core@11.1.27_@nestjs+common@11.1.27_reflect-metadata@0.2.2_rxjs@7.8.2__@nestjs+_0784543a664f2ceb9cb9587477b059cf/node_modules/@nestjs/core/nest-application-context.js:252:13)
    at async NestApplication.init (/usr/src/app/server/node_modules/.pnpm/@nestjs+core@11.1.27_@nestjs+common@11.1.27_reflect-metadata@0.2.2_rxjs@7.8.2__@nestjs+_0784543a664f2ceb9cb9587477b059cf/node_modules/@nestjs/core/nest-application.js:105:9)
    at async NestApplication.listen (/usr/src/app/server/node_modules/.pnpm/@nestjs+core@11.1.27_@nestjs+common@11.1.27_reflect-metadata@0.2.2_rxjs@7.8.2__@nestjs+_0784543a664f2ceb9cb9587477b059cf/node_modules/@nestjs/core/nest-application.js:177:13)
    at async bootstrap (/usr/src/app/server/dist/workers/microservices.js:27:5) {
  [cause]: PostgresError: relation "geodata_places" does not exist
      at ErrorResponse (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:815:30)
      at handle (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:489:6)
      at Socket.data (file:///usr/src/app/server/node_modules/.pnpm/postgres@3.4.9/node_modules/postgres/src/connection.js:324:9)
      at Socket.emit (node:events:508:28)
      at addChunk (node:internal/streams/readable:563:12)
      at readableAddChunkPushByteMode (node:internal/streams/readable:514:3)
      at Readable.push (node:internal/streams/readable:394:5)
      at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
    severity_local: 'ERROR',
    severity: 'ERROR',
    code: '42P01',
    position: '74',
    file: 'namespace.c',
    line: '433',
    routine: 'RangeVarGetRelidExtended'
  }
}
microservices worker error: Error: Metadata service init failed, stack: Error: Metadata service init failed
    at MetadataService.init (/usr/src/app/server/dist/services/metadata.service.js:125:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async MetadataService.onBootstrap (/usr/src/app/server/dist/services/metadata.service.js:104:9)
    at async EventRepository.onEvent (/usr/src/app/server/dist/repositories/event.repository.js:91:13)
    at async MicroservicesModule.onModuleInit (/usr/src/app/server/dist/app.module.js:100:9)
    at async callModuleInitHook (/usr/src/app/server/node_modules/.pnpm/@nestjs+core@11.1.27_@nestjs+common@11.1.27_reflect-metadata@0.2.2_rxjs@7.8.2__@nestjs+_0784543a664f2ceb9cb9587477b059cf/node_modules/@nestjs/core/hooks/on-module-init.hook.js:51:9)
    at async NestApplication.callInitHook (/usr/src/app/server/node_modules/.pnpm/@nestjs+core@11.1.27_@nestjs+common@11.1.27_reflect-metadata@0.2.2_rxjs@7.8.2__@nestjs+_0784543a664f2ceb9cb9587477b059cf/node_modules/@nestjs/core/nest-application-context.js:252:13)
    at async NestApplication.init (/usr/src/app/server/node_modules/.pnpm/@nestjs+core@11.1.27_@nestjs+common@11.1.27_reflect-metadata@0.2.2_rxjs@7.8.2__@nestjs+_0784543a664f2ceb9cb9587477b059cf/node_modules/@nestjs/core/nest-application.js:105:9)
    at async NestApplication.listen (/usr/src/app/server/node_modules/.pnpm/@nestjs+core@11.1.27_@nestjs+common@11.1.27_reflect-metadata@0.2.2_rxjs@7.8.2__@nestjs+_0784543a664f2ceb9cb9587477b059cf/node_modules/@nestjs/core/nest-application.js:177:13)
    at async bootstrap (/usr/src/app/server/dist/workers/microservices.js:27:5)
microservices worker exited with code 1
Killing api process

Additional information

please help in resolving the issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Issue Tracker
    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions