# Building Elasticsearch for Clear Linux, NullPointerException **URL:** \ **Category:** Elasticsearch\ **Created:** [June 13, 2017, 10:52pm UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277 "2017-06-13T22:52:43Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Israel\_Padilla](https://avatars.discourse-cdn.com/v4/letter/i/b38774/32.png) [@Israel\_Padilla](https://discuss.elastic.co/u/Israel_Padilla)\ **Post date:** [June 13, 2017, 10:52pm UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277/1 "2017-06-13T22:52:43Z")
Hi, I work in the Clear Linux ([https://clearlinux.org/](https://clearlinux.org/)) development team and we are trying to include elasticsearch in one of our Big Data bundles for the OS. The build process appears go to well, but when I run elasticsearch for testing I get this error: ```auto Exception in thread "main" java.lang.ExceptionInInitializerError at org.elasticsearch.common.logging.DeprecationLogger.(DeprecationLogger.java:138) at org.elasticsearch.common.xcontent.support.AbstractXContentParser.(AbstractXContentParser.java:57) at org.elasticsearch.common.xcontent.json.JsonXContentParser.(JsonXContentParser.java:44) at org.elasticsearch.common.xcontent.json.JsonXContent.createParser(JsonXContent.java:103) at org.elasticsearch.common.settings.Setting.parseableStringToList(Setting.java:848) at org.elasticsearch.common.settings.Setting.lambda$listSetting$27(Setting.java:802) at org.elasticsearch.common.settings.Setting.listSetting(Setting.java:807) at org.elasticsearch.common.settings.Setting.listSetting(Setting.java:802) at org.elasticsearch.env.Environment.(Environment.java:59) at org.elasticsearch.node.InternalSettingsPreparer.prepareEnvironment(InternalSettingsPreparer.java:90) at org.elasticsearch.cli.EnvironmentAwareCommand.createEnv(EnvironmentAwareCommand.java:72) at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:67) at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:122) at org.elasticsearch.cli.Command.main(Command.java:88) at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91) at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84) Caused by: java.lang.NullPointerException at org.elasticsearch.Build.(Build.java:51) ... 16 more ``` I realize there have been similar questions, with similar errors, however I believe my environment is different and previous answers may not apply in this case. Can you give me a hand? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 13, 2017, 11:07pm UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277/2 "2017-06-13T23:07:26Z")
Last time I've seen such an error, it appears that manifest files were missing in the final artifact. Can you check that? ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [June 13, 2017, 11:10pm UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277/3 "2017-06-13T23:10:52Z")
This is a server stacktrace, not a client stacktrace like you're using to seeing in this situation. That means this is a repackaged, externally packaged distribution, or embedded(?), not one of our officially blessed ones. We do not support this. ---
**Author:** ![Israel\_Padilla](https://avatars.discourse-cdn.com/v4/letter/i/b38774/32.png) [@Israel\_Padilla](https://discuss.elastic.co/u/Israel_Padilla)\ **Post date:** [June 13, 2017, 11:21pm UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277/4 "2017-06-13T23:21:47Z")
You mean inside elasticsearch-5.4.0.jar? There is a META-INF/MANIFEST.MF file there. Should there be more manifest files? ---
**Author:** ![Israel\_Padilla](https://avatars.discourse-cdn.com/v4/letter/i/b38774/32.png) [@Israel\_Padilla](https://discuss.elastic.co/u/Israel_Padilla)\ **Post date:** [June 13, 2017, 11:29pm UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277/5 "2017-06-13T23:29:44Z")
Well, I am building elasticsearch from source to create a Clear Linux package. What is it that you don't support? ---
**Author:** ![rjernst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjernst/32/6363_2.png) [@rjernst](https://discuss.elastic.co/u/rjernst)\ **Post date:** [June 14, 2017, 12:30am UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277/6 "2017-06-14T00:30:08Z")
Why are you building elasticsearch from source instead of using the official distributions? > What is it that you don't support? As @jasontedor said, `repackaged, externally packaged distribution, or embedded`. If you are building from source, that is an externally packaged distribution. We can't support something we have not built and tested ourselves. ---
**Author:** ![Israel\_Padilla](https://avatars.discourse-cdn.com/v4/letter/i/b38774/32.png) [@Israel\_Padilla](https://discuss.elastic.co/u/Israel_Padilla)\ **Post date:** [June 14, 2017, 4:49pm UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277/7 "2017-06-14T16:49:06Z")
Clear Linux is optimized for Intel servers. The reason we build things ourselves is because we plan to optimize not only the OS but also the most requested applications, which may include elasticsearch. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 12, 2017, 4:49pm UTC](https://discuss.elastic.co/t/building-elasticsearch-for-clear-linux-nullpointerexception/89277/8 "2017-07-12T16:49:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.