Issue #5114 has been updated by Nigel Kersten. Status changed from Unreviewed to Accepted Keywords set to lockfile
---------------------------------------- Bug #5114: puppetd should not try to remove lock file in test mode https://projects.puppetlabs.com/issues/5114 Author: Luke Bigum Status: Accepted Priority: Low Assignee: Category: Target version: Affected Puppet version: 2.6.2 Keywords: lockfile Branch: Just wanted to point out a small logic issue with running "puppetd --test" while another puppetd daemon is running on CentOS. If a lock file exists (/var/run/puppet/agent.pid) "puppetd --test" will try to remove it interrupted with SIGINT, probably for other signals as well but I haven't tested any more. It will fail, but probably shouldn't attempt to remove it in the first place. # puppetd --test info: Retrieving plugin info: Caching catalog for mysql-200-46.fasthosts.net.uk info: Applying configuration version '1288194666' ... notice: Caught INT; calling stop err: Could not remove PID file /var/run/puppet/agent.pid -- 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.
