Component 'Forge' is already started - Endeca FORGE

Problem Statement:

When you try to run endeca baseline update you will see message as below:

 BASELINE SCRIPT STARTED
[07.11.15 11:38:32] INFO: Released lock 'update_lock'.
 Copy crawl files to incoming and processing folder
[07.11.15 11:38:33] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[07.11.15 11:38:34] INFO: Definition has not changed.
[07.11.15 11:38:34] INFO: Starting baseline update script.
[07.11.15 11:38:34] INFO: Acquired lock 'update_lock'.
[07.11.15 11:38:34] INFO: [ITLHost] Starting shell utility 'cleanDir_processing'.
[07.11.15 11:38:35] INFO: [ITLHost] Starting shell utility 'cleanDir_forge-output'.
[07.11.15 11:38:36] INFO: [ITLHost] Starting shell utility 'cleanDir_temp'.
[07.11.15 11:38:38] INFO: [ITLHost] Starting shell utility 'move_-_to_processing'.
[07.11.15 11:38:39] INFO: [ITLHost] Starting copy utility 'fetch_config_to_input_for_forge_Forge'.
[07.11.15 11:38:39] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_ConfigurationGeneratorForge'.
[07.11.15 11:38:40] INFO: [ITLHost] Starting component 'ConfigurationGeneratorForge'.
[07.11.15 11:39:10] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Forge'.
[07.11.15 11:39:11] INFO: [ITLHost] Starting component 'Forge'.
[07.11.15 11:39:11] INFO: Component 'Forge' is already started.


Solution:
It will happen if someone killed baseline update process while forge is running. Easy way to release or kill process is to get into Endeca experience manager and stop Forge process.