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/squid --foreground -z # My swap dirs exist, therefore no need to check and re-create. Still Systemd insists to starts Squid before local file systems are mounted. The mount messages for local file systems appear in journalctl just after Squid's start failed finally. Why does Systemd ignore the After- and Require-Clauses set for Squid? Regards -- Tilmann Böß
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 to me that release updates can confuse systemd's startup logic - maybe a hint in the release notes to reinstall systemd after the upgrade might be helpful? IMO it would be better if we can resolve this without asking people to (re)install systemd manually. Were you running a different Squid-4 or a Squid-3 version before this issue came up? The issue appeared after the upgrade from Stretch to Buster. (Sorry i didn't mention that before.) Therefore the previous version of Squid must have been 3.5.23-5+deb9u1. Do you recall what version of systemd were you running before/after the issue? Last version in Stretch: 232-25+deb9u11 PS. Your local-fs.target suggestion was a good one even though it did not help here. I intend to take that upstream in the next few days. I assume the name and email used for this public report are appropriate for me to credit the change to you? Yes (too much honour for such a small thought …) Thanks -- Dr. Tilmann Böß
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 confuse > systemd's startup logic - maybe a hint in the release notes to reinstall > systemd after the upgrade might be helpful? > IMO it would be better if we can resolve this without asking people to (re)install systemd manually. Were you running a different Squid-4 or a Squid-3 version before this issue came up? Do you recall what version of systemd were you running before/after the issue? PS. Your local-fs.target suggestion was a good one even though it did not help here. I intend to take that upstream in the next few days. I assume the name and email used for this public report are appropriate for me to credit the change to you? AYJ
