# Elastichsearch don't work after CentOS upgrade
**URL:** https://community.zammad.org/t/elastichsearch-dont-work-after-centos-upgrade/2842
**Category:** Technical assistance
**Created:** [July 21, 2019, 8:23am UTC](https://community.zammad.org/t/elastichsearch-dont-work-after-centos-upgrade/2842 "2019-07-21T08:23:14Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@sunday](https://community.zammad.org/u/sunday)
#### Post date: [July 21, 2019, 8:23am UTC](https://community.zammad.org/t/elastichsearch-dont-work-after-centos-upgrade/2842/1 "2019-07-21T08:23:14Z")
### Infos:
- Used Zammad version: 3.1.x
- Used Zammad installation source: (source, package, …) RPM
- Operating system: CentOS
- Browser + version: All
### Expected behavior:
- The Elasticsearch service is working properly
### Actual behavior:
- After updating CentOS, the elasticsearch service does not start
### Steps to reproduce the behavior:
- yun update
Here are the LOGs I have collected
[2019-07-13T18:50:55,793][ERROR][o.e.b.Bootstrap] Exception
java.lang.IllegalArgumentException: plugin [ingest-attachment] is incompatible with version [5.6.16]; was designed for version [5.6.15]
at org.elasticsearch.plugins.PluginInfo.readFromProperties(PluginInfo.java:146) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Spawner.spawnNativePluginControllers(Spawner.java:80) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:168) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:342) [elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:132) [elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:123) [elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:70) [elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:134) [elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91) [elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84) [elasticsearch-5.6.16.jar:5.6.16]
[2019-07-13T18:50:55,807][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: plugin [ingest-attachment] is incompatible with version [5.6.16]; was designed for version [5.6.15]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:123) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:70) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:134) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84) ~[elasticsearch-5.6.16.jar:5.6.16]
Caused by: java.lang.IllegalArgumentException: plugin [ingest-attachment] is incompatible with version [5.6.16]; was designed for version [5.6.15]
at org.elasticsearch.plugins.PluginInfo.readFromProperties(PluginInfo.java:146) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Spawner.spawnNativePluginControllers(Spawner.java:80) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:168) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:342) ~[elasticsearch-5.6.16.jar:5.6.16]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:132) ~[elasticsearch-5.6.16.jar:5.6.16]
… 6 more
---
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [August 5, 2019, 11:11am UTC](https://community.zammad.org/t/elastichsearch-dont-work-after-centos-upgrade/2842/2 "2019-08-05T11:11:09Z")
```auto
sudo /usr/share/elasticsearch/bin/elasticsearch-plugin remove ingest-attachment
sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment
```
will do the trick for you.
The first line tells you what the issue is :x
> [@sunday](#):
>
> [2019-07-13T18:50:55,793][ERROR][o.e.b.Bootstrap] Exception
> java.lang.IllegalArgumentException: plugin [ingest-attachment] is incompatible with version [5.6.16]; was designed for version [5.6.15]
> at org.elasticsearch.plugins.PluginInfo.readFromProperties(PluginInfo.java:146) ~[elasticsearch-5.6.16.jar:5.6.16]
---
### Author:  [@sunday](https://community.zammad.org/u/sunday)
#### Post date: [August 8, 2019, 11:35am UTC](https://community.zammad.org/t/elastichsearch-dont-work-after-centos-upgrade/2842/3 "2019-08-08T11:35:17Z")
Hi Mr Generation,
so, after updating the operating system with the command
yum clean all && yum update -y && reboot
If the problem arises, do I execute the two commands that you have indicated to me?
---
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [August 8, 2019, 12:11pm UTC](https://community.zammad.org/t/elastichsearch-dont-work-after-centos-upgrade/2842/4 "2019-08-08T12:11:36Z")
That depends what the error is. If the log entry I quoted appears, yes.
It’s imho a bad idea to just reboot the server after upgrading, because migration might have failed and you’ll never notice it that way. We’d like to encourage you to check the output of the update process to ensure everything was okay.
---
### Author:  [@system](https://community.zammad.org/u/system)
#### Post date: [December 6, 2019, 12:11pm UTC](https://community.zammad.org/t/elastichsearch-dont-work-after-centos-upgrade/2842/5 "2019-12-06T12:11:39Z")
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.