[SERVER-4544] "unable to connect to mongo program on port 31000" in auth2.js test Created: 22/Dec/11 Updated: 29/May/12 Resolved: 23/Jan/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | Linux | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
http://buildbot.mongodb.org/builders/Linux%2064-bit/builds/3968/steps/test_1/logs/stdio
|
| Comments |
| Comment by Eric Milkie [ 23/Jan/12 ] | ||||||||||||||||
|
Went away again. I didn't get the Windows build to crash.. | ||||||||||||||||
| Comment by Eric Milkie [ 31/Dec/11 ] | ||||||||||||||||
|
I'm hoping to get this test (and others) running under Windows so that we'll have multiple angles to attack this. Perhaps Windows will detect something or the stack trace will be different. | ||||||||||||||||
| Comment by Spencer Brody (Inactive) [ 30/Dec/11 ] | ||||||||||||||||
|
Submitted d9d0b431f225c4e3369a6e320b2ee45ff6d8c9be to get thread name on segfault, so hopefully we'll have a little more information next time this happens. | ||||||||||||||||
| Comment by Spencer Brody (Inactive) [ 30/Dec/11 ] | ||||||||||||||||
|
This happened in a different test now. replsets/majority.js. Tracked in | ||||||||||||||||
| Comment by Eric Milkie [ 27/Dec/11 ] | ||||||||||||||||
|
Test failed again in Linux 64bit: http://buildbot.mongodb.org:8081/builders/Linux%2064-bit/builds/3994/steps/test_1/logs/stdio
Interestingly, that last line in the snippit above is the last thing we hear from 31000. I guess if we encounter recursive signal 11's, we just immediately abort after the first one? | ||||||||||||||||
| Comment by Spencer Brody (Inactive) [ 22/Dec/11 ] | ||||||||||||||||
|
The problem is that a node segfaulted on startup:
Unfortunately that stack trace tells us very little about what went wrong. |