[squid-users] Permission denied on /usr/share/squid/errors/templates and /usr/share/squid/icons/silk
Amos Jeffries
squid3 at treenet.co.nz
Fri Apr 12 15:34:13 UTC 2019
On 11/04/19 6:38 pm, Ota Coder wrote:
> Hi!
>
> I'm on Slackware 14.2 and installed Squid version 3.5.26 but I'm having
> this problem everytime I ran in the terminal:
>
> # squid -z
> # squid -N -D -d1
>
> and check the /var/log/squid/cache.log
>
> Most of the errors shown is "(13) Permission denied" on the files at
> folders /usr/share/squid/errors/templates/ and usr/share/squid/icons/silk/
>
> Here's an excerpt:
>
> 2019/04/11 14:04:22|
> '/usr/share/squid/errors/templates/ERR_ACCESS_DENIED': (13) Permission
> denied
> 2019/04/11 14:04:22| WARNING: failed to find or read error text file
> ERR_ACCESS_DENIED
...
> Here is the complete output in the cache.log - http://termbin.com/apfa
>
> I typed in lsattr -R on /usr/share/squid and this is the result -
> http://termbin.com/k37c
>
> I checked the permissions and owner at
> /usr/share/squid/errors/templates/ and it is correct -
> http://termbin.com/jo0e
IIRC; Squid also needs read access to all directories along in the path.
If you are manually setting permissions that may have been overlooked.
Also, check if there is anything like SELinux or AppArmor running on the
machine. They can prevent access to files despite what the Unix
permissions say.
>
> The cache_effective_user in /etc/squid/squid.conf is "squid" and the
> cache_effective_group is "squid"
>
> I mostly followed the settings written in this post -
> https://www.linuxquestions.org/questions/blog/arniekat-436077/slackware-14-1-squid-3-4-7-36215/
>
> But yeah, when I ran:
>
> # squid -N -D -d1
>
> squid really doesn't start when I checked when I ran:
According to your cache.log Squid exited due to inability to write to
the access.log files:
2019/04/11 14:04:30| logfileHandleWrite:
daemon:/var/log/squid/access.log: error writing ((32) Broken pipe)
Amos
More information about the squid-users
mailing list