Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Squid SMP Workers Not Working

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 1 Posters 2.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jalmeida1008
      last edited by

      Hello All,
      I Don´t know if this is the correct place to put this question, sorry If i´m wrong.

      I´m having a problem for almost a month with a Squid 3.4 install on Pfsense, after suffering with performance issues when my clients computers are set up to use the proxy, I realize that squid only open one process and this process just use one core of my proc.
      So after found that, I started try to use SQUID SMP workers to open more instances so squid can use all my cores and balance load.
      But when I set the workers variable on squid "Custom ACLS (Before Auth)" I got some error on cache.log and only the coordinator process loads.
      Please is anyone can help me with that?
      Bellow my configuration:

      workers 3
      auth_param ntlm program /usr/pbi/squid-amd64/local/libexec/squid/ntlm_auth –configfile=/usr/pbi/squid-amd64/etc/smb4.conf --helper-protocol=squid-2.5-ntlmssp
      auth_param ntlm children 500
      auth_param ntlm keep_alive on
      acl password proxy_auth REQUIRED
      http_access allow all password

      When I start the services I got the following errors on cache.log:

      2016/01/21 20:44:15 kid3| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.1...
      2016/01/21 20:44:15 kid2| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.1...
      2016/01/21 20:44:15 kid4| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.1...
      2016/01/21 20:44:15 kid1| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.1...
      FATAL: kid2 registration timed out
      Squid Cache (Version 3.4.10): Terminated abnormally.
      CPU Usage: 0.182 seconds = 0.094 user + 0.088 sys
      Maximum Resident Size: 106880 KB
      Page faults with physical i/o: 0
      FATAL: kid3 registration timed out
      Squid Cache (Version 3.4.10): Terminated abnormally.
      CPU Usage: 0.182 seconds = 0.114 user + 0.068 sys
      Maximum Resident Size: 107072 KB
      Page faults with physical i/o: 0
      FATAL: kid1 registration timed out
      Squid Cache (Version 3.4.10): Terminated abnormally.
      CPU Usage: 0.181 seconds = 0.118 user + 0.063 sys
      Maximum Resident Size: 107040 KB
      Page faults with physical i/o: 0
      2016/01/21 20:44:24 kid2| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.1...
      2016/01/21 20:44:27 kid1| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.1...
      2016/01/21 20:44:27 kid3| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.1...
      FATAL: kid2 registration timed out
      Squid Cache (Version 3.4.10): Terminated abnormally.
      CPU Usage: 0.163 seconds = 0.129 user + 0.034 sys
      Maximum Resident Size: 107008 KB
      Page faults with physical i/o: 0
      FATAL: kid1 registration timed out
      Squid Cache (Version 3.4.10): Terminated abnormally.
      CPU Usage: 0.167 seconds = 0.117 user + 0.050 sys
      Maximum Resident Size: 107040 KB
      Page faults with physical i/o: 0
      FATAL: kid3 registration timed out
      Squid Cache (Version 3.4.10): Terminated abnormally.
      CPU Usage: 0.171 seconds = 0.123 user + 0.047 sys
      Maximum Resident Size: 106624 KB
      Page faults with physical i/o: 0

      I already changed this configurations on sysclt as mentioned on oficial wiki "http://wiki.squid-cache.org/Features/SmpScale"

      net.local.dgram.recvspace: 262144
      net.local.dgram.maxdgram: 16384

      do anyone have an idea to resolve that?

      Thanks

      1 Reply Last reply Reply Quote 0
      • J
        jalmeida1008
        last edited by

        Hi I´m back,

        I resolved that, just putted the net.local.dgram.recvspace: 262144 net.local.dgram.maxdgram: 16384 variables on advanced tab of pfsense and it´s working now.
        Thanks everyone.

        1 Reply Last reply Reply Quote 1
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.