In /mnt/c/data/db/ created by the 'wiredTiger' storage engine, so setting SpecifyingĪ dbpath and port was working for me previously with 2.4.9 but no love Only problem is that now I getĮrrors when attempting mongod or the shell, and it is unusable. I followed the steps on the installation guide and Here's the output of that command:Įxecuting: gpg -ignore-time-conflict -no-options -no-default-keyring -homedir /tmp/tmp.wjm2zfd5JA -no-auto-check-trustdb -trust-model always -keyring /etc/apt/trusted.gpg -primary-keyring /etc/apt/trusted.gpg -keyserver hkp://:80 -recv EA312927 echo deb trusty/mongodb-org/3.2 multiverse gpg: "echo" not a key ID: skipping gpg: "deb" not a key ID: skipping gpg: "" not a key ID: skipping gpg: "trusty/mongodb-org/3.2" not a key ID: skipping gpg: "multiverse" not a key ID: skipping gpg: requesting key EA312927 from hkp server gpg: key EA312927: public key "MongoDB 3.2 Release Signing Key " imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) Which threw an error, so I tried again with:Īnd it's still failing to install.
Uninstall mongodb windows service install#
Sudo apt-key adv -keyserver hkp://:80 -recv EA312927 echo "deb trusty/mongodb-org/3.2 multiverse" | sudo tee /etc/apt//mongodb-org-3.2.list sudo apt-get update sudo apt-get install -y mongodb-org Is there any way one of you can post an exact set of commands for downloading and getting MongoDb running on WSL? I tried this: Hey! Sorry, but I'm a bit of a noob and I'm not quite able to to follow all of the instructions you guys have laid out. Similarly, if there is a problem getting mongodb runniing in its barest, cleanest implementation, it may be helpful for it to be reported to the WSL folks separate from the issue of not being able to run it as a service. Yes, we all know sudo service mongodb start is the proper way to start it, but since services aren't yet implemented, and we want to get some work done, we look for workarounds. Just a comment: right now we are using WSL when many things are broken or not yet implemented. If you can get the executable running that way, you can work from there to getting a script working. That's even more simple than running it from a bash script. Frequently there is a way to make it run from a command line (usually for testing, or special applications). The other option is to find the executable for the service/daemon's executable. Right now, invoking it with the service command, before services are supported, it's hard to say where the problem is. If you run the script and then it reports an error, you can be sure it is an error in that script or in the way your service runs. Your mileage may vary, and there may not be a bash script in /etc/init.d you can run. Note that the script is not called sshd, as you might expect. I've been doing that with sshd, sudo /etc/init.d/ssh start rather than sudo service ssh start. Then it won't matter if upstart or service isn't implemented fully.
Uninstall mongodb windows service full#
In other words, remove the word "service" from the command and call the script by its full path. Run it like any other bash script, with start as a parameter.
If you get the initctl error message about not being able to talk to upstart, and the service doesn't start, you might want to look for the script in /etc/init.d, which is (usually) a standard bash script.
0 kommentar(er)
