From 4d94612df8bc4059fbfebf61c18f4b6281159e17 Mon Sep 17 00:00:00 2001 From: Spencer Date: Fri, 22 Nov 2019 09:53:50 -0700 Subject: [PATCH] [7.3] Update where log files are written using systemd (#47570) (#51466) 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 --- docs/setup/install/systemd.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/setup/install/systemd.asciidoc b/docs/setup/install/systemd.asciidoc index 07d995244d511..3053972f9e384 100644 --- a/docs/setup/install/systemd.asciidoc +++ b/docs/setup/install/systemd.asciidoc @@ -18,5 +18,5 @@ sudo systemctl stop kibana.service -------------------------------------------- These commands provide no feedback as to whether Kibana was started -successfully or not. Instead, this information will be written in the log -files located in `/var/log/kibana/`. +successfully or not. Log information can be accessed via +`journalctl -u kibana.service`.