I suspect the latter as I faced this issue previously during development, but thought the bat file use of daemonize had fixed it.
This can be verified by later running in a regular cmd window:
wsl -l-v
Which often shows that Windows has stopped WSL outright,
(If I open up VSCode instead, as it has the WSL plugins loaded, it will re-load WSL and mask if that was the issue)
Currently investigating. If WSL and Ollama are starting up fine but WSL is later being stopped by Windows, I will consider if there is a alternative to the current daemonize line that might fix it, or whether a simple 'heartbeat' request to Ollama could work e.g.:
I suspect the latter as I faced this issue previously during development, but thought the bat file use of
daemonize
had fixed it.This can be verified by later running in a regular cmd window:
Which often shows that Windows has stopped WSL outright,
(If I open up VSCode instead, as it has the WSL plugins loaded, it will re-load WSL and mask if that was the issue)
Currently investigating. If WSL and Ollama are starting up fine but WSL is later being stopped by Windows, I will consider if there is a alternative to the current
daemonize
line that might fix it, or whether a simple 'heartbeat' request to Ollama could work e.g.: