Issue #7201 has been updated by Simon Boulet.
Hello I'm also having this issue. I've been running Puppet on Debian Squeeze for some time, attempted to add Puppetlabs repo to my sources.list, then apt-get upgrade'd puppet (updated facter, puppet and puppet-common). Now I am getting the "finished with exit code 3" message on puppet kick. Also, during startup I am not seeing the usual "Finished catalog run" message in the log. The last message from the log is "Starting Puppet client version 2.7.6"... until I gave up and killed -9 puppet. Now, I apt-get remove'd facter, puppet and puppet-common and reverted my sources.list, and reinstalled Puppet from the Squeeze repo. I'm back on Puppet 2.6.2 and everything is fine. I am not seeing this issue on my CentOS 5.7 nodes, all running 2.7.6 from the Puppetlabs RPM repo. My server is also running 2.7.6 on CentOS 5.7 without issues. Thanks Simon ---------------------------------------- Bug #7201: [puppet2.7]puppet kick exit code 3 https://projects.puppetlabs.com/issues/7201 Author: joy huang Status: Needs More Information Priority: High Assignee: Category: server Target version: Affected Puppet version: Keywords: Branch: 1.when i run the following " puppet kick"command on puppet master,it return failed message: <pre> [root@master puppet]# puppet kick -p 10 --host client.joy.com Triggering client.joy.com Getting status status is running Host client.joy.com is already running client.joy.com finished with exit code 3 Failed: client.joy.com </pre> 2.puppet agent relative setting is: <pre> [root@client puppet]cat /etc/puppet/auth.conf path ~ ^/catalog/([^/]+)$ method find allow $1 path /certificate_revocation_list/ca method find allow * # allow all nodes to store their reports path /report method save allow * # inconditionnally allow access to all files services # which means in practice that fileserver.conf will # still be used path /file allow * ### Unauthenticated ACL, for clients for which the current master doesn't ### have a valid certificate # allow access to the master CA path /certificate/ca auth no method find allow * path /certificate/ auth no method find allow * path /certificate_request auth no method find, save allow * path /run method save allow * # this one is not stricly necessary, but it has the merit # to show the default policy which is deny everything else path / auth any [root@client puppet]# cat namespaceauth.conf [fileserver] allow * [puppetmaster] allow * [puppetrunner] allow * [puppetbucket] allow * [puppetreports] allow * [resource] allow * [root@client puppet]# cat puppet.conf [main] confdir = /etc/puppet vardir=/var/lib/puppet logdir = $vardir/log # Where Puppet PID files are kept. # The default value is $vardir/run. rundir = $vardir/run # The default value is $confdir/ssl. ssldir = $confdir/ssl [agent] pidfile = /var/lib/puppet/run/agent.pid classfile = $vardir/state/classes.txt localconfig = $vardir/localconfig server = master.joy.com #report = true listen = true </pre> 3.[root@client puppet]# netstat -lntp <pre> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:8139 0.0.0.0:* LISTEN 2515/ruby </pre> The "puppetrun problem" is bothering me for a long time ,from puppet2.6.XX to puppet 2.7 release. I need your help! any suggestion is welcome Thanks joy -- 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.
