Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ElasticSearch failing to start #27

Open
czerasz opened this issue Jul 22, 2013 · 2 comments
Open

ElasticSearch failing to start #27

czerasz opened this issue Jul 22, 2013 · 2 comments

Comments

@czerasz
Copy link

czerasz commented Jul 22, 2013

I have a problem with the es service wrapper.

First it was not working when I tried to install it:

/etc/init.d $ ./elasticsearch install
Unable to locate any of the following binaries:
  /home/user_name/elasticsearch-0.90.2/bin/service/exec/elasticsearch-linux-intel(r)xeon(r)[email protected]
  /home/user_name/elasticsearch-0.90.2/bin/service/exec/elasticsearch-linux-intel(r)xeon(r)[email protected]
  /home/user_name/elasticsearch-0.90.2/bin/service/exec/elasticsearch

It was due to this line.
I had to change it to (btw I use gentoo):

DIST_ARCH=`uname -m 2>/dev/null | $TREXE "[A-Z]" "[a-z]" | $TREXE -d ' '`

And it installed successfully.

But when I try to run it. I get the following:

/etc/init.d $ ./elasticsearch start
Starting ElasticSearch...
Waiting for ElasticSearch......................
WARNING: ElasticSearch may have failed to start.

The service.log shows the following:

~/elasticsearch-0.90.2 $ tail -n0 -f logs/service.log
STATUS | wrapper  | 2013/07/22 11:36:16 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2013/07/22 11:36:16 | Java Service Wrapper Community Edition 64-bit 3.5.14
STATUS | wrapper  | 2013/07/22 11:36:16 |   Copyright (C) 1999-2011 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper  | 2013/07/22 11:36:16 |     http://wrapper.tanukisoftware.com
STATUS | wrapper  | 2013/07/22 11:36:16 |
WARN   | wrapper  | 2013/07/22 11:36:16 | The value of wrapper.java.command does not appear to be a java binary.
WARN   | wrapper  | 2013/07/22 11:36:16 | The use of scripts is not supported. Trying to continue, but some features may not work correctly..
STATUS | wrapper  | 2013/07/22 11:36:16 | Launching a JVM...
ERROR  | wrapper  | 2013/07/22 11:36:16 | JVM exited while loading the application.
INFO   | jvm 1    | 2013/07/22 11:36:16 | * run-java-tool was invoked directly
INFO   | jvm 1    | 2013/07/22 11:36:16 | * run-java-tool should only be used via symlinks to it
WARN   | wrapper  | 2013/07/22 11:36:20 | The value of wrapper.java.command does not appear to be a java binary.
WARN   | wrapper  | 2013/07/22 11:36:20 | The use of scripts is not supported. Trying to continue, but some features may not work correctly..
STATUS | wrapper  | 2013/07/22 11:36:21 | Launching a JVM...
ERROR  | wrapper  | 2013/07/22 11:36:21 | JVM exited while loading the application.
INFO   | jvm 2    | 2013/07/22 11:36:21 | * run-java-tool was invoked directly
INFO   | jvm 2    | 2013/07/22 11:36:21 | * run-java-tool should only be used via symlinks to it
WARN   | wrapper  | 2013/07/22 11:36:25 | The value of wrapper.java.command does not appear to be a java binary.
WARN   | wrapper  | 2013/07/22 11:36:25 | The use of scripts is not supported. Trying to continue, but some features may not work correctly..
STATUS | wrapper  | 2013/07/22 11:36:25 | Launching a JVM...
ERROR  | wrapper  | 2013/07/22 11:36:25 | JVM exited while loading the application.
INFO   | jvm 3    | 2013/07/22 11:36:25 | * run-java-tool was invoked directly
INFO   | jvm 3    | 2013/07/22 11:36:25 | * run-java-tool should only be used via symlinks to it
WARN   | wrapper  | 2013/07/22 11:36:30 | The value of wrapper.java.command does not appear to be a java binary.
WARN   | wrapper  | 2013/07/22 11:36:30 | The use of scripts is not supported. Trying to continue, but some features may not work correctly..
STATUS | wrapper  | 2013/07/22 11:36:30 | Launching a JVM...
ERROR  | wrapper  | 2013/07/22 11:36:30 | JVM exited while loading the application.
INFO   | jvm 4    | 2013/07/22 11:36:30 | * run-java-tool was invoked directly
INFO   | jvm 4    | 2013/07/22 11:36:30 | * run-java-tool should only be used via symlinks to it
WARN   | wrapper  | 2013/07/22 11:36:34 | The value of wrapper.java.command does not appear to be a java binary.
WARN   | wrapper  | 2013/07/22 11:36:34 | The use of scripts is not supported. Trying to continue, but some features may not work correctly..
STATUS | wrapper  | 2013/07/22 11:36:34 | Launching a JVM...
ERROR  | wrapper  | 2013/07/22 11:36:35 | JVM exited while loading the application.
INFO   | jvm 5    | 2013/07/22 11:36:35 | * run-java-tool was invoked directly
INFO   | jvm 5    | 2013/07/22 11:36:35 | * run-java-tool should only be used via symlinks to it
FATAL  | wrapper  | 2013/07/22 11:36:35 | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2013/07/22 11:36:35 |   There may be a configuration problem: please check the logs.
STATUS | wrapper  | 2013/07/22 11:36:35 | <-- Wrapper Stopped
@jeremylynch
Copy link

I am experiencing the same issue, did you find a solution?

@czerasz
Copy link
Author

czerasz commented Nov 29, 2013

Unfortunately no :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants