c-icap for Squid 5.1 on 2.4.4 Developer not starting
Verified his fix works:
Googling, you'd find this: https://sourceforge.net/p/c-icap/mailman/message/36379708/
It seems, on 0.5.x, ListenAddress has been removed in favor of the Port statement.
To fix C-ICAP, you must:
Remove ListenAddress 127.0.0.1 statement on line 134 of c-icap.conf
Replace Port 1344 statement on line 142 of c-icap.conf with Port 127.0.0.1:1344
To prevent pfSense from overwriting, chmod -w that file to prevent writes to it.
Hopefully this helps someone. :)
#2 Updated by Jim Pingle 12 months ago
- Project changed from pfSense to pfSense Packages
- Category set to Squid
#5 Updated by Jim Pingle 11 months ago
This is a problem in the FreeBSD c-icap port. The port itself contains a patch that adds the ListenAddress line.
#6 Updated by Steve Wheeler 11 months ago
the guy from the mailing list is me.
The "Listen" directive was removed from 0.4 to 0.5.
Upstream port should be fine.
We also had the same problem and switched in templating1. No idea how you guys at pfsense do this.
Hope this helps you to fix it.
#9 Updated by Jim Pingle 11 months ago
The upstream port is not fine. See the file I linked. The FreeBSD port is explicitly adding the ListenAddress directive to the default c-icap.conf which is deprecated.
We can certainly fix it by altering the c-icap config, sure, but the FreeBSD port would still have a broken default config. I'd like to see a fix upstreamed no matter what we choose to do here.