-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import stop on any failure, FR: add a retry option #699
Comments
Apparently there easy "Internal Errors" where the server replies immediately, and immich-go may do something smart with the error. A long timeout is needed to give to the server enough time to process large files. The server remains quite during long minutes. At the moment, I try to find conditions (or logical errors in the immich-go code) that lead this kind of freezing errors. |
Absolutely, they appear to be quite random, and that would make sense from your point of view if they are server-side. Thing is, in my case, I run it on 180k medias, so it always fails over time, and I run into some edge cases like #700 #701 #703 and actually #706 (sorry!). #700 / #699 (mines) and #706 seem to be the same issue though. The UI isn't condusive of whether immich-go is hanging waiting for the server, or simply had stopped, so I killed immich-go and restarted over afer a while. Regardless, 2 nights I went to bed with immich-go running to wake up to the error, meaning it probably hanged for hours, instead of timing out and retrying.
I'm restarting now with |
Grab the server log as well |
Hi there,
I'm on my way to upload my 177k (!) pictures, and unfortunately at the first sign of failure... the whole program stops and doesn't go forward. Between the "immich content" step and the "google photo puzzle" steps, it takes already more than 1h to go back to the same step.
Sounds like there should be an option to either:
In particular now, I'm facing an Internal Server Error on a file and not sure I can ever go beyond that. (Filing a separate issue right now)
The text was updated successfully, but these errors were encountered: