[SERVER-35736] WiredTiger error (-31804) [1529626394:169565][36076:140706182402176], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic Fatal Assertion 28558 at src\mongo\db\storage\wiredtiger\wiredtiger_util.cpp 361 Created: 22/Jun/18 Updated: 04/Sep/18 Resolved: 22/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.6.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Angel Giraldo [X] | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rns, rpu, trct, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | Windows | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: |
| Description |
|
Mi problema se estructura en: 1) No puedo iniciar el servidor de la base de datos "mongod" porque se cierra y me lanza el error mencionado anteriormente en el titulo y este "***aborting after fassert() failure" ademas de que ya intente con el comando mongod --repair sin conseguir exito. 2) Necesito urgentemente rescatar la base de datos y ciertas colecciones ya que desarrolle un programa para un almacen y no se puede perder esa informacion, asi que tambien me gustaria saber como puedo recuperarla en caso de no poder iniciar el servidor desde este pc para importar los datos en otra. nota: no puedo usar mongodump o mongoexport porque el servidor no esta funcionando. Ojala me puedan ayudar, estaría muy agradecido.
|
| Comments |
| Comment by Nick Brewer [ 22/Jun/18 ] |
|
AnnonymousDO Yes, if there's no replica or backup, there's nothing that can be done. I wish we could help you out, and it's certainly not a matter of money - the fact is that the WiredTiger.turtle file is used to interpret all other files; without any working copy of it from a backup or replica, there's simply nothing we can do. Nick |
| Comment by Angel Giraldo [X] [ 22/Jun/18 ] |
|
the problem is that i haven't done any copy or replica or backup , so it means that we cannot make anything? and i'd like to know if maybe exists a possibility in a specific place, be it a web page or you offer some repairs service to archives but collecting money and then in case you can solve the problem? |
| Comment by Nick Brewer [ 22/Jun/18 ] |
|
I can certainly empathize with the tough situation you're in - I'll see if I can explain your options moving forward: You would need to already have a replica set in place in order to resync a mongod node that has been affected by this type of corruption. A replica set is a group of mongod processes that all contain the same data set - if you only have a single mongod instance, you would not have any additional copies to resync from. If you are not using replication at the mongod level, you'll need to take a look at any backups you've taken on the machine that is running mongod - whether that's an offsite backup, a separate hard drive/filesystem, or anywhere outside of your system that you've recreated your dbpath data. Nick |
| Comment by Angel Giraldo [X] [ 22/Jun/18 ] |
|
Ramon hello, please excuse me... i have a really big problem but i dont understand how can i one backup with a replica set, we have some possibility to text in whatever social media and you could explain to me ? sorry that's very disrespectful but seriously you are my only option |
| Comment by Ramon Fernandez Marina [ 22/Jun/18 ] |
|
AnnonymousDO, I'm sorry to hear that you had trouble with your installation; these issues are commonly caused by unclean shutdowns and storage problems (e.g.: bad disks). It is strongly recommended you follow the recommendations above, specially the ones about backing up your data and using a replica set. Regards, |
| Comment by Angel Giraldo [X] [ 22/Jun/18 ] |
|
the computer has a windows 7 piracy and i think that is the reason, or i dont know |
| Comment by Nick Brewer [ 22/Jun/18 ] |
|
If you do not have a replica set, you would need to retrieve the information from any backups you've taken. As I am not familiar with your environment, it would be difficult to speculate as to the cause. This type of issue is commonly caused by an unclean shutdown of the database, or corruption at the filesystem level. Nick |
| Comment by Angel Giraldo [X] [ 22/Jun/18 ] |
|
If i had never done a replica i could'nt get it again ? And the last question... Why did that happen ? why the turtle file crashed, i must explain that situation to my customers. Thanks Angel :#
|
| Comment by Nick Brewer [ 22/Jun/18 ] |
|
AnnonymousDO I'm afraid that is not possible. In this situation, our best recommendation would be to resync the affected node if it is a member of a replica set, or restore from a backup if possible. A newly generated .turtle file would not contain the necessary metadata to retrieve the information you need. Nick |
| Comment by Angel Giraldo [X] [ 22/Jun/18 ] |
|
Y hay alguna forma de copiar los archivos de index y collection del dbPath para crear otro dbpath y que el nuevo me cree un .turtle que funcione asi poder recuperar las collections ?
|
| Comment by Nick Brewer [ 22/Jun/18 ] |
|
The corruption on the WiredTiger.turtle file appears to be bad enough that a repair is not going to work. I've uploaded my repair attempt on the .wt file, however I believe you're still going to run into the same error related to your .turtle file. The .turtle file contains important metadata used to interpret the WiredTiger.wt file, which is in turn used to interpret all other .wt files. Because of this, it's not possible to retrieve a specific collection's .wt file without the corresponding metadata files. For future reference, here's some precautions you can take to mitigate issues related to unreliable storage layers or server failures:
Regards, |
| Comment by Angel Giraldo [X] [ 22/Jun/18 ] |
|
@NickBrewer @nick.brewer Thank you so much, i hope that you can fix it, that said, i'd like to know if i have another opcion to get just the collection that i actually need, it got more 2500 documents and i cannot lose them. DBName: facturacion CollectionName: test |
| Comment by Nick Brewer [ 22/Jun/18 ] |
|
Unfortunately, based on the state of your WiredTiger.turtle file, it's appears unlikely that we will be able to recover the WiredTiger.wt file, which contains the essential metadata for interpreting other WiredTiger files. That said, if you could upload the WiredTiger.wt file itself, I'd be happy to try restoring it for you. You can add it as an attachment to this issue. — Desafortunadamente, según el estado de su archivo WiredTiger.turtle, parece poco probable que podamos recuperar el archivo WiredTiger.wt, que contiene los metadatos esenciales para interpretar otros archivos WiredTiger. Dicho esto, si pudiera subir el archivo WiredTiger.wt en sí mismo, me gustaría intentar restaurarlo para usted. Puede agregarlo como un archivo adjunto a este problema. — Thanks, |
| Comment by Angel Giraldo [X] [ 22/Jun/18 ] |
|
Porfavor alguien que me ayude con eso, ya no se que hacer y puedo perder mucho dinero.
|