While performing few “emgr_update”operations, sometimes we get “Could not open acquire_lock.status.” error.
For example performing dimension upgrade or performing set_template and other for Endeca Experience Manager.
emgr_update --host localhost:172.20.187.149 --action set_templates --prefix MyDemo --dir /opt/endeca/apps/MyDemo/config/cartridge_templates -app_name MyDemo
In the above example, we miss to add port entry, adding correct port will fix the above issue.
C:\Endeca\PlatformServices\11.1.0\bin>emgr_update.bat --host localhost:8888 --app_name <appname> --prefix <appprefix> --action set_post_forge_dims --post_forge_file C:\Endeca\Apps\<appname>\<appname>.dimensions.xml ERROR: Could not open acquire_lock.status.
In the above example and many other similar, we have to confirm that used “HOST” and “PORT” are correct. As if any of the entries are wrong we will get “Could not open acquir_lock.status.”
Below is USAGE for emgr_update for more details.
================================================= USAGE: emgr_update <parameters> DESCRIPTION: Utility to assist in updating the instance configuration of a production system based on changes made with the Endeca Tools in a staging environment. REQUIRED PARAMETERS: --host <name:port> Hostname and port of the IAP Workbench. --app_name <string> Application on the Central Server. --action <op> <op> is one of the following operations: get_ws_settings Gets only the instance configuration settings that can be modified by IAP Workbench. These configuration settings include the following IAP Workbench features: - Dynamic Business Rules - Keyword Redirects - Thesaurus Entries - Automatic Phrases - Stopwords - Dimension Order REQUIRED PARAMETERS: --dir, --prefix OPTIONAL PARAMETERS: --filter get_mdex_settings Gets only the instance configuration settins that can be modifed by IAP Workbench that do not require a baseline update to update the MDEX Engine. IAP Workbench features: - Dynamic Business Rules - Keyword Redirects - Thesaurus Entries - Automatic Phrases REQUIRED PARAMETERS: --dir, --prefix OPTIONAL PARAMETERS: --filter get_all_settings Gets all the instance configuration settings from the IAP Workbench in the staging environment, for use in the production system. REQUIRED PARAMETERS: --dir, --prefix OPTIONAL PARAMETERS: --filter update_mgr_settings Updates the IAP Workbench in the production environment with the instance configuration settings that were extracted from the staging environment. REQUIRED PARAMETERS: --dir, --prefix remove_all_settings Remove all the instance configuration settings from the IAP Workbench. set_post_forge_dims Update the IAP Workbench copy of the post forge dimensions. REQUIRED PARAMETERS: --post_forge_file get_post_forge_dims Get the IAP Workbench copy of the post forge dimensions. OPTIONAL PARAMETERS: --dir set_templates Update the IAP Workbench copy of the templates. REQUIRED PARAMETERS: --dir get_templates Get the IAP Workbench copy of the templates. REQUIRED PARAMETERS: --dir remove_templates Remove all templates from the IAP Workbench. OPTIONAL ACTION PARAMETERS: --dir <string> The path of the directory where the instance configuration files are written to or read from. --prefix <string> The prefix used for the instance configuration files. --filter Filters out dynamic business rules that have a state of inactive. --post_forge_file <string> File containing post forge dimensions. OPTIONAL GLOBAL PARAMETERS --ignore_warnings Continue without asking user if target directory is not empty before a get operation, or if there are extra or missing files before an update operation. --stop_on_warnings Stop without asking user if target directory is not empty before a get operation, or if there are extra or missing files before an update operation. --help Displays this message. --version Displays version. --ssl_enabled Checks if SSL is enabled or not. --truststore <string> Location of trust store certificate. --keystore <string> Location of key store certificate. --cipher <string> Algorithm used for encryption of SSL certificates. EXAMPLE: emgr_update --host localhost:8006 --action get_ws_settings --prefix <appname> --dir /apps/appname/data/forge_input --app_name <appname>
Hi Mandar,
I’m having endeca 11.1, I already had three apps running, while deploying fourth endeca application, initialize_services.bat is throwing error after I got ATG set up done through using CIM, which also utilizes 8006 port(Server Instance COnfiguration)(configured using weblogic server, even when weblogic servers have not been started) –
Severe- Utility ’emgr_update_update_mgr_settings’ failed (WorkbenchManager.updateWsConfig())
Could not open acquire_lock.status in log file present at endeca_conf\logs\shell location.
Is there a way to solve this?
Thanks.
Try and run below command and then run initialize_services.bat
runcommand.bat LockManager releaseLock update_lock