[SERVER-25945] Replica set keeps sequentially crashing Created: 02/Sep/16  Updated: 21/Sep/16  Resolved: 21/Sep/16

Status: Closed
Project: Core Server
Component/s: Replication, Stability, WiredTiger
Affects Version/s: 3.2.7
Fix Version/s: None

Type: Question Priority: Critical - P2
Reporter: J Scott Chapman Assignee: Kelsey Schubert
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File _usr_bin_mongod.106.crash    
Participants:

 Description   

The replica set is stable for some time. HD space, memory, and swap file seem to be all in line. Checked the mongodb log and it reports no error and shows where we restarted the servers with a large time gap in between. Checked the oplog size and it says it's good for 1000hours. I tested the connections between the members using ping and the "mongo --host m2.example.net --port 27017" method. Everything looks good.



 Comments   
Comment by Kelsey Schubert [ 21/Sep/16 ]

Hi jscott.developer@gmail.com,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Regards,
Thomas

Comment by Kelsey Schubert [ 02/Sep/16 ]

Hi jscott.developer@gmail.com,

Thanks for reporting this issue. So we can continue to investigate, would you please upload the complete mongod logs as well as an archive of the diagnostic.data directory?

I've created a secure upload portal for you to use here.

Kind regards,
Thomas

Generated at Thu Feb 08 04:10:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.