Investigate why server freezes when a connection to the db ever fails

(node:3870) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 10.0.0.4:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
(node:3870) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:3870) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Postgres.ts should probably have a try/catch.

Since it doesn’t crash, it doesn’t cause it to restart and it instead gets stuck in a broken state.

[HanabishiRecca]

In any case, I think the server should handle unexpected events. At least just restart. Like:

const panic = (e: Error) => {
    console.error(e);
    // Hope for the best
    process.exit(1);
};

process.on('uncaughtException', panic);
process.on('unhandledRejection', panic);

Of course there should be a service/script that watches the process and restarts it.

[HanabishiRecca]

Hard to say what is happening without a more detailed stack trace. Are you sure that the rejection happens exactly here?