Issue #4301 has been reported by Peter Meier. ---------------------------------------- Bug #4301: "empty" catalogs produced by master on subsequent compiles http://projects.puppetlabs.com/issues/4301
Author: Peter Meier Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 2.6.0 Keywords: Branch: This is kinda tricky, as it only appears after a while and totally by random. Problem: Clients requesting to compile manifest a 2nd or 3rd or 4th time and so on takes about 0.01s on the master. The 2.6 clients then receives a catalog which it applies super fast. But that catalog doesn't seem to contain any instructions (which might be the reason it is super fast), as no resources are managed. This means for example that the output with @--debug@ doesn't show any managed resources and also a resource that should be managed (for example a service that should be started) isn't managed. Observations: Running puppetmaster as webrick didn't show that problem it looks like it only appears on mongrel based masters. But this is a total guess, as the 2.6 with webrick was only tested against one client and only with 2-3 compile requests. Another observation is that around that time the master might choke about too many connections to the MySQL Server. Might this be a reason that the compilation is aborted and an "empty" catalog is sent to the client? I wasn't able to enforce a new proper compile request from the client, as every subsequent request also seemed to be "empty". Further investigations: I think I should try to examine further what is actually sent to the client. But so far I was only able to find the 2.5 yaml catalog (or is 2.6 still yaml?) which looks totally fine. Further guidelines would be nice. -- 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.
