Le 08/09/2014 22:59, Dale Schroeder a écrit : > > On 09/08/2014 3:24 PM, Gilles Darold wrote: >> Le 08/09/2014 19:31, Dale Schroeder a écrit : >>> It looks like I have found the culprit, and it seems to be specific to >>> users of squidclamav, like me. If I comment the following lines in >>> squid.conf, then squid3 starts and restarts with no errors. >>> >>> icap_service service_req reqmod_precache bypass=1 >>> icap://127.0.0.1:1344/squidclamav >>> adaptation_access service_req allow all >>> icap_service service_resp respmod_precache bypass=1 >>> icap://127.0.0.1:1344/squidclamav >>> adaptation_access service_resp allow all >>> >>> So, there now appears to be a conflict of some sort between >>> squidclamav and squid3. I have tried with squidclamav versions 6.10 >>> and 6.11, having identical results. >>> >>> I've copied the squidclamav developer on this message to see if the >>> cause of the problem can be determined. Thanks. >>> >>> Dale >> Hi, >> >> I'm the maintainer of SquidClamav and I'm afraid that the culprit is not >> the one you are suspecting or at least it is not so obvious. >> >> I have a VM with squid3 3.3.8-1 and SquidClamav 6.11, I used it a few >> days ago to test icap service chaining with qlproxy. Everything works >> great, I'm able to watch a web TV stream scanned by clamd through >> SquidClamav. I have run logrotate and stop/start squid3 manually but I'm >> not able to reproduce your issue. >> >> There's some differences with your installation : >> >> * even if the base is a Debian jessie/sid this is an Ubuntu server >> distribution >> * I have not updated squid to 3.3.8-1.2 >> * I've run c-icap + squidclamav on an other server. >> >> Ok I know that's not really helpful. Let me install c-icap on the >> server with squidclamav. >> >> Done. Using c-icap 0.3.4 and SquidClamav 6.11 installed on the same >> server than squid doesn't change anything, I'm still able to watch the >> web TV. Of course when I stop squid3, the service is interrupted but >> after restarting squid I don't any segfault in the logs. >> >> So I hope you are agree that SquidClamav is not the culprit in your bug. >> >> What is your version of c-icap ? Note that if you are using c-icap >> 0.1.6, it will not works with SquidClamav. >> >> Let me known if/how I can help more. >> >> Regards, >> > Gilles, > > Thank you for replying. Obviously, you are correct in that c-icap is > also involved. Perhaps Jessie's versions of squid3 and c-icap do not > cooperate with each other. I cannot say, as there are no other > entries in the logs other than what I posted in my initial bug > report. Since the config lines I disabled were about squidclamav, I > made the deduction that it was the problem, and the assumption I made > may not be correct. The evidence you have provided is quite compelling. > > c-icap is version 0.3.4-1 > squid is version 3.3.8-1.2 > squidclamav is version 6.11 > > As Debian no longer has squidclamav in its repositories, it may be > difficult to find a solution, but I will add c-icap's maintainers to > this thread to see if any are willing to look at this for potential > conflicts. > > Thanks again. > > Dale Schroeder
Hum, if you use c-icap 0.3.4 I don't any reason of that failure. The only difference with my installation is that I use a self compiled version of c-icap and squidclamav. Can you tell me how I can install the c-icap 0.3.4-1 and squid 3.3.8-1.2 package ? Is there's a particular repo for those package ? I suppose that squidclamav is self compiled on the server. I will install a Debian with this configuration and make tests, that's more easy for me to do that. The longer here for me is to download the Debian iso as I have very low bandwidth. Regards, -- Gilles GPL tools at http://www.darold.net/ (squidclamav - sendmailanalyzer - ora2pg - modproxyhtml - pgCluu squidguardmgr - sysusage - squidanalyzer - pgbadger - pgformatter) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org