github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-16 05:05:37 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #2293] Error: unmarshal #1322

New Issue
Closed
opened 2026-04-12 11:09:17 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-12 11:09:17 -05:00
Owner
Copy Link

Originally created by @hemanth on GitHub (Jan 31, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2293

Noticing a Error: unmarshal: invalid character 'p' after top-level value on ollama run llava

image

client version is 0.1.22

Originally created by @hemanth on GitHub (Jan 31, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2293 Noticing a `Error: unmarshal: invalid character 'p' after top-level value` on `ollama run llava` <img width="923" alt="image" src="https://github.com/ollama/ollama/assets/18315/84f04d3e-a64e-4da5-9131-20ccf56cdeca"> `client version is 0.1.22`
GiteaMirror commented 2026-04-12 11:09:18 -05:00
Author
Owner
Copy Link

@hemanth commented on GitHub (Feb 3, 2024):

❯ ollama --version
Warning: could not connect to a running Ollama instance
Warning: client version is 0.1.23

❯ ollama run llava
Error: unmarshal: invalid character 'p' after top-level value
<!-- gh-comment-id:1925171702 --> @hemanth commented on GitHub (Feb 3, 2024): ``` ❯ ollama --version Warning: could not connect to a running Ollama instance Warning: client version is 0.1.23 ``` ``` ❯ ollama run llava Error: unmarshal: invalid character 'p' after top-level value ```
GiteaMirror commented 2026-04-12 11:09:18 -05:00
Author
Owner
Copy Link

@mogest commented on GitHub (Feb 6, 2024):

I'm getting the same from a completely fresh install and wiped ~/.ollama directory.

Installed on MacOS Sonoma 14.2.1, from download using the link on the GitHub README, onto a Mac M1 Max 32 GB.

Also tried the brew install, same result.

> ollama run mistral
pulling manifest
pulling e8a35b5937a5... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 4.1 GB
pulling 43070e2d4e53... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  11 KB
pulling e6836092461f... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏   42 B
pulling ed11eda7790d... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏   30 B
pulling f9b1e3196ecf... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  483 B
verifying sha256 digest
writing manifest
removing any unused layers
success
Error: unmarshal: invalid character 'p' after top-level value
<!-- gh-comment-id:1928857227 --> @mogest commented on GitHub (Feb 6, 2024): I'm getting the same from a completely fresh install and wiped `~/.ollama` directory. Installed on MacOS Sonoma 14.2.1, from download using the link on the GitHub README, onto a Mac M1 Max 32 GB. Also tried the `brew` install, same result. ``` > ollama run mistral pulling manifest pulling e8a35b5937a5... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 4.1 GB pulling 43070e2d4e53... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 11 KB pulling e6836092461f... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 42 B pulling ed11eda7790d... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 30 B pulling f9b1e3196ecf... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 483 B verifying sha256 digest writing manifest removing any unused layers success Error: unmarshal: invalid character 'p' after top-level value ```
GiteaMirror commented 2026-04-12 11:09:19 -05:00
Author
Owner
Copy Link

@mogest commented on GitHub (Feb 6, 2024):

Problem only seems to have started in 0.1.21. 0.1.20 functions correctly.

<!-- gh-comment-id:1928964428 --> @mogest commented on GitHub (Feb 6, 2024): Problem only seems to have started in 0.1.21. 0.1.20 functions correctly.
GiteaMirror commented 2026-04-12 11:09:19 -05:00
Author
Owner
Copy Link

@terminalkitten commented on GitHub (Feb 26, 2024):

In my case this issue was fixed after restarting:

brew services start ollama or brew services restart ollama

<!-- gh-comment-id:1965536454 --> @terminalkitten commented on GitHub (Feb 26, 2024): In my case this issue was fixed after restarting: `brew services start ollama` or `brew services restart ollama`
GiteaMirror commented 2026-04-12 11:09:20 -05:00
Author
Owner
Copy Link

@bmizerany commented on GitHub (Mar 11, 2024):

ollama run llava is working on the latest release of Ollama on macOS. Closing, but please reopen if continue to have issues.

<!-- gh-comment-id:1989619848 --> @bmizerany commented on GitHub (Mar 11, 2024): `ollama run llava` is working on the latest release of Ollama on macOS. Closing, but please reopen if continue to have issues.
GiteaMirror commented 2026-04-12 11:09:20 -05:00
Author
Owner
Copy Link

@tirithen commented on GitHub (Apr 22, 2024):

@bmizerany

I'm getting the same error after re-installing ollama on Arch Linux, it worked just minutes before my re-install.

$ ollama run mistral
Error: unmarshal: invalid character 'p' after top-level value

$ ollama --version
Warning: could not connect to a running Ollama instance
Warning: client version is 0.1.32

I think that it would be helpful if the ollama cli had some health check mode where it could verify if the models are valid/have the correct format as well as that the client and server versions are compatible (I suppose that they are mostly bundled together). Anyhow, some sub command that helps troubleshoot what would be causing parsing errors.

<!-- gh-comment-id:2070913581 --> @tirithen commented on GitHub (Apr 22, 2024): @bmizerany I'm getting the same error after re-installing ollama on Arch Linux, it worked just minutes before my re-install. ``` $ ollama run mistral Error: unmarshal: invalid character 'p' after top-level value ``` ``` $ ollama --version Warning: could not connect to a running Ollama instance Warning: client version is 0.1.32 ``` I think that it would be helpful if the ollama cli had some health check mode where it could verify if the models are valid/have the correct format as well as that the client and server versions are compatible (I suppose that they are mostly bundled together). Anyhow, some sub command that helps troubleshoot what would be causing parsing errors.
GiteaMirror commented 2026-04-12 11:09:21 -05:00
Author
Owner
Copy Link

@littson commented on GitHub (Apr 24, 2024):

@bmizerany

I'm getting the same error after re-installing ollama on Arch Linux, it worked just minutes before my re-install.

$ ollama run mistral
Error: unmarshal: invalid character 'p' after top-level value

$ ollama --version
Warning: could not connect to a running Ollama instance
Warning: client version is 0.1.32

I think that it would be helpful if the ollama cli had some health check mode where it could verify if the models are valid/have the correct format as well as that the client and server versions are compatible (I suppose that they are mostly bundled together). Anyhow, some sub command that helps troubleshoot what would be causing parsing errors.

I am getting the same error on macOS 14.4.1:

$ ollama list
NAME                                               	ID          	SIZE  	MODIFIED
llama3:latest                                      	71a106a91016	4.7 GB	4 days ago

$ ollama run llama3
Error: unmarshal: invalid character 'p' after top-level value

$ ollama -v
Warning: could not connect to a running Ollama instance
Warning: client version is 0.1.32

reinstall does not help.

<!-- gh-comment-id:2074079418 --> @littson commented on GitHub (Apr 24, 2024): > @bmizerany > > I'm getting the same error after re-installing ollama on Arch Linux, it worked just minutes before my re-install. > > ``` > $ ollama run mistral > Error: unmarshal: invalid character 'p' after top-level value > ``` > > ``` > $ ollama --version > Warning: could not connect to a running Ollama instance > Warning: client version is 0.1.32 > ``` > > I think that it would be helpful if the ollama cli had some health check mode where it could verify if the models are valid/have the correct format as well as that the client and server versions are compatible (I suppose that they are mostly bundled together). Anyhow, some sub command that helps troubleshoot what would be causing parsing errors. I am getting the same error on macOS 14.4.1: ``` $ ollama list NAME ID SIZE MODIFIED llama3:latest 71a106a91016 4.7 GB 4 days ago $ ollama run llama3 Error: unmarshal: invalid character 'p' after top-level value $ ollama -v Warning: could not connect to a running Ollama instance Warning: client version is 0.1.32 ``` reinstall does not help.
GiteaMirror commented 2026-04-12 11:09:21 -05:00
Author
Owner
Copy Link

@eamonburns commented on GitHub (Apr 30, 2024):

@bmizerany Could you please reopen this? Me and two other people are getting the error.

$ OLLAMA_HOST='http://10.10.10.10:11434' ollama run orca-mini
Error: unmarshal: invalid character 'p' after top-level value

10.10.10.10 is a server which I can run ollama list, ollama show, and ollama pull on without issue.

$ OLLAMA_HOST='http://10.10.10.10:11434' ollama -v
Warning: could not connect to a running Ollama instance
Warning: client version is 0.1.32
<!-- gh-comment-id:2084528158 --> @eamonburns commented on GitHub (Apr 30, 2024): @bmizerany Could you please reopen this? Me and two other people are getting the error. ``` $ OLLAMA_HOST='http://10.10.10.10:11434' ollama run orca-mini Error: unmarshal: invalid character 'p' after top-level value ``` `10.10.10.10` is a server which I can run `ollama list`, `ollama` show, and `ollama pull` on without issue. ``` $ OLLAMA_HOST='http://10.10.10.10:11434' ollama -v Warning: could not connect to a running Ollama instance Warning: client version is 0.1.32 ```
GiteaMirror commented 2026-04-12 11:09:22 -05:00
Author
Owner
Copy Link

@eamonburns commented on GitHub (Apr 30, 2024):

@littson @tirithen I was able to fix it. My server was running v0.1.12 and my client was running v0.1.32. I can see you both are running it locally though, so maybe it has something to do with you running the newest version of ollama, and maybe there was some sort of change in the encoding

<!-- gh-comment-id:2087726436 --> @eamonburns commented on GitHub (Apr 30, 2024): @littson @tirithen I was able to fix it. My server was running `v0.1.12` and my client was running `v0.1.32`. I can see you both are running it locally though, so maybe it has something to do with you running the newest version of ollama, and maybe there was some sort of change in the encoding
GiteaMirror commented 2026-04-12 11:09:22 -05:00
Author
Owner
Copy Link

@littson commented on GitHub (May 2, 2024):

@littson @tirithen I was able to fix it. My server was running v0.1.12 and my client was running v0.1.32. I can see you both are running it locally though, so maybe it has something to do with you running the newest version of ollama, and maybe there was some sort of change in the encoding

@Agent-E11 Thanks.

I fixed the issue too. By following your instructions, I realized I had two ollama version installed in my system:

  1. installed from homebrew.
  2. installed from ollama website as .dmg application.

The issue is fixed after I remove the .dmg application.

<!-- gh-comment-id:2089376317 --> @littson commented on GitHub (May 2, 2024): > @littson @tirithen I was able to fix it. My server was running `v0.1.12` and my client was running `v0.1.32`. I can see you both are running it locally though, so maybe it has something to do with you running the newest version of ollama, and maybe there was some sort of change in the encoding @Agent-E11 Thanks. I fixed the issue too. By following your instructions, I realized I had two ollama version installed in my system: 1. installed from `homebrew`. 2. installed from ollama website as `.dmg` application. The issue is fixed after I remove the `.dmg` application.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#1322
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?