- Puppet 2.7 Cookbook
- John Arundel
- 224字
- 2021-04-02 18:20:03
Logging command output
"Computer says no."—Little Britain
Detailed feedback on problems can be helpful. When you use exec
resources to run commands on the node, it's not always easy to find out why they haven't worked. Puppet will give you an error message if a command returns a non-zero exit status. The error will be similar to the following:
err: /Stage[main]//Node[cookbook]/Exec[this-will-fail]/returns: change from notrun to 0 failed: /bin/ls file-that-doesnt-exist returned 2 instead of one of [0] at /etc/puppet/manifests/nodes.pp:10
Often we would like to see the actual output from the command that failed, rather than just the numerical exit status. You can do this with the logoutput
parameter.
How to do it…
Define an exec
resource with the logoutput
parameter as follows:
exec { "this-will-fail": command => "/bin/ls file-that-doesnt-exist", logoutput => on_failure, }
How it works…
Now, if the command fails, Puppet will also print its output:
notice: /Stage[main]//Node[cookbook]/Exec[this-will-fail]/returns: /bin/ls: cannot access file-that-doesnt-exist: No such file or directory err: /Stage[main]//Node[cookbook]/Exec[this-will-fail]/returns: change from notrun to 0 failed: /bin/ls file-that-doesnt-exist returned 2 instead of one of [0] at /etc/puppet/manifests/nodes.pp:11
There's more…
You can set this to be the default for all exec
resources by defining the following:
Exec { logoutput => on_failure, }
If you want to see the command output whether it succeeds or fails, use the following:
logoutput => true,
- Instant Vert.x
- Animate 2022動畫制作:團體操隊形
- Swing Extreme Testing
- 中文版Maya 2012實用教程(第2版)
- 數字孿生體:第四次工業革命的通用目的技術
- 穿越Photoshop CC
- 視覺封王:Photoshop CC 2019立體化教程(素材+視頻+教案)
- RESTful PHP Web Services
- SolidWorks 2019快速自學寶典
- AutoCAD 2024建筑設計從入門到精通(升級版)
- 正則表達式必知必會(修訂版)
- 零基礎學會聲會影2018(全視頻教學版)
- 三維建模與3D打印從入門到精通
- Premiere Pro基礎與實戰教程
- Unity 3D游戲開發(第2版)