b2e200437e
At least for kibana-oss 7.4, this is how I can access Kibana logs. The file `/var/log/kibana` is not created and if I set it as a log file, kibana does not have permission to write there. See also: https://github.com/elastic/kibana/issues/6579
23 lines
703 B
Plaintext
23 lines
703 B
Plaintext
==== Running Kibana with `systemd`
|
|
|
|
To configure Kibana to start automatically when the system boots up,
|
|
run the following commands:
|
|
|
|
[source,sh]
|
|
--------------------------------------------------
|
|
sudo /bin/systemctl daemon-reload
|
|
sudo /bin/systemctl enable kibana.service
|
|
--------------------------------------------------
|
|
|
|
Kibana can be started and stopped as follows:
|
|
|
|
[source,sh]
|
|
--------------------------------------------
|
|
sudo systemctl start kibana.service
|
|
sudo systemctl stop kibana.service
|
|
--------------------------------------------
|
|
|
|
These commands provide no feedback as to whether Kibana was started
|
|
successfully or not. Log information can be accessed via
|
|
`journalctl -u kibana.service`.
|