squid-deb-proxy fails to resolve dns entry : needs to be restarted
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | squid-deb-proxy (Ubuntu) |
Medium
|
Unassigned | ||
| | Trusty |
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 |
As it turns out, mvo has just uploaded the fix along with some other bug fix for this bug : http://
| Launchpad Janitor (janitor) wrote : | #5 |
This bug was fixed in the package squid-deb-proxy - 0.8.11
---------------
squid-deb-proxy (0.8.11) unstable; urgency=low
[ Vagrant Cascadian ]
* add /etc/resolvconf
[ Robie Basak ]
* Simplify upstart "start on" to match squid3, to fix runlevel
transition problem (LP: #1456662)
-- Michael Vogt <email address hidden> Wed, 27 May 2015 09:12:49 +0200
| Changed in squid-deb-proxy (Ubuntu): | |
| status: | Confirmed → Fix Released |
Hello Louis, or anyone else affected,
Accepted squid-deb-proxy into trusty-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-
Further information regarding the verification process can be found at https:/
| 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 |
This bug was fixed in the package squid-deb-proxy - 0.8.6ubuntu1
---------------
squid-deb-proxy (0.8.6ubuntu1) trusty-proposed; urgency=medium
[ Vagrant Cascadian ]
* add /etc/resolvconf
[ Robie Basak ]
* Simplify upstart "start on" to match squid3, to fix runlevel
transition problem (LP: #1456662)
-- Louis Bouchard <email address hidden> Tue, 02 Jun 2015 11:24:16 +0200
| Changed in squid-deb-proxy (Ubuntu Trusty): | |
| status: | Fix Committed → Fix Released |
| Chris J Arges (arges) wrote : Update Released | #9 |
The verification of the Stable Release Update for squid-deb-proxy has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
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