Read ECONRESET AT TCP.onStream NodeJs
Hello,
I'm using railway to deploy my nodeJs api,
when i'm not using the api during few hours i see this message in the console ,
I don't know how to fix this problem ...
i add a screenshot of my database.js
Thank you π
24 Replies
Project ID:
727b055e-3bcf-4dee-88c9-e7f10645b1b5Project ID : 727b055e-3bcf-4dee-88c9-e7f10645b1b5
1. do not use nodemon on railway, remove nodemon from your start command immediately please
2. this has been fixed in the path by specifying pool.min = 0, but you've done that already
Oh ok, there is another alternativ ?
have you done #1 yet?
Not yet i'm not at home π₯²
nodemon was removed
is pool even a valid client config? i cant find anyting about it in their docs
I'll try to see if the error recurs without nodemon
how opposed would you be to moving over to knex
I don't know, I'll have to find out
the default pool min is zero according to the pooling library pg uses
ok I had put 0
yeah i know, but the pg docs doesnt say thats a valid config
doesnt matter though since the default is zero
but I thought I saw an example in the documentation ok thanks that's good to know lol
if there is an example, its not where it should be
https://node-postgres.com/apis/client#new-client
yes I saw it on this site
wanna try this instead?
require('pg').native;but the mistake I made happened a few hours later
Maybe I should wait before changing the code?
maybe
can we leave the ticket open until the error recurs or not?
of course
Than for your time π
*Thank
no problem
p.s. you can edit discord messages
yes lool