Hi,
I was looking at our log files and noticed the following ERROR:
com.day.cq.replication.impl.ReplicationContentFactoryProviderImpl Unable to read replication content stored in /var/replication/data/1a80cfd3-0179-4392-ba73-8c7775f51933/c8/c82e1905-9b6f-47b7-a36e-eae5410c2d18. Node is missing.
As far as I can tell, replication has completely stopped after this error as there aren't any other logs (INFO/ERROR) for the com.day.cq.replication package in the log file.
Is there a way to prevent these fatal "node missing" errors from occurring?
Solved! Go to Solution.
Views
Replies
Total Likes
follow [1] for now. To prevent happening need complete set of log to find what caused to get into that state. Generally I have see this happening if miscommunication in team collaboration between maintenance & authoring activity.
[1] http://helpx.adobe.com/experience-manager/kb/replication-stuck.html
Views
Replies
Total Likes
follow [1] for now. To prevent happening need complete set of log to find what caused to get into that state. Generally I have see this happening if miscommunication in team collaboration between maintenance & authoring activity.
[1] http://helpx.adobe.com/experience-manager/kb/replication-stuck.html
Views
Replies
Total Likes
This may help you find the missing content nodes so you avoid this error: http://aemfaq.blogspot.com/2013/12/how-to-find-missing-content-nodes-in.html
Views
Replies
Total Likes
Views
Like
Replies