HashtagOctothorp
HashtagOctothorp
Explore posts from servers
SSolidJSIImmich
PostsComments
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
*hacker voice* I'm in. Thanks for your help guys.
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
BUT! The backup from the existing auto-generated backups... *chefs kiss*
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
No description
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
Its gunna be an 8-9 hour break XD
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
Sounds like me in my youth... I was eating ~6000 calories a day and barely keeping the weight on.
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
but this is promising.
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
will pick up tonight after the kids are down.
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
kk. I'm going to pause for now becuase I REALLY need to do some work-work.
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
yall went straight to synology snapshots
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
No description
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
from here? 
docker compose down -v  # CAUTION! Deletes all Immich data to start from scratch
## Uncomment the next line and replace DB_DATA_LOCATION with your Postgres path to permanently reset the Postgres database
# rm -rf DB_DATA_LOCATION # CAUTION! Deletes all Immich data to start from scratch
docker compose pull             # Update to latest version of Immich (if desired)
docker compose create           # Create Docker containers for Immich apps without running them
docker start immich_postgres    # Start Postgres server
sleep 10                        # Wait for Postgres server to start up
# Check the database user if you deviated from the default
gunzip < "/path/to/backup/dump.sql.gz" \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --dbname=postgres --username=<DB_USERNAME>  # Restore Backup
docker compose up -d            # Start remainder of Immich apps
docker compose down -v  # CAUTION! Deletes all Immich data to start from scratch
## Uncomment the next line and replace DB_DATA_LOCATION with your Postgres path to permanently reset the Postgres database
# rm -rf DB_DATA_LOCATION # CAUTION! Deletes all Immich data to start from scratch
docker compose pull             # Update to latest version of Immich (if desired)
docker compose create           # Create Docker containers for Immich apps without running them
docker start immich_postgres    # Start Postgres server
sleep 10                        # Wait for Postgres server to start up
# Check the database user if you deviated from the default
gunzip < "/path/to/backup/dump.sql.gz" \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --dbname=postgres --username=<DB_USERNAME>  # Restore Backup
docker compose up -d            # Start remainder of Immich apps
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
nope
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
I didn't realize you wanted me not to do the main container when booting the pg container
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
oh sorry
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
hmmm... main container: 
[Nest] 7  - 03/17/2025, 11:37:08 AM     LOG [Microservices:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}

[Nest] 7  - 03/17/2025, 11:37:08 AM     LOG [Microservices:StorageService] Successfully verified system mount folder checks
[Nest] 7  - 03/17/2025, 11:37:08 AM     LOG [Microservices:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}

[Nest] 7  - 03/17/2025, 11:37:08 AM     LOG [Microservices:StorageService] Successfully verified system mount folder checks
But still "unhealthy", while the DB container says "starting" but normal log output 
2025-03-17 18:35:53.673 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-03-17 18:35:53.684 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-03-17 18:35:53.684 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-03-17 18:35:54.178 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-03-17 18:35:54.808 UTC [26] LOG:  database system was shut down at 2025-03-17 18:35:38 UTC
[2025-03-17T18:35:54Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17332".
[2025-03-17T18:35:54Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17576".
[2025-03-17T18:35:54Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17576/segments/ddb25af1-8278-4232-9e58-49c9e46c35cd".
[2025-03-17T18:35:54Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17332/segments/b89b74f3-8935-444d-9f8d-847f6a26fca1".
2025-03-17 18:35:55.186 UTC [1] LOG:  database system is ready to accept connections
2025-03-17 18:35:53.673 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-03-17 18:35:53.684 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-03-17 18:35:53.684 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-03-17 18:35:54.178 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-03-17 18:35:54.808 UTC [26] LOG:  database system was shut down at 2025-03-17 18:35:38 UTC
[2025-03-17T18:35:54Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17332".
[2025-03-17T18:35:54Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17576".
[2025-03-17T18:35:54Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17576/segments/ddb25af1-8278-4232-9e58-49c9e46c35cd".
[2025-03-17T18:35:54Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17332/segments/b89b74f3-8935-444d-9f8d-847f6a26fca1".
2025-03-17 18:35:55.186 UTC [1] LOG:  database system is ready to accept connections
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
recreating with default command, one sec, unless you want me to run the command manually
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
makes sense
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
Write-ahead log reset 🤞
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
yep
192 replies
IImmich
Created by HashtagOctothorp on 3/17/2025 in #help-desk-support
Corrupt database - any options? (Solution: use the backups Immich already saves by default)
that's what's in all the default .env files no?
192 replies