When you run a consistency check and fix on your PersistenceManager, you get one or more of the following errors in the log. (It's likely that your uuids differ from these errors.)
Or, when you are reindexing the search index, it fails with this error (with the same uuid displayed):
NoSuchItemStateException: deadbeef-cafe-babe-cafe-babecafebabe.
If your problem matches one those listed above, then the following process will help you fix the corruption.
Until CRX 2.2 , use the old CRX Console :
From the CRX Console, follow these steps:
From the CRX Console, follow these steps:
From the CRX Console, follow these steps:
Note: If you have many errors to fix then you can prepare multiple items in these steps:
In step 4, open a text file and prepare multiple rm commands then paste the whole file's contents into the CRX console, for example:
rm [<child uuid 1>]
rm [<child uuid 2>]
save
exit
In step 6, you would have multiple items in the redo_X.log enter as below:
1 DEL <child uuid 1>
1 DEL <child uuid 2>
1 COM
You would replace the <child uuid 1> with the actual uuids of the child node in the error message, like in the example given above this would be 80b19738-b62b-4a6a-af9b-70f245d2a7bc
From the CRX Console, follow these steps:
Note: If you have many errors to fix then you can prepare multiple items in these steps:
In step 4, open a text file and prepare multiple rm commands then paste the whole file's contents into the CRX console, for example:
rm [<child uuid 1>]
rm [<child uuid 2>]
save
exit
In step 6, you would have multiple items in the redo_X.log enter as below:
1 DEL <child uuid 1>
1 DEL <child uuid 2>
1 COM
You would replace the <child uuid 1> with the actual uuids of the child node in the error message, like in the example given above this would be 46bbf932-3bd1-466d-bf93-7e0c99dc5707
See this article
CRX 1.4.x, CRX 2.x
Log ind på din konto