On Thu, 16 Feb 2017 09:25:33 +0100 Andreas Rittershofer wrote: > Package: squid > Version: 3.5.23-1 > > * What led up to the situation? > > I tried to install squid via apt-get install squid > > The problem is here: > > > Feb 16 08:32:08 dx151 systemd[1]: Starting LSB: Squid HTTP Proxy > version 3.x... > Feb 16 08:32:08 dx151 squid[5885]: Starting Squid HTTP Proxy: squid > failed! > Feb 16 08:32:08 dx151 systemd[1]: squid.service: PID file > /var/run/squid.pid not readable (yet?) after start: No such file or > directory > Obviously the installer script tries to put the PID file in /var/run. > This can not work, because squid has no write access to /var/run which > is owned by root.root. Instead squid should put its PID file in > /var/run/squid which is owned by proxy.proxy.
Things are not quite that obvious unfortunately. systemd does not have all the facts, yet assumes that it does and thus produces incorrect info about the problem. Or rather it is telling you about a problem *it* has - which is merely a side effect of what is failing for Squid. The Squid PID file has always existed at that location and works fine. The real problem is elsewhere. > The error seems to be in multiple places, also in some autogenerated > systemd files for squid.service. There are at least three errors happening in a cascade. One is whatever stops Squid from starting correctly. The next is systemd cannot find Squid's PID file - (because Squid did not start). The third is that the way systemd is hacked into the LSB init system prevents it finding out and reporting the initial probem Squid is having. Please run "squid -k parse 2>&1" and provide the output. Also please mention if you had any other version of squid installed in the past, and which that was. Amos
