[SERVER-29958] waiting for daemon up ... Created: 03/Jul/17 Updated: 16/Aug/18 Resolved: 06/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.10 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | ludovic lachevre | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envc, envm, openshift, rge, rps, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
test |
||
| Attachments: |
|
| Participants: |
| Description |
|
hi,
is someone got an idea ? very thanks a lot ludo |
| Comments |
| Comment by ludovic lachevre [ 07/Jul/17 ] |
|
Hi Mark, Thanks a lot for your advice. Thanks for everything Ludo |
| Comment by Mark Agarunov [ 06/Jul/17 ] |
|
Hello llachevre, Thanks for your response. I'm glad to hear that this fixed the issue and everything is working again. To prevent this type of problem in the future, we recommend implementing regular backups and/or replication to mitigate any issues related to unreliable storage layers or server failures. Thanks, |
| Comment by ludovic lachevre [ 04/Jul/17 ] |
|
Hi mark, thanks a lot for your help. i will try to answer to your 7 questions. in fact we are in an openshift platform and we installed RHMAP 1. so the storage is not local but over a network (openshift) 2. pvc-fed5f527-4ace-11e7-8729-0050569a54b5 50Gi RWO Delete Bound mbaas-rhmap/mongodb-claim-1 27d mongodb-claim-1 Bound pvc-fed5f527-4ace-11e7-8729-0050569a54b5 50Gi RWO 27d 3. db version v3.2.10 4. 5. 6. 7. please joined, a list of packages updated the 2 of july Thanks a lot Ludo |
| Comment by Mark Agarunov [ 03/Jul/17 ] |
|
Hello llachevre, Thank you for the report. I've attached a repair attempt of the files you've provided. Would you please extract these files and replace them in your $dbpath and let us know if it resolves the issue? If you are still seeing errors after replacing these files, please provide the complete logs from mongod so that we can further investigate. Additionally, if this issue persists, please provide the following information:
Thanks, |
| Comment by ludovic lachevre [ 03/Jul/17 ] |
|
the files you want thanks ludo |
| Comment by ludovic lachevre [ 03/Jul/17 ] |
|
ok no problem. in my case the mongodb pod 2 and 3 are ok but not the 1, why ? i don't know. thanks for your help so. please joined the files you want thanks a lot ludo |
| Comment by Kelsey Schubert [ 03/Jul/17 ] |
|
Hi llachevre, If you can provide the files, we can attempt a repair. However, please note note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server, and this corruption was likely the result of an issue outside of MongoDB. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, |
| Comment by ludovic lachevre [ 03/Jul/17 ] |
|
Hi Thomas, thanks a lot for your quick answer. another problem is : how can i recover files from a pod to my linux server ? (outside the pod) thanks a lot ludo |
| Comment by Kelsey Schubert [ 03/Jul/17 ] |
|
Hi llachevre, It appears that WiredTiger.wt file has suffered some form of disk corruption. Would you please upload WiredTiger.wt and WiredTiger.turtle files so we can attempt a repair? If the files cannot be repaired, I would suggest resyncing from another node or, if that is not possible, restoring from a backup. Kind regards, |