Bug#932593:

The new location of the PID file needs to be added in the bundled apparmor profile. Without it starting the service will fail with something like this: -- AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/squid" name="/run/squid/squid.pid" pid=64342 comm="squid" requested_mask="c"

Bug#932593: Similar problem of Squid service failing to start at boot

Hello, I've encountered a similar problem : upgrading a Debian Stretch system with Squid package installed to Debian Buster version, the Squid service (in version 4.6-1+deb10u) doesn't start anymore at boot ! My system has a separate partition for /var, and Squid fails to start beca

Bug#932593: squid: started by systemd before local file systems are up and therefore fails

Hi, the error reappeared again - reinstallation of packages "systemd" and "squid" was futile. I modified "/lib/systemd/system/squid.service" even further without success: Requires=local-fs.target network.target network-online.target nss-lookup.target # Commented out: ExecStartPre=/usr/sbin/s

Bug#932593: squid: started by systemd before local file systems are up and therefore fails

Am 22.07.19 um 08:31 schrieb Amos Jeffries: On Sun, 21 Jul 2019 12:57:16 +0200 =?UTF-8?B?VGlsbWFubiBCw7bDnw==?= wrote: Hi, please close the bug report #932593. The problem disappeared after I manually reinstalled the packages systemd and squid („apt --reinstall install systemd squid“). It seems

Bug#932593: squid: started by systemd before local file systems are up and therefore fails

On Sun, 21 Jul 2019 12:57:16 +0200 =?UTF-8?B?VGlsbWFubiBCw7bDnw==?= wrote: > Hi, > > please close the bug report #932593. The problem disappeared after I > manually reinstalled the packages systemd and squid („apt --reinstall > install systemd squid“). It seems to me that release updates can con

Bug#932593: Acknowledgement (squid: Squid is started by systemd before local file systems are up and therefore fails)

Hi, please close the bug report #932593. The problem disappeared after I manually reinstalled the packages systemd and squid („apt --reinstall install systemd squid“). It seems to me that release updates can confuse systemd's startup logic - maybe a hint in the release notes to reinstall syst

Bug#932593: squid: Squid is started by systemd before local file systems are up and therefore fails

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)