PARTIAL backups

[jolson]

Let's see what your path setting looks like:

Code: Select all

curl -s -XGET localhost:9200/_nodes/?pretty | grep path -A7

If you're missing the 'repo' setting, you might have to remake your repository via the web GUI. After remaking the repository, does the 'repo' setting show up? If so, try deleting your PARTIALs and initializing another backup.

A working server of mine reports results as follows:

curl -s -XGET localhost:9200/_nodes/?pretty | grep path -A7
"path" : {
"data" : "/usr/local/nagioslogserver/elasticsearch/data",
"work" : "/usr/local/nagioslogserver/tmp/elasticsearch",
"home" : "/usr/local/nagioslogserver/elasticsearch",
"conf" : "/usr/local/nagioslogserver/elasticsearch/config",
"logs" : "/var/log/elasticsearch",
"repo" : "/"
},

[stecino]

Let's see what your path setting looks like:

Code: Select all

curl -s -XGET localhost:9200/_nodes/?pretty | grep path -A7

If you're missing the 'repo' setting, you might have to remake your repository via the web GUI. After remaking the repository, does the 'repo' setting show up? If so, try deleting your PARTIALs and initializing another backup.

A working server of mine reports results as follows:

curl -s -XGET localhost:9200/_nodes/?pretty | grep path -A7
"path" : {
"data" : "/usr/local/nagioslogserver/elasticsearch/data",
"work" : "/usr/local/nagioslogserver/tmp/elasticsearch",
"home" : "/usr/local/nagioslogserver/elasticsearch",
"conf" : "/usr/local/nagioslogserver/elasticsearch/config",
"logs" : "/var/log/elasticsearch",
"repo" : "/"
},

# curl -s -XGET localhost:9200/_nodes/?pretty | grep path -A7
"path" : {
"data" : "/usr/local/nagioslogserver/elasticsearch/data",
"work" : "/usr/local/nagioslogserver/tmp/elasticsearch",
"home" : "/usr/local/nagioslogserver/elasticsearch",
"conf" : "/usr/local/nagioslogserver/elasticsearch/config",
"logs" : "/var/log/elasticsearch",
"repo" : "/"
},
--
"path" : {
"data" : "/usr/local/nagioslogserver/elasticsearch/data",
"work" : "/usr/local/nagioslogserver/tmp/elasticsearch",
"home" : "/usr/local/nagioslogserver/elasticsearch",
"conf" : "/usr/local/nagioslogserver/elasticsearch/config",
"logs" : "/var/log/elasticsearch"
},
"config" : {
--
"path" : {
"data" : "/usr/local/nagioslogserver/elasticsearch/data",
"work" : "/usr/local/nagioslogserver/tmp/elasticsearch",
"home" : "/usr/local/nagioslogserver/elasticsearch",
"conf" : "/usr/local/nagioslogserver/elasticsearch/config",
"logs" : "/var/log/elasticsearch",
"repo" : "/"
},
--
"path" : {
"data" : "/usr/local/nagioslogserver/elasticsearch/data",
"work" : "/usr/local/nagioslogserver/tmp/elasticsearch",
"home" : "/usr/local/nagioslogserver/elasticsearch",
"conf" : "/usr/local/nagioslogserver/elasticsearch/config",
"logs" : "/var/log/elasticsearch",
"repo" : "/"
},

Looks like one of the nodes is missing the repo, also I have setup the backup as /NSL_BACKUP does it matter that repository name isn't properly recongnized?

[jolson]

does it matter that repository name isn't properly recongnized?

No - that does not matter, what does matter is that the 'repo' shows up. Have you tried remaking your repo via the Web GUI and checking on the path once more?

[stecino]

does it matter that repository name isn't properly recongnized?

No - that does not matter, what does matter is that the 'repo' shows up. Have you tried remaking your repo via the Web GUI and checking on the path once more?

Repo doesn't show up for one of the nodes, does that matter? I can delete the repo and add it again through the gui.

[jolson]

Repo doesn't show up for one of the nodes, does that matter?

Yes it does.

I can delete the repo and add it again through the gui.

Please give that a try and see if your instance picks up the 'repo' path.

Code: Select all

curl -s -XGET localhost:9200/_nodes/?pretty | grep path -A7

Thanks!

Jesse