does not start on install / depends on squid which is squid3

Bug #1544719 reported by Scott Moser
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
squid-deb-proxy (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

on xenial:
 apt-get install squid-deb-proxy

then
# systemctl status squid-deb-proxy | cat
● squid-deb-proxy.service - LSB: Squid Deb Package HTTP Proxy
   Loaded: loaded (/etc/init.d/squid-deb-proxy; bad; vendor preset: enabled)
   Active: active (running) since Thu 2016-02-11 20:39:42 UTC; 17s ago
     Docs: man:systemd-sysv-generator(8)

Feb 11 20:39:42 squidtest systemd[1]: Starting LSB: Squid Deb Package HTTP Proxy...
Feb 11 20:39:42 squidtest systemd[1]: Started LSB: Squid Deb Package HTTP Proxy.
Feb 11 20:39:45 squidtest systemd[1]: Started LSB: Squid Deb Package HTTP Proxy.

# ps axw | grep squid
 2968 ? Ss 0:00 avahi-daemon: running [squidtest.local]
 3959 ? Ss 0:00 /usr/sbin/squid3 -YC -f /etc/squid3/squid.conf
 3961 ? S 0:00 (squid-1) -YC -f /etc/squid3/squid.conf
 3971 ? S 0:00 (logfile-daemon) /var/log/squid3/access.log
 6335 ? S+ 0:00 grep --color=auto squid

The only squid running is squid3.
The issue is jsut that squid-deb-proxy depends on 'squid'. and in xenial, 'squid' is squid3. Then the init script finds no DAEMON=/usr/sbin/squid and does nothing.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: squid-deb-proxy 0.8.14
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
Date: Thu Feb 11 20:34:39 2016
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
SourcePackage: squid-deb-proxy
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Scott Moser (smoser) wrote :
Changed in squid-deb-proxy (Ubuntu):
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Louis Bouchard (louis) wrote :
Revision history for this message
Louis Bouchard (louis) wrote :

Either I goofed with bzr or the patch has been applied backward :

# bzr diff -r-2..-1
=== modified file 'debian/changelog'
--- debian/changelog 2015-08-24 09:56:49 +0000
+++ debian/changelog 2016-01-29 16:56:25 +0000
@@ -1,3 +1,10 @@
+squid-deb-proxy (0.8.14) unstable; urgency=medium
+
+ * depend on squid3 instead of squid, thanks to
+ HIGUCHI Daisuke (VDR dai), closes: #813082
+
+ -- Michael Vogt <email address hidden> Fri, 29 Jan 2016 17:55:43 +0100
+
 squid-deb-proxy (0.8.13) unstable; urgency=medium

   * add README.md to squid-deb-proxy install, thanks to

=== modified file 'debian/control'
--- debian/control 2013-05-16 18:09:24 +0000
+++ debian/control 2016-01-29 16:56:25 +0000
@@ -15,7 +15,7 @@
 Architecture: all
 Depends: ${python:Depends},
          ${misc:Depends},
- squid3
+ squid
 Recommends: avahi-utils
 Description: Squid proxy configuration to optimize package downloads
  This package contains a Squid proxy configuration to manage a cache of

=== modified file 'debian/squid-deb-proxy.init'
--- debian/squid-deb-proxy.init 2013-12-19 08:28:46 +0000
+++ debian/squid-deb-proxy.init 2016-01-29 16:56:25 +0000
@@ -17,7 +17,7 @@

 NAME=squid-deb-proxy
 DESC="Squid Deb HTTP Proxy"
-DAEMON=/usr/sbin/squid3
+DAEMON=/usr/sbin/squid
 PIDFILE=/var/run/$NAME.pid
 CONFIG=/etc/squid-deb-proxy/squid-deb-proxy.conf
 SQUID_ARGS="-YC -f $CONFIG"

=== modified file 'debian/squid-deb-proxy.logrotate'
--- debian/squid-deb-proxy.logrotate 2012-04-18 13:58:46 +0000
+++ debian/squid-deb-proxy.logrotate 2016-01-29 16:56:25 +0000
@@ -12,8 +12,6 @@
  postrotate
   if [ -x /usr/sbin/squid ]; then
       SQUID=/usr/sbin/squid
- elif [ -x /usr/sbin/squid3 ]; then
- SQUID=/usr/sbin/squid3
   else
       echo "No squid binary found"
       exit 1

=== modified file 'debian/squid-deb-proxy.upstart'
--- debian/squid-deb-proxy.upstart 2014-03-19 13:46:32 +0000
+++ debian/squid-deb-proxy.upstart 2016-01-29 16:56:25 +0000
@@ -26,8 +26,6 @@
 script
   if [ -x /usr/sbin/squid ]; then
       SQUID=/usr/sbin/squid
- elif [ -x /usr/sbin/squid3 ]; then
- SQUID=/usr/sbin/squid3
   else
       echo "No squid binary found"
       exit 1

=== modified file 'init-common.sh'
--- init-common.sh 2014-12-17 12:27:25 +0000
+++ init-common.sh 2016-01-29 16:56:25 +0000
@@ -24,8 +24,6 @@
 pre_start() {
   if [ -x /usr/sbin/squid ]; then
       SQUID=/usr/sbin/squid
- elif [ -x /usr/sbin/squid3 ]; then
- SQUID=/usr/sbin/squid3
   else
       echo "No squid binary found"
       exit 1
@@ -84,7 +82,7 @@
   rm -f $AVAHIFILE
 }

-# from the squid3 debian init script
+# from the squid debian init script
 find_cache_dir () {
         w=" " # space tab
         res=`sed -ne '

=== modified file 'squid-deb-proxy.conf'
--- squid-deb-proxy.conf 2015-07-14 14:53:01 +0000
+++ squid-deb-proxy.conf 2016-01-29 16:56:25 +0000
@@ -93,5 +93,5 @@
 # And finally deny all other access to this proxy
 http_access deny all

-# we don't want to clash with the squid3 netdb state file
+# we don't want to clash with the squid netdb state file
 netdb_filename stdio:/var/log/squid-deb-proxy/netdb.state

Revision history for this message
Louis Bouchard (louis) wrote :

well, it's not applied backward, it's just that Debian uses squid & not squid3 as with Xenial. Maybe we should revert this patch

Revision history for this message
Stuart Bishop (stub) wrote :

@louis-bouchard yes, that patch does not work under Xenial.

Workaround is to manually replace all occurrences of /usr/sbin/squid with /usr/sbin/squid3 in /etc/init.d/squid-deb-proxy, /etc/init/squid-deb-proxy.conf and /usr/share/squid-deb-proxy/init-common.sh

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

This bug does not break the operating system, so it has not an importance of "critical".

Changed in squid-deb-proxy (Ubuntu):
importance: Critical → High
importance: High → Medium
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Moreover squid is not a core software, so this bug has not an importance of "high" either.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.