Bug #8940: ICAP Inteface for Squid and ClamAV integration - service not starting - pfSense Packages - pfSense bugtracker

Actions

Copy link

Bug #8940

closed

ICAP Inteface for Squid and ClamAV integration - service not starting

Added by Marcel Beerli about 6 years ago. Updated about 6 years ago.

Status:

Duplicate

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

09/24/2018

Due date:

% Done:

Estimated time:

Plus Target Version:

Affected Version:

Affected Plus Version:

Affected Architecture:

Description

After the upgrade I had a crash report but it seemed to run. But on a new restart of the pcengines APU2 it would not start the service ICAP

when visiting for example: http://www.freebsd.org/doc/en/books/handbook/, I get the following.

The following error was encountered while trying to retrieve the URL: http://www.freebsd.org/doc/en/books/handbook/

ICAP protocol error.

The system returned: [No Error]

This means that some aspect of the ICAP communication failed.

Some possible problems are:

The ICAP server is not reachable.

An Illegal response was received from the ICAP server.

When editing the Squid Guard Proxy Filter I noticed that the settings after saving are not loaded.
Example: Target Rules List: "WhiteList !BlackList all"
when loading the list:
Common ACL - Target Rules List - does not load, it shows the WhileList as "----" and it should be preselected as "allow"

servicewatchdog_cron.php: Service Watchdog detected service c-icap stopped. Restarting c-icap (ICAP Inteface for Squid and ClamAV integration)

Packages:
squid: 0.4.44_2
squidGuard: 1.16.17_3