[SERVER-31319] Invalid access at address: 0x400000 Created: 29/Sep/17 Updated: 07/Nov/17 Resolved: 01/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | SuperSuJJ [X] | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
os version:7.2 when i restart the machine after power failure and initialise the replication member,it issue:
|
| Comments |
| Comment by SuperSuJJ [X] [ 30/Sep/17 ] |
|
thanks for you help! I think this problem is the hardware too,because we rebuild the os yesterday,but when after we add the member with this machine,issue still error, when use the other server add this replication,it can use normal. The error log see we can find some memory issue,so we want change memory first,thank you very much. |
| Comment by Kelsey Schubert [ 29/Sep/17 ] |
|
Hi Su, Thank you for providing the additional log messages. These errors indicate a hardware issue external to mongod. To better understand what is happening, would you please upload the complete syslog from the affected machine? Kind regards, |
| Comment by SuperSuJJ [X] [ 29/Sep/17 ] |
|
thanks for you help. I update the log in the attachment,but i am sorry we lose the log during power failure. and the first.log is the first issue log,the second.txt is the second time, third is the last log. And it have the different error. we rm the data_path and initialization the member, it still have issue with the second.txt and third.txt. So i do not know how can do? |
| Comment by Kelsey Schubert [ 29/Sep/17 ] |
|
Hi Su, Would you please provide the complete log files starting before the power failure? I've created a secure upload portal for you to use. Files uploaded to this portal are only visible to MongoDB employees investigating this issue and are routinely deleted after some time. Thank you, |