Why does creating a repository fail?

Can you post the output from mount and ls -ld /mounts
/mounts/prod_backup
?

On 16 March 2015 at 13:33, David Reagan jerrac@gmail.com wrote:

Why does this happen?

curl -XPUT 'http://localhost:9200/_snapshot/my_backup?pretty=true' -d '{

"type": "fs",
"settings": {
    "location": "/mounts/prod_backup/my_backup",
    "compress": true
}

}'
{
"error" :
"RemoteTransportException[[log-elasticsearch-02][inet[/10.x.x.83:9300]][cluster:admin/repository/put]];
nested: RepositoryVerificationException[[my_backup]
[vxUQwUTCQwOaLyCy0eMK8A,
'RemoteTransportException[[log-elasticsearch-04][inet[/10.x.x.80:9300]][internal:admin/repository/verify]];
nested: RepositoryVerificationException[[my_backup] store location
[/mounts/prod_backup/my_backup] is not accessible on the node
[[log-elasticsearch-04][vxUQwUTCQwOaLyCy0eMK8A][log-elasticsearch-04][inet[/10.x.x.80:9300]]]];
nested:
FileNotFoundException[/mounts/prod_backup/my_backup/tests-yZ57gviiQUGS55tr_ULhhg-vxUQwUTCQwOaLyCy0eMK8A
(Permission denied)]; '], [GMTt6Y-3Qle1Fm3SGl-LTQ,
'RemoteTransportException[[log-estools-01][inet[/10.x.x.8:9300]][internal:admin/repository/verify]];
nested: RepositoryVerificationException[[my_backup] store location
[/mounts/prod_backup/my_backup] is not accessible on the node
[[log-estools-01][GMTt6Y-3Qle1Fm3SGl-LTQ][log-estools-01][inet[/10.x.x.8:9300]]{data=false}]];
nested:
FileNotFoundException[/mounts/prod_backup/my_backup/tests-yZ57gviiQUGS55tr_ULhhg-GMTt6Y-3Qle1Fm3SGl-LTQ
(Permission denied)]; '], [ffpuQF_zRZGGPRkZRgq1mw,
'RemoteTransportException[[log-elasticsearch-03][inet[/10.x.x.92:9300]][internal:admin/repository/verify]];
nested: RepositoryVerificationException[[my_backup] store location
[/mounts/prod_backup/my_backup] is not accessible on the node
[[log-elasticsearch-03][ffpuQF_zRZGGPRkZRgq1mw][log-elasticsearch-03][inet[/10.x.x.92:9300]]]];
nested:
FileNotFoundException[/mounts/prod_backup/my_backup/tests-yZ57gviiQUGS55tr_ULhhg-ffpuQF_zRZGGPRkZRgq1mw
(Permission denied)]; ']]]; ",
"status" : 500
}

/mounts/prod_backup is an NFS share mounted on all my ES nodes.

The only thing I can think of is that file permissions are wrong. But I'm
not sure how to fix that.

On the two nodes not listed in the error, the elasticsearch gid and uid
are different that on the other three nodes. So I can't just chown -R
elasticsearch:elasticsearch
.

Do I have to make sure that the uid and gid are the same on all nodes? How
am I supposed to do that when I install from the apt repositories?

Also, log-estools-01 has data.node = false. Why does it still need the
prod_backup mount?

log-estools-01 is on Ubuntu 14.04.

Everything else is Ubuntu 12.04.

Running ES 1.4.4.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/8bf960fd-c629-4e1a-92c1-9cc92f43487b%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/8bf960fd-c629-4e1a-92c1-9cc92f43487b%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9YtDD2H_0uuaoXJ%3DGCSAoDYeBuQpc-wQfe8Yd1m%3D7Q_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.