New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with bash hanging on startup #4968
Comments
Having the same issue |
Same issue |
1 similar comment
Same issue |
Same issue with Windows 10 Home 1903 18362.720, Ubuntu 16.04. This problem only started happening recently. If I recall correctly, it started after some windows updates, namely after KB4537759, a little longer than a week ago. The init file is in the CanoicalGroupLimited/LocalState/rootfs folder. It looks like there is also a suspended mount process in task manager. mount is is rootfs/bin. |
In addition, the init processes sometimes start without even having to intentionally launch Ubuntu. It seems like this happens when I am checking windows update. When this happens, the CPU usage is also quite high. The LxssManager service is also not able to be stopped when this happens, although a message does appear in console that WSL has stopped, despite the init processes still going at it. |
I'm having the same problem. My computer is Window 10 Pro, version 1903. |
had the same issue, followed this link to update the Linux kernel and it worked: https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel for more context, I tried starting bash in the command prompt and got this error message: |
The issue is that I don't have WSL 2, I have the first version. You can see that my version is 18363, not 18917 or higher |
Seeing these multiple init processes go to that level is odd. The WSL init should only be mounting /mnt/c and any other custom mounts you have configured in /etc/wsl.conf This issue should not be confused with issues with the kernel in WSL2 in the recent change in slow ring that @laybak had. KB4537759 was an Adobe flash security update, so I am not sure about that one. I will monitor this thread for more reports. Some things to try:
|
So, this is quite odd, but simply navigating to the LocalState folder seems to start up the init processes. It could also just be coincidence, but I believe this has happened to me multiple times already. There are only three init processes this time though. I also don't seem to have a wsl.conf file in the rootfs/etc folder. I'll try some of the other things sirredbeard mentioned when I have time. |
So, wsl --terminate Ubuntu-16.04 doesn't seem to do anything when there are multiple init processes. It just sits there until I Ctrl-C out of it. LxssManager seems to be stuck on STOP_PENDING when I try to stop it and query it afterwords. And there also seems to be a different number of init processes every time. Sometimes 3, 7, 9, etc. I've also noticed that when working normally, there are also two init processes in task manager. When exiting or logging out of the shell, one init process ends immediately, while the other takes some time to end. |
Do you have any third-party security software running that could be interfering with the init mounting process? |
(Again, new at programming so not 100% following, so sorry) I have tried your suggestions and nothing different happened. However, it is quite difficult to even try them, as having bash open for 10 minutes triggers the init processes, hanging the terminal and torturing my CPU to the point that a restart is necessary. So I end up restarting every few couple of minutes. I'm considering just reinstalling Windows, reseting the whole computer (I have a separate drive just for software and all of my Linux data backed up so it wouldn't be that bad). Do you think that would fix the error? |
Third party security software will often detect things WSL is doing as malware and block it, it could be interfering with the mount process in your case @juannegro. Before you reinstall Windows at least try |
Same issue, |
Yep. Deleted Avast, restarted, now it's working as usual. Didn't hang in the 3 hours the computer was on, while before it hanged in the first 15 minutes. Will let you know if anything new happens. I'm new to github. Should I close the thread? There are people who had the same issue and I doubt that they can fix it the same way I could. |
I have Avast too, so that might just be the issue. I'll try to see if I can make exceptions for the wsl processes. |
I completely reinstalled windows 10 home edition, with no antivirus software, no other software, just Windows 10. I foillowed the complete procedure to install WSL and Ubuntu 18.04 release. Just did the update and upgrade. I did not install Xming this time. |
Removing Avast solved the problem for me. |
I am running wsl 2 Ubuntu and I am having the same issue of multiple init process. souradeep@LAPTOP-L9AIV34E:~$ ps -aux I have already tried restarting the lxss daemon, shutdown of Ubuntu, restarting the OS and |
I am running wsl 2 Ubuntu and I am having the same issue of multiple init process. souradeep@LAPTOP-L9AIV34E:~$ ps -aux I have already tried restarting the lxss daemon, shutdown of Ubuntu, restarting the OS and |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
System info: Microsoft Windows [Version 1909 18363.719]
Distribution: 20190521 build of Ubuntu 18.04 LTS
When I open it with Windows Terminal, Ubuntu, or even cmd, the result is the same. The terminal just hangs, I can't do anything. Ctrol + C doesn't do anything either. I can write all I want but nothing is ever done, it just shows what I write and does nothing.
The only way to get it operational again is rebooting the computer. And even then, sometimes it will just randomly stop working and hangs again, it just freezes. Plus, whenever this happens, there are like 8 files, all called "init" that appear on the Task Manager and takes up 70% of my CPU, rendering my computer useless until the next reboot.
I have seen this issue on other threads (#3392 for example) but those are quite old, I wouldn't know if they could work on my case. I am quite new to programming, so I don't understand a bunch of these things.
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: