ElasticSearch Error after OC restart

[ypa...@gmail.com]

Hello,

after restarting OC (4.3) the log shows the following:

###
2018-05-16 08:16:04,739 | INFO  | (AbstractElasticsearchIndex:366) - Detected existing index 'externalapi'
2018-05-16 08:17:04,875 | ERROR | (?:?) - [org.opencastproject.external.impl.index.ExternalIndex(171)] The activate method has thrown an exception
org.osgi.service.component.ComponentException: Error initializing elastic search index
[...]
Caused by: org.elasticsearch.action.UnavailableShardsException: [externalapi][0] Primary shard is not active or isn't assigned to a known node. Timeout: [1m], request: index {[externalapi][version][root], source[{"version":"101"}]}
[...]
2018-05-16 08:17:04,887 | ERROR | (?:?) - FrameworkEvent ERROR - matterhorn-external-api
org.osgi.framework.ServiceException: Service factory returned null. (Component: org.opencastproject.external.impl.index.ExternalIndex (171))
[...]
2018-05-16 08:17:04,891 | ERROR | (?:?) - FrameworkEvent ERROR - matterhorn-kernel
org.osgi.framework.ServiceException: Service factory returned null. (Component: org.opencastproject.external.endpoint.BaseEndpoint (166))
[...]
2018-05-16 08:17:04,891 | INFO  | (RestPublisher$JaxRsServiceTracker:414) - JAX-RS service [org.opencastproject.external.endpoint.BaseEndpoint] has not been instantiated yet, or has already been unregistered. Skipping endpoint creation.
2018-05-16 08:17:04,897 | INFO  | (AbstractElasticsearchIndex:366) - Detected existing index 'externalapi'
2018-05-16 08:17:18,326 | WARN  | (Response:565) - Committed before 500 null
2018-05-16 08:18:05,078 | ERROR | (?:?) - [org.opencastproject.external.impl.index.ExternalIndex(171)] The activate method has thrown an exception
org.osgi.service.component.ComponentException: Error initializing elastic search index
        at org.opencastproject.external.impl.index.ExternalIndex.activate(ExternalIndex.java:71)
[...]
###

Furthermore, after upgrading to 4.3 the opencast restart process takes much longer and the Admin UI is not as responsive. Any ideas why that might be?


Thanks,
y

[Sven Stauber]

Depending from what version you have upgraded to 4.3, the index schema might have changed which requires a rebuilt of the index. See https://docs.opencast.org/develop/admin/upgrade/#upgrading-opencast-30-to-40 for more details in case you upgrade from a version smaller than 4.x. 

Furthermore, after upgrading to 4.3 the opencast restart process takes much longer and the Admin UI is not as responsive. Any ideas why that might be?

No, maybe because of the index problems you encounter.

What version of Opencast were you using previously?

Best

Sven 

[ypa...@gmail.com]

Hello,

apparently the main problem was that activeMQ wasn't working properly – or not working at all.
After increasing the heap memory for activeMQ and rebuilding the index, the problem was resolved.

For the record, we upgraded from 3.4 to 4.3 (too symmetric to work right away :)


Thanks,
y