Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47669 - [elasticsearch] directory config/scripts is not created
Attached to Project:
Community Packages
Opened by E. Bolloff (ebolloff) - Friday, 08 January 2016, 10:38 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Wednesday, 03 February 2016, 19:49 GMT
Opened by E. Bolloff (ebolloff) - Friday, 08 January 2016, 10:38 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Wednesday, 03 February 2016, 19:49 GMT
|
DetailsHey,
when installing Elasticsearch from the AUR, the directory /usr/share/elasticsearch/config/scripts is not created. This leads to errors like this $ Exception in thread "main" java.lang.IllegalStateException: Unable to access 'path.conf' (/usr/share/elasticsearch/config) $ Likely root cause: java.nio.file.AccessDeniedException: /usr/share/elasticsearch/config This happens, when I try to start a test cluster on port 9250; it'll exit with status 1. When I create a directory config/scripts, everything is fine and working. I use ES in a Ruby on Rails Application and start the test cluster via a rake task of the ruby elasticsearch bindings: https://github.com/elastic/elasticsearch-ruby. It basically spawns a process by the command $ elasticsearch \ $ -D es.http.port=9250 \ $ -D es.cluster.name=elasticsearch-test-myhostname \ $ -D es.node.name=node-1 \ $ -D es.path.data=/tmp/elasticsearch_test \ $ -D es.path.work=/tmp \ $ -D es.path.logs=/var/log/elasticsearch \ $ -D es.discovery.zen.ping.multicast.enabled=true \ $ -D es.network.host=localhost \ $ > /dev/null Details of the process spawning can be seen there: https://github.com/elastic/elasticsearch-ruby/blob/master/elasticsearch-extensions/lib/elasticsearch/extensions/test/cluster.rb#L78-L155 I don't exactly know, at which version this error occurs, but I guess it was since version > 2.0.0, I have 2.1.1-1. Shouldn't the directory be created during the installation? |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Wednesday, 03 February 2016, 19:49 GMT
Reason for closing: Fixed
Additional comments about closing: elasticsearch-2.2.0-3
Wednesday, 03 February 2016, 19:49 GMT
Reason for closing: Fixed
Additional comments about closing: elasticsearch-2.2.0-3
If you use the provided service file this is set correctly.
You need to create it yourself if you need it in a different location.
If you created that directory yourself you will need to (re)move it manually before updating to elasticsearch-2.2.0-3