Issue #9290 has been updated by Nacho Barrientos. Support Urls deleted (https://support.puppetlabs.com/tickets/1819)
In our particular case, this problem was found when migrating from Puppet 2.7.18 to Puppet 3.2.2. Apparently the situation improves for a short period of time when we restart the masters. We noticed it when we tried to apply the patch attached above. Basically we applied it, restarted all our masters backend and we didn't see any "stack level too deep" for a while (~1h hour) so we thought it was fixed. However, later on we began to experience the problem again. In short: * Patch in comment#1 didn't work. * Forcing activerecord version didn't work either (we use puppetdb, though) -- tried with 3.0.11 and 3.0.15. We're now at 2.3.16. * Reducing the number of deprecation warnings like [1] alleviated a bit the number of 400s we were getting. Finally, we were forced to roll back to Puppet 2 :( [1] > Variable access via 'serveradmin' is deprecated. Use '@serveradmin' instead. > template[/etc/puppet/environments/devel/modules/apache/templates/httpd.conf.erb]:181 ---------------------------------------- Bug #9290: Puppet master fails with 'stack level too deep' error when storeconfigs = true with rails stack 3.1.0 https://projects.puppetlabs.com/issues/9290#change-93232 * Author: Mark Stanislav * Status: Accepted * Priority: High * Assignee: eric sorenson * Category: Rails * Target version: 3.1.x * Affected Puppet version: 2.7.3 * Keywords: storeconfigs rails activerecord 3.1.0 customer * Branch: ---------------------------------------- Out of nowhere, a known-working Puppet stack build script started to fail. The tell-tale error is 'stack level too deep' which from other historical bug reports always seems related to Ruby directly. After many hours of digging around, I checked for updated gem versions on the system. There was an update to rails 3.1.0 (and activerecord, etc.) which apparently is breaking the Puppet master when working with storeconfigs = true. Disabling storeconfigs immediately works as expected again. When reverting from rails and friends 3.1.0 to 3.0.10, Puppet again works as expected. I don't have any insight into where exactly this is all failing, only the version which is causing the issue and the condition to emulate it. This was only tested again Puppet 2.7.3 using the gem install with both webrick and Apache+Passenger. Attached is a debug output. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
