Add better internet/database connection warning #2

New Issue

oysteikt · 2023-05-31T17:51:12+02:00

h7x4 commented

2023-05-31 17:51:12 +02:00

(Migrated from github.com)

Sometimes, dibbler is not able to communicate with the database. There has been different reasons for this. It would be nice if the program could try to determine which of these scenarios are the most likely, and report a human readable error instead of printing a long stack trace.

One way of doing this would be to check the database connection (implicit failure, since it probably triggered this check), in addition to pinging 2 machines, one being the database host. This would allow us to guess whether only the database service is down, the whole database host, or whether it's a network problem. But there might be more reliable ways to do this.

Sometimes, dibbler is not able to communicate with the database. There has been different reasons for this. It would be nice if the program could try to determine which of these scenarios are the most likely, and report a human readable error instead of printing a long stack trace. One way of doing this would be to check the database connection (implicit failure, since it probably triggered this check), in addition to pinging 2 machines, one being the database host. This would allow us to guess whether only the database service is down, the whole database host, or whether it's a network problem. But there might be more reliable ways to do this.

oysteikt added the

feature request

label 2024-07-28 15:41:23 +02:00

Sign in to join this conversation.