On Tue, 2014-11-18 at 00:04 +0000, Philipp Hug wrote:

> 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.

Ah, interesting, thanks. That would certainly explain some of the
messages and odd behaviour that I've been seeing while testing this -
including it not appearing that setting START_DAEMON=true made any
difference, when starting it without explicitly stopping it first).
Still my own stupid fault, though!

Thanks so much for the help!


This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to