elasticsearch service fails to start due to permissions on /usr/share/elasticsearch/

Bug #1809275 reported by Jeff Hillman
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Elasticsearch Charm
Expired
High
Unassigned

Bug Description

The elasticsearch charm fails on peer-relation-joined because the service itself fails to start. looking at the logs in /var/log/syslog, elastic search is complainig that it can't write to /usr/share/elasticsearch/logs

That directory doesn't exist, if we creaete that dir and give it ownership by elasticsearch, the error message goes away.

Charm elasticsearch-32 from charmstore.

using the 6.x repository

Tags: cpe-onsite
Revision history for this message
Jeff Hillman (jhillman) wrote :

UPDATE: We re-deployed and just giving logs permissions isn't enough, ES also wants to create and add to /usr/share/elasticsearch/data. Giving user.gorup ownership to elasticsearch for /usr/share/elasticsearch seems to resolve this better.

This could be an elastic search package issue, or I suppose the charm could make the permissions change...

Revision history for this message
Vern Hart (vern) wrote :

Is this being seen anywhere else? If not, what is special about this deployment?

Revision history for this message
Sander Borny (sborny) wrote :

I also encountered this issue.
Deployed via `juju deploy cs:elasticsearch --config apt-repository="deb https://artifacts.elastic.co/packages/6.x/apt stable main"`.

Revision history for this message
Xav Paice (xavpaice) wrote :

I've been unable to reproduce this, is there something specific we can do to get a reproducer?

Changed in charm-elasticsearch:
status: New → Incomplete
Revision history for this message
Jeff Hillman (jhillman) wrote : Re: [Bug 1809275] Re: elasticsearch service fails to start due to permissions on /usr/share/elasticsearch/

We no longer have access to the environment that this was found in. It was
both offline and air-gapped.

Using Elasticsearch-32 and 'artifacts.elastic.co/packages/6.x/apt/ stable
main', all hosted on a local mirror.

Jeff Hillman
Principal Cloud Consultant
Canonical
Mobile: +1 512 743 1815

On Wed, Mar 11, 2020 at 4:25 PM Xav Paice <email address hidden> wrote:

> I've been unable to reproduce this, is there something specific we can
> do to get a reproducer?
>
> ** Changed in: charm-elasticsearch
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1809275
>
> Title:
> elasticsearch service fails to start due to permissions on
> /usr/share/elasticsearch/
>
> Status in Elasticsearch Charm:
> Incomplete
>
> Bug description:
> The elasticsearch charm fails on peer-relation-joined because the
> service itself fails to start. looking at the logs in
> /var/log/syslog, elastic search is complainig that it can't write to
> /usr/share/elasticsearch/logs
>
> That directory doesn't exist, if we creaete that dir and give it
> ownership by elasticsearch, the error message goes away.
>
> Charm elasticsearch-32 from charmstore.
>
> using the 6.x repository
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charm-elasticsearch/+bug/1809275/+subscriptions
>

Changed in charm-elasticsearch:
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Elasticsearch Charm because there has been no activity for 60 days.]

Changed in charm-elasticsearch:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.