Immich•7mo ago

rpi - Upgrade from 1.25.7 to 1.34.0, immich_postgres fails to start with latest postgres image

I'm running on a pi 5 with an external hdd (ext4). I am attempting to upgrade to 1.34.0 and see that in 1.33.0, the postgres image changed. I'm using the stock docker-compose yaml. With the updated redis to valkey, there are no issues. When I make the change to use the latest docker-compose file, the immich_postgres container fails to start with the following error:

Using HDD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-02 15:59:05.863 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-02 15:59:05.864 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
memory allocation of 16 bytes failed

Using HDD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-02 15:59:05.863 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-02 15:59:05.864 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
memory allocation of 16 bytes failed

Using HDD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-02 15:59:05.863 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-02 15:59:05.864 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
memory allocation of 16 bytes failed

Using HDD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-02 15:59:05.863 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-06-02 15:59:05.864 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
memory allocation of 16 bytes failed

I saw a few other github issues around this, but none were current or really even in the immich repo.

I saw that the previous db image will be supported for a while and that's what I left in for now to keep the system up and running, but I'd like to get on the new image if possible to stay in lock step with the releases.

I am not sure if starting from a fresh instance and restoring the db would help fix this. It's something I could try (hoping I don't screw it up somehow and blow all my data away).

Any help would be appreciated!

Immich•6/3/25, 4:51 PM

:wave: Hey @lawnjarae,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.

References

Container Logs:
```
docker compose logs
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
docker ps -a
```
docs
Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA

Immich•6/3/25, 4:51 PM

Checklist

I have...

:ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
:ballot_box_with_check: read applicable release notes.
:ballot_box_with_check: reviewed the FAQs for known issues.
:ballot_box_with_check: reviewed Github for known issues.
:blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
:ballot_box_with_check: uploaded the relevant information (see below).
:blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

Your docker-compose.yml and .env files.
Logs from all the containers and their status (see above).
All the troubleshooting steps you've tried so far.
Any recent changes you've made to Immich or your system.
Details about your system (both software/OS and hardware).
Details about your storage (filesystems, type of disks, output of commands like
```
fdisk -l
```
```
fdisk -l
```
and
```
df -h
```
```
df -h
```
).
The version of the Immich server, mobile app, and other relevant pieces.
Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the

/close

/close

command, and re-open it later if needed.

Mraedis•6/3/25, 9:00 PM

Please post your compose/env

lawnjaraeOP•6/3/25, 9:12 PM

The compose file is the exact same that's in the 1.34.0 release. No changes. I'll grab the .env file in a few mins.

Mraedis•6/4/25, 5:43 AM

Alright please post the output of getconf PAGE_SIZEgetconf PAGE_SIZE @lawnjarae

Mraedis•6/4/25, 5:43 AM

on the Pi

lawnjaraeOP•6/4/25, 1:22 PM

page_size = 16384

lawnjaraeOP•6/4/25, 1:25 PM

# The location where your uploaded files are stored
UPLOAD_LOCATION=/data/Expansion/immich
# The location where your database files are stored
DB_DATA_LOCATION=/data/Expansion/immich-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_zones#List
TZ=America/Denver

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=v1.134.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=postgres

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

# The location where your uploaded files are stored
UPLOAD_LOCATION=/data/Expansion/immich
# The location where your database files are stored
DB_DATA_LOCATION=/data/Expansion/immich-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_zones#List
TZ=America/Denver

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=v1.134.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=postgres

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

Where /data/Expansion is the external drive. I can get more details on that if need be, but it's just an ext4 formatted drive. No issues with old database image.

lawnjaraeOP•6/4/25, 4:26 PM

Just tried starting from scratch via the backup and restore method with the docker-compose.ymldocker-compose.yml file that's tagged to 1.34.0. docker start immich_postgresdocker start immich_postgres still produces the same page size error. This error shows up even before I add the data back into the db. The container itself spits the error.

Mraedis•6/4/25, 7:57 PM

Did you ever mess with page size or jemalloc @lawnjarae ?

Mraedis•6/4/25, 7:57 PM

Actually what OS image is on your Pi

mertalev•6/4/25, 8:46 PM

It's weird because pgvecto.rs already uses jemalloc, so I guess the new image has a different build of jemalloc? vchord doesn't use jemalloc (it uses mimalloc, also used in other immich containers).

Assuming there's no problem with mimalloc, it might be possible to do a manual migration (see the section for when both extensions can't exist at the same time) starting with your existing db image. In step 3, change the image to ghcr.io/immich-app/postgres:14-vectorchord0.3.0ghcr.io/immich-app/postgres:14-vectorchord0.3.0 before running the remaining SQL commands

mertalev•6/4/25, 8:46 PM

Of course, make a db backup first

Mraedis•6/4/25, 9:12 PM

Just wondering why this is the first RPi5 report on this because I know there are many out there

mertalev•6/4/25, 9:14 PM

Maybe different kernels idk

Mraedis•6/4/25, 9:14 PM

Yeah that's why I asked about the pi's image

Mraedis•6/4/25, 9:15 PM

Looking at similar reports for certain linux distros and Home Assistant Supervisor

mertalev•6/4/25, 9:18 PM

I very vaguely remember something about some builds making 64 divisible allocations because it works for more system page sizes or something

Mraedis•6/4/25, 9:20 PM

Might get around it by setting page size to 4kb instead of 16

lawnjaraeOP•6/4/25, 11:10 PM

Sorry for the delay! I am running a stock pi 5. Linux raspberrypi 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/LinuxLinux raspberrypi 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux

lawnjaraeOP•6/4/25, 11:13 PM

Immich is really the only main service I'm running on there. Though I'd like to run more in the future. So Docker is on there, but I haven't really been messing about with much on this machine.

lawnjaraeOP•6/4/25, 11:17 PM

Just did the random software updates today, actually. But the same issue was seen the other day before those updates were rolled in.

Mraedis•6/5/25, 6:09 AM

I haven't found anything specific related to postgres but try mert's suggestion first @lawnjarae and if that doesn't work you could "simply" set kernel=kernel8.imgkernel=kernel8.img in /boot/config.txt/boot/config.txt

k2helix•6/19/25, 2:45 PM

I'm getting this exact error after upgrading to v1.135.0 and changing the database from ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0 to ghcr.io/immich-app/postgres:14-vectorchord0.4.1-pgvectors0.2.0ghcr.io/immich-app/postgres:14-vectorchord0.4.1-pgvectors0.2.0. Using 0.3.0 seems to work fine

k2helix•6/19/25, 2:45 PM

Also running on a Pi 5

mertalev•6/19/25, 2:47 PM

It's an upstream issue. You can follow https://github.com/tensorchord/VectorChord/issues/277 to see if/how this will be resolved

k2helix•6/19/25, 7:08 PM

I see, thanks for pointing it out

rpi - Upgrade from 1.25.7 to 1.34.0, immich_postgres fails to start with latest postgres image

References

Checklist

Information

Similar Threads

Similar Threads

References

Checklist

Information

Similar Threads