ECONNRESET when user returns after one day

[Alwinator]

MikroORM works perfectly. However, when nobody requests data from the database for 24 hours, the first request fails with the following exception. When retrying the exact same query, it works. Is it maybe something such as an "energy saving mode". How can I prevent it?

2022-05-23T10:39:54.812899274Z DriverException: select "u0".* from "user" as "u0" where "u0"."id" = 1 limit 1 - read ECONNRESET
2022-05-23T10:39:54.812926514Z     at PostgreSqlExceptionConverter.convertException (/app/node_modules/@mikro-orm/core/platforms/ExceptionConverter.js:8:16)
2022-05-23T10:39:54.812949292Z     at PostgreSqlExceptionConverter.convertException (/app/node_modules/@mikro-orm/postgresql/PostgreSqlExceptionConverter.js:42:22)
2022-05-23T10:39:54.813011180Z     at PostgreSqlDriver.convertException (/app/node_modules/@mikro-orm/core/drivers/DatabaseDriver.js:173:54)
2022-05-23T10:39:54.813033587Z     at /app/node_modules/@mikro-orm/core/drivers/DatabaseDriver.js:177:24
2022-05-23T10:39:54.813053957Z     at runMicrotasks (<anonymous>)
2022-05-23T10:39:54.813074013Z     at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-05-23T10:39:54.813093716Z     at async PostgreSqlDriver.find (/app/node_modules/@mikro-orm/knex/AbstractSqlDriver.js:46:24)
2022-05-23T10:39:54.813113068Z     at async PostgreSqlDriver.findOne (/app/node_modules/@mikro-orm/knex/AbstractSqlDriver.js:64:21)
2022-05-23T10:39:54.813132309Z     at async SqlEntityManager.findOne (/app/node_modules/@mikro-orm/core/EntityManager.js:298:22)
2022-05-23T10:39:54.813151697Z     at async SqlEntityManager.findOneOrFail (/app/node_modules/@mikro-orm/core/EntityManager.js:321:24)
2022-05-23T10:39:54.813170957Z 
2022-05-23T10:39:54.813189271Z previous Error: read ECONNRESET
2022-05-23T10:39:54.813207975Z     at TCP.onStreamRead (node:internal/stream_base_commons:211:20)
2022-05-23T10:39:54.813226882Z     at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
2022-05-23T10:39:55.020396756Z Connection Error: Connection ended unexpectedly

[B4nan]

Where do you host your app?

[chriscarpenter12]

Since seeing this issue days ago I added this to my config and I haven't seen the issue occur again.

    pool: {
      min: 1,
      max: 10,
    },
    driverOptions: {
      keepAlive: true,
      connectionTimeoutMillis: 10000,
    },

[Guergeiro]

Unfortunately, the solution provided by @chriscarpenter12 didn't work in my case.

[itxtoledo]

I have this same problem using mysql, all my services is under docker

[B4nan]

FWIW, keepAlive and connectionTimeoutMillis are both supposed to be nested under connection object, as with driverOptions you are overriding the whole options object of knex, not just the connection part.

driverOptions: {
-  keepAlive: true,
-  connectionTimeoutMillis: 10000,
+  connection: {
+    keepAlive: true,
+    connectionTimeoutMillis: 10000,
+  },
},

And more importantly, those are postgres dialect options, mysql2 has a different one called enableKeepAlive (not sure if there is an equivalent for connectionTimeoutMillis).

(no idea if that hels with the actual problem)

[WhereJuly]

@Guergeiro, @Alwinator Hi guys,

I run Postgres in a Docker container behind Traefik on some generic cloud VPS and experienced the same behaviour: system returned ECONNRESET with connection reset by peer reason afer the system had been left idle for a dosen minutes or so.

The driverOptions.connection.keepAlive=true did not make any difference. connectionTimeoutMills is probably not what would work accoring to the docs.

I checked the tcp_keepalives_idle on my postgres server container and saw it was 7200. I changed it to 300 via command: ["postgres", "-c", "tcp_keepalives_idle=300"] in my Swarm compose file and the issue looks like gone.