Opencast Update 2.2.4: rebuild SOLR-index

[ypatios]

Hello,

is there another way to rebuild the SOLR-index in 2.2.4, apart from deleting the search folder (../data/solr-indexes/search)?

Reason: we run into issues after deleting the search folder; apparently the SOLR-index fails to rebuild:
e.g. (error in opencast log):
Received unexpected response status 403 while trying to download from https://example.tld/static/engage-player/ffd86896-d865-4c18-857c-137245503572/982e0ff1-629b-4768-8692-8ac2fabf2db6/slidetext.xml


Any help would be appreciated!

Thank you
ypatios

[Ruth Lang]

Hi,

do you use Stream Security ? 

When we tried to rebuild the SOLR-index (1.6.x) an active Stream Security prevented the rebuilding.

Regards

Ruth

_______________________________

Universität zu Köln

Regionales Rechenzentrum (RRZK)

--
You received this message because you are subscribed to the Google Groups "Opencast Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

[ypatios]

Dear Ruth,

> On 14 Dec 2016, at 13:19, Ruth Lang <la...@uni-koeln.de> wrote:
>
> do you use Stream Security ?
> When we tried to rebuild the SOLR-index (1.6.x) an active Stream Security prevented the rebuilding.

no, we don’t use Stream Security – thanks for your reply.

Does anyone have an idea how can the SOLR-index be rebuilt without deleting the search directory under OC 2.2.4?


Thank you,
ypatios

[Lars Kiesow]

Hi,
please find some comments below

> is there another way to rebuild the SOLR-index in 2.2.4, apart from
> deleting the search folder (../data/solr-indexes/search)?

No, that is the way. The folder contains the Solr index and if you do
not remove it, you cannot rebuild it since it is already there.

> Reason: we run into issues after deleting the search folder;
> apparently the SOLR-index fails to rebuild: e.g. (error in opencast
> log): Received unexpected response status 403 while trying to
> download from
> https://example.tld/static/engage-player/ffd86896-d865-4c18-857c-137245503572/982e0ff1-629b-4768-8692-8ac2fabf2db6/slidetext.xml

First, the actual problem is that missing file. The slide texts are
included into the search index and the re-build seems to be failing
because that file is missing.

Obviously that file missing should not have happened and it points to
some kind of problem in the past. But it is hard to say, what exactly
went wrong and it is probably impossible to find out now. Hence, we need
to find a way to deal with it.

The next problem is that Opencast stops the index from populating when
it hit this issue. True, it is an error and this should not have
happened, etc. but Opencast should be able to deal with it and not
break the whole process. That is why it would be great if you could
create a Jira ticket for this, adding some more specific information
like the opencast.log. I am not promising anything but feel free to
assign the Jira ticket to me :-)

Now, since fixing that might take some time, let's have a look at some
quick fixes: The best idea I can come up with is that since Opencast
stops the process when hitting the missing file, you could just put
a fitting file on the file system.

The easiest thing would probably be to just copy another slidetext.xml
to the right location. The only side-effect should be that one episode
might be found under weird keywords if searched for. But to prevent
that, you could just create a slidetext.xml without any real content.

Let me know if that helps.

Regards,
Lars

[ypatios]

Hello,

we saw that you’ve issued a ticket in jira (https://opencast.jira.com/browse/MH-11961), that describes the problem exactly – thanks.
Meanwhile, we were able to circumvent the problem by running the upgrade process once again; after that, the problem didn’t reappear.


Thanks for your support,
y