[SERVER-23793] core dump on mongod Created: 19/Apr/16 Updated: 29/Apr/16 Resolved: 29/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 3.2.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Malie | Assignee: | Jonathan Reams |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | 1.I connect cfg servers through server A like this 3.step 1 once more 4.cores appered(and I also found it in 3.0 version) 5.but I open another window to connect cfg servers it is normal so I get confused (maybe his core can't reproduce,so I uploading the core file) |
||||||||
| Sprint: | Platforms 13 (04/22/16), Platforms 14 (05/13/16) | ||||||||
| Participants: | |||||||||
| Description |
|
-bash-4.1$ mongo admin -usiteRootAdmin -proot -host res_cfg/10.45.6.237:37017,10.45.6.237:37018,10.45.6.237:37019
|
| Comments |
| Comment by Jonathan Reams [ 29/Apr/16 ] | ||||||||||||||||||
|
I agree that the error message wasn't clear at all, and I've opened | ||||||||||||||||||
| Comment by Malie [ 29/Apr/16 ] | ||||||||||||||||||
|
I just think these error outputs can not let me know what happend I don't know how to analyze it ,it makes me confused。 | ||||||||||||||||||
| Comment by Jonathan Reams [ 22/Apr/16 ] | ||||||||||||||||||
|
I've confirmed that we can repro this by setting ulimit -u to a very low number and trying to start the mongo shell. I'll open a ticket to handle std::thread creation failure better. | ||||||||||||||||||
| Comment by Jonathan Reams [ 22/Apr/16 ] | ||||||||||||||||||
|
402309718@qq.com, This is failing because mongo is unable to start a new thread while initializing the javascript engine. The shell hasn't even gotten to the point where it could connect to a config server, so I don't think killing/restarting the config servers has anything to do with this. What version/distro of Linux are you running? What is the output of ulimit -u on your system? Can you try raising the number of threads your user is allowed to start? | ||||||||||||||||||
| Comment by Jonathan Reams [ 22/Apr/16 ] | ||||||||||||||||||
|
symbolized backtrace:
|