Squid will not start on boot-up in transparent mode

[dmiller]

Squid will not start on boot-up in transparent mode. The service also stops when certain changes are made to the firewall. (Example: changing web-gui access from HTTP to HTTPS). I experienced the same problem onto different systems.

My quick fix for the boot-up was to add two lines before exit 0 in /etc/rc:

/usr/local/bin/beep.sh start 2>&1 >/dev/null
sleep 15
/usr/local/etc/rc.d/proxy_monitor.sh&
exit 0

If the service stops when firewall changes are made, I reapply my access control list, and SQUID starts working again. (Just starting the service from the gui seems to be hit and miss with respect to the access control rules actually working).

[dmiller]

@dmiller:

Squid will not start on boot-up in transparent mode. The service also stops when certain changes are made to the firewall. (Example: changing web-gui access from HTTP to HTTPS). I experienced the same problem onto different systems.

My quick fix for the boot-up was to add two lines before exit 0 in /etc/rc:

/usr/local/bin/beep.sh start 2>&1 >/dev/null
sleep 15
/usr/local/etc/rc.d/proxy_monitor.sh&
exit 0

If the service stops when firewall changes are made, I reapply my access control list, and SQUID starts working again. (Just starting the service from the gui seems to be hit and miss with respect to the access control rules actually working).

Looks like this is fixed with 1.01  :)

[trendchiller]

same problem here… but if there still remain some errors, just freshly reinstall 1.0.1 and then even more errors will be gone....

same problems have been here ;-)