A NOTE has been added to this issue. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5163 ====================================================================== Reported By: hudesd Assigned To: dam ====================================================================== Project: squid Issue ID: 5163 Category: regular use Reproducibility: have not tried Severity: crash Priority: normal Status: confirmed ====================================================================== Date Submitted: 2014-04-11 23:13 CEST Last Modified: 2014-05-23 15:30 CEST ====================================================================== Summary: squid 3.4.4 crashes on Solaris 10 Description: I have been using Squid 3.1 for quite awhile with no problem. I recently upgraded all my CSW packages and Squid 3.4.4 came with it, no option otherwise it's in stable/unstable/testing. The problem is that it is NOT stable: it exits after awhile. It's running as a service (cswsquid) as per the package. This on a T2000 Solaris 10 148888-05 with 8GB RAM and about 600GB of available disk space . I had made no change to the configuration between 3.1 and 3.4. I subsequently have tried both aufs and my original ufs (diskd isn't available) to no avail. I increased the size of the disk and memory cache to no avail. Squid will run happily as long as users are only tunneling through it; once some caching gets going with regular http it exits.
I'm not finding any core dumps in /var/opt/csw/squid/cache or the 00 directory under that. I can provide squid config files and log files. ====================================================================== ---------------------------------------------------------------------- (0010839) hudesd (reporter) - 2014-05-23 15:30 https://www.opencsw.org/mantis/view.php?id=5163#c10839 ---------------------------------------------------------------------- I found a problem. The configuration file from 3.1 had been overwrittn by the default 3.4 file. I had changed memory cache to 1G but not incread disk cache from default 100 16 256. I thought that was 100*16*256 but I reread docs and found it is 100M. So memory cache presumably fills. But it is bigger than disk cache so it can't swap all out. So it exits, silently. When I tried similar on squid 3.1 as delivered with Solaris 11.1, squid complained about the configuration and refused to start (appropriate behavior). Changing the disk cache to 1024 16 256 resolved that issue but squid 3.4 should complain just as 3.1 did not gamely try to work then fail. I'll see about 3.4.5 on a test machine.
