[GH-ISSUE #7465] Error raised when using llama3.2 vision #66803

Closed
opened 2026-05-04 08:14:46 -05:00 by GiteaMirror · 11 comments
Owner

Originally created by @uzhao on GitHub (Nov 1, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7465

What is the issue?

ollama run x/llama3.2-vision:latest "describe this image: /home/papillon/Downloads/objectdetection.jpg"
Added image '/home/papillon/Downloads/objectdetection.jpg'
Error: POST predict: Post "http://127.0.0.1:32927/completion": EOF

ollama run x/llama3.2-vision:latest "hello"
Error: POST predict: Post "http://127.0.0.1:39683/completion": EOF

ollama run x/llama3.2-vision:latest

Hello
Error: POST predict: Post "http://127.0.0.1:39645/completion": EOF

OS

Linux

GPU

Nvidia

CPU

AMD

Ollama version

0.4.0-rc5

Originally created by @uzhao on GitHub (Nov 1, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7465 ### What is the issue? ollama run x/llama3.2-vision:latest "describe this image: /home/papillon/Downloads/objectdetection.jpg" Added image '/home/papillon/Downloads/objectdetection.jpg' Error: POST predict: Post "http://127.0.0.1:32927/completion": EOF ollama run x/llama3.2-vision:latest "hello" Error: POST predict: Post "http://127.0.0.1:39683/completion": EOF ollama run x/llama3.2-vision:latest >>> Hello Error: POST predict: Post "http://127.0.0.1:39645/completion": EOF ### OS Linux ### GPU Nvidia ### CPU AMD ### Ollama version 0.4.0-rc5
GiteaMirror added the bug label 2026-05-04 08:14:46 -05:00
Author
Owner

@jessegross commented on GitHub (Nov 1, 2024):

Can you please post the server logs?

<!-- gh-comment-id:2452520094 --> @jessegross commented on GitHub (Nov 1, 2024): Can you please post the [server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues)?
Author
Owner

@uzhao commented on GitHub (Nov 1, 2024):

Sure, here it is
[
ollama_logs.txt
](url)

<!-- gh-comment-id:2452526679 --> @uzhao commented on GitHub (Nov 1, 2024): Sure, here it is [ [ollama_logs.txt](https://github.com/user-attachments/files/17603810/ollama_logs.txt) ](url)
Author
Owner

@jessegross commented on GitHub (Nov 1, 2024):

Thanks for the logs. This looks mostly the same as #7440 although the log messages are slightly different. We are currently working on a fix for that and it will be available in rc7.

I think most likely it will solve your problem but would it be possible for you to test it when it comes out and report back to confirm?

<!-- gh-comment-id:2452566998 --> @jessegross commented on GitHub (Nov 1, 2024): Thanks for the logs. This looks mostly the same as #7440 although the log messages are slightly different. We are currently working on a fix for that and it will be available in rc7. I think most likely it will solve your problem but would it be possible for you to test it when it comes out and report back to confirm?
Author
Owner

@uzhao commented on GitHub (Nov 5, 2024):

It works now with rc8

<!-- gh-comment-id:2456045146 --> @uzhao commented on GitHub (Nov 5, 2024): It works now with rc8
Author
Owner

@theodufort commented on GitHub (Nov 7, 2024):

Thanks for the logs. This looks mostly the same as #7440 although the log messages are slightly different. We are currently working on a fix for that and it will be available in rc7.

I think most likely it will solve your problem but would it be possible for you to test it when it comes out and report back to confirm?

I am getting the same issue, is my only resort to build the rcx image manually?

<!-- gh-comment-id:2461133831 --> @theodufort commented on GitHub (Nov 7, 2024): > Thanks for the logs. This looks mostly the same as #7440 although the log messages are slightly different. We are currently working on a fix for that and it will be available in rc7. > > I think most likely it will solve your problem but would it be possible for you to test it when it comes out and report back to confirm? I am getting the same issue, is my only resort to build the rcx image manually?
Author
Owner

@jessegross commented on GitHub (Nov 7, 2024):

0.4.0 has been officially released and contains the fix, so you can just install it from the binaries on the download page.

<!-- gh-comment-id:2461138792 --> @jessegross commented on GitHub (Nov 7, 2024): 0.4.0 has been officially released and contains the fix, so you can just install it from the binaries on the download page.
Author
Owner

@theodufort commented on GitHub (Nov 7, 2024):

0.4.0 has been officially released and contains the fix, so you can just install it from the binaries on the download page.
Still not working for me on 0.0.4...

image

<!-- gh-comment-id:2462258773 --> @theodufort commented on GitHub (Nov 7, 2024): > 0.4.0 has been officially released and contains the fix, so you can just install it from the binaries on the download page. Still not working for me on 0.0.4... ![image](https://github.com/user-attachments/assets/00460684-2b6a-4938-8af2-87a2370e58e2)
Author
Owner

@theodufort commented on GitHub (Nov 7, 2024):

0.4.0 has been officially released and contains the fix, so you can just install it from the binaries on the download page.

It works on Windows but not on Linux

<!-- gh-comment-id:2462459376 --> @theodufort commented on GitHub (Nov 7, 2024): > 0.4.0 has been officially released and contains the fix, so you can just install it from the binaries on the download page. It works on Windows but not on Linux
Author
Owner

@jessegross commented on GitHub (Nov 7, 2024):

@theodufort Can you please post the full server logs?

There's a good chance it is the same as #7546, which was just fixed in main.

<!-- gh-comment-id:2462855010 --> @jessegross commented on GitHub (Nov 7, 2024): @theodufort Can you please post the full [server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues)? There's a good chance it is the same as #7546, which was just fixed in `main`.
Author
Owner

@theodufort commented on GitHub (Nov 7, 2024):

@theodufort Can you please post the full server logs?

There's a good chance it is the same as #7546, which was just fixed in main.
Here (I checked and doesn't seem to have any specific errors):
ollama_logs.txt

Here:

<!-- gh-comment-id:2463008564 --> @theodufort commented on GitHub (Nov 7, 2024): > @theodufort Can you please post the full [server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues)? > > There's a good chance it is the same as #7546, which was just fixed in `main`. Here (I checked and doesn't seem to have any specific errors): [ollama_logs.txt](https://github.com/user-attachments/files/17668100/ollama_logs.txt) Here:
Author
Owner

@jessegross commented on GitHub (Nov 7, 2024):

Thanks for the logs - this looks like it is the same as #7558 so we can track it there.

<!-- gh-comment-id:2463211176 --> @jessegross commented on GitHub (Nov 7, 2024): Thanks for the logs - this looks like it is the same as #7558 so we can track it there.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#66803