ollama icon indicating copy to clipboard operation
ollama copied to clipboard

Error: could not connect to ollama app, is it running? on Windows 10

Open Alias4D opened this issue 2 years ago • 1 comments

Error: could not connect to ollama app, is it running? on windows 10

image

log file 👍

time=2024-02-24T14:24:23.004+03:00 level=WARN source=server.go:113 msg="server crash 1 - exit code 2 - respawning" time=2024-02-24T14:24:23.513+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-24T14:24:24.208+03:00 level=WARN source=server.go:113 msg="server crash 24 - exit code 2 - respawning" time=2024-02-24T14:24:24.528+03:00 level=WARN source=server.go:113 msg="server crash 2 - exit code 2 - respawning" time=2024-02-24T14:24:24.717+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-24T14:24:25.036+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-24T14:24:27.039+03:00 level=WARN source=server.go:113 msg="server crash 3 - exit code 2 - respawning" time=2024-02-24T14:24:27.545+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-24T14:24:29.295+03:00 level=WARN source=server.go:113 msg="server crash 11 - exit code 2 - respawning" time=2024-02-24T14:24:29.796+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-24T14:24:30.556+03:00 level=WARN source=server.go:113 msg="server crash 4 - exit code 2 - respawning" time=2024-02-24T14:24:30.807+03:00 level=WARN source=server.go:113 msg="server crash 15 - exit code 2 - respawning" time=2024-02-24T14:24:31.072+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-24T14:24:31.309+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-24T14:24:33.097+03:00 level=INFO source=lifecycle.go:87 msg="Waiting for ollama server to shutdown..." time=2024-02-24T14:24:34.350+03:00 level=INFO source=lifecycle.go:87 msg="Waiting for ollama server to shutdown..." time=2024-02-24T14:24:35.086+03:00 level=INFO source=lifecycle.go:91 msg="Ollama app exiting" time=2024-02-24T14:24:36.017+03:00 level=INFO source=lifecycle.go:87 msg="Waiting for ollama server to shutdown..." time=2024-02-24T14:24:40.805+03:00 level=INFO source=lifecycle.go:91 msg="Ollama app exiting" time=2024-02-24T14:24:46.324+03:00 level=INFO source=lifecycle.go:91 msg="Ollama app exiting" time=2024-02-24T14:24:48.722+03:00 level=WARN source=server.go:113 msg="server crash 25 - exit code 2 - respawning" time=2024-02-24T14:24:49.228+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started"

Alias4D avatar Feb 24 '24 11:02 Alias4D

I try reinstall ollama but same error message 😌 App.log below 👇 time=2024-02-25T17:50:52.780+03:00 level=WARN source=server.go:113 msg="server crash 1 - exit code 2 - respawning" time=2024-02-25T17:50:53.293+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-25T17:50:53.451+03:00 level=WARN source=server.go:113 msg="server crash 30 - exit code 2 - respawning" time=2024-02-25T17:50:53.957+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-25T17:50:54.308+03:00 level=WARN source=server.go:113 msg="server crash 2 - exit code 2 - respawning" time=2024-02-25T17:50:54.815+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-25T17:50:56.822+03:00 level=WARN source=server.go:113 msg="server crash 3 - exit code 2 - respawning" time=2024-02-25T17:50:57.327+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-25T17:51:00.328+03:00 level=WARN source=server.go:113 msg="server crash 4 - exit code 2 - respawning" time=2024-02-25T17:51:00.836+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-25T17:51:04.841+03:00 level=WARN source=server.go:113 msg="server crash 5 - exit code 2 - respawning" time=2024-02-25T17:51:05.348+03:00 level=ERROR source=server.go:116 msg="failed to restart server exec: already started" time=2024-02-25T17:51:10.358+03:00 level=WARN source=server.go:113 msg="server crash 6 - exit code 2 - respawning" image

what is solution , Please ............. ☺

Alias4D avatar Feb 25 '24 14:02 Alias4D

Try this after installing ollama, run $ ollama serve

let that be there. open another shell and run ollama [commands], as an example: $ ollama run llama2

shreyahegde18 avatar Feb 28 '24 16:02 shreyahegde18

Thanks, problem fixed

Alias4D avatar Feb 28 '24 19:02 Alias4D

Thanks, problem fixed

Alias4D avatar Feb 28 '24 19:02 Alias4D

You might have to enable the systemctl service manually, after that the ollama serve should be redundant.

systemctl enable ollama
systemctl start ollama

MartianInGreen avatar Mar 12 '24 19:03 MartianInGreen

You might have to enable the systemctl service manually, after that the ollama serve should be redundant.

systemctl enable ollama
systemctl start ollama

I tried this and i am getting this error not sure what it means

└─$ systemctl enable ollama systemctl start ollama System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down

roshdwivedi avatar Mar 21 '24 16:03 roshdwivedi

You started on a windows host with windows backend but your posted error message suggests that you are using the wsl with a linux distribution.

My wild guess is that you use the default distro wich would be Ubuntu LTS. Luckily systemd is supported and can now be activated for your WSL distro: https://learn.microsoft.com/en-us/windows/wsl/systemd

After activating systemd, you should be able to systemctl enable ollama

mybr4inhurts avatar Mar 25 '24 13:03 mybr4inhurts

here just to mention that ollama service has to be launched first (verify that on ubuntu : systemctl status ollama.service) then you can start working with it

DeepNeurons avatar Apr 02 '24 19:04 DeepNeurons

Getting error is ollama running right after updating to the latest version of ollama

Toppbeatz avatar Apr 08 '24 23:04 Toppbeatz

Try this after installing ollama, run $ ollama serve

let that be there. open another shell and run ollama [commands], as an example: $ ollama run llama2

TY! this worked. Just had to open another shell. TY

jayrodathome avatar May 21 '24 23:05 jayrodathome

You might have to enable the systemctl service manually, after that the ollama serve should be redundant.

systemctl enable ollama
systemctl start ollama

that's not working on mac, also lunchctl wasn't recgonized by the zsh terminal

danydin avatar Jun 30 '24 05:06 danydin

Mine are listening on specific addresses, it would seem:

netstat -tupln|grep -F :11434

This is what worked for me:

OLLAMA_HOST=my-host:11434 ollama run my-model

lmaddox avatar Jul 28 '24 19:07 lmaddox

So simple problem, just do this, and this will solve this error - ollama serve

GunjaGupta1233 avatar Aug 03 '24 11:08 GunjaGupta1233