On Fri, Sep 6, 2019 at 9:58 AM Jeremy Evans <[email protected]> wrote:
> > Can you see if you can reproduce the issue using nginx/(unicorn|puma) > instead of nginx/passenger, to determine if this issue is passenger > specific? > Good idea, I will try out it too. Related to that, I'm also seeing the same error in a separate app which is ActiveRecord/Sidekiq and just started happening recently (that app's been running for years with similar sidekiq/ar pool settings. The app that uses Sequel/Passenger has seen it for a longer period, but it's gotten more frequent recently, so there may be something happening on the MySQL/network side to dig into. Thanks, Ryan -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/CAOq_b1wc%2BQ322iwp34P6OVja%2BFVT0L61JfyNbWZxKJNpKCoHZg%40mail.gmail.com.
