Error with elasticsearch


#1

Hi,
i have installed elasticsearch on my Ubuntu 18.10 and Nextcloud 13.05.

When i create a new Index i receive the following error:

 Progress:       /10   done
│ Error:      6/6
│ Exception: Elasticsearch\Common\Exceptions\ServerErrorResponseException
│ Message: java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: field [content] not present as part of path [attachment.content]

Can anybody help me?
What can i do?

Regards
Hermann


#2

This is discussed here: https://github.com/nextcloud/fulltextsearch/issues/365

and fixed next release


#3

Ok. Thx for the Info.


#4

HI,

I am new (few days) to NextCloud. I have some success with NC and ES settings but come across the same error. I have some beginner questions and see if anyone could help.

Given:-

Error: 1/11
Index: files:560
Exception: Elasticsearch\Common\Exceptions\ServerErrorResponseException
Message: java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: field [content] not present as part of path [attachment.content]

What can I do so that to show the path and filename of file:560 ?

Secondly, after the bug is fixed in next release, what can I do so that I can come back and index the particular file(s) that failed before ?

Thanks in advance.

Alex


#5

create your own thread next time:

./occ fulltextsearch:document:platform files 560
./occ fulltextsearch:document:provider <owner> files 560

#6

Dear Cult,

Noted with thanks.

Alex


#7

Still have the same issue:

│ Error: 4407/4407
│ Index: files:937834
│ Exception: Elasticsearch\Common\Exceptions\ServerErrorResponseException
│ Message: java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: field [content] not present as part of path [attachment.content]

  • Ubuntu 16.0.4
  • NC 14.0.4.2
  • Apps:
    • bookmarks_fulltextsearch: 1.0.0
    • files_fulltextsearch: 1.1.1
    • files_fulltextsearch_tesseract: 1.0.0
    • fulltextsearch: 1.1.0
    • fulltextsearch_elasticsearch: 1.0.2

All searches find only bookmarks!

Here my settings:


#8

can you run a test before the first index ?

occ fulltextsearch:reset
occ fulltextsearch:test
occ fulltextserch:index


#9

Done:

  • Reset
  • Test all is green.

Now new index is running … takes a lot of time. Will report … but until now no errors!