Issue #16280 has been updated by Banio Carpenter.
Yeah, basically. If we captured the shell output that would solve it. ---------------------------------------- Feature #16280: Provide a logoutput for service like exec https://projects.puppetlabs.com/issues/16280#change-70850 Author: Banio Carpenter Status: Needs More Information Priority: Normal Assignee: Banio Carpenter Category: Target version: Affected Puppet version: Keywords: Branch: If I have a service defined that fails, and the service does not log anywhere, it becomes near impossible to troubleshoot the issue. I have this case for memcached, which at least on Centos does not have a way of logging. Even for those services that do have logging, this would be extremely helpful. Example of current output: Sep 6 15:38:18 domU-12-31-39-0B-C4-71 puppet-agent[1109]: (/Stage[main]/Elmer::Virtualenvtest/Service[memcached]/ensure) change from stopped to running failed: Could not start Service[memcached]: Execution of '/sbin/service memcached start' returned 1: at /etc/puppet/modules/elmer/manifests/virtualenvtest.pp:37 OK I know it failed but I have no idea why. Without knowing the stderr, one has to attempt to reproduce the exact situation in a shell, which would be difficult. If we could just be able to use the same feature currently available for exec like below, my life would be a lot easier: service {memcached: ensure => running, logoutput => "on failure", } -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
