# Pastebin W6kTcLLE
+ systemctl restart systemd-journald.service
Job for systemd-journald.service failed because start of the service was attempted too often. See "systemctl status systemd-journald.service" and "journalctl -xe" for details.
To force a start use "systemctl reset-failed systemd-journald.service" followed by "systemctl start systemd-journald.service" again.
+ systemctl status systemd-journald.service
● systemd-journald.service - Journal Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static; vendor preset: disabled)
  Drop-In: /etc/systemd/system/systemd-journald.service.d
           └─no-start-limit.conf
   Active: failed (Result: start-limit) since Tue 2020-06-02 08:23:25 UTC; 6ms ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
  Process: 28588 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=0/SUCCESS)
 Main PID: 28588 (code=exited, status=0/SUCCESS)
   Status: "Processing requests..."

Jun 02 08:23:24 may201530-015177 systemd-journal[28588]: Runtime journal is using 8.0M (max allowed 184.6M, trying to leave 276.9M free of 1.7G available → current limit 184.6M).
Jun 02 08:23:24 may201530-015177 systemd-journal[28588]: Journal started
Jun 02 08:23:25 may201530-015177 systemd-journal[28588]: Journal stopped
+ true
+ echo 'Failed to restart systemd-journald.service, exiting...'
Failed to restart systemd-journald.service, exiting...