github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #10985] Logs flooded with Ollama errors #69301

New Issue
Closed
opened 2026-05-04 17:43:52 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-04 17:43:52 -05:00
Owner
Copy Link

Originally created by @jcubic on GitHub (Jun 5, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10985

What is the issue?

I don't use Ollama anymore. I think that last time I used it a few weeks ago to test something. But my logs are flooded with errors that look like this:

cze 05 06:16:23 jcubic ollama[195547]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key.
cze 05 06:16:23 jcubic ollama[195547]: Error: could not create directory mkdir /usr/share/ollama: permission denied
cze 05 06:16:23 jcubic systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE
cze 05 06:16:23 jcubic systemd[1]: ollama.service: Failed with result 'exit-code'.
cze 05 06:16:23 jcubic audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=ollama comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

And it crashes my system. I don't turn off my computer at night, I only make the LCD on my laptop turn off. Today I was not able to wake it up. It was the second time when it happened.

I'm using Fedora 42 (just updated from 41 where Ollama was installed) with Dell Inspiron 15 5570 i7-8550U laptop.

I deleted Ollama, not sure if it will fix the crash, but the last log (above) before the crash suggest that it was caused with recurring errors from Ollama.

Please let me know if this issue with Ollama or something with Fedora update, or if they can do something about this.

OS

Linux

GPU

AMD

CPU

AMD

Ollama version

No response

Originally created by @jcubic on GitHub (Jun 5, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10985 ### What is the issue? I don't use Ollama anymore. I think that last time I used it a few weeks ago to test something. But my logs are flooded with errors that look like this: ``` cze 05 06:16:23 jcubic ollama[195547]: Couldn't find '/usr/share/ollama/.ollama/id_ed25519'. Generating new private key. cze 05 06:16:23 jcubic ollama[195547]: Error: could not create directory mkdir /usr/share/ollama: permission denied cze 05 06:16:23 jcubic systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE cze 05 06:16:23 jcubic systemd[1]: ollama.service: Failed with result 'exit-code'. cze 05 06:16:23 jcubic audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=ollama comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' ``` And it crashes my system. I don't turn off my computer at night, I only make the LCD on my laptop turn off. Today I was not able to wake it up. It was the second time when it happened. I'm using Fedora 42 (just updated from 41 where Ollama was installed) with Dell Inspiron 15 5570 i7-8550U laptop. I deleted Ollama, not sure if it will fix the crash, but the last log (above) before the crash suggest that it was caused with recurring errors from Ollama. **Please let me know if this issue with Ollama or something with Fedora update, or if they can do something about this.** ### OS Linux ### GPU AMD ### CPU AMD ### Ollama version _No response_
GiteaMirror added the bug label 2026-05-04 17:43:52 -05:00
GiteaMirror commented 2026-05-04 17:43:55 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jun 8, 2025):

cze 05 06:16:23 jcubic ollama[195547]: Error: could not create directory mkdir /usr/share/ollama: permission denied

The update may have erased the contents of /usr/share, which is where the ollama home directory was created when ollama was installed. Since ollama is only officially supported on Feodra 42 or later, the previous installation may not have matched the general guidelines for package installation on Fedora, so got broken in the upgrade.

<!-- gh-comment-id:2954230053 --> @rick-github commented on GitHub (Jun 8, 2025): ``` cze 05 06:16:23 jcubic ollama[195547]: Error: could not create directory mkdir /usr/share/ollama: permission denied ``` The update may have erased the contents of `/usr/share`, which is where the ollama home directory was created when ollama was installed. Since ollama is only [officially supported](https://docs.fedoraproject.org/en-US/quick-docs/ollama/) on Feodra 42 or later, the previous installation may not have matched the general guidelines for package installation on Fedora, so got broken in the upgrade.
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#69301
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?