Jira (PUP-5604) Add journalctl command when service fails for systemd

[Peter Souter (JIRA)]

Title: Message Title

Peter Souter created an issue   Puppet / PUP-5604 Add journalctl command when service fails for systemd Issue Type: Improvement Assignee: Unassigned Created: 2015/12/12 2:57 PM Priority: Normal Reporter: Peter Souter 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. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.