Many thanks, indeed I had not upgraded passenger like I thought. I moved it to 5.0.13.
Since adding the DB:disconnect, things do appear better, although our DBAs still report a high number of disonnected processes. Looks like that may be a known mysql2 issue: https://github.com/brianmario/mysql2/issues/606 I'll continue to watch the app for DatabaseDisconnect errors. So far there have been none for the past 12 hours. On Monday, August 3, 2015 at 7:25:01 PM UTC-4, Jeremy Evans wrote: > > On Monday, August 3, 2015 at 1:49:38 PM UTC-7, Joel Collins wrote: >> >> Thank you. I added a DB:disconnect at the end of config.ru. Something >> special about disconnecting the database so the database will stop >> disconnecting... >> >> Should this not have been something that the 'connection validator' >> extension should have caught however? My settings are such that all >> connections are validated, right? >> > > Yes, but if the connection is shared, the query used to check connection > validity may not fail, while the query you are actually executing can still > fail. It's a race condition at that point, and if you lose the race.... > There is nothing Sequel can do to fix the case where you are sharing a > socket connection between processes. You need to disconnect before fork to > make sure that isn't the case. > > If you are still having problems after the disconnect before fork, then > let me know. One thing to consider is you mentioned using passenger 5.0.5, > but your backtrace shows passenger 4.0.41, you may want to investigate that. > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk. For more options, visit https://groups.google.com/d/optout.
