How to run mongod in the background on unix (mac osx)

background-processmac-osxmongodbunix

I would like to run mongod in the background as an always present sort of thing. What would be the best way to do this? Kind of like the way I can run MySQL on startup and it's just always there running in the background. Maybe it's just some bash scripts, but it would be nice to hear if there is a better way. If it is just bash – what would that look like? Thanks.

Best Answer

The MongoDB daemon (mongod) has a command-line option to run the server in the background...

--fork

This command-line option requires that you also specify a file to log messages to (since it can not use the current console). An example of this command looks like:

mongod --fork --logpath /var/log/mongod.log

You could put this into an /etc/init.d/mongod bash script file. And then to have the service run at startup, create the standard symbolic links (S## & K##) inside of /etc/rc#.d/. Here is a tutorial that explains this process in more detail. Scroll down to the section titled "Init Script Activation". This also has the added benefit of being able to execute commands like...

service mongod status
service mongod start
service mongod stop

Related Solutions

How to set the global PATH environment variable on OS X

palmer's GUI information is correct, but there is a more maintainable way to modify the path seen by the shell. Like mediaslave said, you can edit /etc/paths, but even better you can drop a text file in /etc/paths.d/ that has a path in it and all shells will construct the path correctly.

For example, on my system:

$ cat /etc/paths
/usr/bin
/bin
/usr/sbin
/sbin
/usr/local/bin
$ ls /etc/paths.d
X11       git      postgres
$ cat /etc/paths.d/postgres
/Library/PostgreSQL/8.4/bin
$ echo $PATH
/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/Library/PostgreSQL/8.4/bin:/usr/X11/bin:/usr/local/mysql/bin

Linux – Running multiple PHP CLI’s in the background gives MySQL errors

Martin,

I am definitely not an expert on this, but a couple of things come to mind.

I think that php loads support for mysql whether you use it or not in your script, but it shouldn't start a connection unless you are using Persistent connections.I wouldn't think that the cli scripts would inherit the mysql connection from the Apache child, but apparently it must based on your testing.

You might also be running into to too many files limit on mysql. There is also reference to running out of RAM/resources being a cause of the mysql error. You said that it is showing less load than your old setup, but could it be too much? When these scripts are running, is there an opportunity to start a connection to the mysql server using the GUI (mysql administrator)? If so, you could potentially see it run out of resources...

It might be more efficient from a database point of view to have your 20 searches only be in one script, rather than spawning multiple scripts. This would allow you to use one mysql connection for all 20 searches and should increase your connection capacity accordingly. In other words, Web Script ---- spawns -----> CLI script in the background which loops through all of your searches.
Not knowing your code, or exactly what you are doing, this is just a guess as a coding fix.

Good luck

Best Answer

Related Solutions

How to set the global PATH environment variable on OS X

Linux – Running multiple PHP CLI’s in the background gives MySQL errors

Related Topic