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
    18
    60
    19.2k
    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.
    • N
      Nevski
      last edited by

      Hi,

      try ln -s /usr/pbi/squid-i386/local/lib/libmd5.so.0 /usr/lib/ (creates a symlink of the file from the squid directory to /usr/lib/)

      Worked for me.

      I'm running pfSense 2.2Beta and got the same error after upgrading from pkg Squid 3.3.11 to 3.3.13

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

        I haven't had any luck with the 2 latest versions, 3.3.13_2 and 3.4.9_1. Anyway of rolling back to the previous version?

        squid 3.3.13_2
        php-fpm[96097]: /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 '1', the output was 'squid: ERROR: No running copy'

        a bunch of starts and stops followed by

        squid[58837]: Exiting due to repeated, frequent failures

        squid 3.4.9_1
        php-fpm[79482]: /pkg_edit.php: The command '/usr/pbi/squid-amd64/local/sbin/squid -z -f /usr/pbi/squid-amd64/local/etc/squid/squid.conf' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"'

        1 Reply Last reply Reply Quote 0
        • N
          nelsonbt2001
          last edited by

          tried symlinking lbmd5.so.0 into /usr/lib, and that got rid of that error in the syslog, but it still wouldn't start. No new errors in the syslog, though, which seemed odd.

          Did another firmware upgrade today (so now versions 2.2-BETA (i386) built on Thu Dec 04 08:23:23 CST 2014 FreeBSD 10.1-RELEASE and squid3 3.4.9_1 pkg 0.1).

          Tried again symlinking libmd5.so.0 and got a bit further. Started getting the following:

          squid: MIME Config Table /usr/local/etc/squid/mime.conf: (2) No such file or directory

          Found that file in the squid's package directory, so I tied symlinking that too. Cleared that error but then  I got:

          squid: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory

          I stopped after that error. Sure seems like something is wrong with the chroot since it keeps looking for files in the system directories that it has in its package directory.

          1 Reply Last reply Reply Quote 0
          • H
            hmh
            last edited by

            It working if you create all symlinks for missing components

            ln -s /lib/libmd.so.6 /usr/lib/libmd5.so.0
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
            1 Reply Last reply Reply Quote 0
            • R
              rexki
              last edited by

              I am getting the config pathing errors as well after upgrading to 2.2 rc x64,  some breaking squid glass in the background noise.

              The above do not work as it appears they are incorrect for my default system of 2.2 RC x64"

              /usr/local/etc/squid/squid.conf and target of /usr/pbi/squid-amd64/etc/squid   notice the non existent /local/ from above.

              Have to engineer some ln command to undue and redo it correctly!!

              I have two sets of configs that appear to be valid and equivalent: 
              1.  /usr/pbi/squid-amd64/local/etc/squid/squid.conf
              2.  /usr/pbi/squid-amd64/local/local/etc/squid/squid.conf

              Now I am getting crash reports as follows:

              amd64
              10.1-RELEASE
              FreeBSD 10.1-RELEASE #0 29f4af5(releng/10.1)-dirty: Tue Dec  9 10:21:46 CST 2014    root@pfsense-22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10

              Crash report details:

              Filename: /var/crash/crashreport_header.txt
              Crash report begins.  Anonymous machine information:

              amd64
              10.1-RELEASE
              FreeBSD 10.1-RELEASE #0 29f4af5(releng/10.1)-dirty: Tue Dec  9 10:21:46 CST 2014    root@pfsense-22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10

              Crash report details:

              Filename: /var/crash/minfree
              2048

              Uninstalled ipguard and now I am getting this crash report:

              Crash report begins.  Anonymous machine information:

              amd64
              10.1-RELEASE
              FreeBSD 10.1-RELEASE #0 29f4af5(releng/10.1)-dirty: Tue Dec  9 10:21:46 CST 2014    root@pfsense-22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10

              Crash report details:

              PHP Errors:
              [14-Dec-2014 17:42:25 US/Central] PHP Fatal error:  Maximum execution time of 900 seconds exceeded in /usr/local/pkg/squid.inc on line 94

              Removed SARG and then rebooted and have not gotten a crash report since - approx 1 hour

              pfSense 2.3.4-Release(amd64) - 31 watts Min d-power mode - 843-853 mbps across LANs -  i5-2400 3xGigE - Asus P8H61-M -All slotted Intel single NICS EM drivers -  shooting for 6 watts - to save $27/year in electricity.  In Hawaii $50 per year savings over 20 watt delta!!

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

                Installed via 2.2-RC 20150102-1450 snapshot: pfSense-LiveCD-2.2-RC-amd64-20150102-1450.iso
                Left everything at defaults.
                Installed squid3 package.  Version is  3.4.10.

                I got the same errors as everyone else about missing libraries, etc.

                The following four commands did it for me, but transparent proxy doesn't work.  Just get ACL errors.  See below.

                ln -s /usr/pbi/squid-amd64/local/lib/libmd5.so.0 /usr/lib/libmd5.so.0
                ln -s /usr/pbi/squid-amd64/local/lib/libecap.so.2 /usr/lib/libecap.so.2
                ln -s /usr/pbi/squid-amd64/local/etc/squid /usr/local/etc/squid
                ln -s /usr/pbi/squid-amd64/bin /usr/local/libexec/squid

                === ACL errors if used as transparent proxy ===
                ERROR

                The requested URL could not be retrieved

                The following error was encountered while trying to retrieve the URL: http://www.squid-cache.org/Doc/config/maximum_object_size/

                Connection to 2001:4b78:2003::1 failed.

                The system returned: (101) Network is unreachable

                The remote host or network may be down. Please try the request again.

                Your cache administrator is webmaster.

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

                  All four errors for your reference.

                  [2.2-RC][admin@pfSense.localdomain]/var/squid: Shared object "libmd5.so.0" not found, required by "squid"
                  Shared object "libmd5.so.0" not found, required by "squid"
                  Shared object "libmd5.so.0" not found, required by "squid"
                  Shared object "libmd5.so.0" not found, required by "squid"
                  Shared object "libmd5.so.0" not found, required by "squid"

                  [2.2-RC][admin@pfSense.localdomain]/var/squid: Shared object "libecap.so.2" not found, required by "squid"
                  Shared object "libecap.so.2" not found, required by "squid"
                  Shared object "libecap.so.2" not found, required by "squid"
                  Shared object "libecap.so.2" not found, required by "squid"
                  Shared object "libecap.so.2" not found, required by "squid"

                  [2.2-RC][admin@pfSense.localdomain]/var/squid: FATAL: Unable to open configuration file: /usr/local/etc/squid/squid.conf: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.010 seconds = 0.010 user + 0.000 sys
                  Maximum Resident Size: 50592 KB
                  Page faults with physical i/o: 0
                  FATAL: Unable to open configuration file: /usr/local/etc/squid/squid.conf: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.009 seconds = 0.009 user + 0.000 sys
                  Maximum Resident Size: 45744 KB
                  Page faults with physical i/o: 0
                  FATAL: Unable to open configuration file: /usr/local/etc/squid/squid.conf: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.009 seconds = 0.009 user + 0.000 sys
                  Maximum Resident Size: 46256 KB
                  Page faults with physical i/o: 0
                  FATAL: Unable to open configuration file: /usr/local/etc/squid/squid.conf: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.009 seconds = 0.009 user + 0.000 sys
                  Maximum Resident Size: 46256 KB
                  Page faults with physical i/o: 0
                  FATAL: Unable to open configuration file: /usr/local/etc/squid/squid.conf: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.009 seconds = 0.009 user + 0.000 sys
                  Maximum Resident Size: 46080 KB
                  Page faults with physical i/o: 0

                  [2.2-RC][admin@pfSense.localdomain]/var/squid: 2015/01/04 14:28:52 kid1| ERROR: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  FATAL: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.010 seconds = 0.010 user + 0.000 sys
                  Maximum Resident Size: 46256 KB
                  Page faults with physical i/o: 0
                  2015/01/04 14:28:55 kid1| ERROR: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  FATAL: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.010 seconds = 0.005 user + 0.005 sys
                  Maximum Resident Size: 51088 KB
                  Page faults with physical i/o: 0
                  2015/01/04 14:28:58 kid1| ERROR: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  FATAL: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.010 seconds = 0.000 user + 0.010 sys
                  Maximum Resident Size: 46080 KB
                  Page faults with physical i/o: 0
                  2015/01/04 14:29:01 kid1| ERROR: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  FATAL: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.010 seconds = 0.010 user + 0.000 sys
                  Maximum Resident Size: 46256 KB
                  Page faults with physical i/o: 0
                  2015/01/04 14:29:04 kid1| ERROR: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  FATAL: unlinkd_program /usr/local/libexec/squid/unlinkd: (2) No such file or directory
                  Squid Cache (Version 3.4.10): Terminated abnormally.
                  CPU Usage: 0.010 seconds = 0.010 user + 0.000 sys
                  Maximum Resident Size: 46080 KB
                  Page faults with physical i/o: 0

                  1 Reply Last reply Reply Quote 0
                  • 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
                                            • First post
                                              Last post