The situation is that I cannot continue testing it since there is a bug with the sibling proxies communication. The idea was to verify if it would be possible to let different instances communicate via htcp\icp as the "signaling" or "communication" channel instead of shared memory. Just to add that one of my current test labs of squid is a combination of:ġ haproxy as balancer(or a custom LB I wrote)Ģ+ squid instances with the proxy protocol enabled and each has it's own ufs\aufs cache_dir Various Buffer's, but some other things do as well. I would look at the next few entries to see if there is a good clueĪbout what system might be worth a closer look (largest amount of thingsĪctive, or anything else not being released). So anything that is using a generic 2KB of memory. (KB) high (KB) high (hrs) %alloc (#) (KB) high (KB)Īh. %Frag (#) (KB) high (KB) high (hrs) %Tot (#) Unclear to me which is the default and whether "workers 1" switches to There is SMP and no SMP at all - both have 1 worker. Seems that my memory problem is somehow related to 4g of "2K Buffers" IIRC that does, and there were some issues with CONNECT exceedingĬan also cause nasty issues on busy proxy as the cache disk overflows "Fix memory leak of HttpRequest objects" that is fixed in 3.5.16 applies Or was the creash caused by something else? restart with "workers 1" worked, but isn't that the default? Shm_open(/.shm): (2) No such file or directory Squid Cache (Version 3.4.8): Terminated abnormally. Store and kid3 is the single worker process?Ģ 18:32:18 kid3| Max Mem size: 262144 KB Ģ 18:32:18 kid2| Max Mem size: 262144 KB Ģ 18:32:18 kid1| WARNING: disk-cache maximum object size is too large for mem-cache: 16384.00 KB > 32.00 KBĢ 18:32:18 kid2| Max Swap size: 1048576 KBĢ 18:32:18 kid3| Using Least Load store dir selectionĢ 18:32:18 kid3| Set Current Directory to /var/spool/squid3įATAL: Ipc::Mem::Segment::open failed to shm_open(/squid-cache_mem.shm): (2) No such file or directory do I get it right that kid1 is the Master, kid2 is the disker for rock I configured rock store (for smaller files) and (later) standard aufs for others:Ĭache_dir rock /var/spool/squid3/rock 1024 max-size=32768 That is fixed in 3.5.16 applies to 3.4 too. Use (certificated, Surrogate capability), unless the: Shows some leaks fixed but they all seem to be related to something we don't does this version have known memory leaks? Real problem distribution isn't able to fix) (I know it's old, but I prefer using distribution-provided SW unless it has I have installed squid 3.4.8 on linux 3.16/64bit (debian 8 / jessie version)
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |