If you restart beanstalkd, the workers cannot reconnect

[mexisme]

You get continual Exception Beaneater::NotConnected -> Could not connect! even when beanstalkd has been correctly restarted.

[mexisme]

This is actually quite a nasty one.
It may be in Backburner, as that's the system that manages the workers, or it may be in Beaneater, as that tries to pool/cache several connections, and may not be cleaning them up correctly.

[mexisme]

This appears to be a bug in beaneater, and fixed in beanstalkd/beaneater@7fd69f6

(Not cleaning-up pooled connections when the fail)

[mexisme]

This seems to be caused by nesquena/backburner#93.
Changing to ::ThreadsOnFork worker fixes the problem.

[mexisme]

FYI: @kuahyeow, @tigerwnz

Backburner collaborator replied to my bug:
nesquena/backburner#93 (comment) :

I see what you're saying with the conflation bit there.
What it should probably do is pass the newly-minted Connection into the work_one_job method (which accepts an optional Connection instance).
The Worker doesn't seem to have/use a @connection instance var.