Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5470] [BUG]: Can't download model from ollama #5110

New Issue
Closed
opened 2026-06-05 14:52:03 -04:00 by yindo · 1 comment
yindo commented 2026-06-05 14:52:03 -04:00
Owner
Copy Link
Copy Source

Originally created by @R-Josef on GitHub (Apr 19, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5470

How are you running AnythingLLM?

Docker (local)

What happened?

I am trying to download model from ollama, in LLM Preference, by input "ollama run qwen3.5:35b-a3b-q4_K_M" and press enter.

But nothing will be downloaded, No bandwith in Windows task manager from AnythingLLM, it actually stuck.

I also tried run the program through CMD to check debug log, here is the output:

[backend] info: [AnythingLLMOllama] Applying custom fetch w/timeout of 10 minutes.
[backend] info: [NativeEmbedder] Initialized Xenova/all-MiniLM-L6-v2
[backend] info: [AnythingLLMOllama] initialized with model: qwen3.5:35b-a3b-q4_K_M
[backend] info: [AnythingLLMOllama] Context windows cached for all models!
[backend] info: [AnythingLLMOllama] Applying custom fetch w/timeout of 10 minutes.
[backend] info: [NativeEmbedder] Initialized Xenova/all-MiniLM-L6-v2
[backend] info: [AnythingLLMOllama] initialized with model: qwen3.5:35b-a3b-q4_K_M
[backend] info: [AnythingLLMOllama] Starting pull of model tag "qwen3.5:35b-a3b-q4_k_m".
[backend] info: [AnythingLLMOllama] Context windows cached for all models!
prisma:info Starting a sqlite pool with 33 connections.
[backend] info: [41720:17172]: No direct uploads path found - exiting.
[bg-worker][cleanup-orphan-documents] info: [41720:17172]: No direct uploads path found - exiting.
[backend] warn: Child process exited with code 0 and signal null
[backend] info: Worker for job "cleanup-orphan-documents" exited with code 0
prisma:info Starting a sqlite pool with 33 connections.
[backend] warn: Child process exited with code 0 and signal null

I think it may not the network problem, because i tried to download the model directly by curl

curl -L "https://registry.ollama.ai/v2/library/qwen3.5/blobs/sha256:900dde62fb7ebe8a5a25e35d5b7633f403f226a310965fed51d50f5238ba145a" -o "sha256-900dde62fb7ebe8a5a25e35d5b7633f403f226a310965fed51d50f5238ba145a"
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
  0      0   0      0   0      0      0      0           00:02              0
 15 22.22G  15  3.39G   0      0  6.56M      0   57:44   08:49   48:55      0
curl: (56) Recv failure: Connection was reset

With curl: I can at least initiate the download and see data being transferred (as shown in the log, it reached ~3.39GB before the connection was reset). This proves the registry is reachable from my network.

With AnythingLLM: There is zero network activity shown in the Windows Task Manager. It seems to be completely stuck at the "Starting pull" stage without ever initiating a data transfer.

Are there known steps to reproduce?

No response

LLM Provider & Model (if applicable)

No response

Embedder Provider & Model (if applicable)

No response

Originally created by @R-Josef on GitHub (Apr 19, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5470 ### How are you running AnythingLLM? Docker (local) ### What happened? I am trying to download model from ollama, in LLM Preference, by input "ollama run qwen3.5:35b-a3b-q4_K_M" and press enter. But nothing will be downloaded, No bandwith in Windows task manager from AnythingLLM, it actually stuck. I also tried run the program through CMD to check debug log, here is the output: ``` [backend] info: [AnythingLLMOllama] Applying custom fetch w/timeout of 10 minutes. [backend] info: [NativeEmbedder] Initialized Xenova/all-MiniLM-L6-v2 [backend] info: [AnythingLLMOllama] initialized with model: qwen3.5:35b-a3b-q4_K_M [backend] info: [AnythingLLMOllama] Context windows cached for all models! [backend] info: [AnythingLLMOllama] Applying custom fetch w/timeout of 10 minutes. [backend] info: [NativeEmbedder] Initialized Xenova/all-MiniLM-L6-v2 [backend] info: [AnythingLLMOllama] initialized with model: qwen3.5:35b-a3b-q4_K_M [backend] info: [AnythingLLMOllama] Starting pull of model tag "qwen3.5:35b-a3b-q4_k_m". [backend] info: [AnythingLLMOllama] Context windows cached for all models! prisma:info Starting a sqlite pool with 33 connections. [backend] info: [41720:17172]: No direct uploads path found - exiting. [bg-worker][cleanup-orphan-documents] info: [41720:17172]: No direct uploads path found - exiting. [backend] warn: Child process exited with code 0 and signal null [backend] info: Worker for job "cleanup-orphan-documents" exited with code 0 prisma:info Starting a sqlite pool with 33 connections. [backend] warn: Child process exited with code 0 and signal null ``` I think it may not the network problem, because i tried to download the model directly by curl ``` curl -L "https://registry.ollama.ai/v2/library/qwen3.5/blobs/sha256:900dde62fb7ebe8a5a25e35d5b7633f403f226a310965fed51d50f5238ba145a" -o "sha256-900dde62fb7ebe8a5a25e35d5b7633f403f226a310965fed51d50f5238ba145a" % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 00:02 0 15 22.22G 15 3.39G 0 0 6.56M 0 57:44 08:49 48:55 0 curl: (56) Recv failure: Connection was reset ``` With curl: I can at least initiate the download and see data being transferred (as shown in the log, it reached ~3.39GB before the connection was reset). This proves the registry is reachable from my network. With AnythingLLM: There is zero network activity shown in the Windows Task Manager. It seems to be completely stuck at the "Starting pull" stage without ever initiating a data transfer. ### Are there known steps to reproduce? _No response_ ### LLM Provider & Model (if applicable) _No response_ ### Embedder Provider & Model (if applicable) _No response_
yindo added the possible bug label 2026-06-05 14:52:03 -04:00
yindo closed this issue 2026-06-05 14:52:03 -04:00
yindo commented 2026-06-05 14:52:03 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 20, 2026):

This is fixed already in future update. The reason is the current ollama version (intentionally) is behind the main ollama version for stability guarantees.

Either way, it is bumped already and to be released

<!-- gh-comment-id:4282204141 --> @timothycarambat commented on GitHub (Apr 20, 2026): This is fixed already in future update. The reason is the current ollama version (intentionally) is behind the main ollama version for stability guarantees. Either way, it is bumped already and to be released
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5110
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?