# Bug: X-Pack install via Puppet breaks ES startup after meta-plugin introduction in 6.2.0
**URL:** https://discuss.elastic.co/t/bug-x-pack-install-via-puppet-breaks-es-startup-after-meta-plugin-introduction-in-6-2-0/119477
**Category:** Elasticsearch
**Created:** [February 12, 2018, 1:53pm UTC](https://discuss.elastic.co/t/bug-x-pack-install-via-puppet-breaks-es-startup-after-meta-plugin-introduction-in-6-2-0/119477 "2018-02-12T13:53:23Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@st0nez](https://discuss.elastic.co/u/st0nez)
#### Post date: [February 12, 2018, 1:53pm UTC](https://discuss.elastic.co/t/bug-x-pack-install-via-puppet-breaks-es-startup-after-meta-plugin-introduction-in-6-2-0/119477/1 "2018-02-12T13:53:23Z")
Tested on Ubuntu 16.04, Elasticsearch/X-pack 6.2.0 and 6.2.1, puppet module elastic-elasticsearch v6.2.0.
Issue:
6.2.0 included [this merge](https://github.com/elastic/elasticsearch/pull/28022) regarding meta-plugins. When installing x-pack (a meta-plugin) via puppet, a file called '.name' is created in the root x-pack plugin directory (see [here](https://github.com/elastic/puppet-elasticsearch/issues/643)). Since this '.name' file is not a valid plugin directory, an error [1] is raised during Elasticsearch startup.
Possible solution:
Adding an additional check [here](https://github.com/elastic/elasticsearch/blob/a55eda626fa6eee5766f570ba68b13f9daba4fc2/server/src/main/java/org/elasticsearch/plugins/PluginInfo.java#L165) in PluginInfo.extractAllPlugins to exclude .name files.
Workaround:
Individual plugins (like ingest-attachment) do not seem to be impacted. Deleting the .name file will allow Elasticsearch to start.
Repro:
- install elasticsearch via official puppet module
- install x-pack via puppet module
[1]: org.elasticsearch.bootstrap.StartupException: org.elasticsearch.bootstrap.BootstrapException: java.nio.file.FileSystemException: /usr/share/elasticsearch/plugins/x-pack/.name/plugin-descriptor.properties: Not a directory
---
### Author:  [@tylerjl](https://discuss.elastic.co/u/tylerjl)
#### Post date: [February 12, 2018, 5:07pm UTC](https://discuss.elastic.co/t/bug-x-pack-install-via-puppet-breaks-es-startup-after-meta-plugin-introduction-in-6-2-0/119477/2 "2018-02-12T17:07:54Z")
Hi @st0nez, thanks for reporting this. That's definitely a bug, and a by-product of the mechanism that the module uses to track plugins that it installs. I'll take a look at fixing this on the Puppet side in a more maintainable way that doesn't require creating arbitrary files from Puppet.
---
### Author:  [@st0nez](https://discuss.elastic.co/u/st0nez)
#### Post date: [February 12, 2018, 5:26pm UTC](https://discuss.elastic.co/t/bug-x-pack-install-via-puppet-breaks-es-startup-after-meta-plugin-introduction-in-6-2-0/119477/3 "2018-02-12T17:26:34Z")
Great, thanks!
---
### Author:  [@tylerjl](https://discuss.elastic.co/u/tylerjl)
#### Post date: [February 14, 2018, 5:48pm UTC](https://discuss.elastic.co/t/bug-x-pack-install-via-puppet-breaks-es-startup-after-meta-plugin-introduction-in-6-2-0/119477/4 "2018-02-14T17:48:17Z")
FYI , [the fix has been released](https://forge.puppet.com/elastic/elasticsearch/changelog#621-february-14-2018).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 14, 2018, 5:48pm UTC](https://discuss.elastic.co/t/bug-x-pack-install-via-puppet-breaks-es-startup-after-meta-plugin-introduction-in-6-2-0/119477/5 "2018-03-14T17:48:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.