Hi Jamie,

I suspect you did also run into the following problem, which is related:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768178

So after having elasticsearch installed with START_DAEMON not set, systemd
still thinks that elasticsearch is running because the init script returned
0.
Running "service elasticsearch start" will have no effect because of this.

Philipp

On Tue Nov 18 2014 at 12:48:48 AM Jamie Norrish <ja...@artefact.org.nz>
wrote:

> On Mon, 2014-11-17 at 23:06 +0000, Philipp Hug wrote:
>
> > Ist it possible that you just missed to set "START_DAEMON=true"
> > in /etc/default/elasticsearch
>
> I had been trying it with both, and it seemed to make no difference. But
> having just tested the whole process again, elasticsearch is starting
> and running more or less consistently (I suspect the "less" part is just
> a problem with me rather than the program).
>
> So it's likely that, with the path issue fixed, this bug can be closed.
>
> > But I guess it would make sense to have this set to true by default.
>
> I don't mind either way, provided it's documented.
>
> Jamie
>
>
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to