This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 74%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
I configured redis-server service in wsl2, but wsl sudo service redis-server start wsl instance will stop after running for a while after starting the service, how to prevent wsl from stopping, or what is the mechanism of wsl stopping
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 81%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
I am seeing this same behavior in Win11 WSL. Running the procedure outlined in the answer only works for 10-15 seconds then the Ubuntu process seems to just stop. The only way I have got this to work is by manually opening a WSL terminal tab and keeping it open. My hunch is that the Redis daemon is working fine, but Windows is killing the Ubuntu WSL process after the command executes and kills the Redis daemon with it. So the answer will seem to lie somewhere in how to tell Windows to keep WSL running after the command executes. Haven't found that tidbit yet..... please lmk if you do.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 23%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
This solution will solve the problem, but this is a far-fetched solution
Is there any official configuration to make WSL instance live？
I found this [https://github.com/microsoft/WSL/issues/10138]
which indicates wsl --exec dbus-launch true will keep the wsl process alive.
Thus far it seems to be working.
So full Poweshell cmd would be:
cmd /c "wsl --exec dbus-launch true && wsl --exec sudo service redis-server start --daemonize yes && wsl --exec redis-cli PING && Exit /B 5"