Hi all,
I have the exact same problem as described in
this issue on the beanstalkd Github repo, however I don't know how to solve it.
Starting the beanstalkd service (I'm using Ubuntu Server 16.04.1 LTS) using
service beanstalkd start seems to ignore the config parameters in the
/etc/default/beanstalkd file although it was running fine for the 5 last months.
Any help is welcome :)