The only related effect that tproxy has on this is that it gives the
process some additional rights it normally doesn't have. But I don't see
how this can cause it to not have permissions to open the pid file..
Is there perhaps a squid.pid file with bad permissions in the directory?
Or missing execute permission for the cache_effective_user on any of the
directories in the path? Or missing write permission on the logs
directory?
grep cache_effective_user squid.conf
ls -ld /usr
ls -ld /usr/local
ls -ld /usr/local/squid26s9TP
ls -ld /usr/local/squid26s9TP/var/
ls -ld /usr/local/squid26s9TP/var/logs/
ls -l /usr/local/squid26s9TP/var/logs/squid.pid
[root@sed-co squid26s9TP]# pwd
/usr/local/squid26s9TP
[root@sed-co squid26s9TP]# grep cache_effective_user etc/squid.conf
# TAG: cache_effective_user
# to UID to nobody. If you define cache_effective_user, but not
# cache_effective_user.
# cache_effective_user nobody
[root@sed-co squid26s9TP]# ls -ld /usr
drwxr-xr-x 16 root root 4096 Sep 25 11:09 /usr
[root@sed-co squid26s9TP]# ls -ld /usr/local
drwxr-xr-x 45 root root 4096 Feb 3 12:37 /usr/local
[root@sed-co squid26s9TP]# ls -ld /usr/local/squid26s9TP
drwxr-xr-x 9 root root 4096 Feb 5 23:43 /usr/local/squid26s9TP
[root@sed-co squid26s9TP]# ls -ld /usr/local/squid26s9TP/var/
drwxr-xr-x 4 nobody nobody 4096 Feb 3 12:40 /usr/local/squid26s9TP/var/
[root@sed-co squid26s9TP]# ls -ld /usr/local/squid26s9TP/var/logs/
drwxr-xr-x 2 nobody nobody 4096 Feb 5 23:48
/usr/local/squid26s9TP/var/logs/
[root@sed-co squid26s9TP]# ls -l /usr/local/squid26s9TP/var/logs/squid.pid
ls: /usr/local/squid26s9TP/var/logs/squid.pid: No such file or directory
[root@sed-co squid26s9TP]#
If /usr/local/squid26s9TP/var/logs is given a group writable permission or
if the PID file is given at /var/run which is owned by root:root then the
issue disappears.
-logu
