{"id":12390,"date":"2016-08-10T08:30:50","date_gmt":"2016-08-10T03:00:50","guid":{"rendered":"http:\/\/blog.taragana.com\/?p=12390"},"modified":"2016-08-10T08:30:50","modified_gmt":"2016-08-10T03:00:50","slug":"possible-causes-solutions-for-mongodb-not-running","status":"publish","type":"post","link":"https:\/\/blog.taragana.com\/possible-causes-solutions-for-mongodb-not-running-12390","title":{"rendered":"Possible causes &amp; solutions for MongoDB not running"},"content":{"rendered":"<p>Is your MongoDB properly running? A simple way to check it would be with:<\/p>\n<pre>service mongod status<\/pre>\n<p>On my CentOS 5.x it gave:<\/p>\n<pre>mongod dead but subsys locked<\/pre>\n<p>There are two possible causes I could find. First is related to disk space. If you do not have enough space for dbpath (database directory) then you may get this message.<\/p>\n<div class=\"post-text\">\nTo solve it you can add following to the config file provided when running <code>mongod --config mongod.conf<\/code><br \/>\nFor MongoDB <strong>3.x<\/strong> (latest version)<\/p>\n<pre class=\"lang-js prettyprint prettyprinted\"><code><span class=\"pln\">storage<\/span><span class=\"pun\">:<\/span><span class=\"pln\">\n   mmapv1<\/span><span class=\"pun\">:<\/span><span class=\"pln\">\n      smallFiles<\/span><span class=\"pun\">:<\/span> <span class=\"kwd\">true<\/span><\/code><\/pre>\n<p>For version <strong>2.6+<\/strong><\/p>\n<pre class=\"lang-js prettyprint prettyprinted\"><code><span class=\"pln\">storage<\/span><span class=\"pun\">:<\/span><span class=\"pln\">\n   smallFiles<\/span><span class=\"pun\">:<\/span> <span class=\"kwd\">true<\/span><\/code><\/pre>\n<p>For version <strong>2.4<\/strong> and less<\/p>\n<pre class=\"lang-js prettyprint prettyprinted\"><code><span class=\"pln\">smallfiles <\/span><span class=\"pun\">=<\/span> <span class=\"kwd\">true<\/span><\/code><\/pre>\n<p>Then just execute mongod to accept your config file (here it assumes that location of the config is <em>\/etc\/mongodb.conf<\/em>):<\/p>\n<pre class=\"lang-js prettyprint prettyprinted\"><code><span class=\"pln\">mongod <\/span><span class=\"pun\">-<\/span><span class=\"pln\">f <\/span><span class=\"pun\">\/<\/span><span class=\"pln\">etc<\/span><span class=\"pun\">\/<\/span><span class=\"pln\">mongodb<\/span><span class=\"pun\">.<\/span><span class=\"pln\">conf<\/span><\/code><\/pre>\n<p><a href=\"http:\/\/docs.mongodb.org\/manual\/reference\/configuration-options\/#storage.mmapv1.smallFiles\">Documentation<\/a> for <strong>smallfiles<\/strong> parameter:<\/p>\n<pre class=\"lang-js prettyprint prettyprinted\"><code><span class=\"typ\">Set<\/span><span class=\"pln\"> to <\/span><span class=\"kwd\">true<\/span><span class=\"pln\"> to modify <\/span><span class=\"typ\">MongoDB<\/span><span class=\"pln\"> to use a smaller <\/span><span class=\"kwd\">default<\/span><span class=\"pln\"> data file size<\/span><span class=\"pun\">.<\/span>\n<span class=\"typ\">Specifically<\/span><span class=\"pun\">,<\/span><span class=\"pln\"> smallfiles reduces the initial size <\/span><span class=\"kwd\">for<\/span><span class=\"pln\"> data files and\nlimits them to <\/span><span class=\"lit\">512<\/span><span class=\"pln\"> megabytes<\/span><span class=\"pun\">.<\/span> <span class=\"typ\">The<\/span><span class=\"pln\"> smallfiles setting also reduces the\nsize of each journal files from <\/span><span class=\"lit\">1<\/span><span class=\"pln\"> gigabyte to <\/span><span class=\"lit\">128<\/span><span class=\"pln\"> megabytes<\/span><span class=\"pun\">.<\/span><\/code><\/pre>\n<\/div>\n<pre>Alternatively you can run mongod with --smallfiles parameter like:\nmongod --smallfiles<\/pre>\n<p>On my machine the problem was different. It was expecting a directory \/var\/lib\/mongod with proper permissions, which was not there. The solution is simple:<\/p>\n<pre>sudo mkdir \/var\/lib\/mongod\nsudo chown -R mongod \/var\/lib\/mongod<\/pre>\n<p>However how did I find out about the problem(s) in the first place. Again the solution is very simple. I looked in the log file:<\/p>\n<pre>vi \/var\/log\/mongodb\/mongodb.log<\/pre>\n<p>Always start with the log file.<br \/>\nFinally you can verify that your system is running properly with:<\/p>\n<pre>sudo service mongod status<\/pre>\n<p>After fixing it gave:<\/p>\n<pre>mongod (pid 26194) is running...<\/pre>\n<p>Now that&#8217;s solved, let&#8217;s get back to mongodb coding..<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Is your MongoDB properly running? A simple way to check it would be with: service mongod status On my CentOS 5.x it gave: mongod dead but subsys locked There are two possible causes I could find. First is related to disk space. If you do not have enough space for dbpath (database directory) then you [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":12391,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[6,12],"tags":[72],"_links":{"self":[{"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/posts\/12390"}],"collection":[{"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/comments?post=12390"}],"version-history":[{"count":0,"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/posts\/12390\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.taragana.com\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/media?parent=12390"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/categories?post=12390"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.taragana.com\/wp-json\/wp\/v2\/tags?post=12390"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}