|
Hey, There are couple things which are unclear about both the system you are running and the situation. In the post mentioned a CentOS 6.5 and SElinux policy for a specific thing. The specific policy in the post seems "sensible" but the default policy for squid in CentOS works fine as far as I can tell. It is mentioned that after installing squid 3.5.0 on CentOS this issue appeared. Since I am building the unofficial CentOS RPMs it's pretty simple for me to understand that there are scenarios which you would be better without SElinux or other restrictions or "binding" tools by the OS of the running process\software\script. Specifically the pid file is not related in any way to the SElinux mentioned in the blog post.. If you can post the content of the "te" file of the audit2allow result it would help to understand the issue better. Have you tried my RPMs? If something is missing in them let me know please. Eliezer On 11/04/2016 22:11, amadaan wrote:
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 |
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
