Immich latest update issue #1502

Closed
opened 2026-02-05 01:21:33 +03:00 by OVERLORD · 13 comments
Owner

Originally created by @Maxzhao1999 on GitHub (Aug 21, 2025).

Originally assigned to: @vhsdream on GitHub.

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Immich

📂 What was the exact command used to execute the script?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Immich does not start after update, starting manually shows:
[Nest] 2022 - 08/20/2025, 10:26:22 PM ERROR [Microservices:MetadataService] Unable to initialize reverse geocoding: Error: ENOENT: no such file or directory, open '/build/geodata/geodata-date.txt'

🔄 Steps to reproduce the issue.

type "update" into LXC container and follow steps

Paste the full error output (if available).

Starting api worker
Starting microservices worker
[Nest] 2022 - 08/20/2025, 10:26:21 PM LOG [Microservices:EventRepository] Initialized websocket server
[Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for clip_index of 12112 rows
[Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for face_index of 23634 rows
[Nest] 2030 - 08/20/2025, 10:26:22 PM WARN [Api:ApiService] Unable to open /build/www/index.html, skipping SSR.
[Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:EventRepository] Initialized websocket server
[Nest] 2022 - 08/20/2025, 10:26:22 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] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:StorageService] Successfully verified system mount folder checks
[Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:DatabaseRepository] targetLists=1, current=1 for clip_index of 12112 rows
[Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:MetadataService] Bootstrapping metadata service
[Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:MetadataService] Initializing metadata service
[Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:DatabaseRepository] targetLists=1, current=1 for face_index of 23634 rows
[Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:MapRepository] Initializing metadata repository
[Nest] 2022 - 08/20/2025, 10:26:22 PM ERROR [Microservices:MetadataService] Unable to initialize reverse geocoding: Error: ENOENT: no such file or directory, open '/build/geodata/geodata-date.txt'
Error: ENOENT: no such file or directory, open '/build/geodata/geodata-date.txt'
at async open (node:internal/fs/promises:639:25)
at async readFile (node:internal/fs/promises:1243:14)
at async MapRepository.init (/opt/immich/app/dist/repositories/map.repository.js:48:29)
at async /opt/immich/app/dist/repositories/database.repository.js:379:27
at async /opt/immich/app/node_modules/kysely/dist/cjs/kysely.js:535:20
at async DefaultConnectionProvider.provideConnection (/opt/immich/app/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
at async /opt/immich/app/dist/repositories/database.repository.js:376:13
Error: Metadata service init failed
at MetadataService.init (/opt/immich/app/dist/services/metadata.service.js:118:19)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async MetadataService.onBootstrap (/opt/immich/app/dist/services/metadata.service.js:97:9)
at async EventRepository.onEvent (/opt/immich/app/dist/repositories/event.repository.js:126:13)
at async MicroservicesModule.onModuleInit (/opt/immich/app/dist/app.module.js:83:9)
at async callModuleInitHook (/opt/immich/app/node_modules/@nestjs/core/hooks/on-module-init.hook.js:51:9)
at async NestApplication.callInitHook (/opt/immich/app/node_modules/@nestjs/core/nest-application-context.js:242:13)
at async NestApplication.init (/opt/immich/app/node_modules/@nestjs/core/nest-application.js:103:9)
at async NestApplication.listen (/opt/immich/app/node_modules/@nestjs/core/nest-application.js:175:13)
at async bootstrap (/opt/immich/app/dist/workers/microservices.js:25:5)
microservices worker error: Error: Metadata service init failed, stack: Error: Metadata service init failed
at MetadataService.init (/opt/immich/app/dist/services/metadata.service.js:118:19)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async MetadataService.onBootstrap (/opt/immich/app/dist/services/metadata.service.js:97:9)
at async EventRepository.onEvent (/opt/immich/app/dist/repositories/event.repository.js:126:13)
at async MicroservicesModule.onModuleInit (/opt/immich/app/dist/app.module.js:83:9)
at async callModuleInitHook (/opt/immich/app/node_modules/@nestjs/core/hooks/on-module-init.hook.js:51:9)
at async NestApplication.callInitHook (/opt/immich/app/node_modules/@nestjs/core/nest-application-context.js:242:13)
at async NestApplication.init (/opt/immich/app/node_modules/@nestjs/core/nest-application.js:103:9)
at async NestApplication.listen (/opt/immich/app/node_modules/@nestjs/core/nest-application.js:175:13)
at async bootstrap (/opt/immich/app/dist/workers/microservices.js:25:5)
[Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}
[Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:StorageService] Successfully verified system mount folder checks
microservices worker exited with code 1
Killing api process

🖼️ Additional context (optional).

No response

Originally created by @Maxzhao1999 on GitHub (Aug 21, 2025). Originally assigned to: @vhsdream on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Immich ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Immich does not start after update, starting manually shows: [Nest] 2022 - 08/20/2025, 10:26:22 PM ERROR [Microservices:MetadataService] Unable to initialize reverse geocoding: Error: ENOENT: no such file or directory, open '/build/geodata/geodata-date.txt' ### 🔄 Steps to reproduce the issue. type "update" into LXC container and follow steps ### ❌ Paste the full error output (if available). Starting api worker Starting microservices worker [Nest] 2022 - 08/20/2025, 10:26:21 PM LOG [Microservices:EventRepository] Initialized websocket server [Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for clip_index of 12112 rows [Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for face_index of 23634 rows [Nest] 2030 - 08/20/2025, 10:26:22 PM WARN [Api:ApiService] Unable to open /build/www/index.html, skipping SSR. [Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:EventRepository] Initialized websocket server [Nest] 2022 - 08/20/2025, 10:26:22 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] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:StorageService] Successfully verified system mount folder checks [Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:DatabaseRepository] targetLists=1, current=1 for clip_index of 12112 rows [Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:MetadataService] Bootstrapping metadata service [Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:MetadataService] Initializing metadata service [Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:DatabaseRepository] targetLists=1, current=1 for face_index of 23634 rows [Nest] 2022 - 08/20/2025, 10:26:22 PM LOG [Microservices:MapRepository] Initializing metadata repository [Nest] 2022 - 08/20/2025, 10:26:22 PM ERROR [Microservices:MetadataService] Unable to initialize reverse geocoding: Error: ENOENT: no such file or directory, open '/build/geodata/geodata-date.txt' Error: ENOENT: no such file or directory, open '/build/geodata/geodata-date.txt' at async open (node:internal/fs/promises:639:25) at async readFile (node:internal/fs/promises:1243:14) at async MapRepository.init (/opt/immich/app/dist/repositories/map.repository.js:48:29) at async /opt/immich/app/dist/repositories/database.repository.js:379:27 at async /opt/immich/app/node_modules/kysely/dist/cjs/kysely.js:535:20 at async DefaultConnectionProvider.provideConnection (/opt/immich/app/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20) at async /opt/immich/app/dist/repositories/database.repository.js:376:13 Error: Metadata service init failed at MetadataService.init (/opt/immich/app/dist/services/metadata.service.js:118:19) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async MetadataService.onBootstrap (/opt/immich/app/dist/services/metadata.service.js:97:9) at async EventRepository.onEvent (/opt/immich/app/dist/repositories/event.repository.js:126:13) at async MicroservicesModule.onModuleInit (/opt/immich/app/dist/app.module.js:83:9) at async callModuleInitHook (/opt/immich/app/node_modules/@nestjs/core/hooks/on-module-init.hook.js:51:9) at async NestApplication.callInitHook (/opt/immich/app/node_modules/@nestjs/core/nest-application-context.js:242:13) at async NestApplication.init (/opt/immich/app/node_modules/@nestjs/core/nest-application.js:103:9) at async NestApplication.listen (/opt/immich/app/node_modules/@nestjs/core/nest-application.js:175:13) at async bootstrap (/opt/immich/app/dist/workers/microservices.js:25:5) microservices worker error: Error: Metadata service init failed, stack: Error: Metadata service init failed at MetadataService.init (/opt/immich/app/dist/services/metadata.service.js:118:19) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async MetadataService.onBootstrap (/opt/immich/app/dist/services/metadata.service.js:97:9) at async EventRepository.onEvent (/opt/immich/app/dist/repositories/event.repository.js:126:13) at async MicroservicesModule.onModuleInit (/opt/immich/app/dist/app.module.js:83:9) at async callModuleInitHook (/opt/immich/app/node_modules/@nestjs/core/hooks/on-module-init.hook.js:51:9) at async NestApplication.callInitHook (/opt/immich/app/node_modules/@nestjs/core/nest-application-context.js:242:13) at async NestApplication.init (/opt/immich/app/node_modules/@nestjs/core/nest-application.js:103:9) at async NestApplication.listen (/opt/immich/app/node_modules/@nestjs/core/nest-application.js:175:13) at async bootstrap (/opt/immich/app/dist/workers/microservices.js:25:5) [Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}} [Nest] 2030 - 08/20/2025, 10:26:22 PM LOG [Api:StorageService] Successfully verified system mount folder checks microservices worker exited with code 1 Killing api process ### 🖼️ Additional context (optional). _No response_
OVERLORD added the buginvestigation labels 2026-02-05 01:21:33 +03:00
Author
Owner

@umrath commented on GitHub (Aug 21, 2025):

Update fails for me as well. immich-ml is not starting.
Not sure if this is related or a different bug, though.

@umrath commented on GitHub (Aug 21, 2025): Update fails for me as well. immich-ml is not starting. Not sure if this is related or a different bug, though.
Author
Owner

@Maxzhao1999 commented on GitHub (Aug 21, 2025):

Apparently still exists after #7035

Image
@Maxzhao1999 commented on GitHub (Aug 21, 2025): Apparently still exists after #7035 <img width="959" height="250" alt="Image" src="https://github.com/user-attachments/assets/16f1acb5-6218-4e69-a067-0b4e018c11fb" />
Author
Owner

@vhsdream commented on GitHub (Aug 21, 2025):

@Maxzhao1999 from what version were you updating?

@vhsdream commented on GitHub (Aug 21, 2025): @Maxzhao1999 from what version were you updating?
Author
Owner

@vhsdream commented on GitHub (Aug 21, 2025):

@Maxzhao1999 for regarding the original reason you opened this issue; whatever reason it seems that the command on line 176 didn't run or failed for you.

Making sure that both services are stopped (systemctl stop immich-web immich-ml), if you run the command again perhaps it will change the relevant files:

cd /opt/immich/app
grep -rlE "'/build'" | xargs -n1 sed -i "s|'/build'|'/opt/immich/app'|g"

Then restart immich-ml and immich-web and tail the logs.

@vhsdream commented on GitHub (Aug 21, 2025): @Maxzhao1999 for regarding the original reason you opened this issue; whatever reason it seems that the command on [line 176](https://github.com/community-scripts/ProxmoxVE/blob/c9b5e27d743bba3016307226edb071e6e54618e7/ct/immich.sh#L176) didn't run or failed for you. Making sure that both services are stopped (`systemctl stop immich-web immich-ml`), if you run the command again perhaps it will change the relevant files: ``` cd /opt/immich/app grep -rlE "'/build'" | xargs -n1 sed -i "s|'/build'|'/opt/immich/app'|g" ``` Then restart immich-ml and immich-web and tail the logs.
Author
Owner

@umrath commented on GitHub (Aug 21, 2025):

@Maxzhao1999 from what version were you updating?

I cannot answer for @Maxzhao1999 but I tried to update from 0.137.3.
I'm running 0.138.0 now and will try to update to 0.138.1 in a moment.

(corrected wrong versioning)

Edit: The Update from 0.138.0 to 0.138.1 worked fine.

@umrath commented on GitHub (Aug 21, 2025): > [@Maxzhao1999](https://github.com/Maxzhao1999) from what version were you updating? I cannot answer for @Maxzhao1999 but I tried to update from 0.137.3. I'm running 0.138.0 now and will try to update to 0.138.1 in a moment. (corrected wrong versioning) Edit: The Update from 0.138.0 to 0.138.1 worked fine.
Author
Owner

@trinoklingenberg commented on GitHub (Aug 21, 2025):

Hello,

I copied the directory ‘geodata’ from /opt/geodata/
to the directory /opt/app/geodata/
Then I started bash start.sh and the error was fixed.

cd /opt/immich/app/bin/
bash start.sh

but after reboot does not start immich
I have startet self

@trinoklingenberg commented on GitHub (Aug 21, 2025): Hello, I copied the directory ‘geodata’ from /opt/geodata/ to the directory /opt/app/geodata/ Then I started bash start.sh and the error was fixed. cd /opt/immich/app/bin/ bash start.sh but after reboot does not start immich I have startet self
Author
Owner

@vhsdream commented on GitHub (Aug 21, 2025):

Apparently still exists after #7035
Image

This was my error and the PR that was merged fixes it. The rest is just bad timing.

Please @umrath @Maxzhao1999 and @trinoklingenberg tell me what version of Proxmox you are on.

@vhsdream commented on GitHub (Aug 21, 2025): > Apparently still exists after [#7035](https://github.com/community-scripts/ProxmoxVE/pull/7035) > <img alt="Image" width="959" height="250" src="https://private-user-images.githubusercontent.com/21307071/480447565-16f1acb5-6218-4e69-a067-0b4e018c11fb.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTU3Nzg2NTMsIm5iZiI6MTc1NTc3ODM1MywicGF0aCI6Ii8yMTMwNzA3MS80ODA0NDc1NjUtMTZmMWFjYjUtNjIxOC00ZTY5LWEwNjctMGI0ZTAxOGMxMWZiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA4MjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwODIxVDEyMTIzM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZkMGI0ZDI5OWMzMTEzYzU3YWQ3N2YwZWI5OGI3MDI0ZTdiN2IxOGE5NzdkZWI3OWY1OGEwYzk0NGI3OTJhMGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dbUijlqmZWasn06d0cSsn_SV0Jj-KoCqr3yLGKGdVaE"> This was my error and the PR that was merged fixes it. The rest is just bad timing. Please @umrath @Maxzhao1999 and @trinoklingenberg tell me what version of Proxmox you are on.
Author
Owner

@trinoklingenberg commented on GitHub (Aug 21, 2025):

I have Immich run on Proxmox
and startet the update via
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"

Immich version 1.137.3

@trinoklingenberg commented on GitHub (Aug 21, 2025): I have Immich run on Proxmox and startet the update via bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" Immich version 1.137.3
Author
Owner

@Maxzhao1999 commented on GitHub (Aug 21, 2025):

Hi,
I'm on proxmox 9.0.5 and was updating immich from v1.138.0

@Maxzhao1999 commented on GitHub (Aug 21, 2025): Hi, I'm on proxmox 9.0.5 and was updating immich from v1.138.0
Author
Owner

@Maxzhao1999 commented on GitHub (Aug 21, 2025):

Can confirm: I restored to working backup and did "update" 5 minutes ago and it now works as expected. I will leave this issue open until end of play for any comments but it seems fixed for me

@Maxzhao1999 commented on GitHub (Aug 21, 2025): Can confirm: I restored to working backup and did "update" 5 minutes ago and it now works as expected. I will leave this issue open until end of play for any comments but it seems fixed for me
Author
Owner

@vhsdream commented on GitHub (Aug 21, 2025):

I have Immich run on Proxmox and startet the update via bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"

@trinoklingenberg in your Proxmox, run pveversion and tell me what it says.

@vhsdream commented on GitHub (Aug 21, 2025): > I have Immich run on Proxmox and startet the update via bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" @trinoklingenberg in your Proxmox, run `pveversion` and tell me what it says.
Author
Owner

@trinoklingenberg commented on GitHub (Aug 21, 2025):

I have Immich run on Proxmox and startet the update via bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"

@trinoklingenberg in your Proxmox, run pveversion and tell me what it says.

pve-manager/8.4.11/14a32011146091ed (running kernel: 6.8.12-13-pve)

@trinoklingenberg commented on GitHub (Aug 21, 2025): > > I have Immich run on Proxmox and startet the update via bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" > > [@trinoklingenberg](https://github.com/trinoklingenberg) in your Proxmox, run `pveversion` and tell me what it says. pve-manager/8.4.11/14a32011146091ed (running kernel: 6.8.12-13-pve)
Author
Owner

@trinoklingenberg commented on GitHub (Aug 21, 2025):

I have Immich run on Proxmox and startet the update via bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"

@trinoklingenberg in your Proxmox, run pveversion and tell me what it says.

Hello
After the snapshot, the update is now working perfectly.
Thank you very much.
I am very pleased with the update.

@trinoklingenberg commented on GitHub (Aug 21, 2025): > > I have Immich run on Proxmox and startet the update via bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" > > [@trinoklingenberg](https://github.com/trinoklingenberg) in your Proxmox, run `pveversion` and tell me what it says. Hello After the snapshot, the update is now working perfectly. Thank you very much. I am very pleased with the update.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1502