The following issue requires your FEEDBACK. ====================================================================== 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: feedback ====================================================================== Date Submitted: 2014-04-11 23:13 CEST Last Modified: 2014-12-11 11:19 CET ====================================================================== 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. ====================================================================== ---------------------------------------------------------------------- (0010996) dam (administrator) - 2014-12-11 11:19 https://www.opencsw.org/mantis/view.php?id=5163#c10996 ---------------------------------------------------------------------- Meanwhile I released 3.4.10 and adjusted some build flags as reported in another bug, can you please retry and see if the error is still present?