Sometimes when you execute your baseline update, Forge fails and produces no logs.
[06.28.13 11:34:01] SEVERE: Batch component 'Forge' failed. Refer to component logs in /data/endeca/apps/usapseattlesmall/./logs/forges/Forge on host ITLHost. Occurred while executing line 23 of valid BeanShell script: 20| 21| // archive logs and run ITL 22| Forge.archiveLogDir(); 23| Forge.run(); 24| Dgidx.archiveLogDir(); 25| Dgidx.run(); 26| [06.28.13 11:34:01] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks. Caused by java.lang.reflect.InvocationTargetException sun.reflect.NativeMethodAccessorImpl invoke0 - null Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script. Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException com.endeca.soleng.eac.toolkit.component.BatchComponent run - Batch component 'Forge' failed. Refer to component logs in /data/endeca/apps/usapseattlesmall/./logs/forges/Forge on host ITLHost. [06.28.13 11:34:01] INFO: Released lock 'update_lock'.
Possible issue here are:
1. Pipeline has incorrect XML format due your custom calculations
2. Forge did not start because of Environment Variables
To help with the Issue you should inspect your logs at $ENDECA_CONF/logs: process.x.log , invoke.x.log , main.x.log will give you hints on what went wrong.
Check Validity of Pipeline’s XML Content
You can execute a linux command to check whether your XMLs are properly formatted by:
xmllint --noout *.xml
if anything was printed on your terminal there is an issue with XML formatting.