Stuck Connection to database
See original GitHub issueFailure Logs
$ lumber generate "<app-name>" --connection-url "<db-url> "ardyfeb@juabali.com" --token "<token>"
Connecting to your database
Context
- Lumber Package Version: 3.6.0
- Database Dialect: pg
- Database Version: 10.6
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Custom Processes stuck due to database connection pool issue
It's an indication that the database connections have run out. This usually only happens when a custom process or job is opening SQL...
Read more >Database connection status stuck as "Connecting" - Ignition
The status was stuck as connecting despite it being connected. Everything was working fine while “connecting.” Came in the next day and the ......
Read more >sql - Interview task, stuck on local database connection, need ...
I'm using .NET CORE Web App MVC and I believe it requires me to use a database but I would need to upload...
Read more >Dashboard stuck connecting to database #6637 - GitHub
For some reason, my database is stuck connecting. It keeps saying 'This may take a few minutes, but if your dashboard hasn't connected...
Read more >Unable to connect to a database, connection to a ... - IBM
When you are trying to connect to or activate a database, nothing happens. It seems like connection just hangs.
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 FreeTop 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
Top GitHub Comments
Hello guys, we have released a fix for this one, I linked it to this thread.
Can you confirm it is working now please ?
Hi @ardyfeb & @jean-tymate 👋
You’ll have to update lumber to the latest version that includes the fix mentioned by @SteveBunlon. (3.6.1+)
Since it should have been fixed, let me close the issue for now; feel free to re-open it if the problem persists.