So I actually dig deeper into this issue and found stack traced error of squid: ERROR: Could not read pid file /var/run/squid.pid: (13) Permission denied Tried one of the responses from one of the forums. Saying the issue is with SELinux being enabled. I disabled that and it worked fine after that. But that means I am removing security from my system. Now this awesome blog tells me how to add policy rules to allow your new software to run when SELinux is enabled. http://sharadchhetri.com/2014/03/07/selinux-squid-service-failed-startrestart/ Quite helpful but not sure if that is real solution. Can any changes be done on squid end to ignore above steps . Any suggestions on this will be of help. Thanks -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/FATAL-Ipc-Mem-Segment-create-failed-to-shm-open-squid-cf-metadata-shm-13-Permission-denied-tp4677044p4677045.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
