#ON CONFLICT DO UPDATE command cannot affect row a second time

1 messages · Page 1 of 1 (latest)

stray stratus
#

I am getting this error repeatedly in the syslog. This is a new install on a new NAS . How can I determine the issue and correct? Version is 1.106.4. Loges attached

ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time

PHOTOS 30081
VIDEOS 552
STORAGE 59G

lament badgeBOT
#

:wave: Hey @stray stratus,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: I have read applicable release notes.
  3. :blue_square: I have reviewed the FAQs for known issues.
  4. :blue_square: I have reviewed Github for known issues.
  5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
  7. :blue_square: I have 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)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

astral sand
#

What else are you running? That does not look like an error from Immich to me

stray stratus
#

Since the messages indicated a file exists (/volume1/docker/immich/postgres/pg_stat_tmp/db_0.stat) and the error stopped when I stopped the immich-postgres container I concluded it was the issue. However I am running portainer, ngnix proxy manager, watchtower, speedtest_tracker and tailscale as well (so 9 containers in all).

astral sand
stray stratus
#

Will review logs again. In the meantime I am rebuilding an system idex database (new to the UGOS NAS stuff) and I eliminated the docker immich folder. Will see if that is the issue and if so will close this out. Thanks

#

This is the other log message set (truncated):
2024-06-19T17:17:33.329545-07:00 DXP8800PLUS-913B pg_ctl[1762131]: 2024-06-19 18:17:33.328 MDT [1762131] ERROR: duplicate key value violates unique constraint "uni_file_search_info_file_path"
2024-06-19T17:17:33.329850-07:00 DXP8800PLUS-913B pg_ctl[1762131]: 2024-06-19 18:17:33.328 MDT [1762131] DETAIL: Key (file_path)=(/volume1/docker/immich/postgres/pg_stat_tmp/db_0.stat) already exists.
2024-06-19T17:17:33.329900-07:00 DXP8800PLUS-913B pg_ctl[1762131]: 2024-06-19 18:17:33.328 MDT [1762131] STATEMENT: INSERT INTO "file_search_info"

astral sand
#

This sounds more like errors from your NAS's control software

stray stratus
#

I agree in reviewing the log ... sigh.