cURL caching prevents landscape-broker from working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Medium
|
Kevin McDermott | ||
landscape-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Apparently cURL might be caching failures to resolve DNS for way too long. When looking at my broker logs, I saw the following message repeated many many times:
2010-02-16 09:39:51,198 ERROR [Dummy-1 ] Error contacting the server at https:/
Traceback (most recent call last):
File "/usr/lib/
curly, data = self._curl(
File "/usr/lib/
headers=
File "/usr/lib/
raise PyCurlError(
PyCurlError: Error 6: Couldn't resolve host 'staging.
It's unclear if that's actually related to DNS caching, but it's the best guess so far.
The message below explains the different options for DNS caching, straight from the author:
Related branches
- Free Ekanayaka (community): Approve
- Sidnei da Silva (community): Approve
-
Diff: 84 lines (+15/-7)2 files modifiedlandscape/lib/fetch.py (+1/-0)
landscape/lib/tests/test_fetch.py (+14/-7)
Changed in landscape-client: | |
status: | In Progress → Fix Committed |
tags: | added: testing |
tags: | added: needs-testing |
tags: | removed: testing |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
tags: | removed: verification-needed |
http:// curl.haxx. se/mail/ lib-2002- 01/0076. html
curl_ easy_setopt( handle, CURLOPT_ DNS_CACHE_ TIMEOUT, 15);
With two special cases, 0 and -1... O will completely disable dns
caching and -1 will make it so that the DNS cache *never* expires.