[SERVER-6247] mongod is no longer running, "terminate called()" error Created: 29/Jun/12 Updated: 15/Aug/12 Resolved: 29/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Melanie Galloway | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mongo installed on a Unix machine, I'm accessing it from a windows computer via putty/ssh |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Never had issues with mongo before. I'd recently installed it on a cluster at my University because there were several .bson files I needed to analyze there, and I've been working with it from my laptop. Was able to restore all the files, make queries successfully, etc. Yesterday when I started mongo and typed "show dbs" I got some error and found a lock file in data/db (sorry I don't have the specific error anymore), but searching online indicated that the databases may have been corrupted due to not exiting mongo properly (very likely, I didn't realize being careless with this would cause problems. Lesson learned.) I couldn't find a way to fix this, so I simply removed everything from data/db, the goal being to just restore them all. However, then when I started mongod, the following error occurred. I tried removing and reinstalling mongo, but I still get this error. Please help! ./mongod --dbpath='/home/user1/data/db' Thu Jun 28 21:38:08 terminate() called, printing stack: Thu Jun 28 21:38:08 Backtrace: |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 29/Jun/12 ] |
|
Weird! It's difficult to tell from this. It sounds like a system error? If you get it again, we might be able to use GDB to figure out where it's crashing. |
| Comment by Melanie Galloway [ 29/Jun/12 ] |
|
Thank you for the reply. What I pasted originally was everything up until the terminal prompt. I just went to start mongod to repaste everything again just in case, and it's working fine now! For future reference, is it possible that this was a temporary error with the server I was on, or do you know if this was an error with mongo specifically? Thanks again, even though the problem seems to have corrected itself. |
| Comment by Kristina Chodorow (Inactive) [ 29/Jun/12 ] |
|
Please paste all of the output from the terminal, from the ./mongod line to when it exits and you get the terminal prompt again. |
| Comment by Melanie Galloway [ 29/Jun/12 ] |
|
I don't know how to do that.. (inexperienced/new with all this). Do you have an idea of what's going on? |
| Comment by Eliot Horowitz (Inactive) [ 29/Jun/12 ] |
|
Can you attach full server log? |