Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors during indexing-process #1

Closed
rgl1234 opened this issue Jan 5, 2018 · 8 comments
Closed

Errors during indexing-process #1

rgl1234 opened this issue Jan 5, 2018 · 8 comments

Comments

@rgl1234
Copy link

rgl1234 commented Jan 5, 2018

If I activate this app, I get a lot of the following errors during the indexing-process:

. Indexing: servername/foldername/problematic-file

[Elasticsearch\Common\Exceptions\BadRequest400Exception]
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline with id [attachment] does not exist"}],"type":"illegal_argument_exception","reason":"pipeline with id [attachment] does not exist"}
,"status":400}

If this error occures, the indexing-process is stopped immediately. After the problematic-file has been deleted, the process does not stop until the next problematic-file is going to be indexed....

@ArtificialOwl
Copy link
Member

@rgl1234
Copy link
Author

rgl1234 commented Jan 5, 2018

thanks for this. I just installed the plugin but I still get the same error. But I also get the error on plaintext content such as txt files.....

@ArtificialOwl
Copy link
Member

Even after a restart of the elasticsearch servlet and the ./occ fullnextsearch:reset ?

@rgl1234
Copy link
Author

rgl1234 commented Jan 5, 2018

thanks.....after a complet reboot of the server and fullnextsearch:reset it seems to work now as expected. I now have to wait until the process is finished.....

@rgl1234
Copy link
Author

rgl1234 commented Jan 5, 2018

Is there a possibility to limit the indexing-process of files to certain file-types such as docx, etc ...? No a lot of unwanted files seems to be indexed too and I got this error at a specific file:

[Elasticsearch\Common\Exceptions\BadRequest400Exception]
{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"failed to parse [attachment.date]"}],"type":"mapper_parsing_exception","reason"
:"failed to parse [attachment.date]","caused_by":{"type":"illegal_argument_exception","reason":"Invalid format: "10091-02-18T08:28:45Z" is malform
ed at "1-02-18T08:28:45Z""}},"status":400}

@ArtificialOwl
Copy link
Member

Yes, there will be more settings/options in a future version. Can you provide more information regarding this file (format, size, ...) ? Is the index stuck on that file ?

@Japhys
Copy link

Japhys commented Jan 13, 2018

I am not sure what I am doing wrong

Clean NC 13 beta
Clean Elastic search
Clean FullTextSearch

But when i run index command i also get:

[Elasticsearch\Common\Exceptions\BadRequest400Exception]
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline with id [attachment] does not exist"}],"type":"illegal_argument_e
xception","reason":"pipeline with id [attachment] does not exist"},"status":400}

**Edit:

I give this a second try:

sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment

a reset and a restart

Now it does work!**

@ArtificialOwl
Copy link
Member

Yes, next release will first check that the plugin is installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants