Getting following error while running the Baseline update

[12.06.19 14:18:24] INFO: Starting baseline CAS crawl with id ‘MyAppen-last-mile-crawl’.

[12.06.19 14:18:24] SEVERE: Error starting baseline crawl ‘MyAppen-last-mile-crawl’.

Occurred while executing line 11 of valid BeanShell script:

[[

 

8|      Dgidx.cleanDirs();

9|

10|      // run crawl and archive any changes in dvalId mappings

11|      CAS.runBaselineCasCrawl(“MyAppen-last-mile-crawl”);

12|      CAS.archiveDvalIdMappingsForCrawlIfChanged(“MyAppen-last-mile-crawl”);

13|

14|      // archive logs and run the indexer

 

]]

 

[12.06.19 14:18:24] SEVERE: Caught an exception while invoking method ‘run’ on object ‘BaselineUpdate’. Releasing locks. Failed with error Error executing valid BeanShell script.

[12.06.19 14:18:24] INFO: Released lock ‘update_lock’.

Casservice.log –

2019-12-06 14:18:24,443 INFO [cas] [606548741@jetty-5] com.endeca.itl.cas.api.CrawlMetrics.[MyAppen-last-mile-crawl]: End Time = 12/6/19 2:18:24 PM EST

2019-12-06 14:18:24,445 ERROR [cas] [606548741@jetty-5] com.endeca.itl.service.CasCrawlerImpl: [MyAppen-last-mile-crawl] Error starting crawlCrawl failed to start: com.endeca.itl.executor.FatalExecutionException: Error retrieving attributes from the config repository

2019-12-06 14:18:24,445 ERROR [cas] [606548741@jetty-5] com.endeca.itl.service.CasCrawlerImpl: Error executing method CasCrawlerImpl.startCrawl()

com.endeca.itl.cas.api.ItlException: Crawl failed to start: com.endeca.itl.executor.FatalExecutionException: Error retrieving attributes from the config repository

at com.endeca.itl.service.CrawlRun.start(CrawlRun.java:155)

at com.endeca.itl.service.CrawlManager.startCrawl(CrawlManager.java:309)

at com.endeca.itl.service.CasCrawlerImpl.startCrawl(CasCrawlerImpl.java:277)

at sun.reflect.GeneratedMethodAccessor461.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)

at com.endeca.itl.service.ServicePublisher$2.performInvocation(ServicePublisher.java:158)

at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)

at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSMethodInvoker.java:178)

at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:64)

…

…

Caused by: com.endeca.itl.cas.api.ItlException: com.endeca.itl.executor.FatalExecutionException: Error retrieving attributes from the config repository

at com.endeca.itl.executor.Pipeline.start(Pipeline.java:163)

at com.endeca.itl.service.CrawlRun.start(CrawlRun.java:148)

… 51 more

Caused by: com.endeca.itl.executor.FatalExecutionException: Error retrieving attributes from the config repository

at com.endeca.itl.executor.output.mdex.MdexConfiguration.retrieveAttributes(MdexConfiguration.java:387)

at com.endeca.itl.executor.output.mdex.MdexConfiguration.<init>(MdexConfiguration.java:147)

at com.endeca.itl.executor.output.mdex.FullMdexOutputHandler.<init>(FullMdexOutputHandler.java:131)

at com.endeca.itl.executor.output.mdex.MdexOutputSink.prepareForAcquisition(MdexOutputSink.java:145)

at com.endeca.itl.executor.Pipeline.start(Pipeline.java:159)

… 52 more

Caused by: java.io.IOException: Error retrieving attributes: Internal Server Error(500). See config repository log for more details.

at com.endeca.repository.reader.ConfigRepositoryReader.fetchJson(ConfigRepositoryReader.java:344)

at com.endeca.repository.reader.ConfigRepositoryReader.fetchAttributes(ConfigRepositoryReader.java:246)

at com.endeca.repository.reader.ConfigRepositoryReader.getMergedAttributes(ConfigRepositoryReader.java:162)

at com.endeca.itl.executor.output.mdex.repository.ConfigRepositoryClient.getAttributes(ConfigRepositoryClient.java:218)

at com.endeca.itl.executor.output.mdex.MdexConfiguration.retrieveAttributes(MdexConfiguration.java:383)

… 56 more

FIX

As it says “error retrieving attributes from the config repository”. That means ECR does not have attributes set up correctly. If you have an export of attributes from the current app or some other app you want to replicate precedence rules from and run following

<app-folder>/control/runcommand.sh IFCR importContent attributes /tmp/import/attributes/

Now if you don’t have the attributes, you can use the attributes from reference apps –

<ToolsAndFrameworks-installation>/11.3.0/reference/discover-data-cas/import/attributes

Bonus – How to export attributes from an app

<app-folder>/control/runcommand.sh IFCR exportContent attributes /tmp/import/precedenceRules/