Kibana: Setting pid.file in /etc/kibana/kibana.yml cause: EACCES: permission denied, open '/var/run/kibana.pid'

Created on 28 May 2017  路  6Comments  路  Source: elastic/kibana

elasticsearch-5.4.0.deb
filebeat-5.4.0-amd64.deb
kibana-5.4.0-amd64.deb

bash# uname -a
Linux desktop 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) x86_64 GNU/Linux

Steps to reproduce:

  1. Grab from official site and pkgs -i *.deb
  2. uncomment pid.file: /var/run/kibana.pid in /etc/kibana/kibana.yml
  3. sudo service kibana start

cat /var/log/kibana/kibana.stderr:

FATAL { Error: EACCES: permission denied, open '/var/run/kibana.pid'
    at Error (native)
  cause: 
   { Error: EACCES: permission denied, open '/var/run/kibana.pid'
       at Error (native)
     errno: -13,
     code: 'EACCES',
     syscall: 'open',
     path: '/var/run/kibana.pid' },
  isOperational: true,
  errno: -13,
  code: 'EACCES',
  syscall: 'open',
  path: '/var/run/kibana.pid' }
Operations bug

Most helpful comment

I change the owner of /var/run/kibana.pid to kibana to solve this(work around way).

All 6 comments

I'd like for this to be the default setting on packages. The problem here is the kibana server is running as user kibana and /var/run needs root. The package service will need to create a folder owned by kibana on startup.

+1

I change the owner of /var/run/kibana.pid to kibana to solve this(work around way).

@jbudz Is this still an issue? Looks like you merged a PR that reference this issue. Can this be closed?

Running kibana 7.6.0 on CentOs 7.7 and just faced this problem. Using /var/run/kibana folder with proper ownership resolves the problem. To support this, elasticsearch package uses exactly the same approach.

OpenSUSE 15.1, no /var/run/kibana pid file created by default. Elasticsearch does, as mentioned, and handles all permissions. pid files are so standard on Linux, Kibana should support it out of the box.

Was this page helpful?
0 / 5 - 0 ratings