Story #1915
closed
expose connect_timeout and read_timeout via configuration
0%
Description
My pulp installation was having issues completing synchronization of certain external repos due to timeouts. Following discussions on this thread[0], I found that I was able to resolve this timeout by increasing the values found in /usr/lib/python2.6/site-packages/nectar/config.py:22.
I'm hoping that these timeout values can be made available from a configuration file.
My patch diff (rpm python-nectar-1.5.1-1.el6.noarch):
22c22
< connect_timeout=9.05, read_timeout=57, working_dir="/tmp"):
---
> connect_timeout=6.05, read_timeout=27, working_dir="/tmp"):
[0] https://groups.google.com/forum/#!topic/foreman-users/J8xvzGHbz9w
Files
Updated by dkliban@redhat.com almost 8 years ago
- Tracker changed from Issue to Story
- Groomed set to No
- Sprint Candidate set to No
Updated by bmbouter about 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter about 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Updated by smithwig almost 5 years ago
- File clipboard-201904261722-08kj4.png clipboard-201904261722-08kj4.png added
- File clipboard-201904261723-mvpcv.png clipboard-201904261723-mvpcv.png added
Updated by Anonymous over 4 years ago
- File clipboard-201910101414-c0r2h.png clipboard-201910101414-c0r2h.png added
- File clipboard-201910101415-7nl5a.png clipboard-201910101415-7nl5a.png added
Updated by Anonymous almost 4 years ago
Nice information I have solved my problem [[Bollyquick]]
.
