[PUP-5604] Add journalctl command when service fails for systemd Created: 2015/12/12 Updated: 2019/03/28 Resolved: 2016/06/30
|Fix Version/s:||PUP 4.6.0|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Epic Link:||Service Phase 1 Type/Provider Improvements|
|Sprint:||Client 2016-06-29, Client 2016-07-13 (HA, 1.5.3)|
|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.|
It's not super easy to diagnose issues when services fail to start with systemd:
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.
|Comment by Tim Meusel [ 2015/12/12 ]|
+1 for this. Would be great if Puppet could run "systemctl -u $servicewebroke --full". "-n linenumberthatwelike" would also be good so we don't blow up the output.
|Comment by Ranjit Viswakumar [ 2016/06/14 ]|
Work around in the meantime.
|Comment by Eric Thompson [ 2016/06/30 ]|
validated against puppet agent master sha: 2e1f658732ca423ee43860cb3a7ce7b2c549938e