Checkout our demo site to practice selenium https://magento.softwaretestingboard.com/

0 like 0 dislike
359 views
in Others by
closed by
I am getting below error while starting up MongoDB.

 

Fri Apr 22 18:58:27
Fri Apr 22 18:58:27 warning: 32-bit servers don't have journaling enabled by def
ault. Please use --journal if you want durability.
Fri Apr 22 18:58:27
Fri Apr 22 18:58:27 [initandlisten] MongoDB starting : pid=2696 port=27017 dbpat
h=C:\Users\mayurb\Documents\-db 32-bit host=SCI-DT-164
Fri Apr 22 18:58:27 [initandlisten]
Fri Apr 22 18:58:27 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are
limited to about 2 gigabytes of data
Fri Apr 22 18:58:27 [initandlisten] **       see http://blog.mongodb.org/post/13
7788967/32-bit-limitations
Fri Apr 22 18:58:27 [initandlisten] **       with --journal, the limit is lower
Fri Apr 22 18:58:27 [initandlisten]
Fri Apr 22 18:58:27 [initandlisten] db version v2.2.3, pdfile version 4.5
Fri Apr 22 18:58:27 [initandlisten] git version: f570771a5d8a3846eb7586eaffcf4c2
f4a96bf08
Fri Apr 22 18:58:27 [initandlisten] build info: windows sys.getwindowsversion(ma
jor=6, minor=0, build=6002, platform=2, service_pack='Service Pack 2') BOOST_LIB
_VERSION=1_49
Fri Apr 22 18:58:27 [initandlisten] options: { dbpath: "C:\Users\mayurb\Document
s\-db" }
Fri Apr 22 18:58:27 [initandlisten] Unable to check for journal files due to: bo
ost::filesystem::basic_directory_iterator constructor: The system cannot find th
e path specified: "C:\Users\mayurb\Documents\-db\journal"
**************
Unclean shutdown detected.
Please visit http://dochub.mongodb.org/core/repair for recovery instructions.
*************
Fri Apr 22 18:58:27 [initandlisten] exception in initAndListen: 12596 old lock f
ile, terminating
Fri Apr 22 18:58:27 dbexit:
Fri Apr 22 18:58:27 [initandlisten] shutdown: going to close listening sockets..
.
Fri Apr 22 18:58:27 [initandlisten] shutdown: going to flush diaglog...
Fri Apr 22 18:58:27 [initandlisten] shutdown: going to close sockets...
Fri Apr 22 18:58:27 [initandlisten] shutdown: waiting for fs preallocator...
Fri Apr 22 18:58:27 [initandlisten] shutdown: closing all files...
Fri Apr 22 18:58:27 [initandlisten] closeAllFiles() finished
Fri Apr 22 18:58:27 dbexit: really exiting now

 

How do I resolve those.
closed with the note: This is resolved

1 Answer

0 like 0 dislike
by Master (1.2k points)

It looks like you have to repair your DB.

To do so.

  • Create a backup of the data files.

Create a backup copy of the data files in the --dbpath.

  • Start mongod with --repair.

To repair the data files, start the mongod instance with the --repair option. By default, during the repair operation, MongoDB uses a _tmp directory in the --dbpath.

If the mongod instance uses MMAPv1 Storage Engine, you can include the --repairpath option to specify an alternate temporary directory. For details, see --repairpath.

Issue a command similar to the following:

mongod --dbpath /data/db --repair
 

Upon completion, the dbpath should contain the repaired data files and an empty mongod.lock file


This site is for software testing professionals, where you can ask all your questions and get answers from 1300+ masters of the profession. Click here to submit yours now!

1.4k questions

1.6k answers

866 comments

1.9k users

...