PG_Toast error
[Nest] 16 - 01/09/2025, 4:56:37 PM ERROR [Api:ErrorInterceptor~74564fkl] Database error: QueryFailedError: missing chunk number 0 for toast value 93227 in pg_toast_2619
[Nest] 16 - 01/09/2025, 4:56:37 PM ERROR [Api:ErrorInterceptor~2dmf3bgh] Database error: QueryFailedError: missing chunk number 0 for toast value 93227 in pg_toast_2619
[Nest] 16 - 01/09/2025, 4:56:37 PM ERROR [Api:ErrorInterceptor~3p3l8aan] Database error: QueryFailedError: missing chunk number 0 for toast value 93227 in pg_toast_2619
[Nest] 16 - 01/09/2025, 4:56:37 PM ERROR [Api:ErrorInterceptor~yvxzrmv5] Database error: QueryFailedError: missing chunk number 0 for toast value 93227 in pg_toast_2619
16 Replies
:wave: Hey @Yas,
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_01GY0DAKGXDEHE263BCAYEGFJAChecklist
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.GitHub
immich-app immich · Discussions
Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.
FAQ | Immich
User
GitHub
Issues · immich-app/immich
High performance self-hosted photo and video management solution. - Issues · immich-app/immich
Are you trying to restore a backup?
Power went out earlier, when I turned on my server the uploaded files are not loading - so I tried restoring a backup but still receiving the same error
[Nest] 16 - 01/09/2025, 4:56:37 PM ERROR [Api:ErrorInterceptor~74564fkl] Database error: QueryFailedError: missing chunk number 0 for toast value 93227 in pg_toast_2619
[Nest] 16 - 01/09/2025, 4:56:37 PM ERROR [Api:ErrorInterceptor~2dmf3bgh] Database error: QueryFailedError: missing chunk number 0 for toast value 93227 in pg_toast_2619
[Nest] 16 - 01/09/2025, 4:56:37 PM ERROR [Api:ErrorInterceptor~3p3l8aan] Database error: QueryFailedError: missing chunk number 0 for toast value 93227 in pg_toast_2619
[Nest] 16 - 01/09/2025, 4:56:37 PM ERROR [Api:ErrorInterceptor~yvxzrmv5] Database error: QueryFailedError: missing chunk number 0 for toast value 93227 in pg_toast_2619
Make sure you follow the restore steps precisely
Yes, I did it like 4x already
still the same
I am not sure what to do now as I already uploaded 1.4TB of my files, photos, videos to my immich server
The logs suggest you're trying to restore into a Postgres instance that already has a database in it
So you're not clearing it properly
Sorry for the noob question, but can you point out in the guide where I can see how to clear the database properly before restoring a backup?
ahh seen it now
need to figureout where is the db_data_location - found it, thanks will update if the issue persists
issue fixed, thanks a lot @bo0tzz
Any idea why I am receiving this error?
[Nest] 7 - 01/10/2025, 1:13:54 AM WARN [Microservices:MetadataService] Asset 4b30b2f0-9bb4-4337-b234-f6522d159c02 has no time zone information
[Nest] 7 - 01/10/2025, 1:13:58 AM ERROR [Microservices:JobService] Unable to run job handler (sidecar/sidecar-sync): Error: timeout exceeded when trying to connect
[Nest] 7 - 01/10/2025, 1:13:58 AM ERROR [Microservices:JobService] Error: timeout exceeded when trying to connect
at Timeout._onTimeout (/usr/src/app/node_modules/pg-pool/index.js:205:27)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7)
[Nest] 7 - 01/10/2025, 1:13:58 AM ERROR [Microservices:JobService] Object:
{
"id": "f16efd46-66b4-487e-ab51-a00e6f59bcc0"
}
[Nest] 7 - 01/10/2025, 1:13:59 AM WARN [Microservices:MetadataService] Asset 102fa9f2-f3aa-45b5-916f-627a492261cb has no time zone information
[Nest] 7 - 01/10/2025, 1:14:00 AM WARN [Microservices:MetadataService] Asset bae050e4-6d3e-4074-8e82-7a9b33d9af55 has no time zone information
[Nest] 7 - 01/10/2025, 1:14:00 AM WARN [Microservices:MetadataService] Asset f5ae8e07-731d-4fd3-930c-dd3092d10e5e has no time zone information
[Nest] 7 - 01/10/2025, 1:14:01 AM WARN [Microservices:MetadataService] Asset 3315fea7-3cb4-40e4-91b7-fcd941c456e2 has no time zone information
[Nest] 7 - 01/10/2025, 1:14:05 AM WARN [Microservices:MetadataService] Asset d6d95453-7544-44e7-a2b9-2d30f6b44555 has no time zone information
[Nest] 7 - 01/10/2025, 1:14:10 AM WARN [Microservices:MetadataService] Asset 8052ca94-1898-49d8-a4e4-6bad26cbbf86 has no time zone information
[Nest] 7 - 01/10/2025, 1:14:11 AM WARN [Microservices:MetadataService] Asset f9505c33-1a77-487f-977c-d14554571752 has no time zone information
[Nest] 7 - 01/10/2025, 1:14:14 AM ERROR [Microservices:JobService] Unable to run job handler (sidecar/sidecar-sync): Error: Connection terminated due to connection timeout
[Nest] 7 - 01/10/2025, 1:14:14 AM ERROR [Microservices:JobService] Error: Connection terminated due to connection timeout
at Connection.<anonymous> (/usr/src/app/node_modules/pg/lib/client.js:131:73)
at Object.onceWrapper (node:events:638:28)
at Connection.emit (node:events:524:28)
at Socket.<anonymous> (/usr/src/app/node_modules/pg/lib/connection.js:62:12)
at Socket.emit (node:events:524:28)
at TCP.<anonymous> (node:net:350:12)
[Nest] 7 - 01/10/2025, 1:14:14 AM ERROR [Microservices:JobService] Object:
{
"id": "6452ece5-19a9-4d84-8434-486b8351385a"
}
[Nest] 7 - 01/10/2025, 1:14:19 AM WARN [Microservices:MetadataService] Asset cf3756b7-8b3b-4c0c-be15-66096bebacb6 has no time zone information
[Nest] 7 - 01/10/2025, 1:14:21 AM ERROR [Microservices:JobService] Unable to run job handler (sidecar/sidecar-sync): Error: Connection terminated due to connection timeout
[Nest] 7 - 01/10/2025, 1:14:21 AM ERROR [Microservices:JobService] Error: Connection terminated due to connection timeout
at Connection.<anonymous> (/usr/src/app/node_modules/pg/lib/client.js:131:73)
at Object.onceWrapper (node:events:638:28)
at Connection.emit (node:events:524:28)
at Socket.<anonymous> (/usr/src/app/node_modules/pg/lib/connection.js:62:12)
at Socket.emit (node:events:524:28)
at TCP.<anonymous> (node:net:350:12)
[Nest] 7 - 01/10/2025, 1:14:21 AM ERROR [Microservices:JobService] Object:
{
"id": "9dec3477-40c9-4d4d-892e-d072d2c06072"
}
immich-server logs
Check the postgres logs again