Jira (PUP-911) Puppet silent about inability to acquire pidlock

[Daniel Dreier (JIRA)]

Title: Message Title

Daniel Dreier commented on an issue   Re: Puppet silent about inability to acquire pidlock I've confirmed this behavior on puppet 3.6.2 on Centos 6.5. [root@centos-65-latest ~]# service puppet stop Stopping puppet agent: [ OK ] [root@centos-65-latest ~]# service puppet start Starting puppet agent: [ OK ] [root@centos-65-latest ~]# puppet agent --verbose Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1095:in `issue_deprecations') Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid [root@centos-65-latest ~]# echo $? 0 [root@centos-65-latest ~]# puppet --version 3.6.2 Add Comment   Puppet / PUP-911 Puppet silent about inability to acquire pidlock The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.