[squid-users] squid workers question

[Matus UHLAR - fantomas]

>On 10/03/2017 3:21 a.m., Matus UHLAR - fantomas wrote:
>> I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie
>> version)

>> - does this version have known memory leaks?
>> http://www.squid-cache.org/Versions/v3/3.5/ChangeLog.txt
>> shows some leaks fixed but they all seem to be related to something we
>> don't
>> use (certificated, Surrogate capability), unless the:
>>
>> "Fix memory leak of HttpRequest objects" that is fixed in 3.5.16 applies
>> to 3.4 too.

On 10.03.17 05:00, Amos Jeffries wrote:
>IIRC that does, and there were some issues with CONNECT exceeding
>configured limits.
>
>The Bug 3553 issue
><http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-13903.patch>
>can also cause nasty issues on busy proxy as the cache disk overflows
>from too-slow purging.

seems that my memory problem is somehow related to 4g of "2K Buffers"
whatever that means. This is cachrmgr output:


		(bytes)	KB/ch	obj/ch	(#)	used	free	part	%Frag	(#)	(KB)	high (KB)	high (hrs)	%Tot	(#)	(KB)	high (KB)	high (hrs)	%alloc	(#)	(KB)	high (KB)	(#)		%cnt	%vol	(#)/sec
2K Buffer	2048								1986398	3972796	3972796		0.00		89.763	1986390	3972780	3972796		0.00		100.000	8	16	198		10736355	4.914	19.208	0.009


>> cache_dir rock /var/spool/squid3/rock 1024 max-size=32768
>> #cache_dir aufs /var/spool/squid3 8192 16 256 min-size=32769
>>
>> are those correct values? (bug 3411 says something about 256B metadata)

>Those 256 Byte will matter for Squid-3.4.

doesn't it for later squid versions?

>It may be worthwhile adjusting for anyway.

changed to:

#cache_dir rock /var/spool/squid3/rock 1024 max-size=32512
#cache_dir aufs /var/spool/squid3 4096 16 256 min-size=32513


>> After first start I noticed crash:
>>
>> 2017/03/02 18:32:18 kid3| Max Mem  size: 262144 KB [shared]
>> 2017/03/02 18:32:18 kid2| Max Mem  size: 262144 KB [shared]
>> 2017/03/02 18:32:18 kid3| Max Swap size: 0 KB
>> 2017/03/02 18:32:18 kid1| WARNING: disk-cache maximum object size is too
>> large for mem-cache: 16384.00 KB > 32.00 KB
>> 2017/03/02 18:32:18 kid2| Max Swap size: 1048576 KB
>> 2017/03/02 18:32:18 kid3| Using Least Load store dir selection
>> 2017/03/02 18:32:18 kid3| Set Current Directory to /var/spool/squid3
>> FATAL: Ipc::Mem::Segment::open failed to shm_open(/squid-cache_mem.shm):
>> (2) No such file or directory
>>
>> Squid Cache (Version 3.4.8): Terminated abnormally.
>> FATAL: Ipc::Mem::Segment::open failed to
>> shm_open(/squid-var.spool.squid3.rock.shm): (2) No such file or directory
>>
>> Squid Cache (Version 3.4.8): Terminated abnormally.
>>
>>
>> ... this happened in http://bugs.squid-cache.org/show_bug.cgi?id=3411
>> however that
>> - restart with "workers 1" worked, but isn't that the default?
>
>Maybe. There is SMP and no SMP at all - both have 1 worker. It is
>unclear to me which is the default and whether "workers 1" switches to
>the other or not.
>
>
>>   or was the creash caused by something else?
>> (will try to replicate)
>
>In my experience that "No such X" messages on the SHM usually means
>/dev/shm is not mounted.

I believe it was all the time.

-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I don't have lysdexia. The Dog wouldn't allow that.