Thank you and joseph for providing these important details. If we can reproduce the problem, then we will post a pull request with a fix once it is is available. If we cannot, we will post more questions here (unless there is a report in Squid Bugzilla by then). --Alex. On 02/20/2018 04:57 PM, Yuri wrote: > It's immediately lost swap.state contents after any restart and starts > up with empty swap.state. > > After removal of swap.state with stopped squid, it's correctly > re-indexing cache contents and then run normally. > > > 21.02.2018 05:50, Yuri пишет: >> # ------------------------------------- >> # Store parameters >> # ------------------------------------- >> minimum_object_size 10 bytes >> maximum_object_size 4 GB >> >> cache_dir aufs /data/cache/d1 48000 64 512 >> cache_dir aufs /data/cache/d2 48000 64 512 >> cache_dir aufs /data/cache/d3 48000 64 512 >> cache_dir aufs /data/cache/d4 48000 64 512 >> >> # ------------------------------------- >> # Memory parameters >> # ------------------------------------- >> cache_mem 512 MB >> >> memory_pools off >> #memory_pools_limit 1024 MB >> >> maximum_object_size_in_memory 1 MB >> >> >> 21.02.2018 05:48, Alex Rousskov пишет: >>> On 02/20/2018 04:38 PM, joseph wrote: >>>> alex tested on 2 environment debian 9 and solariss >>>> same shame just keep for 30 minute running caching and do squid restart and >>>> chek your swap.state you will notice its empty almost on 2 environment >>>> totally different ok >>>> i removed that patch and all fine swap.state stay perfect and all fine >>>> so i guess one of the 2 scenario its detecting swap file on start never >>>> exist or detecting wrong size that all >>> Thank you for providing these additional snippets of information. We >>> will, of course, try to reproduce the problem with the info you have >>> already provided. If you would like to increase our chances of >>> reproducing this problem, please see my original response (quoted below). >>> >>> Alex. >>> >>> >>>> On 02/20/2018 04:28 PM, Alex Rousskov wrote: >>>>> ... Please share your Squid >>>>> configuration (at least the SMP-, cache_mem-, and cache_dir-related >>>>> directives). You may want to file a bug report to track this fix better. >>> _______________________________________________ >>> squid-users mailing list >>> squid-users@xxxxxxxxxxxxxxxxxxxxx >>> http://lists.squid-cache.org/listinfo/squid-users > > > > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users > _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
