I have a Chirpstack v4.1.0 with external Postgres SQL 14.5.
When I reboot Postgres SQL server to simulate SQL failure, ChirpStack (or Chirpstack API /api.InternalService…?) seems to spin around even when Postgres SQL is up again.
I need to sudo systemctl restart chirpstack to make ChirpStack work again.
Is there anyone having similar issue?
I’m delighted if there is any workaround for this issue.