After downloading, extracting, creating the data/db folder and cd-ing into where I extracted mongoDB, I tried running this command, as directed by the official mongoDB install instructions: .bin/mongo/ but I keep getting this error:
Error: couldn't connect to server 127.0.0.1:27017 src/mongo/shell/mongo.js:91
I can't find a concise explanation on the internet, though it seems to be a common problem, and the mongoDB docs aren't clear either. Can anyone help me out?
Start the server before trying to connect with a client:
mongod
Or if you want to specifically point it at a db location, and log to a log file:
mongod --logpath /data/log/mongo.log --dbpath /data/db
Or something of this nature. This command will run the server in a foreground process. You can use --fork to daemonize it.
Related
I am working with the Meteor application and I deployed the same over EC2 instance. It was working fine till a few days back.
But now the server process kill automatically without any error log or
console
I tried to get the error but unfortunately, as there are not any logs I am unable to find out why the server is crashing again and again.
I have a medium EC2 machine on which the application is running.
I am using nohup for running the application in the background.
Below is the command I used to start the server:-
nohup meteor --settings SETTINGS-PRODUCTION.JSON &
I am wondering to know about server crashes due to nohup or some other reason is there.
Please let me know how we can console uncaught exception in the meteor-like we do in express.
What should I use to auto restart the server if the process is killed
by any error or exception?
Any help would be much appreciated!
Thanks
Using nohup is quite a low-tech solution. Things like Phusion Passenger, PM2, or forever do a better job.
Also your docker container can be configured to automatically restart the process.
Even better is a tool called Meteor Up, which makes it really simple to deploy Meteor apps to EC2.
EASILY DEPLOY YOUR APP Meteor Up is a production quality Meteor app
deployment tool.
Install with one command:
$ npm install --global mup
http://meteor-up.com/
I’m trying to create a GUI client for connecting to OpenVPN servers using electron and node but I’m struggling to figure out how to actually connect to the servers using the .ovpn files.
My question is what is the best way to connect to an OpenVPN server using node? Would it be best to Tun terminal commands like
“openvpn—config path to config”
Or is there another way applications like tunnelblick do it that might be easier or more efficient?
Hello I have been working with electron and ovpn on my last project, so here are a few tips.
VPNs require admin/root privilege in order to get setup, so running child_process.spawn on openvpn --config <path> will fail unless your electron app is being ran via sudo/admin privilege.
You can also use electron-sudo package, link here. This is basically a child process spawn with sudo/admin. Aka, app runs normally, but vpn command runs with sudo.
However, if your client is sketchy about giving you sudo/admin, the VPN must be ran separately prior to launching your app.
All in all its a admin/sudo thing.
Hope this helps.
I have one Meteor application running on my Ubuntu server (Digital Ocean). I use Meteor Up (MUP) to deploy and keep the app running. Everything works fine.
However, when I try to deploy a second app on the same server, something goes wrong in connecting to the MongoDB. I get a long and unreadable error message that starts "Invoking deployment process: FAILED" and then ends with
Waiting for MongoDB to initialize. (5 minutes)
connected
myapp start/running, process 25053
Waiting for 15 seconds while app is booting up
Checking is app booted or not?
myapp stop/waiting
myapp start/running, process 25114
And the app refuses to run. I have tried a number of things to fix this and will edit this post if more info is requested, but I'm not sure what's relevant. Essentially I don't understand the Error message, so I need to know what the heck is going on?
EDIT:
I want to add that my app runs fine if I go into the project folder and use the "meteor" command. Everything runs as expected. It is only when I try to deploy it for long-term production mode with MUP that I get this error.
EDIT:
I moved on to trying mupx instead of mup. This time I can't even get past the installation process, I get the following error message:
[Neal] x Installing MongoDB: FAILED
-----------------------------------STDERR-----------------------------------
Error response from daemon: no such id: mongodb
Error: failed to remove containers: [mongodb]
Error response from daemon: Cannot start container c2c538d34c15103d1d07bcc60b56a54bd3d23e50ae7a8e4f9f7831df0d77dc56: failed to create endpoint mongodb on network bridge: Error starting userland proxy: listen tcp 127.0.0.1:27017: bind: address already in use
But I don't understand why! Mongod is clearly already running on port 27017 and a second application should just add a new database to that instance, correct? I don't know what I'm missing here, why MUP can't access MongoDB.
It's tricky without your mup.json to see what's going on here. Given what you said, it looks like your 2nd app deployment tries to override/boot mongodb over the 1st one which is locked, the mongodb environment fails to boot, causing then the fail. You should tackle this different ways:
If your objective is to share your mongoDB, point the MONGO_URL from your 2nd mup.jon on your first mongodb instance. It's generally something along the 2701X ports. As it's a shared DB, changes in one database could affect the other.
meteor-up oversees the deployment of your app from a meteor-nice-to-test thing to a node+mongodb environment. You can spawn another mongod instance with :
mongod --port 2701X --dbpath /your/dbpath --fork --logpath /log/path on your DO server and then point MONGO_URL there.
Last but not least, mupx having docker under the hood. Using mupx for your deployments should isolate both apps from each other.
I have nodejs and mongoDB installed on 32bit winXP veteran. And I am trying to link them.
In the mongoDB docs its stated that the easiest way is by this command:
npm install mongodb
Unfortunately it throws the following exception:
"Failed to replace env in config: ${APPDATA}"
I tried to point the NODE_PATH variable to the "npm\node_modules" folder but this does not solve my problem.
What additional configuration am I missing?
In the end just ran the cmd not as Administrator but simply from my account and the command("npm install mongodb") worked as expected.
After that I uninstalled it since this was kind of weird. And again tried as Administrator and it failed again. And again succeeded with my account. So I left it be.
So I've installed mongo using home brew and I've installed it through npm, so I have the JS driver.
When I run mongo in command line though, I get this -
MongoDB shell version: 2.2.2
connecting to: test
Thu Jan 24 02:38:26 Error: couldn't connect to server 127.0.0.1:27017 src/mongo/shell/mongo.js:91
exception: connect failed
why is that happening?
After you've installed MongoDB, open a terminal window and go to the file path where your MongoDB application is stored e.g c:\MongoDB. Then type mongod and hit enter. This should start this process running. Mongod is the database server that you then access via the mongo shell.
After mongod is running, open a new terminal window and type mongo then hit enter. You should now be up and running. You can test that it's working by typing the following into the mongo shell as an example:
>
>db.names.save({'name':"James"})
>db.names.find()
This should then return the document you have just saved to the database as shown in the example below.
>{"_id" ObjectID:"764tdf763dyf6337fd376","name":"James"}
Read through the documentation and look for tutorials online. 10gen have just started an excellent online course. It's free and started this week so you might still be able to register.