On 05/03/2017 10:21 PM, Nil Nik wrote: > Using Squid 3.5.23, After some time found squid dead with below errors. > Even i restart it doesn't start for some time (5-10 minutes). If your Squid started OK at some time and then, after working OK for a while, failed and could not be restarted after that a failure, then your restarting procedure is broken. There are Squid bugs that affect you, but if you fix the restarting procedure, you should be able to restart Squid despite those Squid bugs. Specifically, make sure that there are no Squid processes running when you start a new Squid process. Do not rely exclusively on PID file absence until that becomes safe (we are working on making it safe). Also, search the mailing list archive for ssl_session_cache.shm. You may find threads with other relevant advice. > Apr 28 16:16:18 mysystem (squid-1): Ipc::Mem::Segment::open failed to > shm_open(/squid-ssl_session_cache.shm): (2) No such file or directory This is a sign of OS misconfiguration (if Squid never works OK) or broken Squid [re]starting procedure (if Squid works OK but cannot be restarted after a failure). There are also Squid bugs that may affect you, including: * Race conditions related to shared memory segments maintenance. * Using a shared SSL session cache when none is needed. FWIW, Factory is actively working on fixing the former. > I was using squid 3.3.9 never observed such kind of issue. Older Squids did not use shared SSL session caches (or shared memory segments at all) and tolerated broken restart scripts better. We are working on restoring that robustness (to the extent possible). Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
