My site is in a really bad state

5

I believe I hit a related error today as well. After performing a fly deploy I began to see a similar error to this in my logs: ERROR: cannot init consul: cannot connect to consul: register node "kcd-g3zmqx5x3y49dlp4/litefs": Unexpected response code: 500 (No cluster leader). (of course the error message contained my litefs mount directory, not “kcd”.

There were a few things different about today’s fly deploy, compared to prior working deploys:

  • Today flyctl automatically updated itself (possibly to 0.1.104? But I’m not sure)
  • I modified my litefs.yml file, adding a command to run migrations when is-candidate: true.
  • My app server would have failed because it required some environment variables, and I had not set those variables

(whether any of these were factors in the consul issue, I don’t know)

In case it’s useful, my app is prod-nb-site under the neuronbench organization.

2 Likes