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

    Squid3 can't find libmd5.so.0

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    60 Posts 18 Posters 20.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.
    • C
      chiwalfrm
      last edited by

      Also various pinger errors although these don't seem to do any harm.

      2015/01/04 14:41:58| pinger: Initialising ICMP pinger …
      2015/01/04 14:41:58|  icmp_sock: (1) Operation not permitted
      2015/01/04 14:41:58| pinger: Unable to start ICMP pinger.
      2015/01/04 14:41:58|  icmp_sock: (1) Operation not permitted
      2015/01/04 14:41:58| pinger: Unable to start ICMPv6 pinger.
      2015/01/04 14:41:58| FATAL: pinger: Unable to open any ICMP sockets.

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

        Seems to be a fix on the way.
        https://forum.pfsense.org/index.php?topic=85965.0

        /Anders

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

          While I haven't kept up on every dev build, Squid 3 on 2.2 hasn't worked for me at all since last November.  In that time frame, they have gone from 2.2 Beta to 2.2 RC.  How you can go from a beta to RC with a major package being broken all along is a mystery to me.

          And, honestly, I can't be bothered trying to play around with symlinks and putting on my detective hat to get something working that should already work straight away considering it's an RC.  cmb has already said that any hacks to get it working will likely either break something else or be wiped away with an update.  I must say that I'm a little disappointed.

          1 Reply Last reply Reply Quote 0
          • M
            mir
            last edited by

            squid2 does work though so if there is nothing which is only in squid3 you need you can try with squid2.

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

              I know that, but I'd rather not spend time & effort working with an ancient package.  Squid 2.x hasn't been updated in almost 5 years.  I don't know if the ESF guys tweak it at all, but the base Squid 2.7.9 was released March 2010.

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

                As far as I know squid2 is maintain by the pfsense team while squid3 is by a community forum member.

                1 Reply Last reply Reply Quote 0
                • T
                  Topper727
                  last edited by

                  https://forum.pfsense.org/index.php?topic=85965.0;topicseen

                  in this topic there is someone working on these issues

                  Dell 2950 g3 server
                  Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
                  Current: 2000 MHz, Max: 2667 MHz
                  8 CPUs: 2 package(s) x 4 core(s)
                  8152 MiB and 600meg 10k drive
                  Pfsense 2.4 .. Hoping to get the phpvirtualbox going again.

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

                    yup, the developer of the squid3 package… we just have to be patience.

                    1 Reply Last reply Reply Quote 0
                    • marcellocM
                      marcelloc
                      last edited by

                      @Cino:

                      As far as I know squid2 is maintain by the pfsense team while squid3 is by a community forum member.

                      Squid2 has been removed from freebsd ports. So I think it will not be in pfsense 2.2.

                      The way I'm testing squid3.4 on pfsense 2.2 until pbi builds are ok is using pkg add (very similar the way pfsense 2.0 works)

                      At least with pkg, all squid functions(including captive portal integration) are working.

                      Treinamentos de Elite: http://sys-squad.com

                      Help a community developer! ;D

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

                        Thanks Marcelloc!

                        Would it be possible for you to provide the steps your doing to install it correctly?

                        I'm assuming you install squid3.4 via pfSense Packages.. Once its installed, you then run pkg_add from the cmdline

                        I dont have access to my 2.2 test box at the moment but I looked at http://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages/All/ and only see squid-2.7.9_4.tbz, squid32-3.2.13.tbz, squid33-3.3.11.tbz.. I'm probably looking at the wrong repository since the file dates for those packages at almost a year ago and https://www.freebsd.org/cgi/ports.cgi?query=squid&stype=all shows squid-3.4.10_2 and squid33-3.3.13_2 only; no Squid2.

                        Have you ran into any issues with perl5-5.18.4_11 being installed? This would probably temporary fix the issues with lightsquid not being able to call perl

                        1 Reply Last reply Reply Quote 0
                        • marcellocM
                          marcelloc
                          last edited by

                          This is a workaround to get squid 3.4 working o pfsense 2.2(amd64) until pbi build are ok for this package.

                          This is not supported by core team! Use at your own risk!

                          First install squid package from pfsense gui
                          Next, we need to install pkg on pfsense 2.2, this can be done via console with

                          pkg install axel

                          when it asks to proceed(proceed with this action?), you can cancel it if you do not need axel on your system

                          kill and uninstall any running squid daemon

                          killall squid
pbi delete squid-3.4.10_2-amd64
rm -rf /usr/pbi/squid-amd64

                          if you have applied any patch or symlink while trying to run pbi squid version

                          rm -f /usr/lib/libmd5.so.0
rm -f /usr/lib/libecap.so.2
rm -rf /usr/local/etc/squid
rm -rf /usr/local/libexec/squid

                          create a folder to download squid3.4 package

                          mkdir /root/squid34
cd /root/squid34
fetch http://e-sac.siteseguro.ws/packages/10/All/squid34_pfsense22.tar
tar -xvf squid34_pfsense22.tar
pkg add squid-3.4.10_2.txz
pkg add squidclamav-6.10_2.txz
pkg add clamav-0.98.5_1.txz

                          Save config on gui again and test squid.

                          Treinamentos de Elite: http://sys-squad.com

                          Help a community developer! ;D

                          1 Reply Last reply Reply Quote 0
                          • S
                            samham
                            last edited by

                            I'm getting "Signature for pkg not available"  after the pkg command

                            1 Reply Last reply Reply Quote 0
                            • marcellocM
                              marcelloc
                              last edited by

                              @samham:

                              I'm getting "Signature for pkg not available"  after the pkg command

                              Finish the pkg install axel cmd

                              Treinamentos de Elite: http://sys-squad.com

                              Help a community developer! ;D

                              1 Reply Last reply Reply Quote 0
                              • M
                                mhab12
                                last edited by

                                Will the same procedure work on 2.1.5?

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

                                  @mhab12:

                                  Will the same procedure work on 2.1.5?

                                  It wont work on 2.1.5. The files that marcelloc complied are for freebsd10 amd64. 2.1.5 was built on 8.3.. Squid3-dev works on 2.1.5

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mrancier
                                    last edited by

                                    Transparent proxy still does not work :(

                                    1 Reply Last reply Reply Quote 0
                                    • marcellocM
                                      marcelloc
                                      last edited by

                                      @mhab12:

                                      Will the same procedure work on 2.1.5?

                                      On 2.1.5, install squid3-dev package. I uses squid 3.3.10

                                      Treinamentos de Elite: http://sys-squad.com

                                      Help a community developer! ;D

                                      1 Reply Last reply Reply Quote 0
                                      • marcellocM
                                        marcelloc
                                        last edited by

                                        @mrancier:

                                        Transparent proxy still does not work :(

                                        Maybe related to some 2.2 RC issues, not squid itself.

                                        Check if you don't have this error on your system logs

                                        php: rc.filter_configure: PHP ERROR: Type: 2, File: /etc/inc/util.inc, Line: 184, Message: fsockopen(): unable to connect to unix:///var/run/check_reload_status:-1 (No such file or directory)

                                        tracking this issue I've found this:

                                        ldd /usr/local/sbin/check_reload_status
/usr/local/sbin/check_reload_status:
        libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000)
        libevent-2.0.so.5 => not found (0)
        libc.so.7 => /lib/libc.so.7 (0x800a4f000)

                                        trying a manual fix:

                                        ln -s /usr/local/lib/libevent-2.0.so.5 /lib/libevent-2.0.so.5

                                        and check_reload_status seems to be ok again

                                        ldd /usr/local/sbin/check_reload_status
/usr/local/sbin/check_reload_status:
        libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000)
        libevent-2.0.so.5 => /lib/libevent-2.0.so.5 (0x800a4f000)
        libc.so.7 => /lib/libc.so.7 (0x800c91000)
        libthr.so.3 => /lib/libthr.so.3 (0x801023000)

                                        and also transparent proxy

                                        grep 3128 /tmp/rules.debug
rdr on em1 proto tcp from any to !(em1) port 80 -> 127.0.0.1 port 3128
pass in quick on em1 proto tcp from any to !(em1) port {80,443,3128,3127} flags S/SA keep state

                                        I've opened a redmine for it, so core team can check this issue

                                        Treinamentos de Elite: http://sys-squad.com

                                        Help a community developer! ;D

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          mrancier
                                          last edited by

                                          I can confirm that error.  It was also accompanied by sshd being unable to start.  Reverting changes didn't help, but reinstalling the snapshot fixed sshd.  I will try the fix you described sometime tomorrow.  Thank you!

                                          @marcelloc:

                                          @mrancier:

                                          Transparent proxy still does not work :(

                                          Maybe related to some 2.2 RC issues, not squid itself.

                                          Check if you don't have this error on your system logs

                                          php: rc.filter_configure: PHP ERROR: Type: 2, File: /etc/inc/util.inc, Line: 184, Message: fsockopen(): unable to connect to unix:///var/run/check_reload_status:-1 (No such file or directory)

                                          tracking this issue I've found this:

                                          ldd /usr/local/sbin/check_reload_status
/usr/local/sbin/check_reload_status:
        libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000)
        libevent-2.0.so.5 => not found (0)
        libc.so.7 => /lib/libc.so.7 (0x800a4f000)

                                          trying a manual fix:

                                          ln -s /usr/local/lib/libevent-2.0.so.5 /lib/libevent-2.0.so.5

                                          and check_reload_status seems to be ok again

                                          ldd /usr/local/sbin/check_reload_status
/usr/local/sbin/check_reload_status:
        libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000)
        libevent-2.0.so.5 => /lib/libevent-2.0.so.5 (0x800a4f000)
        libc.so.7 => /lib/libc.so.7 (0x800c91000)
        libthr.so.3 => /lib/libthr.so.3 (0x801023000)

                                          and also transparent proxy

                                          grep 3128 /tmp/rules.debug
rdr on em1 proto tcp from any to !(em1) port 80 -> 127.0.0.1 port 3128
pass in quick on em1 proto tcp from any to !(em1) port {80,443,3128,3127} flags S/SA keep state

                                          I've opened a redmine for it, so core team can check this issue

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

                                            marcelloc

                                            I ran into a small problem after following your steps
                                            "(squid-1): Cannot open '/var/squid/logs/access.log' for writing. The parent directory must be writeable by the user 'proxy', which is the cache_effective_user set in squid.conf." 
                                            I was able to 'monkey' around with winscp to change permissions, not sure what I did but got past that. What would be the correct way of 'doing it right'

                                            transparent proxy still not working, under the real time tab this is what I see

                                            09.01.2015 09:27:24	192.168.1.2	TCP_MISS/403	http://yahoo.com/favicon.ico	-	127.0.0.1
09.01.2015 09:27:24	127.0.0.1	TCP_DENIED/403	http://yahoo.com/favicon.ico	-	-
09.01.2015 09:27:24	192.168.1.2	TCP_MISS/403	http://www.squid-cache.org/Artwork/SN.png	-	127.0.0.1
09.01.2015 09:27:24	127.0.0.1	TCP_DENIED/403	http://www.squid-cache.org/Artwork/SN.png	-	-

                                            grep 3128 /tmp/rules.debug
rdr on em1 proto tcp from any to !(em1) port 80 -> 127.0.0.1 port 3128
pass in quick on em1 proto tcp from any to !(em1) port {80,3128} flags S/SA keep state

                                            This seems to be fixed with the latest build 2.2-RC (amd64) built on Fri Jan 09 01:08:06 CST 2015

                                            ldd /usr/local/sbin/check_reload_status
/usr/local/sbin/check_reload_status:
        libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000)
        libevent-2.0.so.5 => /usr/local/lib/libevent-2.0.so.5 (0x800a4f000)
        libc.so.7 => /lib/libc.so.7 (0x800c91000)
        libthr.so.3 => /lib/libthr.so.3 (0x801023000)

                                            thanks for the steps, I'm learning a lot

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