Mark Havekes

@rosa okay so here are the debug logs, i could't get the exception to trigger this time, weird... Makes it seem like it's maybe something that only happens after it's...

> May I ask how the restart of your containers happen? sure! we use the default docker swarm settings, so that would be SIGTERM followed by a SIGKILL after 10...

@rosa can the cause possibly be that when the supervisor kills its forked processes, those processes terminate the database socket connection that is shared between the different processes? or does...

oh I've been testing a combination of SIGKILL and SIGTERM, they both sometimes trigger the exception and sometimes not... manually killing worker and dispatcher processes work fine and the supervisor...

Hey! I will try this out soon! > is it via Docker's `CMD`? yup! > Is it just `bin/rails solid_queue:start`? yup!

@rosa We've been running #269 on one of our apps for the entire weekend and haven't seen the error yet! It has definitely been rebooted a few times and just...

Hey @rosa I have not, we can consider this fixed, thanks so much! I'm curious if this error returns with version 0.6, but if it does, it's easy to catch...