I am having a problem running elasticsearch-0.90.11.deb on Ubuntu 12.04.4
LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs after I
run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run by
adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure why this
would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to /etc/elasticsearch/elasticsearch.yml
but it doesn't make a difference:
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
I am having a problem running elasticsearch-0.90.11.deb on Ubuntu 12.04.4
LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs after I
run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run by
adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure why this
would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to /etc/elasticsearch/elasticsearch.yml
but it doesn't make a difference:
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
I am having a problem running elasticsearch-0.90.11.deb on Ubuntu 12.04.4
LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs after I
run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run by
adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure why this
would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to /etc/elasticsearch/elasticsearch.yml
but it doesn't make a difference:
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
The activity of the animal beings has become acutely active everywhere on this earth. Bodies do not get time to booty a blow for a while. With the accretion use of altered gadgets of Gps Jammer, the possibilities of accepting the aboriginal of blow accept absolutely finished. The adaptable phones or the corpuscle phones are some of these accessories that accumulate the bodies consistently in blow with the alfresco world. The adaptable building are additionally accessible about everywhere these canicule and due to this the accessibility of the Cell Phone Jammer has become alike added quick and authentic. Today, you cannot break out of ability of these adaptable building as their signals can bolt your about anywhere. The bearings of bodies who accord to altered business professions has become actual analytical of car mobile phone blocker as their authorities bolt them anywhere any moment.
On 8 August 2014 00:34, Jim Adamson <jim.a...@york.ac.uk <javascript:>>
wrote:
I am having a problem running elasticsearch-0.90.11.deb on Ubuntu
12.04.4 LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs
after I run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run by
adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure why this
would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to
/etc/elasticsearch/elasticsearch.yml but it doesn't make a difference:
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
Thanks for the reply. No I haven't but the VM was provisioned by our
central IT so there may be something particular about the VM's
configuration that's the cause of this. I'll try Jörg's suggestion and then
if that doesn't work I'll pursue this line.
Jim
On Friday, 8 August 2014 01:22:26 UTC+1, Mark Walkom wrote:
I just tested this and didn't run into the same problem.
Have you changed something locally around your environment variables, or
in the service defaults?
On 8 August 2014 00:34, Jim Adamson <jim.a...@york.ac.uk <javascript:>>
wrote:
I am having a problem running elasticsearch-0.90.11.deb on Ubuntu 12.04.4
LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs after I
run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run by
adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure why this
would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to /etc/elasticsearch/elasticsearch.yml
but it doesn't make a difference:
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
I am having a problem running elasticsearch-0.90.11.deb on Ubuntu
12.04.4 LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs
after I run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run by
adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure why this
would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to
/etc/elasticsearch/elasticsearch.yml but it doesn't make a difference:
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
I am having a problem running elasticsearch-0.90.11.deb on Ubuntu
12.04.4 LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs
after I run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run
by adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure why
this would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to /etc/elasticsearch/elasticsearch.yml
but it doesn't make a difference:
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
I am having a problem running elasticsearch-0.90.11.deb on Ubuntu
12.04.4 LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs
after I run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run
by adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure why
this would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to /etc/elasticsearch/elasticsearch.yml
but it doesn't make a difference:
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
I am having a problem running elasticsearch-0.90.11.deb on Ubuntu
12.04.4 LTS (VMWare VM, Intel Xeon @ 2.3Ghz, 2GB RAM). The problem occurs
after I run /etc/init.d/elasticsearch start. Although ES appears to start
successfully, grepping for the process shows it is not running.
Issuing the following:
cd /usr/share/elasticsearch/bin
./elasticsearch -f
With help from a developer colleague I have managed to get it to run
by adding a suitable log4j.properties file to /usr/share/elasticsearch/bin,
cd-ing to that directory and running ./elasticsearch -f -Dlog4j.configuration=./log4j.properties. However, I'm not sure
why this would have been required in the first place and feel there must be
something misconfigured that's resulting in the init.d script failing to
start ES.
I have tried adding the following to /etc/elasticsearch/elasticsearch.yml
but it doesn't make a difference:
ES is one of the dependencies for some software we are running
called atom, which only support ES < v1. The install instructions are
available at https://www.accesstomemory.
org/en/docs/2.0/admin-manual/installation/linux/#installation-linux.
The version of Java is Oracle’s JVM distributed by Web Upd8:
java -version
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
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.