[GH-ISSUE #3876] serving llama3 does not work #48914

Closed
opened 2026-04-28 10:01:54 -05:00 by GiteaMirror · 9 comments
Owner

Originally created by @lambdaofgod on GitHub (Apr 24, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3876

What is the issue?

I am able to run llama 3 (ollama run llama3) but when I try to run the server I get

{"error":"model 'llama3' not found, try pulling it first"}

This is in spite of ollama list detecting the model.

Specifically I ran

curl $LLAMA_URL -d '{
  "model": "llama3",      
  "messages": [
    { "role": "user", "content": "why is the sky blue?" }
  ]
}'

OS

Linux

GPU

No response

CPU

No response

Ollama version

0.1.32

Originally created by @lambdaofgod on GitHub (Apr 24, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3876 ### What is the issue? I am able to run llama 3 (`ollama run llama3`) but when I try to run the server I get >{"error":"model 'llama3' not found, try pulling it first"} This is in spite of `ollama list` detecting the model. Specifically I ran ``` curl $LLAMA_URL -d '{ "model": "llama3", "messages": [ { "role": "user", "content": "why is the sky blue?" } ] }' ``` ### OS Linux ### GPU _No response_ ### CPU _No response_ ### Ollama version 0.1.32
GiteaMirror added the bug label 2026-04-28 10:01:54 -05:00
Author
Owner

@EverThingy commented on GitHub (Apr 25, 2024):

Can you try adding a tag to the model parameter (by default it's latest)

curl $LLAMA_URL -d '{
  "model": "llama3:latest",      
  "messages": [
    { "role": "user", "content": "why is the sky blue?" }
  ]
}'
<!-- gh-comment-id:2076689276 --> @EverThingy commented on GitHub (Apr 25, 2024): Can you try adding a tag to the model parameter (by default it's `latest`) ```sh curl $LLAMA_URL -d '{ "model": "llama3:latest", "messages": [ { "role": "user", "content": "why is the sky blue?" } ] }' ```
Author
Owner

@lambdaofgod commented on GitHub (Apr 25, 2024):

That's weird, that was the first thing I tried and it didn't work. Must have been fixed by an update.
Thanks!

<!-- gh-comment-id:2076709925 --> @lambdaofgod commented on GitHub (Apr 25, 2024): That's weird, that was the first thing I tried and it didn't work. Must have been fixed by an update. Thanks!
Author
Owner

@sridvijay commented on GitHub (Apr 26, 2024):

I'm still running into the same issue. I've tried llama3 as well as llama3:latest and still get the same error:

model 'llama3' not found, try pulling it first.

When I run ollama list, I do see the model:

ollama list
NAME            ID              SIZE    MODIFIED    
llama3:latest   a6990ed6be41    4.7 GB  5 hours ago

I've tried reinstalling ollama as well, but no luck either :/

This is running on Ubuntu 20.04 running ollama 0.1.32

EDIT:

I solved it by running curl -X POST http://localhost:[port]/api/pull -d '{"model":"llama3"}'.

Not sure what I got wrong here, as I thought doing ollama pull llama3 in the command line would result in the same thing, but I guess the models are stored separately if you want to serve? Not sure, but it works!

<!-- gh-comment-id:2078364129 --> @sridvijay commented on GitHub (Apr 26, 2024): I'm still running into the same issue. I've tried `llama3` as well as `llama3:latest` and still get the same error: `model 'llama3' not found, try pulling it first`. When I run `ollama list`, I do see the model: ``` ollama list NAME ID SIZE MODIFIED llama3:latest a6990ed6be41 4.7 GB 5 hours ago ``` I've tried reinstalling `ollama` as well, but no luck either :/ This is running on Ubuntu 20.04 running ollama 0.1.32 EDIT: I solved it by running `curl -X POST http://localhost:[port]/api/pull -d '{"model":"llama3"}'`. Not sure what I got wrong here, as I thought doing `ollama pull llama3` in the command line would result in the same thing, but I guess the models are stored separately if you want to serve? Not sure, but it works!
Author
Owner

@lambdaofgod commented on GitHub (Apr 26, 2024):

@sridvijay this basically solves it, thanks! I've updated FAQ accordingly in #3936

<!-- gh-comment-id:2078967093 --> @lambdaofgod commented on GitHub (Apr 26, 2024): @sridvijay this basically solves it, thanks! I've updated FAQ accordingly in #3936
Author
Owner

@m-aliabbas commented on GitHub (May 29, 2024):

same error. not solved

<!-- gh-comment-id:2137437034 --> @m-aliabbas commented on GitHub (May 29, 2024): same error. not solved
Author
Owner

@whichxjy commented on GitHub (Jul 2, 2024):

I met the same error. It seems to be related to the model file path.

<!-- gh-comment-id:2202548939 --> @whichxjy commented on GitHub (Jul 2, 2024): I met the same error. It seems to be related to the model file path.
Author
Owner

@sunaigo commented on GitHub (Sep 23, 2024):

meybe ollama can only access user "ollama",and your serve user is not ollama, if your ps -ef can see the serve user is ollama

<!-- gh-comment-id:2367147627 --> @sunaigo commented on GitHub (Sep 23, 2024): meybe ollama can only access user "ollama",and your serve user is not ollama, if your ps -ef can see the serve user is ollama
Author
Owner

@MotivaoCrypto commented on GitHub (Oct 8, 2024):

I'm still running into the same issue. I've tried llama3 as well as llama3:latest and still get the same error:

model 'llama3' not found, try pulling it first.

When I run ollama list, I do see the model:

ollama list
NAME            ID              SIZE    MODIFIED    
llama3:latest   a6990ed6be41    4.7 GB  5 hours ago

I've tried reinstalling ollama as well, but no luck either :/

This is running on Ubuntu 20.04 running ollama 0.1.32

EDIT:

I solved it by running curl -X POST http://localhost:[port]/api/pull -d '{"model":"llama3"}'.

Not sure what I got wrong here, as I thought doing ollama pull llama3 in the command line would result in the same thing, but I guess the models are stored separately if you want to serve? Not sure, but it works!

I don't understand why but this seems to work, thank you

<!-- gh-comment-id:2400415178 --> @MotivaoCrypto commented on GitHub (Oct 8, 2024): > I'm still running into the same issue. I've tried `llama3` as well as `llama3:latest` and still get the same error: > > `model 'llama3' not found, try pulling it first`. > > When I run `ollama list`, I do see the model: > > ``` > ollama list > NAME ID SIZE MODIFIED > llama3:latest a6990ed6be41 4.7 GB 5 hours ago > ``` > > I've tried reinstalling `ollama` as well, but no luck either :/ > > This is running on Ubuntu 20.04 running ollama 0.1.32 > > EDIT: > > I solved it by running `curl -X POST http://localhost:[port]/api/pull -d '{"model":"llama3"}'`. > > Not sure what I got wrong here, as I thought doing `ollama pull llama3` in the command line would result in the same thing, but I guess the models are stored separately if you want to serve? Not sure, but it works! I don't understand why but this seems to work, thank you
Author
Owner

@wycoal commented on GitHub (Dec 26, 2024):

I restart my computer , then works

<!-- gh-comment-id:2562262528 --> @wycoal commented on GitHub (Dec 26, 2024): I restart my computer , then works
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#48914