Problematic tid found
Nick Sincaglia <[email protected]> Sat, 27 Jul 2024 13:23:42 -0500
| Newsgroups | gmane.text.xml.exist |
|---|---|
| Organization | NueMeta, LLC |
| Message-ID | <[email protected]> |
If our eXist-db has an unclean shutdown and we restart it and we see the below error, in our logs, what is the recommended action we should take? 2024-07-27 18:16:28,239 [main] ERROR (BFile.java [readOffsets]:2547) - Problematic tid found: 12338; trying to recover ... 2024-07-27 18:16:28,240 [main] ERROR (BFile.java [readOffsets]:2547) - Problematic tid found: 19508; trying to recover ... 2024-07-27 18:16:28,240 [main] ERROR (BFile.java [readOffsets]:2547) - Problematic tid found: 17473; trying to recover ... This error does not indicate whether the effort to recover the tid was successful or not. What is a tid? My experience historically, has been to instantiate another server and try to export the data and import it into the new server. I don't believe I have ever been able to reliably fix whatever this error is trying to tell me. I just try to get a new system setup and replace the system that reports this error. I would be interested in hearing what other people do or recommend. Nick -- Nick Sincaglia President/Founder NueMeta, LLC Digital Media & Technology Phone: +1-630-303-7035 [email protected] http://www.nuemeta.com Skype: nsincaglia _______________________________________________ Exist-open mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/exist-open