Package: squid
Version: 4.6-1
Severity: normal

Dear Maintainer,

Squid reproducibly fails to start in system boot. Systemd calls Squid before 
local file systems are up. Therefore Squid
does not find its cache directory under "/srv". Boot messages:

[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Started Helper to synchronize boot up for ifupdown.
[  OK  ] Started udev Kernel Device Manager.
         Starting Network Service...
         Starting Squid Web Proxy Server...
[  OK  ] Started Network Service.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Found device /dev/mmcblk0p3.
[  OK  ] Found device /dev/mmcblk0p1.
[  OK  ] Found device Samsung_SSD_850_EVO_500GB HDD-srv.
[  OK  ] Found device Samsung_SSD_850_EVO_500GB HDD-export.
[  OK  ] Found device Samsung_SSD_850_EVO_500GB HDD-Swap.
[  OK  ] Reached target Sound Card.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
         Activating swap /dev/disk/by-label/HDD-Swap...
         Starting File System Check…ev/disk/by-label/HDD-export...
         Starting File System Check… /dev/disk/by-label/HDD-srv...
         Starting File System Check on /dev/mmcblk0p1...
         Starting File System Check on /dev/mmcblk0p3...
[  OK  ] Activated swap /dev/disk/by-label/HDD-Swap.
[FAILED] Failed to start Squid Web Proxy Server.
See 'systemctl status squid.service' for details.
[  OK  ] Started File System Check …/dev/disk/by-label/HDD-export.
[  OK  ] Started File System Check on /dev/mmcblk0p1.
[  OK  ] Started File System Check on /dev/mmcblk0p3.
[  OK  ] Started File System Check on /dev/disk/by-label/HDD-srv.
         Mounting /srv...
[  OK  ] Started File System Check Daemon to report status.

Re-installation of Squid didn't help.
I added "local-fs.target" to the squid system unit file (After-clause) without 
success.
After my system is completely up, Squid can be started successfully and is 
working as expected.
I removed "/etc/init.d/squid" without any effect (Squid does not start in boot 
and can be started
manually afterwards).
Other services that depend upon local filesystems and networking (e.g. Samba, 
NFSv4) are started after
the service they depend upon are ready.


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.19.0-5-armmp-lpae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages squid depends on:
ii  adduser                  3.118
ii  libc6                    2.28-10
ii  libcap2                  1:2.25-2
ii  libcom-err2              1.44.5-1
ii  libdb5.3                 5.3.28+dfsg1-0.5
ii  libdbi-perl              1.642-1+b1
ii  libecap3                 1.0.1-3.2
ii  libexpat1                2.2.6-2
ii  libgcc1                  1:8.3.0-6
ii  libgnutls30              3.6.7-4
ii  libgssapi-krb5-2         1.17-3
ii  libkrb5-3                1.17-3
ii  libldap-2.4-2            2.4.47+dfsg-3
ii  libltdl7                 2.4.6-9
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnettle6               3.4.1-1
ii  libpam0g                 1.3.1-5
ii  libsasl2-2               2.1.27+dfsg-1
ii  libstdc++6               8.3.0-6
ii  libxml2                  2.9.4+dfsg1-7+b3
ii  logrotate                3.14.0-4
ii  lsb-base                 10.2019051400
ii  netbase                  5.6
ii  squid-common             4.6-1

Versions of packages squid recommends:
ii  ca-certificates  20190110
ii  libcap2-bin      1:2.25-2

Versions of packages squid suggests:
ii  resolvconf   1.79
ii  smbclient    2:4.9.5+dfsg-5
ii  squid-cgi    4.6-1
pn  squid-purge  <none>
pn  squidclient  <none>
pn  ufw          <none>
pn  winbind      <none>

-- Configuration Files:
/etc/init.d/squid [Errno 2] No such file or directory: '/etc/init.d/squid'
/etc/squid/squid.conf changed [not included]

-- no debconf information

Regards,

Tilmann Boess

Reply via email to