No automatical reconnection of Postgres server?

Hi all,
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.

Thanks millions and have a nice weekend.

With the latest master source, I can not reproduce this issue. It should re-connect automatically in case of a PostgreSQL disconnect.

Please note that the latest test version (v4.2.0-test.1) does contain an update of the database library, which might fix your issue. I found the item below in the changelog:

Fixed an issue with PgConnection becoming unusable after hitting a database error in certain situations

1 Like

Thanks a lot for your reply.
Let me try again when v4.2 is official.

This reconnection is useful when the active database goes down and passive database takes over.
It may take 30s to fully recover database service.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.