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

[GH-ISSUE #14963] Missleading bind address after failed ollama serve command #35381

New Issue
Closed
opened 2026-04-22 19:52:03 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-22 19:52:03 -05:00
Owner
Copy Link

Originally created by @karlocehulic19 on GitHub (Mar 19, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14963

What is the issue?

When ollama.service is already running in the background and no OLLAMA_HOST environmental variable is set in desiganted override.conf file, in the bash with exported OLLAMA_HOST=0.0.0.0 running ollama serve will log:

Error: listen tcp 0.0.0.0:11434: bind: address already in use

instead of what is more precise given the default host of 127.0.0.1:

Error: listen tcp 127.0.0.1:11434: bind: address already in use

Why the change is important

I personally got mislead, thinking that I setup host the correctly. Since binding was logging URL I expected. Which caused me to spend unnecessary time confused why Ollama endpoints aren't responding. I assume I am not the first person that this has happened to. That's why I am suggesting to more explicit binding address.


Environmental details

Operating system: Linux Omarchy

Kernel: Linux 6.18.3-arch1-1

Relevant log output

OS

Linux

GPU

AMD

CPU

AMD

Ollama version

0.18.2

Originally created by @karlocehulic19 on GitHub (Mar 19, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14963 ### What is the issue? When `ollama.service` is already running in the background and no `OLLAMA_HOST` environmental variable is set in desiganted `override.conf` file, in the bash with exported `OLLAMA_HOST=0.0.0.0` running `ollama serve` will log: ``` Error: listen tcp 0.0.0.0:11434: bind: address already in use ``` instead of what is more precise given the default host of 127.0.0.1: ``` Error: listen tcp 127.0.0.1:11434: bind: address already in use ``` ### Why the change is important I personally got mislead, thinking that I setup host the correctly. Since binding was logging URL I expected. Which caused me to spend unnecessary time confused why Ollama endpoints aren't responding. I assume I am not the first person that this has happened to. That's why I am suggesting to more explicit binding address. <br> ### Environmental details Operating system: Linux Omarchy<br> Kernel: Linux 6.18.3-arch1-1 ### Relevant log output ```shell ``` ### OS Linux ### GPU AMD ### CPU AMD ### Ollama version 0.18.2
GiteaMirror added the bug label 2026-04-22 19:52:03 -05:00
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#35381
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?