[SERVER-31544] mongodb abnormal downtime Created: 13/Oct/17  Updated: 19/Oct/17  Resolved: 19/Oct/17

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

Type: Question Priority: Critical - P2
Reporter: SuperSuJJ [X] Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File diagnostic.tar    
Backwards Compatibility: Fully Compatible
Participants:

 Description   

os version:centos 6.6
mongodb version : 3.2.8

mongodb abnormal downtime,and i found not unusual and not error in log.

the log last message:

2017-10-13T03:20:49.426+0800 I WRITE    [conn57637] update inventory.sessions query: { _id: "2oHN_UZIEpXivUZfZUNUVQNytEYHykLY" } update: { _id: "2oHN_UZIEpXivUZfZUNUVQNytEYHykLY", session: "{"cookie":{"originalMaxAge":86400000,"expires":"2017-10-13T19:20:49.155Z","secure":false,"httpOnly":true,"path":"/"},"passport":{}}", expires: new Date(1507922449155) } keysExamined:0 docsExamined:0 nMatched:1 nModified:1 upsert:1 keyUpdates:0 writeConflicts:0 numYields:0 locks:{ Global: { acquireCount: { r: 1, w: 1 } }, Database: { acquireCount: { w: 1 } }, Collection: { acquireCount: { w: 1 } } } 252ms
2017-10-13T03:20:49.426+0800 I WRITE    [conn57395] update inventory.sessions query: { _id: "OdFFujyEI3HvWeFGxAGYbIG9Aim8JUk0" } update: { _id: "OdFFujyEI2017-10-13T09:07:13.776+0800 I CONTROL  [main] ***** SERVER RESTARTED *****

but i can not see the diagnostic.data.



 Comments   
Comment by Bruce Lucas (Inactive) [ 19/Oct/17 ]

Thanks for contacting us, and sorry we weren't able to diagnose what happened from the available information. I'll close this ticket as requested.

Bruce

Comment by SuperSuJJ [X] [ 19/Oct/17 ]

hi,
thanks for help! I have nothing to upgrade,please close this ticket,ths!

Comment by Bruce Lucas (Inactive) [ 17/Oct/17 ]

Hi,

Thanks for the additional data. Unfortunately there is nothing in diagnostic data for about 3 months preceding the incident. If you are able to upload all available mongod logs up to the time of the incident possibly we can find some additional clues, although that may be unlikely as you indicate nothing unusual in the logs. Otherwise I think we've reached the end of the road for this ticket.

Bruce

Comment by SuperSuJJ [X] [ 17/Oct/17 ]

thanks for help! I use gzip compress the diagnostic.data and upload it , but i see the diagnostic.data after the issue time i can not see the other log.

Comment by Bruce Lucas (Inactive) [ 16/Oct/17 ]

Hi,

Thanks for attaching the additional files. However, those files are from after the time of the incident. Can you please archive the entire diagnostic.data directory, for example tar cf dd.tar diagnostic.data, and attach the archive to this ticket?

Thanks,
Bruce

Comment by Bruce Lucas (Inactive) [ 13/Oct/17 ]

Hi,

The attached metrics file is from a much earlier time than the last log message that you report. Is it the only file in the diagnostic.data directory? If not can you please archive and attach to this ticket the entire diagnostic.data directory?

Also, can you please attach the entire log file containing the restart?

Thanks,
Bruce

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