If the search index of the system/version workspace cannot be re-built and there is an exception in the log file NoSuchItemStateException: deadbeef-cafe-babe-cafe-babecafebabe
A common reason for the problem is a invalid child node entry from jcr:system to crx:nodeTypes.
If you try to re-create the search index for the system/version workspace, and you get the exception NoSuchItemStateException: deadbeef-cafe-babe-cafe-babecafebabe
If your problem is an invalid child node entry from jcr:system to crx:nodeTypes then the following steps will fix the problem:
server/console.sh
, and set replace REPOSITORY_HOME="$CONTEXT/crx"
with REPOSITORY_HOME="$CONTEXT/../repository"
if this is not yet done. (Please note you can't just add the line at the top of the script, because at that time the CONTEXT may not be set, which would cause the console use a different repository).
cd crx-quickstart/server
./console.sh
cd jcr:system
stat
ChildNode Entries:
+ {http://www.jcp.org/jcr/1.0}versionStorage[1] -> deadbeef-face-babe-cafe-babecafebabe
+ {http://www.jcp.org/jcr/1.0}nodeTypes[1] -> deadbeef-cafe-cafe-cafe-babecafebabe
+ {internal}accessControl[1] -> 2cccff3f-c6fe-4294-a030-7c830c6c36ef
+ {http://www.day.com/crx/1.0}nodeTypes[1] -> c67e22c1-2eee-4e48-9505-f00bcf590a36
+ {http://www.day.com/crx/1.0}nodeTypes[2] -> e4469e5a-4892-4760-acd6-3a3e8f120d4e
crx:nodeTypes
entry, it is a different problem. If you don't see any http://www.day.com/crx/1.0
entries then you are connected to the wrong repository (review step #2 regarding how to fix the REPOSITORY_HOME
the console.sh script).
crx:nodeTypes
entries, then do the following to access them to find out which one is invalid:stat a42b98a1-b4c1-4f11-8c11-734455a4f53d
rm -c a42b98a1-b4c1-4f11-8c11-734455a4f53d
stat
exit
CRX 1.4.x
Sign in to your account