- 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,
- EJB 3.0 Database Persistence with Oracle Fusion Middleware 11g: LITE
- Excel函數、公式、圖表、數據處理從新手到高手
- Protel DXP 2004 SP2原理圖與PCB設計(第4版)
- Talend Open Studio Cookbook
- Cacti 0.8 Beginner's Guide
- 中文版 Photoshop CC 從入門到精通
- SPSS統計分析從基礎到實踐
- Plone 3 Intranets
- 中文版Photoshop CS6應用技法教程
- 科技繪圖/科研論文圖/論文配圖設計與創作自學手冊:科研動畫篇
- iOS智能手機APP界面設計實戰教程
- 3ds Max影視動畫角色設計技法教程
- 3ds Max三維動畫制作項目式教程
- Jasmine JavaScript Testing
- AutoCAD 2021中文版從入門到精通