This discussion is archived
9 Replies Latest reply: Mar 6, 2013 2:29 AM by EndecaUser2013 RSS

Urgent : Error Communication with EAC agent

DevReddy Newbie
Currently Being Moderated
Hi All,

I am facing the below problem when i ran baseline update. Can someone help me what is causing this problem? and what to do to overcome this?

[10.16.12 12:18:08] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[10.16.12 12:18:10] INFO: Definition has not changed.
[10.16.12 12:18:10] INFO: Starting baseline update script.
[10.16.12 12:18:11] INFO: Acquired lock 'update_lock'.
[10.16.12 12:18:11] INFO: Downloading config files from Web Studio.
[10.16.12 12:18:11] INFO: [ITLHost] Starting shell utility 'cleanDir_config'.
[10.16.12 12:18:11] SEVERE: Error communicating with EAC agent while starting utility 'cleanDir_config'.
Occurred while executing line 10 of valid BeanShell script:
[[

7| if (Forge.isDataReady()) {
8| if (ConfigManager.isWebStudioEnabled()) {
9| // get Web Studio config, merge with Dev Studio config
10| ConfigManager.downloadWsConfig();
11| ConfigManager.fetchMergedConfig();
12| } else {
13| ConfigManager.fetchDsConfig();

]]

[10.16.12 12:18:11] 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.EacCommunicationException
com.endeca.soleng.eac.toolkit.utility.Utility start - Error communicating with EAC agent while starting utility 'cleanDir_config'.
Caused by com.endeca.eac.client.EACFault
sun.reflect.NativeConstructorAccessorImpl newInstance0 - null

[10.16.12 12:18:11] INFO: Released lock 'update_lock'.
  • 1. Re: Urgent : Error Communication with EAC agent
    Michael Peel Journeyer
    Currently Being Moderated
    Edit: wasn't paying attention to the error line, ignore this and read Saleh's post below.

    Looks like the baseline is failing at the first command related to the server hosting the Forge. Check your configuration to see if you made a mistake with the settings for the server hosting the Forge component. Alternatively, if the Forge/Dgidx is running on a separate server from the place you are running the script from and also from the Workbench server, check you have started the Endeca EAC service - you can verify by running eaccmd <server-name>:8888 --list-apps or trying to connect to http://<server-name>:8888/endeca_jspref with <server-name> being the server running the forge. 

    Michael

    Edited by: Michael Peel on 16-Oct-2012 02:30
  • 2. Re: Urgent : Error Communication with EAC agent
    sabdelhalim Newbie
    Currently Being Moderated
    Hi,
    it seems your ITL cannot get the merch rules from your Workbench ...
    can you chek if you workbench config ? (are you running on windows ? if so check that your tools service (port 8006) is started) and that no user is connected (no active session or modification of rules being active)
    hope that helps
    regards
    Saleh
  • 3. Re: Urgent : Error Communication with EAC agent
    DevReddy Newbie
    Currently Being Moderated
    Hi Michael,

    I am able to execute the below two commands successfully

    eaccmd <server-name>:8888 --list-apps  - giving me the list of endeca apps on my machine.

    http://<server-name>:8888/endeca_jspref - this is pointing me to the jsp ref application as usual, prompting me to enter host and port.

    I am able to login to workbech using http://<server_name>:8006
  • 4. Re: Urgent : Error Communication with EAC agent
    Michael Peel Journeyer
    Currently Being Moderated
    Ah, the problem is on the Forge server not the workbench server, the actual error is due to a script within the downloadWsConfig() call ... For information, the downloadWsConfig() call does a few things, the first of which is it clears the contents of a temporary directory that it uses to store the Workbench configuration in. This directory is on the server running the baseline script, and is by default:
    <directory name="webStudioConfigDir">./data/web_studio/config</directory>

    Can you:
    a) check this directory exists
    b) ensure config is definitely a directory and not a file (due to a weird perl bug)
    c) try manually deleting the contents of the directory and resolve any file locks if you can't

    Michael
  • 5. Re: Urgent : Error Communication with EAC agent
    DevReddy Newbie
    Currently Being Moderated
    Now i am getting a different Error: what else i need to do to avoid this.

    Now:[10.16.12 15:34:40] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
    [10.16.12 15:34:40] INFO: Definition has not changed.
    [10.16.12 15:34:40] INFO: Starting baseline update script.
    [10.16.12 15:34:40] INFO: Acquired lock 'update_lock'.
    [10.16.12 15:34:40] INFO: Downloading config files from Web Studio.
    [10.16.12 15:34:40] INFO: [ITLHost] Starting shell utility 'emgr_update_get_ws_settings'.
    [10.16.12 15:34:40] SEVERE: Error communicating with EAC agent while starting utility 'emgr_update_get_ws_settings'.
    Occurred while executing line 10 of valid BeanShell script:
    [[

    7| if (Forge.isDataReady()) {
    8| if (ConfigManager.isWebStudioEnabled()) {
    9| // get Web Studio config, merge with Dev Studio config
    10| ConfigManager.downloadWsConfig();
    11| ConfigManager.fetchMergedConfig();
    12| } else {
    13| ConfigManager.fetchDsConfig();

    ]]

    [10.16.12 15:34:40] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.

    Previous Error

    [10.16.12 15:01:10] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
    [10.16.12 15:01:11] INFO: Definition has not changed.
    [10.16.12 15:01:11] INFO: Starting baseline update script.
    [10.16.12 15:01:11] INFO: Acquired lock 'update_lock'.
    [10.16.12 15:01:11] INFO: Downloading config files from Web Studio.
    [10.16.12 15:01:11] INFO: [ITLHost] Starting shell utility 'cleanDir_config'.
    [10.16.12 15:01:11] SEVERE: Error communicating with EAC agent while starting utility 'cleanDir_config'.
    Occurred while executing line 10 of valid BeanShell script:
    [[

    7| if (Forge.isDataReady()) {
    8| if (ConfigManager.isWebStudioEnabled()) {
    9| // get Web Studio config, merge with Dev Studio config
    10| ConfigManager.downloadWsConfig();
    11| ConfigManager.fetchMergedConfig();
    12| } else {
    13| ConfigManager.fetchDsConfig();

    ]]

    [10.16.12 15:01:11] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
  • 6. Re: Urgent : Error Communication with EAC agent
    DevReddy Newbie
    Currently Being Moderated
    I want to add one more info, It was working fine till yesterday

    Last day by mistake i ran two of my applications paralelly, i guess this is what has created the problem, both those baselines failed.

    Now i am not able run even a single app, when i run initialize services its giving me the below problem - plz help
    [10.16.12 15:57:29] INFO: Removing application. Any active components will be forced to stop.
    [10.16.12 15:57:30] INFO: Removing Web Studio config files.
    [10.16.12 15:57:30] INFO: [ITLHost] Starting shell utility 'emgr_update_remove_all_settings'.
    [10.16.12 15:57:30] INFO: Removing definition for custom component 'ConfigManager'.
    [10.16.12 15:57:30] INFO: Updating provisioning for host 'ITLHost'.
    [10.16.12 15:57:30] INFO: Updating definition for host 'ITLHost'.
    [10.16.12 15:57:31] INFO: Removing definition for application 'DEVeCommerceEndecaApp'.
    *[10.16.12 15:57:31] WARNING: Provisioning warning: Could not clean up script invocations on local agent*
    *[10.16.12 15:57:31] WARNING: Provisioning warning: Could not clean up utility invocations on host 'ITLHost' [ 10.251.96.11 , fe80:0:0:0:294c:eb7f:8829:5a2e%10 ] with hostname/port '<SERVERNAME>:8888'*

    *[10.16.12 15:57:31] WARNING: Provisioning warning: Could not stop components on host 'ITLHost' [ 10.251.96.11 , fe80:0:0:0:294c:eb7f:8829:5a2e%10 ] with hostname/port '<SERVERNAME>:8888'*
    *[10.16.12 15:57:31] WARNING: Provisioning warning: Could not clean up utility invocations on host 'MDEXHost' [ 10.251.96.11 , fe80:0:0:0:294c:eb7f:8829:5a2e%10 ] with hostname/port '<SERVERNAME>:8888*
    *'*
    *[10.16.12 15:57:31] WARNING: Provisioning warning: Could not stop components on host 'MDEXHost' [ 10.251.96.11 , fe80:0:0:0:294c:eb7f:8829:5a2e%10 ] with hostname/port '<SERVERNAME>:8888'*
    *[10.16.12 15:57:31] WARNING: Provisioning warning: Could not clean up utility invocations on host 'webstudio' [ 10.251.96.11 , fe80:0:0:0:294c:eb7f:8829:5a2e%10 ] with hostname/port '<SERVERNAME>:888*
    *8'*
    *[10.16.12 15:57:31] WARNING: Provisioning warning: Could not stop components on host 'webstudio' [ 10.251.96.11 , fe80:0:0:0:294c:eb7f:8829:5a2e%10 ] with hostname/port '<SERVERNAME>:8888'*[10.16.12 15:57:31] INFO: Application 'DEVeCommerceEndecaApp' removed.
    Setting EAC provisioning and performing initial setup...
    [10.16.12 15:57:32] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
    [10.16.12 15:57:32] INFO: Setting definition for application 'DEVeCommerceEndecaApp'.
    [10.16.12 15:57:32] SEVERE: Caught an exception while checking provisioning.

    Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
    com.endeca.soleng.eac.toolkit.application.Application setDefinition - Caught exception while defining application 'DEVeCommerceEndecaApp'.
    Caused by com.endeca.eac.client.EACFault
    sun.reflect.NativeConstructorAccessorImpl newInstance0 - null

    Edited by: Dev Reddy on Oct 16, 2012 3:31 AM
  • 7. Re: Urgent : Error Communication with EAC agent
    Michael Peel Journeyer
    Currently Being Moderated
    No idea how to properly fix that. If the server isn't getting used for anything other than your own development then you could just clear the Endeca configuration: stop the EAC (Endeca HTTP Service), rename the directory %ENDECA_CONF%\state to state-backup, create an empty state directory, then start the service again. You'll need to run initialize_services to re-initialise your application(s). If it is a "proper" server, i.e. has other applications running on it that you can't/don't want to re-initialise, ring support - they'll hopefully have a better suggestion.

    Michael
  • 8. Re: Urgent : Error Communication with EAC agent
    DevReddy Newbie
    Currently Being Moderated
    Hi Michael,

    Fantastic , the solution you suggested has worked perfectly.

    Thanks alot for helping me out of this trouble, you are a great help.

    Thanks
    Dev
  • 9. Re: Urgent : Error Communication with EAC agent
    EndecaUser2013 Newbie
    Currently Being Moderated
    Thanks Michael..your suggestion worked like a charm.. though it would be great if you explained the reason behind doing this..thanks!

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points