Hi Marco, unfortunately the BundleFsPersistenceManager has no option to run a consistency check during startup. With the current archiva I see no way to force a consistency check on the running repository.
If you use the standalone archiva, one way could be: stop archiva Backup <archiva_home>/repositories Remove <archiva_home>/repositories completely start archiva Rescan Directories I'm not sure, if this works and/or if this leads to other errors, but at least with a out of the box archiva standalone the repositories directory is rebuilt after the restart. Greetings Martin Am Montag, 10. Oktober 2016, 17:28:14 CEST schrieb m...@mherrn.de: > Hello all, > > I have now had the time to try to fix my problem. > I have stopped archiva, > then I have modified the archiva.xml to point the internal and snapshot > repositories to totally different (empty) directories. > Then I have started archiva up again. > And did a directory scan for both repositories. > However I still get lots of > > 2016-10-10 17:23:48,401 [pool-6-thread-1] ERROR > org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager > [] - failed to read bundle: ed7c5e19-3418-4ab1-a810-a955469969d1: > java.io.EOFException > > message in the log file. And they don't stop. Archiva is writing them on > and on.. > > Also when browing the web UI, I get the message > > failed to retrieve item state of item > 51a07434-8277-41a2-80ad-61d8415b8642 > > for the groupId I have snapshot versions of. > > How can I get the database back into a consistent state? > > > Best regards > Marco > > > Hi Olivier, > > > > only some of them were deleted. > > I will try to remove all of them and if this fixes the problem. > > > > Best regards > > Marco > > > >> Hey > >> Did you delete all files from the repo or only few? > >> I would delete all otherwise the jackrabbit db will be really corrupted! > >> > >> On 28 September 2016 at 20:46, <m...@mherrn.de> wrote: > >>> Hi Martin, > >>> > >>> > a rescan (directories scanning action) does not help? > >>> > >>> I have done that and now the server has massive load since days (the IO > >>> connection is unfortunately very bad, so that may be the main cause). > >>> However the problems about missing bundles still persists. > >>> I have to recheck this with a new empty repository. > >>> > >>> If this doesn't help, do you have an idea on how to best recreate the > >>> repostory then? > >>> > >>> > For 2: would be great if you can create a issue in the Jira. > >>> > >>> OK, I will do that. > >>> > >>> Best regards > >>> Marco > >> > >> -- > >> Olivier Lamy > >> http://twitter.com/olamy | http://linkedin.com/in/olamy
