Thanks for the help! I am so frustrated by this... the terminology is what is killing me. I have a free worker and a free Dyno for this test... and all the code works, until I send a second request to the worker. I suspect it is all me..
I created a gist of the config files I use.. not sure that is too helpful, but anyway, this setup of Puma, Sequel at heroku with a worker, is troubling me... https://gist.github.com/resistorsoftware/f77b15e66c9362b8c9b7f281bccc1851 On Friday, January 19, 2018 at 2:26:59 PM UTC-5, Jeremy Evans wrote: > > On Friday, January 19, 2018 at 10:33:55 AM UTC-8, David Lazar wrote: >> >> My latest Apps deployed to Heroku are now experiencing errors I have not >> seen before. Specifically, during worker tasks, the connection is >> generating an error: >> >> ERROR -- : PG::ConnectionBad: PQconsumeInput() SSL error: decryption >> failed or bad record mac: >> >> The Puma config I use it pretty generic, in that it does not preloadapp! >> calls or anything in the worker_on_boot calls. I just setup my initializer >> for Sequel as usual and expect web and workers to just work. >> >> Any tips on what might be causing this at Heroku? >> > > It does sound like an error you would get if the same connection was used > by multiple processes or threads simultaneously. If you aren't preloading > or forcing use of the single threaded connection pool, I'm not sure what > would cause it. If you can produce a minimal self-contained example > showing the problem, I can look into it. > > 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 https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
