Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mongodb-user
Home
+ new post
About this group
Join this group
Cannot start MongoDB: System error 1067 in Windows
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
gregorinator  
View profile  
 More options Oct 4 2012, 9:12 am
From: gregorinator <gregorina...@gmail.com>
Date: Thu, 4 Oct 2012 09:12:30 -0400
Local: Thurs, Oct 4 2012 9:12 am
Subject: Cannot start MongoDB: System error 1067 in Windows
Print | Individual message | Show original | Report this message | Find messages by this author
We're running MongoDB 2.2 as a service under Windows 2008, 64 bit.
With journaling enabled.  We had a master/slave setup, but wanted to
convert to a replica set .  Perhaps naively, I assumed it was as easy
as this:  I stopped the Windows service, removed the line "master =
true" from the config file, added this line:

replSet = tdms2_rs

and tried to start the Windows service again.  I got this error:

     A system error has occurred.

     System error 1067 has occurred.

     The process terminated unexpectedly.

I quickly put the config file back the way it was, but it made no
difference.  Every time I try to start the service, I get this error.
Mongo is now down.

I'm desperate.  What can I try?

gs


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Discussion subject changed to "SOLVED: Cannot start MongoDB: System error 1067 in Windows" by gregorinator
gregorinator  
View profile  
 More options Oct 4 2012, 4:16 pm
From: gregorinator <gregorina...@gmail.com>
Date: Thu, 4 Oct 2012 13:16:32 -0700 (PDT)
Local: Thurs, Oct 4 2012 4:16 pm
Subject: SOLVED: Cannot start MongoDB: System error 1067 in Windows
Print | Individual message | Show original | Report this message | Find messages by this author

>      System error 1067 has occurred.

I took a couple deep breaths and it occurred to me to do what I guess
was obvious:  Run mongod.exe from the command line, instead of trying
to start it as a service.  That displayed the actual MongoDB error
messages, and it turned out that there wasn't enough free space to
preallocate the journal file.  It was as simple as that.  One that was
resolved, the Windows service started up like a charm.

Then I checked the log file, and sure enough, the messages were there,
too.  So it wasn't an issue with the Windows service.  It was just
that the service, when it encountered the error, wasn't able to pass
through the actual error messages.

gs


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Discussion subject changed to "Cannot start MongoDB: System error 1067 in Windows" by Gregory Chris
Gregory Chris  
View profile  
 More options Jan 29, 4:12 am
From: Gregory Chris <sgch...@gmail.com>
Date: Tue, 29 Jan 2013 01:12:21 -0800 (PST)
Local: Tues, Jan 29 2013 4:12 am
Subject: Re: Cannot start MongoDB: System error 1067 in Windows
Print | Individual message | Show original | Report this message | Find messages by this author

For me it was:

*Unclean shutdown detected.*

*Please visit http://dochub.mongodb.org/core/repair for recovery
instructions.*

a few steps will fix it (as it's written in the link above):
1) remove the file */data/db/mongod.lock*
2) run *mongod.exe --repair*
3) start the mongod service

Greg


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google