Squid3-dev will not start on fresh PFsense VM



  • On my lab environment I setup the latest snapshot on a hyper-v server using the image on the snapshots page. http://snapshots.pfsense.org/

    I was able to configure the router as close to our production router, however when it came to installing Squid3-dev, the process will not stay on despite a full update to clamAV and configuring the services to the best of my abilities.

    Under General logs squid attempts to start but is shut down for unknown reasons:

    Aug 21 12:08:03 squid[32221]: Squid Parent: (squid-1) process 44006 started
    Aug 21 12:08:03 squid[32221]: Squid Parent: (squid-1) process 44006 exited with status 1
    Aug 21 12:08:06 squid[32221]: Squid Parent: (squid-1) process 44453 started
    Aug 21 12:08:06 squid[32221]: Squid Parent: (squid-1) process 44453 exited with status 1
    Aug 21 12:08:09 squid[32221]: Squid Parent: (squid-1) process 44822 started
    Aug 21 12:08:09 squid[32221]: Squid Parent: (squid-1) process 44822 exited with status 1
    Aug 21 12:08:09 squid[32221]: Squid Parent: (squid-1) process 44822 will not be restarted due to repeated, frequent failures
    Aug 21 12:08:09 squid[32221]: Exiting due to repeated, frequent failures
    Aug 21 12:08:55 Squid_Alarm[59119]: Squid has exited. Reconfiguring filter.
    Aug 21 12:08:55 Squid_Alarm[59261]: Attempting restart…
    Aug 21 12:08:55 squid[63767]: Squid Parent: will start 1 kids
    Aug 21 12:08:55 squid[63767]: Squid Parent: (squid-1) process 64459 started
    Aug 21 12:08:55 squid[63767]: Squid Parent: (squid-1) process 64459 exited with status 1
    Aug 21 12:08:58 squid[63767]: Squid Parent: (squid-1) process 64569 started
    Aug 21 12:08:58 squid[63767]: Squid Parent: (squid-1) process 64569 exited with status 1
    Aug 21 12:08:58 Squid_Alarm[64747]: Reconfiguring filter…

    I've tried everything imaginable to get this to work, even under the release image I still get the same issue. Looking up the problem has not resulted in any solutions.

    It would be great if someone had any idea how to get this thing working....



  • You might be able to retrieve more information about the frequent failures in the log files of squid.

    /var/squid/logs/cache.log
    

    Maybe a sample of the GUI produced "squid.conf" file might help to find the issue.

    /usr/pbi/squid-amd64/etc/squid/squid.conf
    

    You can use the command prompt menu in the GUI to issue "cat /var/squid/logs/cache.log" (Warning!!!! might be to big !!!Warning)
    Or you can connect WinSCP to retrieve and look at the above mentioned files.



  • I am getting this error aswell.

    It is a fresh install of:
    2.2-BETA (amd64) built on Mon Oct 27 15:31:41 CDT 2014 FreeBSD 10.1-RC3

    with a fresh install of Squid3-dev 3.3.11_1 pkg 2.2.7

    System is 4 core intel (e3845), with 8gb ram and 160 hhd.

    I have merely installed pfsense, updated, then installed squid.
    and then checked system log.

        • system log (partial) - - -
          php-fpm[4692]: /pkg_mgr_install.php: Beginning package installation for squid3-dev .
          php-fpm[4692]: /pkg_mgr_install.php: Stopping any running proxy monitors
          php-fpm[4692]: /pkg_mgr_install.php: Starting Squid
          php-fpm[4692]: /pkg_mgr_install.php: Starting a proxy monitor script
          squid[28132]: Squid Parent: will start 1 kids
          squid[28132]: Squid Parent: (squid-1) process 28698 started
          squid[28132]: Squid Parent: (squid-1) process 28698 exited with status 1
          … goes on like this for a bit, then ...
          squid[28132]: Squid Parent: (squid-1) process 50205 will not be restarted due to repeated, frequent failures
          squid[28132]: Exiting due to repeated, frequent failures
        • /var/squid/logs/cache.log - - -
          *empty
        • conf - - -

    This file is automatically generated by pfSense

    Do not edit manually !

    http_port 10.42.0.1:3128
    icp_port 0
    dns_v4_first off
    pid_filename /var/run/squid.pid
    cache_effective_user proxy
    cache_effective_group proxy
    error_default_language en
    icon_directory /usr/pbi/squid-amd64/etc/squid/icons
    visible_hostname localhost
    cache_mgr admin@localhost
    access_log /dev/null
    cache_log /var/squid/logs/cache.log
    cache_store_log none
    netdb_filename /var/squid/logs/netdb.state
    pinger_enable on
    pinger_program /usr/pbi/squid-amd64/libexec/squid/pinger

    logfile_rotate 0
    debug_options rotate=0
    shutdown_lifetime 3 seconds
    uri_whitespace strip

    acl dynamic urlpath_regex cgi-bin ?
    cache deny dynamic

    cache_mem 8 MB
    maximum_object_size_in_memory 32 KB
    memory_replacement_policy heap GDSF
    cache_replacement_policy heap LFUDA

    minimum_object_size 0 KB
    maximum_object_size 10 KB
    offline_mode off
    cache allow all

    No redirector configured

    #Remote proxies

    Setup some default acls

    From 3.2 further configuration cleanups have been done to make things easier and safer. The manager, localhost, and to_localhost ACL definitions are now built-in.

    acl localhost src 127.0.0.1/32

    acl allsrc src all
    acl safeports port 21 70 80 210 280 443 488 563 591 631 777 901  3128 3127 1025-65535
    acl sslports port 443 563

    From 3.2 further configuration cleanups have been done to make things easier and safer. The manager, localhost, and to_localhost ACL definitions are now built-in.

    #acl manager proto cache_object

    acl purge method PURGE
    acl connect method CONNECT

    Define protocols used for redirects

    acl HTTP proto HTTP
    acl HTTPS proto HTTPS
    http_access allow manager localhost

    http_access deny manager
    http_access allow purge localhost
    http_access deny purge
    http_access deny !safeports
    http_access deny CONNECT !sslports

    Always allow localhost connections

    From 3.2 further configuration cleanups have been done to make things easier and safer.

    The manager, localhost, and to_localhost ACL definitions are now built-in.

    http_access allow localhost

    Reverse Proxy settings

    Custom options before auth

    Setup allowed acls

    Default block all to be sure

    http_access deny allsrc



  • also having same problem.. out of the box 2.2 11-20-14 with squid3-dev, service will not start



  • I was able to get the squid3-dev package running by issuing the following commands in a shell, after I had installed the package:

    ln -s /lib/libmd.so.6 /usr/lib/libmd5.so.1
    ln -s /usr/pbi/squid-amd64/local/etc/squid /usr/local/etc/squid
    ln -s /usr/pbi/squid-amd64/local/libexec/squid /usr/local/libexec/squid

    (this was on a amd64 2.2 install)

    I only confirmed that it was running, and sort of worked, no idea if it is stable in the long run.

    It will maybe (probably?) also break other things when updating the system or other packages.

    /DJ



  • Hi,

    Any news on this - does it seem to be stable? Just tried (stock) squid3, and agree - it won't start / work.

    Thanks!



  • I can also confirm that Squid-3 will not start on 2.2-RC after a fresh install or upgrade. I am running 64bit edition.



  • Same problem here (but not in VM - on local hardware - 64bit edition too). Is there already any solution out there?

    Thanks.



  • On 2.2, squid package is not -dev. If you're using clamav, you need save config and follow instructions on antivirus tab and then wait first freshclam run to finish. Then a stop and start of squid and c-icap service.

    On 2.1.5 amd64 version squid antivirus integration will not work.



  • Hi there,

    any news concerning that issue? Same problem over here…just spend nearly the whole day trying to fix it. Could one of you guys solve it?

    Cheers


Log in to reply