Issue #2880 has been updated by Frank Sweetser.
So it's entirely possible, then, that I'm simply running into a bug in MySQL that webrick is somehow masking. I'm planning on migrating my puppetmaster over to a CentOS 5 box in the next couple of weeks, so I'll repeat my testing then and see if my real issue is just running an old buggy OS. And if that doesn't work, then I'll break out the hacksaw and start digging. ---------------------------------------- Bug #2880: Fix for mysql 'server has gone away' under passenger http://projects.reductivelabs.com/issues/2880 Author: Frank Sweetser Status: Needs more information Priority: Normal Assigned to: Christian Hofstaedtler Category: Rails Target version: Affected version: 0.25.1 Keywords: mysql passenger Branch: After moving my puppetmaster from webrick to passenger, I found that each backend puppetmaster instance would lose it database connection after the first client finished its run. Searching around, I found that recent versions of rails included a reconnect option, which fixed similar symptoms in other applications. The attached patch appears to have fixed the glitch for me. Gem versions: activerecord (2.3.3) passenger (2.2.7) rack (1.0.1) -- 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.
