Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-5604

Add journalctl command when service fails for systemd

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.6.0
    • Component/s: None
    • Release Notes:
      New Feature
    • Release Notes Summary:
      the systemd service provider now asks journalctl why something failed and reports it back to the user for aid in debugging.

      Description

      It's not super easy to diagnose issues when services fail to start with systemd:

      Error: Could not start Service[corosync]: Execution of '/usr/bin/systemctl start corosync' returned 1: Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details.
      

      Would be nice to add some logic to actually run the journalctl for the service if it fails so we can get full details of the logs.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  peter.souter Peter Souter
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support