#Connection Refused After Update

1 messages · Page 1 of 1 (latest)

atomic surge
#

after an update I cannot access the application. there's seemingly no logs even though I set the IMMICH_LOG_LEVEL to verbose. where should I go from here?

novel caveBOT
#

:wave: Hey @atomic surge,

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

#

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.

atomic surge
#

the error appears to be in postgres with the following error:

$ docker exec -it immich-postgres pg_amcheck --username=postgres --heapallindexed --parent-check --rootdescend --progress --all --install
-missing
heap table "immich.public.user", block 0, offset 3:
    multitransaction ID 3921 equals or exceeds next valid multitransaction ID 3917
heap table "immich.public.user", block 1, offset 24:
    multitransaction ID 3927 equals or exceeds next valid multitransaction ID 3917
btree index "immich.public.user_pkey":
    ERROR:  MultiXactId 3921 has not been created yet -- apparent wraparound
btree index "immich.public.user_email_uq":
    ERROR:  MultiXactId 3921 has not been created yet -- apparent wraparound
btree index "immich.public.user_storageLabel_uq":
    ERROR:  MultiXactId 3921 has not been created yet -- apparent wraparound
btree index "immich.public.user_updatedAt_id_idx":
    ERROR:  MultiXactId 3921 has not been created yet -- apparent wraparound
btree index "immich.public.user_updateId_idx":
    ERROR:  MultiXactId 3921 has not been created yet -- apparent wraparound
1052/1052 relations (100%), 91371/91371 pages (100%)
novel caveBOT
rain vault
#

Your database is corrupted

#

You should restore from backup. Are you using a network storage or had any system crashes?

atomic surge
#

no and no

#

i got the web client back up and can view everything but not upload new images. is there any path of recovery? I've just stupidly done a lot of manual face tagging since my last backup

rain vault
#

there’s not a way to recover that level of database damage unless you pay a professional Postgres DB admin firm

#

Your storage device might be failing