On Thu, 2009-06-18 at 12:56 +0200, Matteo Pelucco wrote: > ********************************** > INFO info.magnolia.cms.beans.config.ContentRepository > ContentRepository.java(loadWorkspace:368) 18.06.2009 10:32:33 System : > loading workspace data > ERROR org.apache.jackrabbit.core.query.OnWorkspaceInconsistency > OnWorkspaceInconsistency.java(handleMissingChildNode:57) 18.06.2009 > 10:49:14 Node /news/latest/2009/04/16 > (6c7fe878-3275-49c9-aea8-cf711e9af1a8) has missing child > 'latestnews-77708' (2e1816d1-bbc3-4d0a-98de-951aca1c1aa8) > ERROR org.apache.jackrabbit.core.RepositoryImpl > RepositoryImpl.java(getWorkspaceInfo:733) 18.06.2009 10:49:14 Unable to > initialize workspace 'data'... > **********************************
It's the whole child node that is missing, so what you can do here is use the tools module to delete the parent (/news/latest/2009/04/16) ... before doing so you can try to export all of its other children so you can re-import them back later. > > (in attachment you can see the full log) > > So, I tried to add these lines on jackrabbit-mysql-search.xml > > <param name="forceConsistencyCheck" value="true" /> > <param name="enableConsistencyCheck" value="true" /> > <param name="autoRepair" value="true" /> > > But nothing happens. Indeed, the consistency check is able to repair missing references within one workspace, but not missing nodes ... unfortunately. > > I've thought: ok, if that node causes so much trouble, why not remove > the parent and all the children? > It is impossible from Magnolia, I'm wondering how to force node removal. > Can magnolia tool help us? And in this case, how can I use Magnolia Tool > for node removal or JCR consistency check? yes, magnolia-tools is the answer as i already said above. If you download the module there is script you can use to remove the node from command prompt while your instance is down. Alternatively on the wiki should be a page that shows how you can remove node at runtime using tools and shell modules. In either case you will have to force reindexing afterwards (by removing "index" folder from the workspace while instance is down). Any ideas as to what caused the error? Did you have to kill this instance in the past, or have you had some OOM errors or some similar situation in which save() operation on "data" repository could not have been successfully performed? HTH, Jan ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
