Squid not working, 2.3.2 on APU2
-
Hi
I've installed a new APU2 board with 16GB SSD from scratch with 2.3.2
Installed the squid package with squidguard and snort.RAM Disk to save the SSD from unnecessary write ops.
/tmp 64 MB
/var 512MBSnort is currently stopped, because it adds a lot of http request from internal to external to the blocked hosts. we can ignore snort :-)
Problem is, that i get a lot of squid errors when i have AV enabled. ICAP protocol error.
attached are the config files, generated by default settings in the web gui and access.log
thanks for your support
files.zip -
hi
the error just happens with AV Enabled. It seems to be a c-icap issue. the service is not responding most of the time. that means i get an squid error page with the url and can click there in it multiple times. and then sometimes it works for few minutes.
i checked the access logs from squid and c-icap, without any findings.
also tried to test c-icap with that http://c-icap.sourceforge.net/install.html
-
An APU2 may not have enough horsepower (CPU/RAM/etc) to run AV in squid, especially not with a huge chunk of the RAM taken by RAM disks.
It is quite a resource hog.
-
An APU2 may not have enough horsepower (CPU/RAM/etc) to run AV in squid, especially not with a huge chunk of the RAM taken by RAM disks.
It is quite a resource hog.
Quad Core 1Ghz with 4 GB RAM with usage about 30% event with RAMDISK…. and you tell me not enough ressources for one user with 1 page load per minute :-)
this is not a performance issue... clamav should brake down the squid performance, but not bring an error in milliseconds... this is no timeout or performance issue.
check that forum... a lot of squid and c-icap erros. and eicar downloads which are not regognized.
-
The OS and your RAM disks eat a large chunk of that RAM, and clamav wants a huge chunk for itself just running daemonized. Yes, it's quite possible you don't have enough to do what you're attempting to do, even if you feel you have enough.
It's still possible you have some other issue present in clamav/squid, but you can't ignore the things you've changed as well.
It's also quite possible clamav will not work properly with /tmp or /var in RAM, period.
That would be the first thing I'd disable.
-
Hi
I'm using a 16GB SSD and im concerned about the durability, when i don't use RAM disk to limit writes to the disk. I run a freshclam before using clam or starting the deamons, and restarted clamav after the download of definition files, stored on a redirected mountpoint.
then started squid with c-icap.
thats the reason why I use Ramdrives, and i think a lot of users will do.
-
The squid cache is going to cause more writes than anything in /var or /tmp would, so it's a wash if you put the cache on your SSD. If you are worried about writes, get a higher quality SSD.
