You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2023. It is now read-only.
is-mongodb-running always returns that no instances are running when mongod is started using WSL. Additionally, if mongod is started from Windows, then it will also not report any instances running.
WSL does not support netstat or lsof yet. Therefore, the PID can be retrieved from ps command but the port is not found for the PID.
Microsoft has said they are working on the issue and hopefully a future release will support netstat and lsof. microsoft/WSL#2249
The text was updated successfully, but these errors were encountered:
Issue should be fixed in v1.5.0 of node-netstat. I am going to submit a PR to update the package JSON so that is used as a minimum, and then will close this issue.
@bubbathump Thanks for your insight, it was extremely helpful!
Ran into another problem that will cause this package to not be usable on WSL. Using Windows netstat command provides PID values on Windows side but WSL has another set of PIDs that do not match up.
Doing some research, it doesn't seem like there is an easy way to map between these PIDs. It seems that we will just have to wait for lsof or netstat support on WSL.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
is-mongodb-running always returns that no instances are running when mongod is started using WSL. Additionally, if mongod is started from Windows, then it will also not report any instances running.
WSL does not support
netstat
orlsof
yet. Therefore, the PID can be retrieved fromps
command but the port is not found for the PID.Microsoft has said they are working on the issue and hopefully a future release will support
netstat
andlsof
. microsoft/WSL#2249The text was updated successfully, but these errors were encountered: