4 Replies Latest reply: Feb 8, 2013 12:07 AM by user776266 RSS

    atg10.1.2+endeca3.1.1 integration error after changing hostname on VM

    user776266
      After changing the hostname of the machine for which atg and endeca is installed, integration does not working fine.

      I got following error on initialize_services.sh, baseline_update.sh and promote_content.sh, and also same for selecting deploy endeca integration for production instance in CIM:

      INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
      INFO: Updating provisioning for host 'AuthoringMDEXHost'
      INFO: Host name of host 'AuthoringMDEXHost' has changed from xxxxxxxxxxxxxxx to yyyyyyyyyyyyyyyy. Components on this host will be re-provisioned.
      SEVERE: Caught an exception while checking provisioning.

      Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
      com.endeca.soleng.eac.toolkit.component.Component getStatus - Caught exception while querying for status of component AuthoringDgraph
      Causedby com.endeca.eac.client.EACFault
      sun.reflect.NativeConstructorAccessorImpl newInstance0 - null

      I have already changed all the xml files and properties file to reflect new hostname.

      Thanks, Yuki
        • 1. Re: atg10.1.2+endeca3.1.1 integration error after changing hostname on VM
          Dan at Branchbird
          Yuki,

          The EAC is trying to contact its component, AuthoringDgraph, to reprovision it with a new host name. I suspect one of the following things is occurring:

          1) AuthoringDgraph is not running on the original host and thus can't be contacted. Check the logs on this host ./logs/dgraphs/AuthoringDgraph/AuthoringDgraph.log to see if anything is amiss.
          2) The scripts are trying to contact AuthoringDgraph on the new host, but it hasn't been provisioned there yet. I can't say for sure if this is the case, but anytime you change the location of where components have been provisioned you should run initialize_services.sh. I would be surprised if initialize_services.sh would offer the exact error below since it starts off by removing the old provisioning configuration of your application. Can you show us the exact error message you get when you run initialize_services.sh?

          HTH,
          Dan
          http://branchbird.com
          • 2. Re: atg10.1.2+endeca3.1.1 integration error after changing hostname on VM
            user776266
            Hi Dan, thank you very much for the responce.

            AuthoringDgraph.log is not created on this folder.

            Following is the full error message when initialize_service.sh has been run with --force option:

            [02.07.13 09:28:29] INFO: Removing application. Any active components will be forced to stop.
            [02.07.13 09:28:30] INFO: Removing Workbench config files.
            [02.07.13 09:28:30] INFO: [ITLHost] Starting shell utility 'emgr_update_remove_all_settings'.
            [02.07.13 09:28:30] INFO: Removing definition for custom component 'WorkbenchManager'.
            [02.07.13 09:28:31] INFO: Updating provisioning for host 'ITLHost'.
            [02.07.13 09:28:31] INFO: Updating definition for host 'ITLHost'.
            [02.07.13 09:28:31] WARNING: Failed to update definition for custom component 'WorkbenchManager''s associated host 'ITLHost': Caught exception while updating host definition.
            [02.07.13 09:28:31] INFO: Removing definition for custom component 'IFCR'.
            [02.07.13 09:28:31] INFO: Updating provisioning for host 'ITLHost'.
            [02.07.13 09:28:31] INFO: Updating definition for host 'ITLHost'.
            [02.07.13 09:28:31] WARNING: Failed to update definition for custom component 'IFCR''s associated host 'ITLHost': Caught exception while updating host definition.
            [02.07.13 09:28:32] INFO: Removing definition for application 'CRS'.
            [02.07.13 09:28:32] SEVERE: Caught an exception while trying to remove application.

            Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
            com.endeca.soleng.eac.toolkit.application.Application removeDefinition - Caught exception while defining application 'CRS'.
            Caused by com.endeca.eac.client.ProvisioningFault
            sun.reflect.NativeConstructorAccessorImpl newInstance0 - null

            [02.07.13 09:28:35] SEVERE: An application already exists with the name, "CRS". Please use the '--force' option if you want to replace all existing configuration.


            Thanks,
            Yuki
            • 3. Re: atg10.1.2+endeca3.1.1 integration error after changing hostname on VM
              user776266
              I found a message on CRS.0.0.log that old hostname cannot be resolved so IP address cannot be found. I have added the old IP-hostname combination on /etc/hosts and ITLHost part is resolved. However, initialize_services.sh still errors out :

              [oracle@jpcoevm915 control]$ ./initialize_services.sh --force
              Removing existing application provisioning...
              [02.07.13 14:51:50] INFO: Removing application. Any active components will be forced to stop.
              [02.07.13 14:51:51] INFO: Removing Workbench config files.
              [02.07.13 14:51:51] INFO: [ITLHost] Starting shell utility 'emgr_update_remove_all_settings'.
              [02.07.13 15:01:51] INFO: Removing definition for custom component 'WorkbenchManager'.
              [02.07.13 15:01:51] INFO: Updating provisioning for host 'ITLHost'.
              [02.07.13 15:01:51] INFO: Updating definition for host 'ITLHost'.
              [02.07.13 15:11:51] WARNING: Failed to update definition for custom component 'WorkbenchManager''s associated host 'ITLHost': Caught exception while updating host definition.
              [02.07.13 15:11:51] INFO: Removing definition for custom component 'IFCR'.
              [02.07.13 15:11:52] INFO: Updating provisioning for host 'ITLHost'.
              [02.07.13 15:11:52] INFO: Updating definition for host 'ITLHost'.
              [02.07.13 15:17:10] INFO: Removing definition for application 'CRS'.
              [02.07.13 15:27:10] SEVERE: Caught an exception while trying to remove application.

              Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
              com.endeca.soleng.eac.toolkit.application.Application removeDefinition - Caught exception while defining application 'CRS'.
              Caused by org.apache.axis.AxisFault
              org.apache.axis.AxisFault makeFault - ; nested exception is:
                   java.net.SocketTimeoutException: Read timed out
              Caused by java.net.SocketTimeoutException
              java.net.SocketInputStream socketRead0 - Read timed out

              [02.07.13 15:37:14] SEVERE: Caught exception while querying for defined application list.
              Occurred while executing line 18 of valid BeanShell script:
              [[

              15|
              16| // If the application is already defined
              17| // log an error and exit with code 1
              18| if (app.isDefined()) {
              19| log.severe("An application already exists with the name, \"" + provObj.getAppName() + "\". " +
              20| "Please use the '--force' option if you want to replace all existing configuration.");
              21| System.exit(1);

              ]]

              [02.07.13 15:37:14] SEVERE: Caught an exception while invoking method 'run' on object 'AssertNotDefined'. 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.application.Application isDefined - Caught exception while querying for defined application list.
              Caused by org.apache.axis.AxisFault
              org.apache.axis.AxisFault makeFault - ; nested exception is:
                   java.net.SocketTimeoutException: Read timed out
              Caused by java.net.SocketTimeoutException
              java.net.SocketInputStream socketRead0 - Read timed out


              Thanks, Yuki
              • 4. Re: atg10.1.2+endeca3.1.1 integration error after changing hostname on VM
                user776266
                Finally, I could resolve the issue by setting time out and running baseline update from ProductCatalogSimpleIndexingAdmin on dynamo admin. Thanks a lot for the help !