Control: retitle -1 elasticsearch: Please provide a systemd service file
> However the fact remains, systemd is confusingly reporting ES as
> being started when it is not. IMHO, that's an issue.
Not an issue here. Without START_DAEMON=true, systemd correctly reports
the unit as run successfully
On Thu, 16 Jul 2015 11:38:05 -0700 "Nathan D. Smith"
wrote:
Any progress on this?
I have the same issues as described above in Jessie. systemctl is
incorrect about the startup state, and it does not run.
I had to edit /etc/default/elasticsearch and uncomment
Any progress on this?
I have the same issues as described above in Jessie. systemctl is
incorrect about the startup state, and it does not run. I found that
installing from sid I could do the sudo -u elastic search manual start
and get it to start up with indexes in /var/lib/elasticsearch.
* Philipp Hug:
I suspect you did also run into the following problem, which is related:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768178
Uh-oh, this is bad. I strongly suspect that elasticsearch is not the
only package that has this issue.
systemd's behavior is interesting, I suspect
Hi Jamie,
Ist it possible that you just missed to set START_DAEMON=true
in /etc/default/elasticsearch
But I guess it would make sense to have this set to true by default.
Philipp
On Mon, 2014-11-17 at 23:06 +, 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
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.
On Tue, 2014-11-18 at 00:04 +, 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
On Thu, 2014-11-06 at 00:50 +0100, Hilko Bengen wrote:
I ended up with systemd at some point, too. And I still have no idea how
to debug daemon startup problems. :-(
Is there someone among the systemd maintainers who might be willing to
lend a hand here?
Jamie
--
To UNSUBSCRIBE, email to
On Tue, 2014-11-04 at 22:34 +0100, Hilko Bengen wrote:
$ sudo -u elasticsearch bash -x
/usr/share/elasticsearch/bin/elasticsearch.
Could you please try if upgrading to version 1.0.3+dfsg-5 (which I just
uploaded to unstable) fixes this problem?
The above command now runs elasticsearch
* Jamie Norrish:
$ sudo -u elasticsearch bash -x
/usr/share/elasticsearch/bin/elasticsearch.
Could you please try if upgrading to version 1.0.3+dfsg-5 (which I just
uploaded to unstable) fixes this problem?
The above command now runs elasticsearch properly.
So far so good...
It
On Wed, 2014-11-05 at 23:57 +0100, Hilko Bengen wrote:
It doesn't appear that /etc/init.d/elasticsearch works, however.
What init system do you have? SysV? systemd?
systemd. Sorry for not specifying that before.
# invoke-rc.d elasticsearch status
● elasticsearch.service - LSB: Starts
* Jamie Norrish:
It doesn't appear that /etc/init.d/elasticsearch works, however.
What init system do you have? SysV? systemd?
systemd. Sorry for not specifying that before.
I ended up with systemd at some point, too. And I still have no idea how
to debug daemon startup problems. :-(
#
* Jamie Norrish:
I am also experiencing this problem, with the IOException trying to
write to /usr/share/elasticsearch/data/elasticsearch/nodes/49 when
running:
$ sudo -u elasticsearch bash -x /usr/share/elasticsearch/bin/elasticsearch.
Could you please try if upgrading to version
I am also experiencing this problem, with the IOException trying to
write to /usr/share/elasticsearch/data/elasticsearch/nodes/49 when
running:
$ sudo -u elasticsearch bash -x /usr/share/elasticsearch/bin/elasticsearch.
My /etc/elasticsearch/elasticsearch.yml does not have path.data set (it
is
We never shipped 0.90.7 within Debian -- am I assuming correctly that
you used the .deb files provided by upstream?
Yes, this is very likely. I must have forgot this, apologies for not mentioning
it before. This must be it.
What output do you get when you run something like the following?
* Gillu:
We never shipped 0.90.7 within Debian -- am I assuming correctly that
you used the .deb files provided by upstream?
Yes, this is very likely. I must have forgot this, apologies for not
mentioning it before. This must be it.
No worries. :-)
What output do you get when you run
Package: elasticsearch
Version: 1.0.3+dfsg-4
Severity: important
Dear Maintainer,
I upgraded my system on 10/18 and from that point onwards elasticsearch (0.90.7
- 1.0.3+dfsg-3) doesn't start when invoking service elasticsearch start.
Running /usr/share/elasticsearch/bin/elasticsearch starts up
* K. Gilden:
I upgraded my system on 10/18 and from that point onwards elasticsearch
(0.90.7
- 1.0.3+dfsg-3) doesn't start when invoking service elasticsearch start.
Running /usr/share/elasticsearch/bin/elasticsearch starts up the server just
fine.
We never shipped 0.90.7 within Debian --
19 matches
Mail list logo