Sometimes when you start up Magnolia, you will see in catalina.out the following message:

 
FATAL  info.magnolia.cms.servlets.Initializer Initializer.java(init:57)
06.07.20 05 11:13:02  Repository \[website\] not loaded 
java.lang.RuntimeException: Repository \[website\] not 
loaded at info.magnolia.cms.beans.config.ContentRepository.checkIfInitialized(ContentRepository.java:192) 
...

This means that the website repository was not loaded. Typically, this simply means that the lucene index is broken, but sometimes the data itself is corrupted, especially if you did a bootstrap that run out of memory .

If the former, make sure that magnolia is not running, then delete the index in question. For the website repository, this is found in repositories/website/workspaces/default/index.dat

Once the index is deleted, simply start Magnolia and check if the website is now loaded.

It has been suggested at the Jackrabbit list that this stems from the fact that we use CQFS to index the data instead of the Jackrabbit filesystem, but is unclear at this time if it makes any difference at all. If you find that using the JR filesystem instead of CQFS for the index resolves this issue, please let us know.

To use the JAckrabbit-filesystem implementation, change the SearchIndex entry in magnolia/WEB-INF/config/repository-configuration.xml