[SERVER-13597] MongoDB 2.6 crashes unexpectedly on Windows (2.4 or earlier was stable) Created: 15/Apr/14 Updated: 10/Dec/14 Resolved: 16/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Kennedy | Assignee: | Mark Benvenuto |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | Windows, crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Not sure, see crash dumps? |
||||||||
| Participants: | |||||||||
| Description |
|
We have been running MongoDB for http://learninglineapp.com and http://develop.com for over a year (maybe almost two). They are hosted in EC2 on Windows server 2008 R2. Until we switched to 2.6 they have been rock solid. But since we upgraded to 2.6, MongoDB has begun crashing unexpectedly. I don't have much information to put in the description. However, I do have the log file and minidumps. They are attached. Here is what is in the Windows event log: The MongoDB (master) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Finally, here is what we get back in .NET as a stack trace (nothing interesting, just the server is missing basically): MongoDB.Driver.MongoConnectionException: Unable to connect to server localhost:27017: No connection could be made because the target machine actively refused it 127.0.0.1:27017. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:27017 I'm happy to work with you (screensharing, whatever) to help track this down. |
| Comments |
| Comment by Michael Kennedy [ 16/Apr/14 ] | |||||||||
|
Great, thanks Dan. | |||||||||
| Comment by Daniel Pasette (Inactive) [ 16/Apr/14 ] | |||||||||
|
fix was made for 2.6.1: | |||||||||
| Comment by Michael Kennedy [ 16/Apr/14 ] | |||||||||
|
Nice to see you have it reproducible. Any idea when the fix is planned for? If it's not the next point release, I need roll back to 2.4. | |||||||||
| Comment by Mark Benvenuto [ 16/Apr/14 ] | |||||||||
|
It is a duplicate of
| |||||||||
| Comment by Michael Kennedy [ 15/Apr/14 ] | |||||||||
|
That's correct Mark. Thank you for reposting it. Jason, I restarted my server with verbose logging. It crashes a few times a day. I'll send you the log when it does. | |||||||||
| Comment by Mark Benvenuto [ 15/Apr/14 ] | |||||||||
|
This is stack trace. mongo::mutablebson::Document::Impl::writeElement<mongo::BSONArrayBuilder>+0x5e [d:\data\mci\git@github.commongodb\mongo.git\mongodb-mongo-v2.6\src\mongo\bson\mutable\document.cpp @ 2095] | |||||||||
| Comment by J Rassi [ 15/Apr/14 ] | |||||||||
|
Hi, Are you able to reproduce this issue? If so, please add the "-vvv" flag to your mongod startup options (or the line "vvv=true" to your mongod config file) and attach the full mongod log file (not just an excerpt, if possible) after reproducing a crash. ~ Jason Rassi | |||||||||
| Comment by Michael Kennedy [ 15/Apr/14 ] | |||||||||
|
Here is the crash in the log (also included in the attached zip file) 2014-04-15T08:17:53.119-0700 [initandlisten] connection accepted from 127.0.0.1:59166 #205 (5 connections now open) |