Rest Service Setup logs error when "api" node already exists

You can enable the generic Rest resources using the Essentials Rest Services setup tool. Just make sure you enable this option and click "Run setup". If you do that again, a stacktrace shows in the log. This should be avoided. Essentials as a rule silently skips steps if they already have been done, so here we should follow the same pattern. It would be much better of course if the UI would prevent you from doing this.

I ran into this when I tried to add the Manual services in a second step. You check the box for it, select a document type and click Run setup. The stacktrace is confusing, especially since no problem occurs.

[INFO] [talledLocalContainer] 03.03.2016 16:42:54 ERROR http-nio-8080-exec-2 [XmlInstruction.copy:136] Error on copy node
[INFO] [talledLocalContainer] javax.jcr.ItemExistsException: Node with the same UUID exists:node /hst:hst/hst:hosts/dev-localhost/localhost/hst:root/api
[INFO] [talledLocalContainer] at org.apache.jackrabbit.core.xml.SessionImporter.startNode(SessionImporter.java:380)
[INFO] [talledLocalContainer] at org.apache.jackrabbit.core.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:93)
[INFO] [talledLocalContainer] at org.apache.jackrabbit.core.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:248)
[INFO] [talledLocalContainer] at org.apache.jackrabbit.core.xml.ImportHandler.endElement(ImportHandler.java:195)
.... etc