Issue #3070 has been updated by Bastian Blank.
The easiest workaround is to use a hard lock around all database access if sqlite is selected and the possibility exists in the puppet core. This would at least allow it to be used with some 100 hosts with thin storedconfig. FYI, I'm able to trigger this with 3 machines, this is not funny. The real fix needs to be done in Rails and sqlite3-ruby. The DB connection is in no usable state after SQLite3::Database::transaction fails while calling rollback and needs to be scrapped forcefully. But this failure also masks the original one. ---------------------------------------- Bug #3070: Leaks transactions http://projects.reductivelabs.com/issues/3070 Author: Bastian Blank Status: Duplicate Priority: Normal Assigned to: Markus Roberts Category: Rails Target version: Affected version: 0.25.1 Keywords: Branch: puppetmaster seems to leak transactions in the storedconfig part. After an error in the rollback, all further operations are blocked. Jan 14 07:57:48 puppet puppetmasterd[13495]: Could not call: cannot rollback transaction - SQL statements in progress Jan 14 07:57:48 puppet puppetmasterd[13495]: Could not call: cannot start a transaction within a transaction Jan 14 07:58:58 puppet puppetmasterd[13495]: Could not call: cannot start a transaction within a transaction Jan 14 08:01:54 puppet puppetmasterd[13495]: Could not call: cannot start a transaction within a transaction See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563657 for further information. -- 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.
