Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
After upgrading to ^8.2.0 we are seing pool errors from knex
See original GitHub issueKnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Once we’ve downgraded to 8.1.0 - they are gone. I am not sure if these are related, but just letting you know.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (2 by maintainers)
Top Results From Across the Web
Knex: Timeout acquiring a connection. The pool is probably ...
Open file node_modules/knex/lib/client.js . You will see this method: async acquireConnection() { if (!this.pool) { throw new Error('Unable ...
Read more >Creating a scalable GraphQL API with MySQL, Node.js, and ...
Have a MySQL database? Learn how to create a usable, scalable GraphQL API using Apollo and Node that you can customize however you...
Read more >knex-generic-errors - npm
Following errors can be accessed through knex-generic-errors property Errors or after attaching to instance from Knex.Errors or knex instance ...
Read more >connect econnrefused 127.0.0.1:5432 at tcpconnectwrap ...
What I want to do, is pass a new postgres pool into the send message function down below, but every time that I...
Read more >Monthly Archive | SystemsDigest
4 Ways to Minimize Your Dependencies in Node.js. Aug 31, 2022 By Dmitry Kudryavtsev In AppSignal. We all know the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just a followup from my comment - I don’t have minimal repro steps, but I was able to fix the issue by downgrading node to 12.18.1. I was on 14.4.0 before that. I think the issue I was experiencing was the same as https://github.com/knex/knex/issues/3831
@flotwig Are you using Lambda functions at all? I am seeing the same issue there.