Squid c-icap exited on signal 11
-
When I enable the squid3-dev Antivirus Clamav anti-virus integration using c-icap and try to visit a web page i get the following error below
but when i disable the squid3-dev Antivirus Clamav anti-virus integration using c-icap I get no errors i can get to web pages does anyone know how to fix this thanks.ERROR
The requested URL could not be retrievedThe following error was encountered while trying to retrieve the URL: http://lists.pfsense.org/pipermail/list/2012-February/001340.html
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.
Mar 20 03:33:38 kernel: pid 36346 (c-icap), uid 9595: exited on signal 11
Mar 20 03:33:38 kernel: pid 43724 (c-icap), uid 9595: exited on signal 11
Mar 20 03:33:39 kernel: pid 43887 (c-icap), uid 9595: exited on signal 11
Mar 20 03:33:39 kernel: pid 32301 (c-icap), uid 9595: exited on signal 11
Mar 20 03:33:39 kernel: pid 32353 (c-icap), uid 9595: exited on signal 11 -
I could not get it working on amd64 version too.
Some users reports that it's working fine on i386 versions.
-
I could not get it working on amd64 version too.
Some users reports that it's working fine on i386 versions.
Hello marcelloc, I'm facing the same errors as Arist, any update if it will work any time soon on amd64 as well? The c-icap service is running, although Proxy server: Antivirus is unchecked.
It's really sad that we have all the RAM on amd64 systems but we can't use such useful feature there.
regards
-
It's really sad that we have all the RAM on amd64 systems but we can't use such useful feature there.
I second that but it's something I can't find time to check or fix.
-
Marcelloc you needto help on both..dansguardian package fixing with clamav functioning and squid 3.3.4 with clamav (squidclamav) on the amd64 platform your help is urgently needed as several of us have accidently upgraded the packages and are left with non functioning pfsense units.
-
It's really sad that we have all the RAM on amd64 systems but we can't use such useful feature there.
I second that but it's something I can't find time to check or fix.
Is there anything we can do, so you can free up a little time?
-
ICAP issue is real handicap, please take out sometime, as it is one of the vital missing link, otherwise a good firewall. Without antivirus at source, pushing it for production use is really not possible.
Help in this regard is needed, we require stable squid service with ssl (https filtering, its working but more stability is required )and antivirus.
-
I'ts related to freebsd, not package configuration.
You can help looking for workarounds searching on google.
http://lists.freebsd.org/pipermail/freebsd-ports/2014-February/090322.html
http://sourceforge.net/p/c-icap/discussion/420422/thread/1a2978aa/
http://bit.ly/1h6nxFAi386 version with same config files works, so in your production environment you can forward proxy requests to a i386 virtual machine with squid and icap.