Site plugins not working for me on 0.17.9

Elastic Stack Elasticsearch
1

I must be doing something stupid, but I can't work out what!
Suggestions on what that might be or how to debug further much
appreciated...

See the following gist: https://gist.github.com/1364037

I install the plugin (happy), check I am running 0.17.9 (I'm upgrading
my pseudo-production environment from 0.16.x) and then try to access
the bigdesk site plugin (the behavior vs elasticsearch-head is
identical)

Either via curl or firefox I get a blank response back from the
server.

Any ideas?

(Looking at the source code, I can't see any useful logging statements
I could turn on. Next step would be sticking some print statements in
I guess, so I'm hoping someone else has had a similar problem and was
more competent at fixing it!)

2

Strange..., just double checked fresh 0.17.9 install and it works (its very
important to have the last /, but you have it in the URL). Not sure whats
missing, can you try on your own dev box and see if it works?

On Mon, Nov 14, 2011 at 5:26 PM, Alex at Ikanow apiggott@ikanow.com wrote:

I must be doing something stupid, but I can't work out what!
Suggestions on what that might be or how to debug further much
appreciated...

See the following gist: https://gist.github.com/1364037

I install the plugin (happy), check I am running 0.17.9 (I'm upgrading
my pseudo-production environment from 0.16.x) and then try to access
the bigdesk site plugin (the behavior vs elasticsearch-head is
identical)

Either via curl or firefox I get a blank response back from the
server.

Any ideas?

(Looking at the source code, I can't see any useful logging statements
I could turn on. Next step would be sticking some print statements in
I guess, so I'm hoping someone else has had a similar problem and was
more competent at fixing it!)

3

Thanks for the sanity check and suggestion ... for some reason my /etc/
init.d/elasticsearch file was setting es.path.home parameter twice on
the command line, the second time to "".

I install/upgrade using Tavisto's RPMs, which have some "noreplace"
clauses, so probably you can break the upgrade with suitable changing
of config files between versions!