[squid-users] building squid 4 terminates with fatal error but doesnt say the error

[Amos Jeffries]

On 26/11/19 1:55 pm, robert k Wild wrote:
> hi all,
> 
> im building squid 4 by following this guide -
> 
> https://wiki.squid-cache.org/ConfigExamples/Intercept/SslBumpExplicit
> 
> and when i try to run it, i get this error -
> 
> [root at squid ~]# /usr/local/squid/sbin/squid -NCd1
> 2019/11/26 00:43:59| Created PID file (/usr/local/squid/var/run/squid.pid)
> 2019/11/26 00:43:59| Set Current Directory to
> /usr/local/squid/var/cache/squid
> 2019/11/26 00:43:59| Starting Squid Cache version 4.9 for
> x86_64-pc-linux-gnu...
> 2019/11/26 00:43:59| Service Name: squid
> 2019/11/26 00:43:59| Process ID 1774
> 2019/11/26 00:43:59| Process Roles: master worker
> 2019/11/26 00:43:59| With 1024 file descriptors available
> 2019/11/26 00:43:59| Initializing IP Cache...
> 2019/11/26 00:43:59| DNS Socket created at [::], FD 3
> 2019/11/26 00:43:59| DNS Socket created at 0.0.0.0, FD 9
> 2019/11/26 00:43:59| Adding domain robo84.home from /etc/resolv.conf
> 2019/11/26 00:43:59| Adding nameserver 8.8.8.8 from /etc/resolv.conf

Not a good idea to use this resolver with SSL-Bump features. See
<https://wiki.squid-cache.org/KnowledgeBase/HostHeaderForgery>.


> 2019/11/26 00:43:59| Logfile: opening log
> daemon:/usr/local/squid/var/logs/access.log
> 2019/11/26 00:43:59| Logfile Daemon: opening log
> /usr/local/squid/var/logs/access.log
...
> 2019/11/26 00:44:00| logfileHandleWrite:
> daemon:/usr/local/squid/var/logs/access.log: error writing ((32) Broken
> pipe)

There is your error message.

Check that the folder path all exists and has the correct permissions
for Squid's low-privilege account to create the access.log file there.


> 2019/11/26 00:44:00| FATAL: I don't handle this error well!
> 2019/11/26 00:44:00| Squid Cache (Version 4.9): Terminated abnormally.


Amos