Issue #10336 has been updated by Ken Perkins.
So, this was part of the config on the module in question:
file { ["/tmp/nginx/proxy_cache", "/tmp/nginx/proxy_tmp"]:
ensure => directory,
recurse => true,
require => Class["common::www"],
}
Something about recurse was the culprit. As the cache size grew, it got longer
and longer to run puppet. There may still be a bug here (perhaps puppet could
better communicate that it was working on this step) but I think it's likely
simply me being a dumb user.
----------------------------------------
Bug #10336: Hang for 600+ seconds during Puppet executing on nodes
https://projects.puppetlabs.com/issues/10336
Author: Ken Perkins
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version: 2.7.3
Keywords:
Branch:
Whenever I run puppet on a specific type of node (3 different machines in 2
environments) I get a hang in the middle of the run for up to 1400 seconds.
You can see the delay in the attached file by searching for timestamp:
22:59:49.191168
I debugged into gdb.rb and did ruby threads 30 seconds apart, and here's the
output:
http://pastebin.com/jNKUUGzs
--
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.
