I have the other instance running and there were no log entries at the
time I started the second instance...that is why I only provided the
one. Let me do this.
I'm going to build two new separate instances ( as I need the one
running now for a prototype and cant be restarting it while our dev's
use the data)....k made (time lapse an hour there, both manually setup
and configured with duplicate configuration options.)
Output from 1st server: https://gist.github.com/1370248
Output from second server: https://gist.github.com/1370242
Configurations : https://gist.github.com/1370255
(Note I seperated them by a line of ********* in the file)
One last thing you mentioned that it looks like I only have
debug....I'm confused in the file I linked before and the
configurations above the entry discovery: TRACE
is present... I'm not following you on how then I'm suppose to set it
to trace any further than that.
Thanks for the help.
On Nov 16, 9:04 am, Shay Banon kim...@gmail.com wrote:
It looks like you provided the log for only one instance, and also, it does
not look like its configured with TRACE, but with DEBUG.
On Tue, Nov 15, 2011 at 6:23 PM, Mehtryx ke...@benedicthome.com wrote:
Sorry I missed your response here.
I have discovery set to trace. I'm copying up the output to this
gist: git://gist.github.com/1367485.git and my logging.yml to this
If I'm missing something let me know Thanks!
On Nov 7, 10:18 pm, Shay Banon kim...@gmail.com wrote:
Can you set in the logging(.yml) config file "discovery" to TRACE
(similar to how action is set to DEBUG), and gist the logs again? It
print what list of servers it gets from the amazon API.
On Fri, Nov 4, 2011 at 8:32 PM, Mehtryx ke...@benedicthome.com wrote:
In the spirit of ever trying to move forward I've done a few things.
- I am not using s3....it seems the preference is EBS for speed of
recovery and persistence anyway and ot wasn't working for me even
though I've configured as documented.
- I have reinstalled the plugin ( doing a ./bin/plugin -remove cloud-
aws and then the install again ), this has not rectified the issue
for me, I again have things configured as per instructions so I would
suspect if everything worked as described...I should see my cluster.
I'll keep looking if there is no one here able to point me to a
mistake then I'll submit a bug on github for it, as I can only assume
something in es is broken then.
Cheers and thanks!