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

Add journalctl command when service fails for systemd

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • PUP 4.6.0
    • None
    • New Feature
    • 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

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. PUP-5686 Add the output of failed "systemctl status (service)" in the report

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support