Failed to Get All Albums: Error 500 ()

Receiving the following
pt@http://192.168.50.***:2283/_app/immutable/chunks/fetch-client.DqMPutSq.js:1:7999
@http://192.168.50.***
:2283/_app/immutable/chunks/fetch-client.DqMPutSq.js:1:7924
pt@http://192.168.50.***:2283/_app/immutable/chunks/fetch-client.DqMPutSq.js:1:7999
@http://192.168.50.***
:2283/_app/immutable/chunks/fetch-client.DqMPutSq.js:1:7924
After upgrading to the latest release. I've updated the docker-compose for the latest vchord and redis but don't think this is the issue?
6 Replies
Immich
Immich3mo ago
:wave: Hey @glueeater, 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 docs - Container Status: 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 Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :ballot_box_with_check: uploaded the relevant information (see below). 7. :ballot_box_with_check: 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 and 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 command, and re-open it later if needed.
glueeater
glueeaterOP3mo ago
Seems like it's in postgres…
Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-07-02 18:52:43.600 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-07-02 18:52:43.600 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-07-02 18:52:43.628 UTC [1] LOG: starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

2025-07-02 18:52:43.628 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432

2025-07-02 18:52:43.628 UTC [1] LOG: listening on IPv6 address "::", port 5432

2025-07-02 18:52:43.630 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2025-07-02 18:52:43.634 UTC [32] LOG: database system was interrupted; last known up at 2025-07-02 18:52:39 UTC

2025-07-02 18:52:43.696 UTC [32] LOG: database system was not properly shut down; automatic recovery in progress

2025-07-02 18:52:43.698 UTC [32] LOG: redo starts at 0/1951898

2025-07-02 18:52:43.698 UTC [32] LOG: invalid record length at 0/19519D0: wanted 24, got 0

2025-07-02 18:52:43.698 UTC [32] LOG: redo done at 0/1951898 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

2025-07-02 18:52:43.711 UTC [1] LOG: database system is ready to accept connections

2025-07-02 18:54:15.366 UTC [63] ERROR: current user cannot be dropped

2025-07-02 18:54:15.366 UTC [63] STATEMENT: DROP ROLE IF EXISTS postgres;

2025-07-02 18:54:15.366 UTC [63] ERROR: role "postgres" already exists

2025-07-02 18:54:15.366 UTC [63] STATEMENT: CREATE ROLE postgres;
Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-07-02 18:52:43.600 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-07-02 18:52:43.600 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-07-02 18:52:43.628 UTC [1] LOG: starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

2025-07-02 18:52:43.628 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432

2025-07-02 18:52:43.628 UTC [1] LOG: listening on IPv6 address "::", port 5432

2025-07-02 18:52:43.630 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2025-07-02 18:52:43.634 UTC [32] LOG: database system was interrupted; last known up at 2025-07-02 18:52:39 UTC

2025-07-02 18:52:43.696 UTC [32] LOG: database system was not properly shut down; automatic recovery in progress

2025-07-02 18:52:43.698 UTC [32] LOG: redo starts at 0/1951898

2025-07-02 18:52:43.698 UTC [32] LOG: invalid record length at 0/19519D0: wanted 24, got 0

2025-07-02 18:52:43.698 UTC [32] LOG: redo done at 0/1951898 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

2025-07-02 18:52:43.711 UTC [1] LOG: database system is ready to accept connections

2025-07-02 18:54:15.366 UTC [63] ERROR: current user cannot be dropped

2025-07-02 18:54:15.366 UTC [63] STATEMENT: DROP ROLE IF EXISTS postgres;

2025-07-02 18:54:15.366 UTC [63] ERROR: role "postgres" already exists

2025-07-02 18:54:15.366 UTC [63] STATEMENT: CREATE ROLE postgres;
Redis
1:M 02 Jul 2025 18:55:57.345 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it 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.

1:M 02 Jul 2025 18:55:57.345 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo

1:M 02 Jul 2025 18:55:57.345 * Valkey version=8.1.2, bits=64, commit=00000000, modified=0, pid=1, just started

1:M 02 Jul 2025 18:55:57.345 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf

1:M 02 Jul 2025 18:55:57.346 * Increased maximum number of open files to 10032 (it was originally set to 1024).

1:M 02 Jul 2025 18:55:57.346 * monotonic clock: POSIX clock_gettime

1:M 02 Jul 2025 18:55:57.346 * Running mode=standalone, port=6379.

1:M 02 Jul 2025 18:55:57.346 * Server initialized

1:M 02 Jul 2025 18:55:57.346 * Ready to accept connections tcp
1:M 02 Jul 2025 18:55:57.345 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it 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.

1:M 02 Jul 2025 18:55:57.345 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo

1:M 02 Jul 2025 18:55:57.345 * Valkey version=8.1.2, bits=64, commit=00000000, modified=0, pid=1, just started

1:M 02 Jul 2025 18:55:57.345 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf

1:M 02 Jul 2025 18:55:57.346 * Increased maximum number of open files to 10032 (it was originally set to 1024).

1:M 02 Jul 2025 18:55:57.346 * monotonic clock: POSIX clock_gettime

1:M 02 Jul 2025 18:55:57.346 * Running mode=standalone, port=6379.

1:M 02 Jul 2025 18:55:57.346 * Server initialized

1:M 02 Jul 2025 18:55:57.346 * Ready to accept connections tcp
Going to try to revert downward… Now I receive a failed to get all albums error?
Using SSD storage
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-07-02 19:03:07.973 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-07-02 19:03:07.973 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-07-02 19:03:07.999 UTC [1] LOG: starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-07-02 19:03:07.999 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-07-02 19:03:07.999 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-07-02 19:03:08.001 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-07-02 19:03:08.004 UTC [32] LOG: database system was interrupted; last known up at 2025-07-02 19:02:41 UTC
2025-07-02 19:03:08.109 UTC [32] LOG: database system was not properly shut down; automatic recovery in progress
2025-07-02 19:03:08.110 UTC [32] LOG: redo starts at 0/A9B23448
2025-07-02 19:03:08.110 UTC [32] LOG: invalid record length at 0/A9B23480: wanted 24, got 0
2025-07-02 19:03:08.110 UTC [32] LOG: redo done at 0/A9B23448 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-07-02 19:03:08.121 UTC [1] LOG: database system is ready to accept connections
Using SSD storage
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-07-02 19:03:07.973 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-07-02 19:03:07.973 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"
2025-07-02 19:03:07.999 UTC [1] LOG: starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-07-02 19:03:07.999 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-07-02 19:03:07.999 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-07-02 19:03:08.001 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-07-02 19:03:08.004 UTC [32] LOG: database system was interrupted; last known up at 2025-07-02 19:02:41 UTC
2025-07-02 19:03:08.109 UTC [32] LOG: database system was not properly shut down; automatic recovery in progress
2025-07-02 19:03:08.110 UTC [32] LOG: redo starts at 0/A9B23448
2025-07-02 19:03:08.110 UTC [32] LOG: invalid record length at 0/A9B23480: wanted 24, got 0
2025-07-02 19:03:08.110 UTC [32] LOG: redo done at 0/A9B23448 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-07-02 19:03:08.121 UTC [1] LOG: database system is ready to accept connections
hmm - i guess it may have been from changing to vectorchord 0.4.3 ? I'm trying to revert all the way back to v1.134.0 and switching back to vectorchord 0.3.0 OK so my immich server logs are normal - sharing here too but the postgres seems broken
glueeater
glueeaterOP3mo ago
rolling back to v1.133.1… oh this is new… it's showing me the onboarding prompts and not letting me login edit: managed to get the login back but stuck at the 500() errors i restarted the server and reverted everything back to 1.333.1 (also running vectorchord 0.3.0 image) everythings back to normal now? if anyone wants to read this for v1.135.x development - feel free to ping me if you need more info okay i just switched to v1.135.3 and it went fine (???)
database:
container_name: immich_postgres
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0@sha256:fa4f6e0971f454cd95fec5a9aaed2ed93d8f46725cc6bc61e0698e97dba96da1
environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_USER: ${DB_USERNAME}
POSTGRES_DB: ${DB_DATABASE_NAME}
POSTGRES_INITDB_ARGS: '--data-checksums'
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
restart: always
database:
container_name: immich_postgres
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0@sha256:fa4f6e0971f454cd95fec5a9aaed2ed93d8f46725cc6bc61e0698e97dba96da1
environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_USER: ${DB_USERNAME}
POSTGRES_DB: ${DB_DATABASE_NAME}
POSTGRES_INITDB_ARGS: '--data-checksums'
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
restart: always
This is the part I edited that apparently caused issues. 0.4.2 or 0.4.3 in the latest docker-compose.yml broke my system god speed everyone, please enjoy.
Immich
Immich3mo ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?