What is the problem with crashing an application on node.js?

Question

JavaScript

Actually, the application works, no crashes, no requests to the server, and I see a crash in a couple of days:

events.js:160
      throw er; // Unhandled 'error' event
      ^
Error: Connection lost: The server closed the connection.
    at Protocol.end (/srv/arcoin/node_modules/mysql/lib/protocol/Protocol.js:109:13)
    at Socket.<anonymous> (/srv/arcoin/node_modules/mysql/lib/Connection.js:115:28)
    at emitNone (events.js:91:20)
    at Socket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

What is the problem?

Answer 1

IMHO you just have code without try catch and the error occurs where no one is reported about it. And the module stack falls out, which already works with an error ....
In general, there is a feeling that the database server has a connection lifetime, and you keep your connection forever. Also https://dev.mysql.com/doc/refman/5.7/en/error-lost
...