[SERVER-14155] Segmentation fault Created: 04/Jun/14 Updated: 10/Dec/14 Resolved: 17/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | qing cao | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 6.3 |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
An error occurred in running after a period of time in a secondary. |
| Comments |
| Comment by Ramon Fernandez Marina [ 17/Jun/14 ] | ||
|
caoqing we're going to mark this issue as resolved. Feel free to reopen if it happens again after removing the nproc limitation. | ||
| Comment by qing cao [ 17/Jun/14 ] | ||
|
I found i had set a wrong parameter by mistake.
After i fixed it the error had never occurred.
But I don't know why I have came across this issue. cat /proc/`pidof mongod`/limits|grep -i "max processes" | ||
| Comment by Ramon Fernandez Marina [ 05/Jun/14 ] | ||
|
Looking at the logs I get the impression that there are too many connection attempts to the secondary, and some OS limit is being hit (e.g.: number of file descriptors, memory allocation). It would be useful to see the mongod.log file for the last few hours/days leading up to this error. If the error happens soon after restarting MongoDB on the secondary, then please proceed as follows:
and send us the resulting mongod.log file when the error happens. The output of ulimit -a could be useful as well. Note that your logs also contain the following:
The SYN flooding message might be legitimate, but could also indicate a DOS attack. Is it possible for you to post the output of netstat -a? | ||
| Comment by qing cao [ 05/Jun/14 ] | ||
|
Hi, , , { "_id" : 6, "host" : "dal05mgo08.sl.dx:27017" } ] | ||
| Comment by J Rassi [ 04/Jun/14 ] | ||
|
Hi, I notice the following from the log except you posted:
I conclude that the the mongod process failed to allocate memory, likely due to an OOM condition in the OS. The next step would be to attempt to determine whether the cause of the issue is a novel memory leak in the server.
~ Jason Rassi |