elasticsearch: java.net.MalformedURLException: unknown protocol: jrt about for-elasticsearch-docs HOT 6 CLOSED

Hi @anelshaer, I assume you were following the RPM installation guide. Can you share more details about the commands you ran to get to this point, operating system and version, and Java version? It's definitely a Java problem, and if we can figure out what went wrong, we can get it into the troubleshooting section.

from for-elasticsearch-docs.

Same issue.
RPM installation, followed instructions exactly as written.
Java 1.8
CentOS 7.6.1810

$systemctl start elasticsearch
$systemctl status elasticsearch -l

● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2019-03-13 11:51:22 MDT; 8s ago
Docs: http://www.elastic.co
Main PID: 11869 (java)
Tasks: 14
CGroup: /system.slice/elasticsearch.service
└─11869 /bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX...

Mar 13 11:51:22 odfe.it..edu systemd[1]: Started Elasticsearch.
Mar 13 11:51:23 odfe.it..edu elasticsearch[11869]: java.security.policy: error adding Entry:
Mar 13 11:51:23 odfe.it..edu elasticsearch[11869]: java.net.MalformedURLException: unknown protocol: jrt
Mar 13 11:51:23 odfe.it..edu elasticsearch[11869]: java.security.policy: error adding Entry:
Mar 13 11:51:23 odfe.it.***.edu elasticsearch[11869]: java.net.MalformedURLException: unknown protocol: jrt

from for-elasticsearch-docs.

Thanks @rlk5546. I'm able to reproduce and am looking into it with engineering. Looks to only be a problem on Java 8.

from for-elasticsearch-docs.

Hi everyone, our engineers tell me that those errors are nothing to worry about. If Elasticsearch fails to start, it's likely an incorrect symlink. I've added some information here: b4df35f

from for-elasticsearch-docs.

Thanks! It is refreshing to see such a quick response.

from for-elasticsearch-docs.

i'm still having this Issue, and when i do systemctl status logstash
i get the following errors:
[WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://localhost:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://localhost:9200/][Manticore::ClientProtocolException] localhost:9200 failed to respond"}

curl http://localhost:9200/
curl: (52) Empty reply from server

from for-elasticsearch-docs.