Started to get that warning after upgrading to 0.9. Tried the usual
configuration options to no avail (config pasted below). Any help would be
appreciated..
To make sure that the paths are set I uncommented all the environment
variables pertaining to logging and config paths ..
and also added /etc/elasticsearch/elasticsearch.yml
path.conf: /etc/elasticsearch
path.data: /var/lib/elasticsearch
path.work: /tmp/elasticsearch
path.logs: /var/log/elasticsearch
This setup was working fine with 0.19.2 .. So I am not sure what changed
and where. Could this be some odd java class path loading issue ? Once
again - thanks for any help.
Forgot to add -
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)
on centos 5.5
On Thursday, May 9, 2013 2:04:43 PM UTC-7, the_nozzle wrote:
Hey everyone
Started to get that warning after upgrading to 0.9. Tried the usual
configuration options to no avail (config pasted below). Any help would be
appreciated..
To make sure that the paths are set I uncommented all the environment
variables pertaining to logging and config paths ..
and also added /etc/elasticsearch/elasticsearch.yml
path.conf: /etc/elasticsearch
path.data: /var/lib/elasticsearch
path.work: /tmp/elasticsearch
path.logs: /var/log/elasticsearch
This setup was working fine with 0.19.2 .. So I am not sure what changed
and where. Could this be some odd java class path loading issue ? Once
again - thanks for any help.
Add $ES_HOME/config/logging.yml to your classpath.
Jörg
Am 09.05.13 23:04, schrieb the_nozzle:
Hey everyone
Started to get that warning after upgrading to 0.9. Tried the usual
configuration options to no avail (config pasted below). Any help
would be appreciated..
To make sure that the paths are set I uncommented all the environment
variables pertaining to logging and config paths ..
and also added /etc/elasticsearch/elasticsearch.yml
path.conf: /etc/elasticsearch
path.data: /var/lib/elasticsearch
path.work: /tmp/elasticsearch
path.logs: /var/log/elasticsearch
This setup was working fine with 0.19.2 .. So I am not sure what
changed and where. Could this be some odd java class path loading
issue ? Once again - thanks for any help.
Unfortunately still no bueno - I tried with ES_INCLUDE and without and
still getting the same result... I also played around with the init.d
script and exported those vars there and not getting any love - anything
else I could try ? My current working setup is 19.8 .. Curious what could
of changed so drastically since then.
On Thursday, May 9, 2013 3:24:31 PM UTC-7, Jörg Prante wrote:
You use the service wrapper, maybe?
Add $ES_HOME/config/logging.yml to your classpath.
Jörg
Am 09.05.13 23:04, schrieb the_nozzle:
Hey everyone
Started to get that warning after upgrading to 0.9. Tried the usual
configuration options to no avail (config pasted below). Any help
would be appreciated..
To make sure that the paths are set I uncommented all the environment
variables pertaining to logging and config paths ..
and also added /etc/elasticsearch/elasticsearch.yml
path.conf: /etc/elasticsearch
path.data: /var/lib/elasticsearch
path.work: /tmp/elasticsearch
path.logs: /var/log/elasticsearch
This setup was working fine with 0.19.2 .. So I am not sure what
changed and where. Could this be some odd java class path loading
issue ? Once again - thanks for any help.
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
Figured it out - added /etc/elasticsearch/logging.yml to the classpath and
exported from init.d scritpt. Thanks.
On Thursday, May 9, 2013 5:46:35 PM UTC-7, the_nozzle wrote:
Unfortunately still no bueno - I tried with ES_INCLUDE and without and
still getting the same result... I also played around with the init.d
script and exported those vars there and not getting any love - anything
else I could try ? My current working setup is 19.8 .. Curious what could
of changed so drastically since then.
On Thursday, May 9, 2013 3:24:31 PM UTC-7, Jörg Prante wrote:
You use the service wrapper, maybe?
Add $ES_HOME/config/logging.yml to your classpath.
Jörg
Am 09.05.13 23:04, schrieb the_nozzle:
Hey everyone
Started to get that warning after upgrading to 0.9. Tried the usual
configuration options to no avail (config pasted below). Any help
would be appreciated..
To make sure that the paths are set I uncommented all the environment
variables pertaining to logging and config paths ..
and also added /etc/elasticsearch/elasticsearch.yml
path.conf: /etc/elasticsearch
path.data: /var/lib/elasticsearch
path.work: /tmp/elasticsearch
path.logs: /var/log/elasticsearch
This setup was working fine with 0.19.2 .. So I am not sure what
changed and where. Could this be some odd java class path loading
issue ? Once again - thanks for any help.
I was talking about the classpath, not ES_INCLUDE (I think it is
ES_CLASSPATH)
The error comes from the logger unable to find logging.yml which is in
$ES_HOME/configuration/
What distribution do you use by any chance? zip? rpm? service wrapper?
Maybe it is a packaging related issue.
Jörg
Am 10.05.13 02:46, schrieb the_nozzle:
Unfortunately still no bueno - I tried with ES_INCLUDE and without and
still getting the same result... I also played around with the init.d
script and exported those vars there and not getting any love -
anything else I could try ? My current working setup is 19.8 ..
Curious what could of changed so drastically since then.
I think the init.d script is the one that came with the 0.19.8 rpm for
centos 5.5. I'm playing around with the generic rpm at the moment . Hmm odd
issue - the configuration does not seem to be read at all for some reason
and all the logging is going to stdout (It doesnt look like ES knows
anything about the rest of the cluster) ..
On Thursday, May 9, 2013 5:55:45 PM UTC-7, Jörg Prante wrote:
Weird... looks like this init.d script is wrong, from which distribution
is it?
Jörg
Am 10.05.13 02:50, schrieb the_nozzle:
Figured it out - added /etc/elasticsearch/logging.yml to the
classpath and exported from init.d scritpt. Thanks.
Just to add - poked at the init.d script a bit and cleaned up/tweaked the
config - so the elasticsearch.yml is being read (connection attempts are
being made to the other nodes), but for some reason I'm still getting the
log output on the console and not in the file...
the final set of option passed to ES is as follows :
-Des.config=/usr/share/elasticsearch/config//elasticsearch.yml
-Des.path.conf=/usr/share/elasticsearch/config/
-Des.path.home=/usr/share/elasticsearch
-Des.path.logs=/var/log/elasticsearch -Des.path.data=/var/lib/elasticsearch
-Des.path.work=/tmp/elasticsearch
-Des.path.plugins=/usr/share/elasticsearch/plugins
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.