Worker no longer starting . connection refused to 7777?

I’ve always had issues with workers refusing to start on boot-up. However now they are refusing to start even when killing the concourse worker service and restarting it.

Any ideas what’s going on?

    Nov 26 20:50:07 hci01.discord.local concourse_worker[916]: {"timestamp":"2019-11-27T02:50:07.305574398Z","level":"error","source":"worker","message":"worker.beacon-runner.beacon.forward-conn.failed-to-dial","data":{"addr":"127.0.0.1:7777","error":"dial tcp 127.0.0.1:7777: connect: connection refused","network":"tcp","session":"4.1.4"}}
    Nov 26 20:50:08 hci01.discord.local concourse_worker[916]: {"timestamp":"2019-11-27T02:50:08.305764469Z","level":"info","source":"worker","message":"worker.beacon-runner.beacon.forward-conn.retrying","data":{"addr":"127.0.0.1:7777","network":"tcp","session":"4.1.4"}}
    Nov 26 20:50:08 hci01.discord.local concourse_worker[916]: {"timestamp":"2019-11-27T02:50:08.305976107Z","level":"error","source":"worker","message":"worker.beacon-runner.beacon.forward-conn.failed-to-dial","data":{"addr":"127.0.0.1:7777","error":"dial tcp 127.0.0.1:7777: connect: connection refused","network":"tcp","session":"4.1.4"}}
    Nov 26 20:50:09 hci01.discord.local concourse_worker[916]: {"timestamp":"2019-11-27T02:50:09.306181935Z","level":"info","source":"worker","message":"worker.beacon-runner.beacon.forward-conn.retrying","data":{"addr":"127.0.0.1:7777","network":"tcp","session":"4.1.4"}}
    Nov 26 20:50:09 hci01.discord.local concourse_worker[916]: {"timestamp":"2019-11-27T02:50:09.306412327Z","level":"error","source":"worker","message":"worker.beacon-runner.beacon.forward-conn.failed-to-dial","data":{"addr":"127.0.0.1:7777","error":"dial tcp 127.0.0.1:7777: connect: connection refused","network":"tcp","session":"4.1.4"}}
    Nov 26 20:50:10 hci01.discord.local concourse_worker[916]: {"timestamp":"2019-11-27T02:50:10.306615101Z","level":"info","source":"worker","message":"worker.beacon-runner.beacon.forward-conn.retrying","data":{"addr":"127.0.0.1:7777","network":"tcp","session":"4.1.4"}}
    Nov 26 20:50:10 hci01.discord.local concourse_worker[916]: {"timestamp":"2019-11-27T02:50:10.306794014Z","level":"error","source":"worker","message":"worker.beacon-runner.beacon.forward-conn.failed-to-dial","data":{"addr":"127.0.0.1:7777","error":"dial tcp 127.0.0.1:7777: connect: connection refused","network":"tcp","session":"4.1.4"}}

Nevermind… looks like a bug in ~concourse~ garden due to a blank /opt/concourse/worker/garden-properties.json file. Raising a ticket.

Sharing the issue here: https://github.com/concourse/concourse/issues/4833

I’m curious, what are the tools you are using to deploy concourse with?