systemd reports warnings

[psaiz]

Kibana version:
7.1.1-oss
Elasticsearch version:
7.1.1-oss
Server OS version:
Centos 7
Browser version:

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):
yum
Describe the bug:
The file /etc/systemd/system/kibana.service contains two lines that generate warnings while checking the status of the service:

# cat /etc/systemd/system/kibana.service 
[Unit]
Description=Kibana
StartLimitIntervalSec=30
StartLimitBurst=3
...


# systemctl status kibana
● kibana.service
   Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-09-02 14:57:22 CEST; 1 months 0 days ago
 Main PID: 25399 (node)
   CGroup: /system.slice/kibana.service
           └─25399 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header-size=65536 /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml

Oct 02 10:50:24 xx : [/etc/systemd/system/kibana.service:3] Unknown lvalue 'StartLimitIntervalSec' in section 'Unit'
Oct 02 10:50:24 xx]: [/etc/systemd/system/kibana.service:4] Unknown lvalue 'StartLimitBurst' in section 'Unit'
...

Steps to reproduce:

1. Install kibana-7.1.1 rpm
2. Start the service with systemd : systemctl start kibana
3. Check the status of the service: systemctl status kibana

Expected behavior:
Not to have those warnings.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[mistic]

@psaiz this is probably happening because those options are not available in your systemd version they were only introduced in systemd v230.

In think in your version the available options would be StartLimitInterval= and StartLimitBurst= under [Service] section not [Unit]. You can check that running man systemd.unit.

@jbudz any ideas here ? Maybe we can should add documentation stating our supported systemd version or ship our service with both parameters configured so it would use what work for a specific systemd version, though the warnings would still be displayed.

[tylersmalley]

This was resolved in #47909 starting with 7.5.0.