mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-12 01:54:38 -05:00
Tolerate interrupted model downloads #173
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @robertvazan on GitHub (Jan 12, 2024).
Bug Report
Description
Bug Summary:
If model download is interrupted (perhaps by restarting ollama as a workaround to #456), WebUI gets stuck on the download. It is impossible to retry the download nor is it possible to download anything else. The problem persists after WebUI restart.
Steps to Reproduce:
Expected Behavior:
Download status is cleared and new download attempts are possible.
Actual Behavior:
UI is stuck in download state with progress bar and with download button disabled. This state persists after WebUI restart.
Reproduction Details
Confirmation:
@robertvazan commented on GitHub (Jan 12, 2024):
Update: The stuck download disappears and new model downloads are possible after some time. This seems to be due to timeout rather than any user action.
@justinh-rahb commented on GitHub (Jan 18, 2024):
Lately, while working with larger models, I have encountered some disruptions due to my WAN failing over to backup. If the download progress doesn't vanish by itself eventually during these events, refreshing the page resolves it; however, upon re-downloading the model, the progress bar returns but has restarted progress automatically. Interestingly, should you close or refresh Ollama WebUI during this time, inputting the previously downloading model name will bring back the progress bar. It appears that in these instances, the background task can restart itself and persists as Ollama continues to download without needing a full reset. I have been unable to reproduce any permanently stuck downloads so far; at worst, refreshing and starting over has sufficed.
@robertvazan commented on GitHub (Jan 18, 2024):
I cannot reproduce this anymore. Has anything changed that could have an effect on the issue?
@tjbck commented on GitHub (Jan 18, 2024):
@robertvazan not that I know of 😅, I'll close this issue then!