# Elasticsearch 5 crash java security policy

**URL:** <https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525>\
**Category:** Elasticsearch\
**Created:** [January 4, 2017, 8:21am UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525 "2017-01-04T08:21:37Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![julian.oxom](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@julian.oxom](https://discuss.elastic.co/u/julian.oxom)\
**Post date:** [January 4, 2017, 8:21am UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/1 "2017-01-04T08:21:37Z")

</div>

Hello,

I'm trying to run Elasticsearch 5.1 on Ubuntu 16.04 virtual machine

Elastisearch is starting but crashes with the following errors :

Jan 4 08:02:20 kibana systemd[1]: Starting Elasticsearch...  
Jan 4 08:02:20 kibana systemd[1]: Started Elasticsearch.  
Jan 4 08:02:29 kibana elasticsearch[27073]: java.security.policy: error adding Entry:  
Jan 4 08:02:29 kibana elasticsearch[27073]: #011java.net.MalformedURLException: no protocol: ${codebase.netty-common-4.1.6.Final.jar}  
Jan 4 08:02:29 kibana elasticsearch[27073]: java.security.policy: error adding Entry:  
Jan 4 08:02:29 kibana elasticsearch[27073]: #011java.net.MalformedURLException: no protocol: ${codebase.netty-transport-4.1.6.Final.jar}  
Jan 4 08:02:29 kibana elasticsearch[27073]: java.security.policy: error adding Entry:  
Jan 4 08:02:29 kibana elasticsearch[27073]: #011java.net.MalformedURLException: no protocol: ${codebase.securesm-1.1.jar}  
Jan 4 08:02:29 kibana elasticsearch[27073]: java.security.policy: error adding Entry:  
Jan 4 08:02:29 kibana elasticsearch[27073]: #011java.net.MalformedURLException: no protocol: ${codebase.lucene-core-6.3.0.jar}  
Jan 4 08:02:29 kibana elasticsearch[27073]: java.security.policy: error adding Entry:  
Jan 4 08:02:29 kibana elasticsearch[27073]: #011java.net.MalformedURLException: no protocol: ${codebase.lucene-misc-6.3.0.jar}  
Jan 4 08:02:35 kibana systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE  
Jan 4 08:02:35 kibana systemd[1]: elasticsearch.service: Unit entered failed state.  
Jan 4 08:02:35 kibana systemd[1]: elasticsearch.service: Failed with result 'exit-code'.

I don't understand these issues, can you help me ?

Thanks !

---

<div class="post-metadata">

**Author:** ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)\
**Post date:** [January 4, 2017, 10:07am UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/2 "2017-01-04T10:07:15Z")

</div>

Hi,  
Is this a new installation of 5.1.1?  
Do you have any plugins installed?

This could be coming from the plugin-security.policy however we need to gauge what has occurred previous to this run of ES 5.1.x.

---

<div class="post-metadata">

**Author:** ![julian.oxom](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@julian.oxom](https://discuss.elastic.co/u/julian.oxom)\
**Post date:** [January 4, 2017, 10:31am UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/3 "2017-01-04T10:31:07Z")

</div>

Hi JKhondhu,

Thank you for your message.

Yes, ElasticSearch instance is new (setup from official repositories).

No plugins are installed (plugins folder is empty).

---

<div class="post-metadata">

**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:** [January 4, 2017, 11:40am UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/4 "2017-01-04T11:40:27Z")

</div>

This looks suspicious. What Java version (`java -version`), are you using an old EA JDK 9 build?

---

<div class="post-metadata">

**Author:** ![julian.oxom](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@julian.oxom](https://discuss.elastic.co/u/julian.oxom)\
**Post date:** [January 4, 2017, 1:11pm UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/5 "2017-01-04T13:11:36Z")

</div>

Here is the java -version output :

openjdk version "9-internal"  
OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src)  
OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, mixed mode)

I have also tried to run with Open JDK 8 but nothing changes about the issue

---

<div class="post-metadata">

**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:** [January 4, 2017, 1:43pm UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/6 "2017-01-04T13:43:39Z")

</div>

As suspected. That EA build of JDK 9 is very old, and you shouldn't be running with any EA build of JDK 9 anyway.

> [@julian.oxom](#):
>
> I have also tried to run with Open JDK 8 but nothing changes about the issue

Sorry, but I'm skeptical of this. Are you sure you correctly set `JAVA_HOME` to point to the JDK 8 install? Would you please completely remove the JDK 9 install from your system?

---

<div class="post-metadata">

**Author:** ![Paul\_Kraus](https://avatars.discourse-cdn.com/v4/letter/p/e9c0ed/32.png) [@Paul\_Kraus](https://discuss.elastic.co/u/Paul_Kraus)\
**Post date:** [January 4, 2017, 5:18pm UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/7 "2017-01-04T17:18:19Z")

</div>

I am running ubuntu gnome 16.10 (fresh install yesterday evening)

I am having the exact same issue. Here is what i did prior...

1. Installed elastic search from default ubuntu repos. During the process i noticed the version number was not that newest (1.7.X something).
2. apt-get purged elasticsearch
3. Installed from the default repos
4. followed systctl instructions.
5. started service
6. reviewed status with the above errors.
7. Noticed i also had the openjdk-9-jdk installed.
8. Installed openjdk-8-jdk. (now i have both installed).
9. Not sure how to proceed i set JAVA\_HOME to the java 8 jdk
10. restarted service
11. Same issue.

Pretty sure its an issue between the jdk's and the prior install from default ubuntu repos. I am just not sure how to unwind this and get it working.

Thanks!

---

<div class="post-metadata">

**Author:** ![Paul\_Kraus](https://avatars.discourse-cdn.com/v4/letter/p/e9c0ed/32.png) [@Paul\_Kraus](https://discuss.elastic.co/u/Paul_Kraus)\
**Post date:** [January 4, 2017, 6:19pm UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/8 "2017-01-04T18:19:01Z")

</div>

Figured it out just needed to set-alternatives in apt.

---

<div class="post-metadata">

**Author:** ![julian.oxom](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@julian.oxom](https://discuss.elastic.co/u/julian.oxom)\
**Post date:** [January 5, 2017, 8:45am UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/9 "2017-01-05T08:45:31Z")

</div>

Thanks Jason !

ElasticSearch is running now. The JAVA\_HOME environment variable was indeed not correctly set.

---

<div class="post-metadata">

**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:** [January 5, 2017, 11:43am UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/10 "2017-01-05T11:43:26Z")

</div>

You're welcome. I'm glad that you got it sorted out.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 2, 2017, 11:43am UTC](https://discuss.elastic.co/t/elasticsearch-5-crash-java-security-policy/70525/11 "2017-02-02T11:43:29Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
