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

    I am now creating new DansGuardian and Squid3 binaries.

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    50 Posts 11 Posters 16.9k 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.
    • jimpJ
      jimp Rebel Alliance Developer Netgate
      last edited by

      Strange, I haven't used an RC yet myself, my workstation is on a late beta, but there were a ton of updates to ports over the last couple weeks.

      When all else fails, pkg delete -fa, and start over with a fresh ports tree (portsnap fetch extract)

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

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

        I've been trying to resolve them manually. That said, I just did a portsnap fetch and portsnap update, followed closely behind by a few _make distclean_s. Portsnap fetch grabbed over 200 patches to my existing tree. Crossing my fingers…

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

          Yeah, going to start with a new ports install. Running rm -rf /usr/ports now. Just ran pkg delete -fa a moment ago. Thanks for that, by the way. I didn't previously know I could force remove all pkgs! I'm assuming that's what is meant by -fa (force all).

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

            I'm back on the case.

            FreeBSD was updated to RC2 on Friday. I had some things going over the weekend. It's now about midnight Monday morning. GTG.

            1 Reply Last reply Reply Quote 0
            • D
              dooldeniya
              last edited by

              Aaron - Thanks for working on this.  Any update on progress.  I am looking to install and would appreciate any guidance you can provide.
              -Chanaka

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

                Actually, I've stopped working on this, as the original maintainer of squid and DansGuardian, namely user MarcelloC, managed to find the time to update them about a month ago. I assume you're having trouble? If so, you're in the right place… (Pfsense forums).

                1 Reply Last reply Reply Quote 0
                • R
                  rjcrowder
                  last edited by

                  @aaronouthier:

                  Actually, I've stopped working on this, as the original maintainer of squid and DansGuardian, namely user MarcelloC, managed to find the time to update them about a month ago. I assume you're having trouble? If so, you're in the right place… (Pfsense forums).

                  That's awesome news… so now the normal Squid3 and DG packages should work under 2.2?

                  1 Reply Last reply Reply Quote 0
                  • C
                    Cino
                    last edited by

                    Do you know where he updated them too?

                    I checked github for php/inc file changes: squid3 hasn't been updated in 2 months, Dansguardian 5 months.

                    binary changes:
                    Checked http://files.pfsense.org/packages/8/All/
                    dansguardian-2.12.0.3_2-i386.pbi                  23-Jun-2014 13:57            19952423
                    squid-3.3.10-i386.pbi                              26-Nov-2013 20:06            17598644

                    Checked http://files.pfsense.org/packages/10/All/
                    dansguardian-2.12.0.3_2-i386.pbi                  27-Jun-2014 03:42            16177170
                    squid-3.3.11-i386.pbi                              22-Apr-2014 12:12            17568448
                    squid-3.3.11_1-i386.pbi                            17-Jul-2014 22:26            17702572

                    amd64 pbi have the same dates

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

                      Ok. I did some more checking, and, now I'm not sure who updated it, or when. I just know that around October 15 or so, I reinstalled my box, and everything worked, whereas a fresh install previously didn't work right without some modifications.

                      Also, note that I am using squid3-dev, not regular squid3, and I am running it on the 2.2 beta, not the 2.1.x stable.

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

                        I have a fresh install of 2.2-BETA (amd64) built on Mon Oct 27 15:31:41 CDT 2014 FreeBSD 10.1-RC3
                        If I install squid3-dev beta 3.3.11_1 pkg 2.2.7 platform: 2.2 - I've never managed to start it.

                        On the previous install, I tried installing libraries it complained were missing ect. to see if I could get it up,
                        but eventually I gave up, and reinstalled from scratch.

                        Would you mind sharing which versions you're running?

                        Thanks in advanced.

                        1 Reply Last reply Reply Quote 0
                        • E
                          Escorpiom
                          last edited by

                          More or less the same situation here, I'm running 2.2 beta snapshot and tried to install Squid 3.3.11_1 pkg 2.2.7, it wouldn't start.
                          I used the workaround described elsewhere on this forum, and now it runs.
                          Downside is that the "workaround" (console commandos) have to be entered again after each update.

                          So it's either "do not update" or "workaround".

                          For my purposes, Squid proxy (and if possible with ad blocking) is really a must-have. 
                          I'm not a programmer, but can test packages if needed.
                          Please keep up the effort.

                          Cheers.

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

                            Hmm. Not sure what happened. I just did a fresh reinstall myself. Squid now segfaults upon launch with core dump. This is with the official versions of everything. Nothing was custom-compiled or copied from another box. Amd64 build. I don't know what to say.

                            1 Reply Last reply Reply Quote 0
                            • E
                              Escorpiom
                              last edited by

                              Exactly.
                              It did that on my box also, but it turned out to be the cache filesystem.
                              If you set it to "aufs", Squid will complain.
                              Leaving it at "ufs" (default) and it runs.

                              I have found a way to block ads with the help of a regex list added to Squid, and that works fine.
                              So for now, all is dandy. No updates though.

                              Cheers.

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

                                Well, I am having some frustrating issues. I have gotten squid to compile just fine, but when I do amake install, it hangs with a series of```
                                lstat: file not found

                                1 Reply Last reply Reply Quote 0
                                • E
                                  Escorpiom
                                  last edited by

                                  Hmm I'm not familiar with the process, wish I could help in some way.
                                  Take your time.

                                  Cheers.

                                  1 Reply Last reply Reply Quote 0
                                  • E
                                    Escorpiom
                                    last edited by

                                    Today, a new Squid package was made available.
                                    As I was feeling adventurous, decided to hit the pkg button and….
                                    Installed just fine, all configs retained. No errors.

                                    I haven't tried to update the beta snapshot yet, better wait until it gets final.

                                    Cheers.

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

                                      No luck on my end, but I am running the latest beta…

                                      2.2-BETA (amd64)
                                      built on Fri Nov 07 13:54:45 CST 2014
                                      FreeBSD 10.1-RC4-p1

                                      squid3-dev
                                      3.3.11_1 pkg 2.2.8

                                      Last 50 system log entries
                                      Nov 8 11:42:45 php-fpm[50841]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
                                      Nov 8 11:42:44 php-fpm[50841]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
                                      Nov 8 11:42:44 php-fpm[50841]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
                                      Nov 8 11:42:43 check_reload_status: Reloading filter
                                      Nov 8 11:42:33 kernel: pid 85517 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:42:33 php-fpm[92516]: /pkg_edit.php: The command '/usr/pbi/squid-amd64/sbin/squid -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '139', the output was ''
                                      Nov 8 11:42:32 php-fpm[92516]: /pkg_edit.php: Starting Squid
                                      Nov 8 11:42:32 kernel: pid 81637 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:42:32 php-fpm[92516]: /pkg_edit.php: 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 ''
                                      Nov 8 11:42:31 kernel: pid 77608 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:42:31 php-fpm[92516]: /pkg_edit.php: 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 ''
                                      Nov 8 11:42:26 kernel: pid 57759 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:42:26 php-fpm[92516]: /pkg_edit.php: The command '/usr/pbi/squid-amd64/sbin/squid -k shutdown -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '139', the output was ''
                                      Nov 8 11:42:25 php-fpm[92516]: /pkg_edit.php: Creating squid cache subdirs in /var/squid/cache
                                      Nov 8 11:42:25 php-fpm[25084]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
                                      Nov 8 11:42:25 php-fpm[25084]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
                                      Nov 8 11:42:25 php-fpm[25084]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
                                      Nov 8 11:42:24 php-fpm[25084]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
                                      Nov 8 11:42:24 php-fpm[25084]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
                                      Nov 8 11:42:24 php-fpm[25084]: /rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
                                      Nov 8 11:42:24 php-fpm[92516]: /pkg_edit.php: [Squid] - Squid_resync function call pr: bp: rpc:no
                                      Nov 8 11:42:24 check_reload_status: Reloading filter
                                      Nov 8 11:42:24 check_reload_status: Syncing firewall
                                      Nov 8 11:42:13 kernel: pid 39066 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:42:13 php-fpm[92516]: /pkg_edit.php: The command '/usr/pbi/squid-amd64/sbin/squid -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '139', the output was ''
                                      Nov 8 11:42:12 php-fpm[92516]: /pkg_edit.php: Starting Squid
                                      Nov 8 11:42:12 kernel: pid 34816 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:42:12 php-fpm[92516]: /pkg_edit.php: 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 ''
                                      Nov 8 11:42:12 kernel: pid 31211 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:42:12 php-fpm[92516]: /pkg_edit.php: 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 ''
                                      Nov 8 11:42:06 kernel: pid 27894 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:42:06 php-fpm[92516]: /pkg_edit.php: The command '/usr/pbi/squid-amd64/sbin/squid -k shutdown -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '139', the output was ''
                                      Nov 8 11:42:06 php-fpm[92516]: /pkg_edit.php: Creating squid cache subdirs in /var/squid/cache
                                      Nov 8 11:42:04 php-fpm[92516]: /pkg_edit.php: [Squid] - Squid_resync function call pr: bp: rpc:no
                                      Nov 8 11:41:20 kernel: pid 93914 (squid), uid 0: exited on signal 11 (core dumped)
                                      Nov 8 11:41:15 syslogd: kernel boot file is /boot/kernel/kernel

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        phil.davis
                                        last edited by

                                        @Escorpiom:

                                        Today, a new Squid package was made available.
                                        As I was feeling adventurous, decided to hit the pkg button and….
                                        Installed just fine, all configs retained. No errors.

                                        I haven't tried to update the beta snapshot yet, better wait until it gets final.
                                         
                                        Cheers.

                                        That update for squid3 (3.1) and squid-dev (3.3) was just to add some extra checks to swapstate_check.php that were in squid (2) but had never been put into the newer squid versions. It does not effect any squid functionality, and has no change to the binaries. So it won't help any issues with running on 2.2-BETA,

                                        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

                                          Fix for Squid. Needs to be run on each box. Survives a reboot. Survives an update to latest beta, as far as I can tell.

                                          Open a command prompt:

                                          
cd /usr/pbi/squid-amd64

```- for x64

–- or ---

                                          cd /usr/pbi/squid-i386

                                          
then:

                                          cp -R local/etc local/lib local/libexec /usr/

                                          
I'm doing this from memory, so please do this on a test box, Virtual Machine, etc. and make a backup or snapshot first. I did this several days ago, and I copied only one folder at a time. I tried to condense the instructions to make it easier. Please let me know if I made a typo.

You then will need to reboot your pfSense box. I was unable to use the Web interface until I did so. YMMV.
                                          1 Reply Last reply Reply Quote 0
                                          • C
                                            cmb
                                            last edited by

                                            That's not a good fix, that'll leave behind files in places where they shouldn't be. The root cause of that issue is being looked into. If you need an immediate work around on 2.2, I guess that's OK, but you're going to want to blow away the system and reinstall from scratch once the root issue is fixed if you do that. Or know exactly what you copied into /usr/ and manually remove only those files.

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