Issue #2661 has been updated by Peter Meier.
James Turnbull wrote: > Pushed in commit:"adc0a4ed939a717e8735485d493bde28ceab5ac0" in branch 0.25.x ok I had this now running for some weeks and I have nearly no problems anymore. However from time to time (maybe once a week) a random client doesn't remove it's lockfile, hence future runs fail. I assume this might still happen due to a uncatched exception, however the problem is a) hard or nearly impossible to reproduce and b) it occurs really by random. The only thing I can see in the logs: <pre> Nov 30 19:27:41 foobar puppetd[26228]: Finished catalog run in 98.79 seconds Nov 30 20:00:02 foobar puppetd[3000]: Could not retrieve catalog from remote server: Error 502 on SERVER: <html>^M <head><title>502 Bad Gateway</title></head>^M <body bgcolor="white">^M <center><h1>502 Bad Gateway</h1></center>^M <hr><center>nginx/0.6.39</center>^M </body>^M </html>^M Nov 30 20:00:03 foobar puppetd[3000]: Using cached catalog Nov 30 20:00:03 foobar puppetd[3000]: Could not retrieve catalog; skipping run Nov 30 20:00:04 foobar puppetd[12169]: Run of Puppet configuration client already in progress; skipping Nov 30 20:30:04 foobar puppetd[21230]: Run of Puppet configuration client already in progress; skipping </pre> as I run puppetd by cron twice an hour with --splay I assume that the run between 19:30 and 20:00 got delayed till 20:00. At this time (20:00) a puppetmaster restart happens and due to that the 502 occured. This was the run of pid 3000, the next run (pid 12169) failed, this could either be as pid 3000 was still running or because there was already no puppetd anymore running and the lock file haven't been removed. However every future run failed as well as the lockfile wasn't removed. Should I file this rather as a new bug report? ---------------------------------------- Bug #2661: puppetd exits if the master is unreachable. http://projects.reductivelabs.com/issues/2661 Author: R.I. Pienaar aka Volcane Status: Closed Priority: Normal Assigned to: Markus Roberts Category: plumbing Target version: 0.25.2 Affected version: 0.25.0 Keywords: Branch: http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/2661 In the event that the master becomes unreachable the puppetd will exit instead of use the cache, retry later etc like older puppetd did. <pre> # iptables -I INPUT -s puppet -j DROP # puppetd --debug --trace --no-daemonize <snip> /usr/lib/ruby/1.8/timeout.rb:54:in `open': execution expired (Timeout::Error) from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout' from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' from /usr/lib/ruby/1.8/net/http.rb:542:in `start' from /usr/lib/ruby/1.8/net/http.rb:1035:in `request' from /usr/lib/ruby/1.8/net/http.rb:772:in `get' ... 28 levels... from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' from /usr/sbin/puppetd:159 </pre> -- 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://reductivelabs.com/redmine/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.
