Hello Odie,
It's possible that the Elasticsearch service is down since you've performed an upgrade. Sometimes, when an Elastic Stack package is updated, it's necessary to re-enable the services, since many files have changed and need to be reloaded.
First of all, let's check if the service is currently active and up. Execute the following command (as superuser):
systemctl status elasticsearch
Check the status of the service. The Active section should indicate active (running).
If that's not the case, let's re-enable and start the service. Execute this as superuser:
systemctl daemon-reload
systemctl enable elasticsearch.service
systemctl start elasticsearch.service
Wait some seconds until the Elasticsearch finishes loading. Use this command, it will give you the Elasticsearch server information if it's fully loaded:
curl localhost:9200/?pretty
{
"name" : "5urh-FJ",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "B5rXKBg2Tr-KWwFdbDHJQg",
"version" : {
"number" : "6.2.2",
"build_hash" : "7299dc3",
"build_date" : "2018-02-07T19:34:26.990113Z",
"build_snapshot" : false,
"lucene_version" : "7.2.1",
"minimum_wire_compatibility_version" : "5.6.0",
"minimum_index_compatibility_version" : "5.0.0"
},
"tagline" : "You Know, for Search"
}
Now you can continue the process and insert the templates.
If you have more questions or doubts, feel free to post a new comment!
Best regards,
Juanjo