Yup, that's exactly what I mean.
I changed the path to the configuration file and the path of the ES
home (int the .bat file) - both of them were set to their absolute
On Apr 28, 1:35 pm, Shay Banon shay.ba...@elasticsearch.com wrote:
You mean the path to executable for the windows service? Sorry, not a windows user, if thats the case, which paths did you change to make it work? Maybe something in addition needs to be set...
On Thursday, April 28, 2011 at 9:15 AM, Nir Rubinstein wrote:
Simple = deployed as a WS, but in windows, the "Path to Executable"
points to the "elasticsearch.conf" under"bin/service" - of course,
since this is not an executable, it does not do anything.
On Apr 27, 8:14 pm, Shay Banon shay.ba...@elasticsearch.com wrote:
Did not understand what the problem is.
On Wednesday, April 27, 2011 at 11:51 AM, Nir Rubinstein wrote:
I downloaded the ES service host and put it in the location it should
be. After running the .bat file and finding that it didn't work, I
modified a few paths to their absolute location (namely, the
configuration file path) and everything works. I even manged to
install the service on my windows machine via the -i parameter.
The problem is that the service's path to executable points to the
configuration file (which, of course, can't be run). Any idea what I'm
doing wrong or how to alter the configuration?