On 3/1/19 1:47 PM, amlgp wrote: > I have about 250 proxies/clients accessing squid and my cache deny all is on > the first line in my squid.conf.
FYI: The position of the set of "cache" directives does not affect how Squid works. Configuration is "compiled" at start time. At runtime, Squid uses the "compiled" version of all the directives. > Clients/proxies are experiencing lag and when checking my Cpu usage is 100%. > I tried to restart and its smooth for a few minutes at 1-2% cpu, but then > jumps to 100% again. You might be suffering from Bug 4885: https://bugs.squid-cache.org/show_bug.cgi?id=4885 > I also tried squid -k debug but nothing shows up in my > /var/log/squid/cache.log which is where the log is supposed to go to(file > doesn't exist). If that file does not exist then your Squid is logging elsewhere or Squid tries to log somewhere it cannot. I would expect the latter to be a fatal startup error, but I have not checked that. > Do I need to manually create the log file first? No, you do not. > Any idea what I can do to debug the problem You should get cache.log working before you proceed any further. That log may contain critical information that is not available in system logs. I would start by checking cache_log option in your squid.conf. If it is not there, see squid.conf.documented for your default location. Also please make sure that debug_options is either absent or set to something like ALL,1. You can also collect stack traces from a running Squid process, but I would get cache.log working first. Alex. _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
