starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Immich server bootloop after v1.135.1 update #1123

New Issue
Closed
opened 2026-02-04 23:11:37 +03:00 by OVERLORD · 15 comments
OVERLORD commented 2026-02-04 23:11:37 +03:00
Owner
Copy Link

Originally created by @vhsdream on GitHub (Jun 19, 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?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"

⚙️ 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.

Here and here.

Confirmed on my own install.

Working on a fix.

🔄 Steps to reproduce the issue.

Run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" or update in the LXC.

❌ Paste the full error output (if available).

[Nest] 10093  - 06/19/2025, 3:04:13 PM    WARN [Microservices:DatabaseRepository] Migration "1750323941566-UnsetPrewarmDimParameter" failed
PostgresError: invalid configuration parameter name "vchordrq.prewarm_dim"
    at ErrorResponse (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:790:26)
    at handle (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:476:6)
    at Socket.data (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:315:9)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
  severity_local: 'ERROR',
  severity: 'ERROR',
  code: '42602',
  detail: '"vchordrq" is a reserved prefix.',
  file: 'guc.c',
  line: '1225',
  routine: 'find_option'
}
microservices worker error: PostgresError: invalid configuration parameter name "vchordrq.prewarm_dim", stack: PostgresError: invalid configuration parameter name "vchordrq.prewarm_dim"
    at ErrorResponse (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:790:26)
    at handle (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:476:6)
    at Socket.data (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:315:9)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
microservices worker exited with code 1
Killing api process

🖼️ Additional context (optional).

I don't think the devs have a handle on this one yet.

My solution worked, but then they introduced a new migration without testing it! And I was pretty sure it was going to break because when I worked the problem, the only solution I found was to backup the DB, strip out any mention of vchord.prewarm_dim and then restore.

Originally created by @vhsdream on GitHub (Jun 19, 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? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. [Here](https://github.com/immich-app/immich/issues/19313) and [here](https://github.com/immich-app/immich/issues/19254#issuecomment-2988911359). Confirmed on my own install. Working on a fix. ### 🔄 Steps to reproduce the issue. Run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"` or `update` in the LXC. ### ❌ Paste the full error output (if available). ``` [Nest] 10093 - 06/19/2025, 3:04:13 PM WARN [Microservices:DatabaseRepository] Migration "1750323941566-UnsetPrewarmDimParameter" failed PostgresError: invalid configuration parameter name "vchordrq.prewarm_dim" at ErrorResponse (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:790:26) at handle (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:476:6) at Socket.data (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:315:9) at Socket.emit (node:events:518:28) at addChunk (node:internal/streams/readable:561:12) at readableAddChunkPushByteMode (node:internal/streams/readable:512:3) at Readable.push (node:internal/streams/readable:392:5) at TCP.onStreamRead (node:internal/stream_base_commons:189:23) { severity_local: 'ERROR', severity: 'ERROR', code: '42602', detail: '"vchordrq" is a reserved prefix.', file: 'guc.c', line: '1225', routine: 'find_option' } microservices worker error: PostgresError: invalid configuration parameter name "vchordrq.prewarm_dim", stack: PostgresError: invalid configuration parameter name "vchordrq.prewarm_dim" at ErrorResponse (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:790:26) at handle (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:476:6) at Socket.data (/opt/immich/app/node_modules/postgres/cjs/src/connection.js:315:9) at Socket.emit (node:events:518:28) at addChunk (node:internal/streams/readable:561:12) at readableAddChunkPushByteMode (node:internal/streams/readable:512:3) at Readable.push (node:internal/streams/readable:392:5) at TCP.onStreamRead (node:internal/stream_base_commons:189:23) microservices worker exited with code 1 Killing api process ``` ### 🖼️ Additional context (optional). I don't think the devs have a handle on this one yet. My solution worked, but then they introduced a new migration without testing it! And I was pretty sure it was going to break because when I worked the problem, the only solution I found was to backup the DB, strip out any mention of `vchord.prewarm_dim` and then restore.
OVERLORD added the bugexternal labels 2026-02-04 23:11:37 +03:00
OVERLORD commented 2026-02-04 23:11:45 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 19, 2025):

Reported to immich? Looks Like an issue of the new Version in core. That can be relevant for docker too

@MickLesk commented on GitHub (Jun 19, 2025): Reported to immich? Looks Like an issue of the new Version in core. That can be relevant for docker too
OVERLORD commented 2026-02-04 23:11:50 +03:00
Author
Owner
Copy Link

@nesalkiN commented on GitHub (Jun 19, 2025):

Reported to immich? Looks Like an issue of the new Version in core. That can be relevant for docker too

They know and yes, docker too..

@nesalkiN commented on GitHub (Jun 19, 2025): > Reported to immich? Looks Like an issue of the new Version in core. That can be relevant for docker too They know and yes, docker too..
OVERLORD commented 2026-02-04 23:11:55 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Jun 19, 2025):

I have a working fix. But I'm hesitant to push it because I bet the dev team's fix is going to break my fix.

I think soon they'll realize this is more of a problem than it appears, if they want to get rid of the "harmless" error messages. It requires a DB dump and restore. If they are OK with leaving the messages to spam the logs, then it's a simple matter of removing this migration.

@vhsdream commented on GitHub (Jun 19, 2025): I have a working fix. But I'm hesitant to push it because I bet the dev team's fix is going to break my fix. I think soon they'll realize this is more of a problem than it appears, __if__ they want to get rid of the "harmless" error messages. It requires a DB dump and restore. If they are OK with leaving the messages to spam the logs, then it's a simple matter of removing [this migration](https://github.com/immich-app/immich/blob/main/server/src/schema/migrations/1750323941566-UnsetPrewarmDimParameter.ts).
OVERLORD commented 2026-02-04 23:11:59 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Jun 19, 2025):

@MickLesk I'm currently testing whether a fresh install of 1.135.1 breaks, will let you know if we might need to pull the script.

@vhsdream commented on GitHub (Jun 19, 2025): @MickLesk I'm currently testing whether a fresh install of 1.135.1 breaks, will let you know if we might need to pull the script.
OVERLORD commented 2026-02-04 23:12:02 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Jun 19, 2025):

@MickLesk Unfortunately what they did breaks a brand new install of v1.135.1 😦

What do you think we should do? Pull the script or put out a fix?

@vhsdream commented on GitHub (Jun 19, 2025): @MickLesk Unfortunately what they did breaks a brand new install of v1.135.1 😦 What do you think we should do? Pull the script or put out a fix?
OVERLORD commented 2026-02-04 23:12:04 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 19, 2025):

New Script break too? Then we should backup the ct\sh to dont destroy all lxc

@MickLesk commented on GitHub (Jun 19, 2025): New Script break too? Then we should backup the ct\sh to dont destroy all lxc
OVERLORD commented 2026-02-04 23:12:11 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 19, 2025):

Or fix the Installer to 1.135? Its just an one liner

Example:
fetch_and_deploy_gh_release "immich" "immich/immich" "tarball" "v.1.135.0" "/opt/immich"

@MickLesk commented on GitHub (Jun 19, 2025): Or fix the Installer to 1.135? Its just an one liner Example: fetch_and_deploy_gh_release "immich" "immich/immich" "tarball" "v.1.135.0" "/opt/immich"
OVERLORD commented 2026-02-04 23:12:15 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 20, 2025):

its now fixed?

@MickLesk commented on GitHub (Jun 20, 2025): its now fixed?
OVERLORD commented 2026-02-04 23:12:17 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Jun 20, 2025):

@MickLesk In a sense, yes. If people choose to update then the script removes the migration. New installs are currently pinned to 1.135.0.

@vhsdream commented on GitHub (Jun 20, 2025): @MickLesk In a sense, yes. If people choose to update then the script removes the migration. New installs are currently pinned to 1.135.0.
OVERLORD commented 2026-02-04 23:12:19 +03:00
Author
Owner
Copy Link

@MadEyez commented on GitHub (Jun 20, 2025):

Is there a possibility to repair an already updated 1.135.1?
Didn't understand exactly what broke...

@MadEyez commented on GitHub (Jun 20, 2025): Is there a possibility to repair an already updated 1.135.1? Didn't understand exactly what broke...
OVERLORD commented 2026-02-04 23:12:21 +03:00
Author
Owner
Copy Link

@gursimarsethi commented on GitHub (Jun 20, 2025):

I believe if you update the script, i.e. install it again, it should fix itself

@gursimarsethi commented on GitHub (Jun 20, 2025): I believe if you update the script, i.e. install it again, it should fix itself
OVERLORD commented 2026-02-04 23:12:24 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 20, 2025):

Is there a possibility to repair an already updated 1.135.1?
Didn't understand exactly what broke...

Edit ~/.immich and Update the Version to .0 and Run Update again

@MickLesk commented on GitHub (Jun 20, 2025): > Is there a possibility to repair an already updated 1.135.1? > Didn't understand exactly what broke... Edit ~/.immich and Update the Version to .0 and Run Update again
OVERLORD commented 2026-02-04 23:12:28 +03:00
Author
Owner
Copy Link

@MadEyez commented on GitHub (Jun 20, 2025):

Didn't have time to try it. Update to 1.135.2 and/or script tweaks seem to have solved the issue.

@MadEyez commented on GitHub (Jun 20, 2025): Didn't have time to try it. Update to 1.135.2 and/or script tweaks seem to have solved the issue.
OVERLORD commented 2026-02-04 23:12:31 +03:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Jun 21, 2025):

Didn't have time to try it. Update to 1.135.2 and/or script tweaks seem to have solved the issue.

Jop, same here.

@pafade89 commented on GitHub (Jun 21, 2025): > Didn't have time to try it. Update to 1.135.2 and/or script tweaks seem to have solved the issue. Jop, same here.
OVERLORD commented 2026-02-04 23:12:34 +03:00
Author
Owner
Copy Link

@Basti-Fantasti commented on GitHub (Jun 22, 2025):

I can also confirm, that the script runs without issues on the now released v1.135.3

@Basti-Fantasti commented on GitHub (Jun 22, 2025): I can also confirm, that the script runs without issues on the now released v1.135.3
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug external
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1123
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?