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

    Unable to get Squid3-dev (and squidGuard-squid3) working on pfSense 2.2

    Scheduled Pinned Locked Moved pfSense Packages
    7 Posts 2 Posters 5.0k 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.
    • A
      azzlack
      last edited by

      I'm unable to get this working on my installation. The service is unable to start, and the only message that appears in the log is```
      kernel: pid 50048 (squid), uid 0: exited on signal 11 (core dumped)

      
      When I try to start it manually from terminal it says
      

      Segmentation fault (core dumped)

      
      When trying to check the config file use squid -k parse i get the following output:
      

      2014/08/12 08:54:02| Startup: Initializing Authentication Schemes ...
      2014/08/12 08:54:02| Startup: Initialized Authentication Scheme 'basic'
      2014/08/12 08:54:02| Startup: Initialized Authentication Scheme 'digest'
      2014/08/12 08:54:02| Startup: Initialized Authentication Scheme 'negotiate'
      2014/08/12 08:54:02| Startup: Initialized Authentication Scheme 'ntlm'
      2014/08/12 08:54:02| Startup: Initialized Authentication.
      2014/08/12 08:54:02| Processing Configuration File: /usr/local/etc/squid/squid.conf (depth 0)
      2014/08/12 08:54:02| Processing: http_port 172.16.101.1:3128
      2014/08/12 08:54:02| Processing: http_port 127.0.0.1:3128 intercept
      2014/08/12 08:54:02| Starting Authentication on port 127.0.0.1:3128
      2014/08/12 08:54:02| Disabling Authentication on port 127.0.0.1:3128 (interception enabled)
      2014/08/12 08:54:02| Disabling IPv6 on port 127.0.0.1:3128 (interception enabled)
      2014/08/12 08:54:02| Processing: icp_port 0
      2014/08/12 08:54:02| Processing: dns_v4_first off
      2014/08/12 08:54:02| Processing: pid_filename /var/run/squid.pid
      2014/08/12 08:54:02| Processing: cache_effective_user proxy
      2014/08/12 08:54:02| Processing: cache_effective_group proxy
      2014/08/12 08:54:02| Processing: error_default_language en
      2014/08/12 08:54:02| Processing: icon_directory /usr/pbi/squid-amd64/etc/squid/icons
      2014/08/12 08:54:02| Processing: visible_hostname squid.eyecatch.no
      2014/08/12 08:54:02| Processing: cache_mgr pfsense@eyecatch.no
      2014/08/12 08:54:02| Processing: access_log /var/squid/logs/access.log
      2014/08/12 08:54:02| Processing: cache_log /var/squid/logs/cache.log
      2014/08/12 08:54:02| Processing: cache_store_log none
      2014/08/12 08:54:02| Processing: netdb_filename /var/squid/logs/netdb.state
      2014/08/12 08:54:02| Processing: pinger_enable on
      2014/08/12 08:54:02| Processing: pinger_program /usr/pbi/squid-amd64/libexec/squid/pinger
      2014/08/12 08:54:02| Processing: logfile_rotate 0
      2014/08/12 08:54:02| Processing: debug_options rotate=0
      2014/08/12 08:54:02| Processing: shutdown_lifetime 3 seconds
      2014/08/12 08:54:02| Processing: acl localnet src  172.16.101.0/24
      2014/08/12 08:54:02| Processing: httpd_suppress_version_string on
      2014/08/12 08:54:02| Processing: uri_whitespace strip
      2014/08/12 08:54:02| Processing: acl dynamic urlpath_regex cgi-bin ?
      2014/08/12 08:54:02| Processing: cache deny dynamic
      2014/08/12 08:54:02| Processing: cache_mem 1024 MB
      2014/08/12 08:54:02| Processing: maximum_object_size_in_memory 128 KB
      2014/08/12 08:54:02| Processing: memory_replacement_policy lru
      2014/08/12 08:54:02| Processing: cache_replacement_policy heap LFUDA
      2014/08/12 08:54:02| Processing: cache_dir aufs /var/squid/cache 3072 16 256
      Segmentation fault (core dumped)

      
      Could it be that the config file is invalid? This is a new installation, and I have not configured it outside the webGUI.
      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Segfaults that lead to core dumps can happen if squid fails some consistency checks.  Try running

        squid -k debug

        and see if that shows anything useful.

        1 Reply Last reply Reply Quote 0
        • A
          azzlack
          last edited by

          Running squid -k debug just yields

          Segmentation fault (core dumped)
          

          and nothing more.

          1 Reply Last reply Reply Quote 0
          • A
            azzlack
            last edited by

            Just tried to remove alle squid-related settings like posted on https://forum.pfsense.org/index.php?topic=78521.0, but I still get the Segmentation fault (core dumped) error when trying to run squid -k debug.

            BTW I'm running on amd64

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              Anything in your System log around the time of the crash?

              1 Reply Last reply Reply Quote 0
              • A
                azzlack
                last edited by

                No, I get the same as I posted in the first post.

                But here is the whole system log when booting up:

                Aug 14 01:02:10	php-fpm[19930]: /rc.start_packages: Starting Squid
                Aug 14 01:02:11	php-fpm[19930]: /rc.start_packages: The command '/usr/pbi/squid-amd64/sbin/squid -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '139', the output was ''
                Aug 14 01:02:11	kernel: pid 14851 (squid), uid 0: exited on signal 11 (core dumped)
                Aug 14 01:02:13	php-fpm[66630]: /rc.start_packages: The command '/usr/pbi/squid-amd64/sbin/squid -k kill -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '139', the output was ''
                Aug 14 01:02:13	kernel: pid 18434 (squid), uid 0: exited on signal 11 (core dumped)
                Aug 14 01:02:14	check_reload_status: Reloading filter
                Aug 14 01:02:14	php-fpm[66630]: /rc.start_packages: The command '/usr/pbi/squid-amd64/sbin/squid -z -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '139', the output was ''
                Aug 14 01:02:14	kernel: pid 21127 (squid), uid 0: exited on signal 11 (core dumped)
                Aug 14 01:02:14	php-fpm[66630]: /rc.start_packages: Starting Squid
                Aug 14 01:02:15	php-fpm[66630]: /rc.start_packages: The command '/usr/pbi/squid-amd64/sbin/squid -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '139', the output was ''
                Aug 14 01:02:15	kernel: pid 26225 (squid), uid 0: exited on signal 11 (core dumped)
                Aug 14 01:02:15	php-fpm[98358]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
                Aug 14 01:02:15	php-fpm[98358]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
                Aug 14 01:02:15	php-fpm[98358]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
                Aug 13 23:02:29	check_reload_status: Reloading filter
                Aug 13 23:02:29	kernel: pid 38557 (squid), uid 0: exited on signal 11 (core dumped)
                Aug 13 23:02:30	php-fpm[31224]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
                Aug 13 23:02:30	login: login on ttyv0 as root
                Aug 13 23:02:30	sshlockout[46387]: sshlockout/webConfigurator v3.0 starting up
                Aug 13 23:02:30	php-fpm[31224]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
                Aug 13 23:02:31	php-fpm[31224]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
                Aug 13 23:02:34	Squid_Alarm[54052]: Squid has exited. Reconfiguring filter.
                Aug 13 23:02:34	Squid_Alarm[54545]: Attempting restart...
                Aug 13 23:02:34	kernel: pid 55411 (squid), uid 0: exited on signal 11 (core dumped)
                
                1 Reply Last reply Reply Quote 0
                • KOMK
                  KOM
                  last edited by

                  I did a little research and the crash seems to be related to a memory access violation by Squid.  You're running an alpha build of 2.2 so I'm not shocked, but still.  What is your configuration? i386, x64?  Virtual, physical server or miniPC (ALIX board etc)?  Any other packages?

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