squid-deb-proxy fails to resolve dns entry : needs to be restarted
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| squid-deb-proxy (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| Trusty |
Fix Released
|
Medium
|
Louis Bouchard | ||
Bug Description
[SRU justification]
In some race situation, squid-deb-proxy is unable to operate and needs to be restarted.
[Impact]
Requires manual intervention from system administrator to function correctly.
[Fix]
Change the "start on" upstart statement to match the one used by squid3
[Test Case]
See Original description.
[Regression]
None expected as the same statement is already in use in the squid3 package and in the upstream debian package.
[ORiginal description of the problem]
In some specific context that I currently cannot identify (i.e. happens everytime on my server but never in VMs), after a reboot, squid-deb-proxy fails to resolve DNS entries for URL that it needs to service. The problem seems systematic on the hardware that I have.
Release : Trusty (squid-
Test :
1) Reboot squid-deb-proxy server
2) From some client, issue :
$ telnet {squid-
GET http://
Trying 192.168.1.11...
Connected to avogadro.
Escape character is '^]'.
HTTP/1.1 503 Service Unavailable
Server: squid/3.3.8
Mime-Version: 1.0
Date: Tue, 19 May 2015 14:21:51 GMT
Content-Type: text/html
Content-Length: 3287
X-Squid-Error: ERR_DNS_FAIL 0
Vary: Accept-Language
Content-Language: en
X-Cache: MISS from squid-deb-proxy
X-Cache-Lookup: MISS from squid-deb-
Via: 1.1 squid-deb-proxy (squid/3.3.8)
Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://
<html><head>
<meta http-equiv=
<title>ERROR: The requested URL could not be retrieved</title>
<style type="text/
/*
Stylesheet for Squid Error pages
Adapted from design by Free CSS Templates
http://
Released for free under a Creative Commons Attribution 2.5 License
*/
...
<div id="content">
<p>The following error was encountered while trying to retrieve the URL: <a href="http://
<blockquote id="error">
<p><b>Unable to determine IP address from host name <q>fr.archive.
</blockquote>
<p>The DNS server returned:</p>
<blockquote id="data">
<pre>No DNS records</pre>
</blockquote>
<p>This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.</p>
<p>Your cache administrator is <a href="mailto:
<br>
Restarting the squid-deb-proxy service fixes the problem
| Changed in squid-deb-proxy (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in squid-deb-proxy (Ubuntu Trusty): | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Louis Bouchard (louis-bouchard) |
| description: | updated |
| tags: | added: sts |
| Louis Bouchard (louis) wrote | #1 |
| Louis Bouchard (louis) wrote | #4 |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in squid-deb-proxy (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Chris J Arges (arges) wrote Please test proposed package | #7 |
| Changed in squid-deb-proxy (Ubuntu Trusty): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed |
| tags: |
added: verification-done removed: verification-needed |
| Launchpad Janitor (janitor) wrote | #8 |
| Changed in squid-deb-proxy (Ubuntu Trusty): | |
| status: | Fix Committed → Fix Released |
| Chris J Arges (arges) wrote Update Released | #9 |
Using the same "start on " clause than for the squid3 job fixes the problem (start on runlevel ...) :
# squid-deb-proxy - a proxy for deb packages
#
description "squid-deb-proxy"
start on runlevel [2345]
stop on runlevel [!2345]
I am going to prepare a debdiff with that modification