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 #6525] ollama collapses CPU #4108

New Issue
Closed
opened 2026-04-12 15:00:27 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-12 15:00:27 -05:00
Owner
Copy Link

Originally created by @Hyphaed on GitHub (Aug 27, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/6525

What is the issue?

ollama collapses CPU

even when I stop the server the CPU still stuck from 75% to 90%

even when I do have an RTX 3070 and terminal is showind that is using the GPU

there is no error in terminal

I have no verbose since I forcelly shutedown the workstation

OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

0.3.6

Originally created by @Hyphaed on GitHub (Aug 27, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/6525 ### What is the issue? ollama collapses CPU even when I stop the server the CPU still stuck from 75% to 90% even when I do have an RTX 3070 and terminal is showind that is using the GPU there is no error in terminal I have no verbose since I forcelly shutedown the workstation ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version 0.3.6
GiteaMirror added the bug label 2026-04-12 15:00:27 -05:00
GiteaMirror commented 2026-04-12 15:00:28 -05:00
Author
Owner
Copy Link

@Hyphaed commented on GitHub (Aug 27, 2024):

@MirsonMboa

you should be banned from github

Trojan:Win32/Wacatac.H!ml

what the fuck? btw: I'm a Linux user, not Windows user

<!-- gh-comment-id:2311926677 --> @Hyphaed commented on GitHub (Aug 27, 2024): @MirsonMboa you should be banned from github Trojan:Win32/Wacatac.H!ml what the fuck? btw: I'm a Linux user, not Windows user
GiteaMirror commented 2026-04-12 15:00:29 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Aug 27, 2024):

Click on the three dots on the upper right hand side of the comment and report it.

<!-- gh-comment-id:2311950758 --> @rick-github commented on GitHub (Aug 27, 2024): Click on the three dots on the upper right hand side of the comment and report it.
GiteaMirror commented 2026-04-12 15:00:29 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Aug 27, 2024):

As to your problem, even if you've rebooted there should be logs, see https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues.

<!-- gh-comment-id:2311955844 --> @rick-github commented on GitHub (Aug 27, 2024): As to your problem, even if you've rebooted there should be logs, see https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues.
GiteaMirror commented 2026-04-12 15:00:29 -05:00
Author
Owner
Copy Link

@igorschlum commented on GitHub (Aug 27, 2024):

@Hyphaed, which LLM were you using? That's strange.

<!-- gh-comment-id:2312769075 --> @igorschlum commented on GitHub (Aug 27, 2024): @Hyphaed, which LLM were you using? That's strange.
GiteaMirror commented 2026-04-12 15:00:30 -05:00
Author
Owner
Copy Link

@Hyphaed commented on GitHub (Aug 27, 2024):

@rick-github
I do not see anything on the logs

apart from

d’ag. 27 16:56:21 z590i systemd[1]: ollama.service: Failed with result 'exit-code'.
d’ag. 27 16:56:25 z590i systemd[1]: ollama.service: Scheduled restart job, restart counter is at 293.
d’ag. 27 16:56:25 z590i systemd[1]: Started ollama.service - Ollama Service.
d’ag. 27 16:56:25 z590i ollama[16243]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key.
d’ag. 27 16:56:25 z590i ollama[16243]: Error: could not create directory mkdir /usr/share/ollama: permission denied

I've just removed ollama service, since when I want to use ollama I run it trough
$ ollama serve

@igorschlum

I'm using Mistral Nemo

<!-- gh-comment-id:2312809087 --> @Hyphaed commented on GitHub (Aug 27, 2024): @rick-github I do not see anything on the logs apart from ```d’ag. 27 16:56:21 z590i systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE d’ag. 27 16:56:21 z590i systemd[1]: ollama.service: Failed with result 'exit-code'. d’ag. 27 16:56:25 z590i systemd[1]: ollama.service: Scheduled restart job, restart counter is at 293. d’ag. 27 16:56:25 z590i systemd[1]: Started ollama.service - Ollama Service. d’ag. 27 16:56:25 z590i ollama[16243]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key. d’ag. 27 16:56:25 z590i ollama[16243]: Error: could not create directory mkdir /usr/share/ollama: permission denied ``` I've just removed ollama service, since when I want to use ollama I run it trough $ ollama serve @igorschlum I'm using Mistral Nemo
GiteaMirror commented 2026-04-12 15:00:30 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Aug 27, 2024):

The ollama service was crash looping and causing elevated CPU usage because of the error shown in the log.

<!-- gh-comment-id:2312826324 --> @rick-github commented on GitHub (Aug 27, 2024): The ollama service was crash looping and causing elevated CPU usage because of the error shown in the log.
GiteaMirror commented 2026-04-12 15:00:31 -05:00
Author
Owner
Copy Link

@Hyphaed commented on GitHub (Aug 27, 2024):

thanks @rick-github

maybe that's why

now there is no service anymore

I guess I was never in need of this, since I use ollama for my local work :: I do not have ollama in a server enviornment

I do close the issue then :: in case it arises again I will reopen

<!-- gh-comment-id:2312839514 --> @Hyphaed commented on GitHub (Aug 27, 2024): thanks @rick-github maybe that's why now there is no service anymore I guess I was never in need of this, since I use ollama for my local work :: I do not have ollama in a server enviornment I do close the issue then :: in case it arises again I will reopen
GiteaMirror commented 2026-04-12 15:00:31 -05:00
Author
Owner
Copy Link

@igorschlum commented on GitHub (Aug 27, 2024):

@Hyphaed there is another issue like this one on MacOS: https://github.com/ollama/ollama/issues/1925

<!-- gh-comment-id:2313425109 --> @igorschlum commented on GitHub (Aug 27, 2024): @Hyphaed there is another issue like this one on MacOS: https://github.com/ollama/ollama/issues/1925
GiteaMirror commented 2026-04-12 15:00:32 -05:00
Author
Owner
Copy Link

@anmolsekhon590 commented on GitHub (Sep 16, 2024):

@rick-github I do not see anything on the logs

apart from

d’ag. 27 16:56:21 z590i systemd[1]: ollama.service: Failed with result 'exit-code'.
d’ag. 27 16:56:25 z590i systemd[1]: ollama.service: Scheduled restart job, restart counter is at 293.
d’ag. 27 16:56:25 z590i systemd[1]: Started ollama.service - Ollama Service.
d’ag. 27 16:56:25 z590i ollama[16243]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key.
d’ag. 27 16:56:25 z590i ollama[16243]: Error: could not create directory mkdir /usr/share/ollama: permission denied

I've just removed ollama service, since when I want to use ollama I run it trough $ ollama serve

@igorschlum

I'm using Mistral Nemo

had similar issue where ollama kept running on my Arch Linux (btw). After reading your comment, I realized ollama runs using systemd. Hence, the processes kept spawning when I killed them using htop

So I ran

sudo systemctl disable ollama

for disabling auto-startup and

sudo systemctl stop ollama

to stop the running processes.

<!-- gh-comment-id:2353990878 --> @anmolsekhon590 commented on GitHub (Sep 16, 2024): > @rick-github I do not see anything on the logs > > apart from > > ``` > d’ag. 27 16:56:21 z590i systemd[1]: ollama.service: Failed with result 'exit-code'. > d’ag. 27 16:56:25 z590i systemd[1]: ollama.service: Scheduled restart job, restart counter is at 293. > d’ag. 27 16:56:25 z590i systemd[1]: Started ollama.service - Ollama Service. > d’ag. 27 16:56:25 z590i ollama[16243]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key. > d’ag. 27 16:56:25 z590i ollama[16243]: Error: could not create directory mkdir /usr/share/ollama: permission denied > ``` > > I've just removed ollama service, since when I want to use ollama I run it trough $ ollama serve > > @igorschlum > > I'm using Mistral Nemo had similar issue where ollama kept running on my Arch Linux (btw). After reading your comment, I realized ollama runs using systemd. Hence, the processes kept spawning when I killed them using `htop` So I ran ```bash sudo systemctl disable ollama ``` for disabling auto-startup and ```bash sudo systemctl stop ollama ``` to stop the running processes.
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 bug
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#4108
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?