Database issues cause non-descriptive process exit codes

[deanpress]

Currently, the output of database issues is non-descriptive. If there's any type of issue with the database connection, you only get process.exit called with "1", pointing back to PostgresConnection.make() failing in packages/core-database-postgres/src/postgres-connection.ts.

There's no logging as to why the database connection fails, making it hard to find the source of the issue and fixing it.

A solution to database error logging during database set-up would be a great feature for developers.

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

[air1one]

Hey @deanpress can you give details on when you get this non-descriptive error ?

I myself got it when running functional tests with a wrong username/password for database. Then I tried running a relay with same wrong username/password, and I got a descriptive error 🤔
Is it the same for you ?

[deanpress]

@air1one I experienced it with incorrect postgres credentials, trying to connect to a non-existent db, or insufficient db read/write rights for the user. Basically anything that will disrupt the postgres connection.

Haven't tried it with a relay yet. Will try that and report back.

[air1one]

Yes what I mean is do you have these errors only when running tests ? Or also when launching a relay / forger.
Thanks.

[faustbrian]

Will be resolved in 3.0.

This issue has been closed. If you wish to re-open it please provide additional information.