Bug #24220
closed
In development: ActiveRecord::ConnectionTimeoutError in the logs..Recovers after a few attempts..
Added by Samir Jha almost 6 years ago.
Updated almost 6 years ago.
Category:
Development tools
|
|
Description
Get this error in the logs and the server takes some time to load since all connections are busy at the moment. ActiveRecord::ConnectionTimeoutError (could not obtain a connection from the pool within 5.000 seconds (waited 5.000 seconds); all pooled connections were in use)
- Project changed from Katello to foreman-tasks
- Subject changed from ActiveRecord::ConnectionTimeoutError in the logs..Recovers after a few attempts.. to In development: ActiveRecord::ConnectionTimeoutError in the logs..Recovers after a few attempts..
- Category deleted (
81)
We've seen this a lot in katello, but it seems to only occur when the dynflow world gets initialized.
- Project changed from foreman-tasks to Foreman
I don't think it has anything to do with Foreman-Tasks, it seems that in rails 5, the lock on 1-request at a time was removed, which leads to the dashboard spinning up more concurrent requests that the db pool is ready for. The proper fix should be to increase the db pool in `config/database.yml`.
- Status changed from New to Ready For Testing
- Assignee set to Ivan Necas
- Pull request https://github.com/theforeman/foreman/pull/5827 added
- Pull request https://github.com/theforeman/puppet-katello_devel/pull/165 added
I've sent patches to foreman and katello_devel to increase the pool size with numbers I've stopped getting the issues like this.
- Target version set to 1.19.0
- Fixed in Releases 1.19.0 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Pull request https://github.com/theforeman/foreman/pull/5822 added
- Category set to Development tools
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by