1 2 Previous Next 24 Replies Latest reply: Sep 19, 2013 2:29 AM by 10manish11 RSS

    Baseline_update Error

    BCHK
      Hi all,

      anyone got this error when running baseline_update.bat? Thanks

      component_Dgidx'.
      [07.03.12 09:51:07] INFO: [ITLHost] Starting component 'Dgidx'.
      [07.03.12 09:51:07] SEVERE: Error communicating with EAC agent while starting co
      mponent.
      Occurred while executing line 32 of valid BeanShell script:
      [[

      29| Forge.archiveLogDir();
      30| Forge.run();
      31| Dgidx.archiveLogDir();
      32| Dgidx.run();
      33|
      34| // distributed index, update Dgraphs
      35| DistributeIndexAndApply.run();

      ]]

      [07.03.12 09:51:07] SEVERE: Caught an exception while invoking method 'run' on o
      bject '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.component.Component start - Error communicating wi
      th EAC agent while starting component.
      Caused by com.endeca.eac.client.EACFault
      sun.reflect.NativeConstructorAccessorImpl newInstance0 - null

      [07.03.12 09:51:07] INFO: Released lock 'update_lock'.
        • 1. Re: Baseline_update Error
          Mandar Shastrakar
          Hi,

          Please check the dgidx log for more details.

          THT
          Mandar
          • 2. Re: Baseline_update Error
            user8307147
            Hi,

            Iam also getting same exception as below:
            SEVERE: Batch component 'Dgidx' failed. Refer to component logs in C:\Endeca\apps\SuperSKU\config\script\..\..\.\logs\dgidxs\Dgidx on host ITLHost.
            Occurred while executing line 32 of valid BeanShell script:
            [[

            29| Forge.archiveLogDir();
            30| Forge.run();
            31| Dgidx.archiveLogDir();
            32| Dgidx.run();
            33|
            34| // distributed index, update Dgraphs
            35| DistributeIndexAndApply.run();

            ]]

            Jul 31, 2012 7:51:33 PM com.endeca.soleng.eac.toolkit.Controller execute
            SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
            java.lang.reflect.InvocationTargetException
                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                 at java.lang.reflect.Method.invoke(Method.java:597)
                 at com.endeca.soleng.eac.toolkit.Controller.invokeRequestedMethod(Controller.java:925)
                 at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:210)
                 at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:89)
            Caused by: com.endeca.soleng.eac.toolkit.exception.AppControlException: Error executing valid BeanShell script.
                 at com.endeca.soleng.eac.toolkit.script.Script.runBeanShellScript(Script.java:134)
                 at com.endeca.soleng.eac.toolkit.script.Script.run(Script.java:82)
                 ... 7 more
            Caused by: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Batch component 'Dgidx' failed. Refer to component logs in C:\Endeca\apps\SuperSKU\config\script\..\..\.\logs\dgidxs\Dgidx on host ITLHost.
                 at com.endeca.soleng.eac.toolkit.component.BatchComponent.run(BatchComponent.java:79)
                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                 at java.lang.reflect.Method.invoke(Method.java:597)
                 at bsh.Reflect.invokeMethod(Unknown Source)
                 at bsh.Reflect.invokeObjectMethod(Unknown Source)
                 at bsh.Name.invokeMethod(Unknown Source)
                 at bsh.BSHMethodInvocation.eval(Unknown Source)
                 at bsh.BSHPrimaryExpression.eval(Unknown Source)
                 at bsh.BSHPrimaryExpression.eval(Unknown Source)
                 at bsh.BSHBlock.evalBlock(Unknown Source)
                 at bsh.BSHBlock.eval(Unknown Source)
                 at bsh.BSHBlock.eval(Unknown Source)
                 at bsh.BSHIfStatement.eval(Unknown Source)
                 at bsh.BSHBlock.evalBlock(Unknown Source)
                 at bsh.BSHBlock.eval(Unknown Source)
                 at bsh.BSHBlock.eval(Unknown Source)
                 at bsh.BSHIfStatement.eval(Unknown Source)
                 at bsh.Interpreter.eval(Unknown Source)
                 at bsh.Interpreter.eval(Unknown Source)
                 at bsh.Interpreter.eval(Unknown Source)
                 at com.endeca.soleng.eac.toolkit.script.Script.runBeanShellScript(Script.java:120)
                 ... 8 more
            Jul 31, 2012 7:51:33 PM com.endeca.soleng.eac.toolkit.base.LockManager releaseLock
            INFO: Released lock 'update_lock'.
            Jul 31, 2012 7:52:59 PM com.endeca.soleng.eac.toolkit.Controller setUpBeanShellInterpreters
            CONFIG: Loading beanshell.imports from /C:/Endeca/apps/SuperSKU/config/script/beanshell.imports
            Jul 31, 2012 7:52:59 PM com.endeca.soleng.eac.toolkit.Controller provision
            INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
            Jul 31, 2012 7:52:59 PM com.endeca.soleng.eac.toolkit.Controller provision
            INFO: Definition has not changed.
            Jul 31, 2012 7:52:59 PM sun.reflect.NativeMethodAccessorImpl invoke0
            INFO: Starting baseline update script.
            Jul 31, 2012 7:52:59 PM com.endeca.soleng.eac.toolkit.base.LockManager acquireLock
            INFO: Acquired lock 'update_lock'.
            Jul 31, 2012 7:52:59 PM sun.reflect.NativeMethodAccessorImpl invoke0
            WARNING: Baseline data not ready for processing.
            Jul 31, 2012 7:52:59 PM com.endeca.soleng.eac.toolkit.base.LockManager releaseLock
            INFO: Released lock 'update_lock'.
            Jul 31, 2012 7:52:59 PM sun.reflect.NativeMethodAccessorImpl invoke0
            INFO: Baseline update script finished.

            Please help me how to solve this issue.
            • 3. Re: Baseline_update Error
              Aanup D
              Hi,

              Please check the contents of Dgidx logs in C:\Endeca\apps\SuperSKU\config\script\\logs\dgidxs\Dgidx.log and post it. We will be able to help you
              • 4. Re: Baseline_update Error
                967507
                WARN     10/11/12 12:38:20.498 UTC (1349959100498)     DGIDX     {dgidx,baseline}     Notice: the '--tmpdir' option has been deprecated; see the product documentation for more details.
                it's from Dgidx.start.log
                FATAL     10/11/12 12:38:21.087 UTC (1349959101086)     DGIDX     {dgidx,baseline}     ENE Indexer: No records file found.     
                It's form Dgidx.log
                • 5. Re: Baseline_update Error
                  sabdelhalim
                  Hi,
                  did you check if the http_service (8888) was started on your machine ?
                  regards
                  Saleh
                  • 6. Re: Baseline_update Error
                    Ravi Honakamble|
                    Hey,

                    It looks like Indexer did not get binary file or got empty binary file from the Forge to process. Could you please check the Forge log for more details? It will give you an idea what went wrong.

                    Regards,
                    Ravi
                    • 7. Re: Baseline_update Error
                      967507
                      Can it depends from Product Catalog?For example if I have some bad products.
                      • 8. Re: Baseline_update Error
                        945963
                        Hi, I have the same issue, I looked at the forge logs and the forge logs are empty. Can you suggest where should I look?
                        • 9. Re: Baseline_update Error
                          Pravin Chikhale
                          Check encoding used in Record adapter and the data you trying to index, both should be of same.
                          Also use *-v* option with forge and dgidx to get more information in logs about what's happening inside.

                          HTH

                          -Pravin
                          • 10. Re: Baseline_update Error
                            Pravin Chikhale
                            Check for file permission on log directory.
                            If forge logs are not generating then you can probably you can post the error message you got on screen while running baseline update.

                            -Pravin
                            • 11. Re: Baseline_update Error
                              SanjuThomas
                              Are you keeping the log files open in any other editor ? This used to happen when the log files are open in another editor.
                              • 12. Re: Baseline_update Error
                                945963
                                I added the -vd option in the forge. I got the following warning

                                *WARN     10/12/12 17:59:51.807 UTC (1350064791806)     FORGE     {config}: Error reading from file 'file://C:\dev\test_data\baseline\TEST_DATA_EXTRACT_BASELINE.TXT' when converting from 'UTF-8': U_ILLEGAL_CHAR_FOUND. Characters will be escaped as hexadecimal as %XE9.*
                                     
                                The source of the data is the text file. Just for testing I had 15 lines and each of the line I got that warning message. Below is header and one line of the file. Do you see any problematic stuff there? FYI: *|@|* is the column delimiter and *@|@* is the end of the line delimiter.

                                listingId|@|makeName|@|modelName|@|makeModel|@|modelYear|@|makeId|@|modelId|@|yearId|@|crossMakeName|@|crossModelName|@|crossModelYear|@|crossMakeId|@|crossModelId|@|crossYearId|@|trimCityMpg|@|trimHwyMpg|@|imagecaption|@|defaultImage|@|modelMinMsrp|@|modelMaxMsrp|@|modelMinCityMpg|@|modelMaxCityMpg|@|modelMinHwyMpg|@|modelMaxHwyMpg|@|newListing|@|dimPlaceholderValue|@|hasPhotoGallery|@|video|@|dmaMarketName|@|pros|@|cons|@|odsMakeId|@|shopperCount|@|odsYearId|@|totNumConsumerRev|@|overAllRating|@|topConsumerRated|@|reviewId|@|topRatedBadge|@|crossSearchType|@|crossYmm|@|searchType@|@
                                1|@|Acura|@|MDX|@|AcuraMDX|@|2012|@|13575|@|luxury,crossover,suv,nearluxury|@|midsize|@| |@|3.7L|@|4dr All-wheel Drive|@|CAC20ACS111C0101.jpg|@|USC20ACS111A0|@|43030|@|16.0|@|21.0|@|2012 Acura MDX 4dr AWD|@|CAC20ACS111C0101.jpg|@|43030|@| |@|16.0|@|16.0|@|21.0|@|21.0|@| |@|yes|@|Y|@| |@|Standard six-speed automatic|Available tech features|Seven seats standard|Standard all-wheel drive|@|Above-average reliability|AWD performance|Handling|Power|Decent gas mileage|@|Mixed opinions on styling|Center console doors|Second row doesn't slide forward and back|DVD video displaces MP3 jack|@|20001|@|21422|@|39723|@|13|@|4.6|@|Y|@|277|@|Y|@|N|@|2012-1-5127|@|carryover@|@
                                • 13. Re: Baseline_update Error
                                  953835
                                  To eliminate the possible issue of invisible control characters in the input file, cut and paste into some thing like Notepad. Even some thing as simple as Wordpad tries to be smart, which for some thing like this you do not want. Maybe Notepad++ would be another good choice, not sure.
                                  • 14. Re: Baseline_update Error
                                    Pravin Chikhale
                                    instal notepad++, open that file in it and there is an option in notepad ++, convert to utf-8. After this run baseline update. This worked for me.

                                    Pravin
                                    1 2 Previous Next