node.js - Can't start mongodb on AWS instance -

i have worked on mongodb database. have installed in server & worked on this. facing problem. mongodb database not responding. when giving command : mongo

mongodb shell version: 2.6.10 connecting to: test 2015-07-02t06:22:11.363+0000 warning: failed connect 127.0.0.1:27017, reason: errno:111 connection refused 2015-07-02t06:22:11.364+0000 error: couldn't connect server 127.0.0.1:27017 (127.0.0.1), connection attempt failed @ src/mongo/shell/mongo.js:146 exception: connect failed 

i have delete lock file, repair mongodb restart mongodb. cant solve problem.

here mongodb.log file:

2015-07-02t06:30:48.789+0000 [initandlisten] mongodb starting : pid=5551 port=27017 dbpath=/var/lib/mongodb 64-bit host=ip-172-31-5-213 2015-07-02t06:30:48.789+0000 [initandlisten] db version v2.6.10 2015-07-02t06:30:48.789+0000 [initandlisten] git version: 5901dbfb49d16eaef6f2c2c50fba534d23ac7f6c 2015-07-02t06:30:48.789+0000 [initandlisten] build info: linux build18.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 smp fri jan 3 21:39:27 utc 2014 x86_64 boost_lib_version=1_49 2015-07-02t06:30:48.789+0000 [initandlisten] allocator: tcmalloc 2015-07-02t06:30:48.789+0000 [initandlisten] options: { config: "/etc/mongod.conf", net: { bindip: "127.0.0.1" }, storage: { dbpath: "/var/lib/mongodb" }, systemlog: { destination: "file", logappend: true, path: "/var/log/mongodb/mongod.log" } } 2015-07-02t06:30:48.800+0000 [initandlisten] journal dir=/var/lib/mongodb/journal 2015-07-02t06:30:48.800+0000 [initandlisten] recover : no journal files present, no recovery needed 2015-07-02t06:30:48.800+0000 [initandlisten]  2015-07-02t06:30:48.800+0000 [initandlisten] error: insufficient free space journal files 2015-07-02t06:30:48.800+0000 [initandlisten] please make @ least 3379mb available in /var/lib/mongodb/journal or use --smallfiles 2015-07-02t06:30:48.800+0000 [initandlisten]  2015-07-02t06:30:48.800+0000 [initandlisten] exception in initandlisten: 15926 insufficient free space journals, terminating 2015-07-02t06:30:48.800+0000 [initandlisten] dbexit:  2015-07-02t06:30:48.800+0000 [initandlisten] shutdown: going close listening sockets... 2015-07-02t06:30:48.800+0000 [initandlisten] shutdown: going flush diaglog... 2015-07-02t06:30:48.800+0000 [initandlisten] shutdown: going close sockets... 2015-07-02t06:30:48.800+0000 [initandlisten] shutdown: waiting fs preallocator... 2015-07-02t06:30:48.800+0000 [initandlisten] shutdown: lock final commit... 2015-07-02t06:30:48.801+0000 [initandlisten] shutdown: final commit... 2015-07-02t06:30:48.801+0000 [initandlisten] shutdown: closing files... 2015-07-02t06:30:48.801+0000 [initandlisten] closeallfiles() finished 2015-07-02t06:30:48.801+0000 [initandlisten] journalcleanup... 2015-07-02t06:30:48.801+0000 [initandlisten] removejournalfiles 2015-07-02t06:30:48.802+0000 [initandlisten] shutdown: removing fs lock... 2015-07-02t06:30:48.803+0000 [initandlisten] dbexit: exiting 

according mongodb.log file:

error: insufficient free space journal files please make @ least 3379mb available in /var/lib/mongodb/journal or use --smallfiles 

you don't have enough disk space start mongodb service. mongodb fails allocate disk space journal files.

i can see 4 possible solutions problem:

• add more disk space (cleanup something, or use larger storage). if you're using aws, expand ebs storage space keeping existing data.
• reduce journal size using --smallfiles key or setting storage.mmapv1.smallfiles true.
• disable journaling using --nojournal key or setting storage.journal.enabled false (not recommended).
• upgrade mongodb 3.x , change storage engine wiredtiger, it'll reduce overall database size , free disk space. you'll need additional disk space data migration.