After the last firmware upgrade for the control board, the Squid proxy (current version: 6.7-2) no longer starts. The cause of this error may be the config files, which are now autogenerated by the init script, so that I can no longer use the old config file. Now, /etc/squid/squid.conf looks like this:
http_port 3128
coredump_dir /tmp/squid
visible_hostname clusterbox
pinger_enable off
mime_table /etc/squid/mime.conf
Many things lack here, particularly the path to the logfile. In this case, Squid takes a default, which is wrong, as the corresponding folder simply does not exist:
2026/05/21 17:02:45| Logfile: opening log daemon:/var/logs/access.log
2026/05/21 17:02:45| Logfile Daemon: opening log /var/logs/access.log
2026/05/21 17:02:46| ERROR: logfileHandleWrite: daemon:/var/logs/access.log:
error writing ((32) Broken pipe)
2026/05/21 17:02:46| FATAL: I don't handle this error well!
Even a softlink from /var/log to /var/logs did not help. Neither can I make an entry in the central config file /etc/config/squid, as it’s simply ignored:
option access_log '/opt/squid/log/access.log'
I’ve also informed the Squid maintainers, but they say this is not a bug in Squid itself, but a “feature” in the particular build: Bug 5540 - Squid looks for log file in non-existing directory: /var/logs/access.log
So: Who can improve the Squid build and possibly the config file generation process?