[SERVER-18382] server died unexpectedly Created: 08/May/15  Updated: 18/Jun/15  Resolved: 18/Jun/15

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Dwayne Mcnab Assignee: Sam Kleinman (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mongodb.log     Text File mongodb.log     File mongodb.log.tbz2    
Participants:

 Description   

Running a 3 member replica set config. Both Secondaries died unexpectedly. I checked the kernel logs I didnt find anything to support my hypothesis of a OOM killer. Here is a snippet of the error in mongodb.log:

mongo_error message
mongo03
mongod(_ZN5mongo4repl14BackgroundSync14producerThreadEv+0x344) [0xc03664]
mongod(+0xBB4844) [0xfb4844]
libpthread.so.0(+0x79D1) [0x32b06079d1]
libc.so.6(clone+0x6D) [0x32b02e88fd]
----- END BACKTRACE -----
2015-05-08T15:44:16.079Z I - [rsBackgroundSync]

mongo02

mongod(_ZN5mongo4repl14BackgroundSync14producerThreadEv+0x344) [0xc03664]
mongod(+0xBB4844) [0xfb4844]
libpthread.so.0(+0x79D1) [0x31644079d1]
libc.so.6(clone+0x6D) [0x31640e88fd]
----- END BACKTRACE -----
2015-05-08T15:47:48.425Z I - [rsBackgroundSync]

Please help.

Thanks,

Dwayne



 Comments   
Comment by Ramon Fernandez Marina [ 18/Jun/15 ]

dmcnab, we haven't heard back from you for some time so I'm going to close this issue. If this behavior persists please send us logs with backtrace snippets as requested above and we can reopen the ticket for further investigation.

Regards,
Ramón.

Comment by Ramon Fernandez Marina [ 21/May/15 ]

dwayne@q1media.com, unfortunately the logs you uploaded do not contain the backtrace snippets you posted in the ticket. Without detailed logs containing the last messages before the backtrace and the complete backtrace information there's not much we can do to troubleshoot this issue. Do you still have those logs?

Comment by Dwayne Mcnab [ 11/May/15 ]

Here you go.

Dwayne Mcnab
Database Developer
Q1Media.com <http://www.q1media.com/>
M: 305-772-6435
LinkedIn <http://www.linkedin.com/in/dwaynemcnab>

Comment by Ramon Fernandez Marina [ 11/May/15 ]

dwayne@q1media.com, you can either upload the compressed logs (which is always a good idea anyway) or upload large files via scp:

scp -P 722 -r <filename> SERVER-18382@www.mongodb.com:

Just press enter when prompted for a password.

Comment by Dwayne Mcnab [ 11/May/15 ]

The last one is too big. Exeeds 500 MB

Dwayne Mcnab
Database Developer
Q1Media.com <http://www.q1media.com/>
M: 305-772-6435
LinkedIn <http://www.linkedin.com/in/dwaynemcnab>

Comment by Dwayne Mcnab [ 11/May/15 ]

Thanks for your reply Ramon. Please see the logs you¹ve requested

Dwayne Mcnab
Database Developer
Q1Media.com <http://www.q1media.com/>
M: 305-772-6435
LinkedIn <http://www.linkedin.com/in/dwaynemcnab>

Comment by Ramon Fernandez Marina [ 09/May/15 ]

dwayne@q1media.com, unfortunately there's is not information above to investigate this issue. Can you please upload full logs from all three members of your replica set from the last startup until the time when the backtraces above were produced?

Thanks,
Ramón.

Generated at Thu Feb 08 03:47:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.