Unable to install ES license

ES: v2.4.4

I recently requested a new basic license for Elasticsearch. When I attempt to install the license remotely by following the documentation, I'm either being denied permission or being prompted for the admin password, which I don't believe I've set.

seth-comp:Downloads Seth$ curl -XPUT -u admin 'http://my_host:9200/_license' -d @my-license-v2.json
Enter host password for user 'admin':
curl: (7) Failed to connect to lmtopslog01 port 9200: Connection refused

If I move the license to the ES node and try to do the curl locally, it also fails:

root@my_host:/usr/share/elasticsearch# curl -XPUT '' -d @my-license-v2.json
{"error":{"root_cause":[{"type":"null_pointer_exception","reason":"No InputStream specified"}],"type":"null_pointer_exception","reason":"No InputStream specified"},"status":500}

Furthermore, even attempting to download the zip is failing due to the servers being at capacity:

seth_comp:Downloads Seth$  wget https://download.elastic.co/elasticsearch/release/org/elasticsearch/plugin/license/2.2.0/license-2.4.4.zip
--2017-02-28 11:22:23--  https://download.elastic.co/elasticsearch/release/org/elasticsearch/plugin/license/2.2.0/license-2.4.4.zip
Resolving download.elastic.co...,,, ...
Connecting to download.elastic.co||:443... connected.
HTTP request sent, awaiting response... 503 Service Unavailable: Back-end server is at capacity
2017-02-28 11:22:24 ERROR 503: Service Unavailable: Back-end server is at capacity.

I've followed the documentation regarding updating my license for my version.

Can anyone please give me some guidance in what I'm doing incorrectly? Thanks in advance.

Same here !

I think their download center is somehow down...

Sorry, all. We are affected by the S3 outage, too.

Sure. My post isn't really about the outage at all though, I have a license I'm trying to install offline.

What happens if you curl yourhost:9200?

I can successfully curl, e.g. getting license data:

root@ES_node:~# curl -XGET 'http://localhost:9200/_license'
  "license" : {
    "status" : "expired",
    "uid" : "license-uid",
    "type" : "trial",
    "issue_date" : "2017-01-18T18:39:25.232Z",
    "issue_date_in_millis" : 1484764765232,
    "expiry_date" : "2017-02-17T18:39:25.232Z",
    "expiry_date_in_millis" : 1487356765232,
    "max_nodes" : 1000,
    "issued_to" : "elasticsearch",
    "issuer" : "elasticsearch"

So the license install works on some clusters but not on others. Can anyone tell me what the error:

{"error":{"root_cause":[{"type":"null_pointer_exception","reason":"No InputStream specified"}],"type":"null_pointer_exception","reason":"No InputStream specified"},"status":500}


Working license install on one node:

root@netmon:~# curl -XPUT 'http://localhost:9200/_license?acknowledge=true' -d @my-license-netmon-v2.json

Non-working license install on another node on another cluster:

root@opslog:~# curl -XPUT 'http://localhost:9200/_license?acknowledge=true' -d @my-license-opslog-v2.json
{"error":{"root_cause":[{"type":"null_pointer_exception","reason":"No InputStream specified"}],"type":"null_pointer_exception","reason":"No InputStream specified"},"status":500}

Hi Seth,

I agree this sounds a bit odd - I haven't seen that particular exception related to licensing (or anything else). What are the differences between the clusters where this works, and where it does not work? (e.g. versions, plugins, etc).

Can you confirm that the my-license-opslog-v2.json license file exists and try that license on the other cluster where applying the license was successful?

On the cluster where you're having the issue, can you share the results of a request to _license?

Apologies for the trouble you're having - this isn't a common problem as far as I can tell.


Thanks Steve. It turned out to be a bug with my ES instance on that node. The default elasticsearch.yml was in place and for some reason it wasn't happy with that. Also I had to install a regular license, uninstall and then I was able to use the RESTful API to install the proper license. Weird issue that may point to some underlying problem with this particular node. Thank you for your help!

Glad you were able to sort it out!

If something like this happens again, don't hesitate to open a new thread, and we'll see if we can get to the bottom of it.

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