From 446e29baf56b004f3ff245ef6e10aa78d60add6d Mon Sep 17 00:00:00 2001 From: mbonsack Date: Tue, 28 Jul 2020 07:06:31 -0700 Subject: [PATCH] Clarify initial troubleshooting steps (#589) * Account for the case where systemd will not issue an immediate error after sc4s service startup --- docs/troubleshooting.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index bcc5682..e14b1ae 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -9,12 +9,13 @@ running out of systemd, you may see this at startup: [root@sc4s syslog-ng]# systemctl start sc4s Job for sc4s.service failed because the control process exited with error code. See "systemctl status sc4s.service" and "journalctl -xe" for details. ``` -A better command than `journalctl -xe` is the following, +In other cases, there may be nothing untoward after starting with systemd, but the container is not running at all +after checking with `podman logs SC4S` or `podman ps`. A more informative command than `journalctl -xe` is the following, ``` journalctl -b -u sc4s | tail -100 ``` which will print the last 100 lines of the system journal in far more detail, which should be sufficient to see the specific failure -(syntax or runtime) and guide you in troubleshooting. +(syntax or runtime) and guide you in troubleshooting why the container exited unexpectedly. As an alternative to launching via systemd during the initial installation phase, you may wish to test the container startup outside of the systemd startup environment. The following commmand will launch the container directly from the CLI. This command assumes the local mounted