meh
meh
PostsComments
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
Thanks
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
No description
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
server logs - don't see any errors yet
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
seems fine ?
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
DB LOG: 
2025-05-05T17:20:53.861208677Z 2025-05-05 17:20:53.861 UTC [1] LOG:  starting PostgreSQL 14.10 (Debian 14.10-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-05-05T17:20:53.887600276Z 2025-05-05 17:20:53.887 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-05-05T17:20:53.887621115Z 2025-05-05 17:20:53.887 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-05-05T17:20:53.894987296Z 2025-05-05 17:20:53.894 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-05-05T17:20:53.930468695Z 2025-05-05 17:20:53.930 UTC [26] LOG:  database system was shut down at 2025-05-05 17:20:53 UTC
2025-05-05T17:20:53.932760537Z [2025-05-05T17:20:53Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/375256".
2025-05-05T17:20:53.932781211Z [2025-05-05T17:20:53Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/375259".
2025-05-05T17:20:53.932787532Z [2025-05-05T17:20:53Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/375259/segments/0d37214e-dba8-4a61-9d17-c76a580e744c".
2025-05-05T17:20:53.937184875Z [2025-05-05T17:20:53Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/375256/segments/c53e83d4-d88e-4fde-bad3-f6766b291bd3".
2025-05-05T17:20:53.954127445Z 2025-05-05 17:20:53.954 UTC [1] LOG:  database system is ready to accept connections
2025-05-05T17:20:53.861208677Z 2025-05-05 17:20:53.861 UTC [1] LOG:  starting PostgreSQL 14.10 (Debian 14.10-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-05-05T17:20:53.887600276Z 2025-05-05 17:20:53.887 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-05-05T17:20:53.887621115Z 2025-05-05 17:20:53.887 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-05-05T17:20:53.894987296Z 2025-05-05 17:20:53.894 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-05-05T17:20:53.930468695Z 2025-05-05 17:20:53.930 UTC [26] LOG:  database system was shut down at 2025-05-05 17:20:53 UTC
2025-05-05T17:20:53.932760537Z [2025-05-05T17:20:53Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/375256".
2025-05-05T17:20:53.932781211Z [2025-05-05T17:20:53Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/375259".
2025-05-05T17:20:53.932787532Z [2025-05-05T17:20:53Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/375259/segments/0d37214e-dba8-4a61-9d17-c76a580e744c".
2025-05-05T17:20:53.937184875Z [2025-05-05T17:20:53Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/375256/segments/c53e83d4-d88e-4fde-bad3-f6766b291bd3".
2025-05-05T17:20:53.954127445Z 2025-05-05 17:20:53.954 UTC [1] LOG:  database system is ready to accept connections
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
Restarted containers
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
cause in DB the last log I see is which makes sense but nothing after: 
2025-05-05T17:12:44.080771404Z 2025-05-05 17:12:44.080 UTC [3219] ERROR:  syntax error at or near "DATABASE" at character 26
2025-05-05T17:12:44.080848389Z 2025-05-05 17:12:44.080 UTC [3219] STATEMENT:  REINDEX DATABASE
2025-05-05T17:12:44.080897559Z     REINDEX DATABASE;
2025-05-05T17:13:03.048711641Z 2025-05-05 17:13:03.048 UTC [3219] ERROR:  syntax error at or near ";" at character 17
2025-05-05T17:13:03.048786338Z 2025-05-05 17:13:03.048 UTC [3219] STATEMENT:  REINDEX DATABASE;
2025-05-05T17:12:44.080771404Z 2025-05-05 17:12:44.080 UTC [3219] ERROR:  syntax error at or near "DATABASE" at character 26
2025-05-05T17:12:44.080848389Z 2025-05-05 17:12:44.080 UTC [3219] STATEMENT:  REINDEX DATABASE
2025-05-05T17:12:44.080897559Z     REINDEX DATABASE;
2025-05-05T17:13:03.048711641Z 2025-05-05 17:13:03.048 UTC [3219] ERROR:  syntax error at or near ";" at character 17
2025-05-05T17:13:03.048786338Z 2025-05-05 17:13:03.048 UTC [3219] STATEMENT:  REINDEX DATABASE;
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
should I restart the containers ?
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
checking
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
done
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
immich=# REINDEX DATABASE immich; REINDEX immich=#
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
Its doing something waiting.
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
so in my case would be REINDEX immich; ?
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
i assuming the database is the database name
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
sorry 
immich-# REINDEX DATABASE;
ERROR:  syntax error at or near "DATABASE"
LINE 2: REINDEX DATABASE;
                ^
immich=# REINDEX DATABASE;
ERROR:  syntax error at or near ";"
LINE 1: REINDEX DATABASE;
                        ^
immich=#
immich-# REINDEX DATABASE;
ERROR:  syntax error at or near "DATABASE"
LINE 2: REINDEX DATABASE;
                ^
immich=# REINDEX DATABASE;
ERROR:  syntax error at or near ";"
LINE 1: REINDEX DATABASE;
                        ^
immich=#
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
server:~$ docker exec -it immich_postgres psql --dbname=***--username=**
psql (14.10 (Debian 14.10-1.pgdg120+1))
Type "help" for help.

immich=# REINDEX DATABASE
immich-#
server:~$ docker exec -it immich_postgres psql --dbname=***--username=**
psql (14.10 (Debian 14.10-1.pgdg120+1))
Type "help" for help.

immich=# REINDEX DATABASE
immich-#
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
So...as I was thinking about how to proceed (cautiously) it somewhat fixed itself (I haven't done anything yet). I am able to access the service, latest images are uploaded from my mobile but showing corrupted in the webview and below errors are in the logs. should I try to upgrade to the latest version ? Immich server excerpt: 
2025-05-05T15:12:28.646611853Z [Nest] 17  - 05/05/2025, 3:12:28 PM   ERROR [Api:ErrorInterceptor~bpaar13q] Unknown error: PostgresError: index "IDX_asset_exif_update_id" contains unexpected zero page at block 53
2025-05-05T15:12:28.646617072Z PostgresError: index "IDX_asset_exif_update_id" contains unexpected zero page at block 53
2025-05-05T15:12:28.646621168Z     at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)
2025-05-05T15:12:28.646624997Z     at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)
2025-05-05T15:12:28.646628892Z     at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)
2025-05-05T15:12:28.646632973Z     at Socket.emit (node:events:518:28)
2025-05-05T15:12:28.646636655Z     at addChunk (node:internal/streams/readable:561:12)
2025-05-05T15:12:28.646640576Z     at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
2025-05-05T15:12:28.646645149Z     at Readable.push (node:internal/streams/readable:392:5)
2025-05-05T15:12:28.646649293Z     at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-05T15:12:28.646653107Z     at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
2025-05-05T16:55:42.937808673Z [Nest] 17  - 05/05/2025, 4:55:42 PM     LOG [Api:EventRepository] Websocket Connect:    -yZLThB3sQitvWyEAAAF
2025-05-05T16:55:53.350879300Z [Nest] 17  - 05/05/2025, 4:55:53 PM     LOG [Api:EventRepository] Websocket Disconnect: -yZLThB3sQitvWyEAAAF
2025-05-05T16:57:11.672137410Z [Nest] 17  - 05/05/2025, 4:57:11 PM     LOG [Api:EventRepository] Websocket Connect:    PSNAVQZ9UFC0OB19AAAH
2025-05-05T15:12:28.646611853Z [Nest] 17  - 05/05/2025, 3:12:28 PM   ERROR [Api:ErrorInterceptor~bpaar13q] Unknown error: PostgresError: index "IDX_asset_exif_update_id" contains unexpected zero page at block 53
2025-05-05T15:12:28.646617072Z PostgresError: index "IDX_asset_exif_update_id" contains unexpected zero page at block 53
2025-05-05T15:12:28.646621168Z     at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)
2025-05-05T15:12:28.646624997Z     at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)
2025-05-05T15:12:28.646628892Z     at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)
2025-05-05T15:12:28.646632973Z     at Socket.emit (node:events:518:28)
2025-05-05T15:12:28.646636655Z     at addChunk (node:internal/streams/readable:561:12)
2025-05-05T15:12:28.646640576Z     at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
2025-05-05T15:12:28.646645149Z     at Readable.push (node:internal/streams/readable:392:5)
2025-05-05T15:12:28.646649293Z     at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
2025-05-05T15:12:28.646653107Z     at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
2025-05-05T16:55:42.937808673Z [Nest] 17  - 05/05/2025, 4:55:42 PM     LOG [Api:EventRepository] Websocket Connect:    -yZLThB3sQitvWyEAAAF
2025-05-05T16:55:53.350879300Z [Nest] 17  - 05/05/2025, 4:55:53 PM     LOG [Api:EventRepository] Websocket Disconnect: -yZLThB3sQitvWyEAAAF
2025-05-05T16:57:11.672137410Z [Nest] 17  - 05/05/2025, 4:57:11 PM     LOG [Api:EventRepository] Websocket Connect:    PSNAVQZ9UFC0OB19AAAH
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
And is my issue similar to this ? https://discord.com/channels/979116623879368755/1367564549561126993 Which may be fixed without a reinstall?
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
So essentially this is a new install with a restore of old DB ?
66 replies
IImmich
Created by meh on 4/27/2025 in #help-desk-support
Upgraded to latest version and getting DB error suddenly
I'm assuming the new stack should have non default volume location and name so it doesn't mess up the old stack?
66 replies