Updated code for spacing and line breaks

This commit is contained in:
Jennifer Travinski
2021-08-30 14:37:25 -04:00
parent 27a5f54240
commit 59c8822504
@@ -75,14 +75,14 @@ In Rancher logging, `SystemdLogPath` must be configured for K3s and RKE2 Kuberne
K3s and RKE2 Kubernetes distributions log to journald, which is the subsystem of systemd that is used for logging. In order to collect these logs, the `systemdLogPath` needs to be defined. While the `run/log/journal` directory is used by default, some Linux distributions do not default to this path. For example, Ubuntu defaults to `var/log/journal`. To determine your `systemdLogPath` configuration, see steps below.
**Steps for Systemd Configuration:** <br />
**Steps for Systemd Configuration:**
Run `cat /etc/systemd/journald.conf | grep -E ^\#?Storage | cut -d"=" -f2` on one of your nodes.
* If `persistent` is returned, your `systemdLogPath` should be `/var/log/journal`.
* If `volatile` is returned, your `systemdLogPath` should be `/run/log/journal`.
* If `auto` is returned, check if `/var/log/journal` exists. <br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - If `/var/log/journal` exists, then use `/var/log/journal`. <br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - If `/var/log/journal` does not exist, then use `/run/log/journal`.
* If `auto` is returned, check if `/var/log/journal` exists.
* If `/var/log/journal` exists, then use `/var/log/journal`.
* If `/var/log/journal` does not exist, then use `/run/log/journal`.
* If any value not described above is returned, Rancher Logging will not be able to collect control plane logs. To address this issue, set `Storage=volatile` in journald.conf, reboot your machine, and set `systemdLogPath` to `/run/log/journal`.