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

    Snort: 2.9.2.3 pkg v. 2.2.1 /usr/local/lib/libdnet.1: unsupported file layout

    Scheduled Pinned Locked Moved pfSense Packages
    25 Posts 13 Posters 9.3k 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.
    • M
      mschiek01
      last edited by

      @mbmb:

      Hello

      I have the same problem as reported by many others, after upgrade of snort to 2.9.2.3 pkg v. 2.2.1, Snort won't start
      anymore. When trying to start it from the command line i get:
      /libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layout

      I'm running 2.0.1-RELEASE (amd64)

      Checking a few things:
      file /libexec/ld-elf.so.1
      /libexec/ld-elf.so.1: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped
      file /usr/local/lib/libdnet.1
      /usr/local/lib/libdnet.1: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped

      file /usr/local/bin/snort
      /usr/local/bin/snort: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.1, stripped

      Why is Snort a 32bit executable? in a supposedly 64bit package??????????????????

      Hope someone comes up with a solution soon.

      See this post:

      http://forum.pfsense.org/index.php/topic,50609.0.html

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        remove/reinstall and see if this is OK now. I uploaded a new 64-bit binary package a few minutes ago.

        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
        • F
          feadin
          last edited by

          @jimp:

          remove/reinstall and see if this is OK now. I uploaded a new 64-bit binary package a few minutes ago.

          It runs now, but there's a new error:

          Jun 19 13:36:19	snort[5114]: FATAL ERROR: /usr/local/etc/snort/snort_13270_re0/snort.conf(324) Unknown output plugin: "alert_pf"
          Jun 19 13:36:19	snort[5114]: FATAL ERROR: /usr/local/etc/snort/snort_13270_re0/snort.conf(324) Unknown output plugin: "alert_pf"
          

          It only goes away if I disable the "Block Offenders" option, but I don't want to do that. That option is the main reason why I want to use snort.

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

            @mschiek01:

            @mbmb:

            Hello

            I have the same problem as reported by many others, after upgrade of snort to 2.9.2.3 pkg v. 2.2.1, Snort won't start
            anymore. When trying to start it from the command line i get:
            /libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layout

            I'm running 2.0.1-RELEASE (amd64)

            Checking a few things:
            file /libexec/ld-elf.so.1
            /libexec/ld-elf.so.1: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped
            file /usr/local/lib/libdnet.1
            /usr/local/lib/libdnet.1: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped

            file /usr/local/bin/snort
            /usr/local/bin/snort: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.1, stripped

            Why is Snort a 32bit executable? in a supposedly 64bit package??????????????????

            Hope someone comes up with a solution soon.

            See this post:

            http://forum.pfsense.org/index.php/topic,50609.0.html

            Tried the above post, no luck!

            Setting my hope to the newly build package

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              Whoops, how about now?

              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
              • S
                sprout
                last edited by

                @jimp:

                remove/reinstall and see if this is OK now. I uploaded a new 64-bit binary package a few minutes ago.

                Great stuff jimp! the pig is flying again thanks to you :D

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  I'd prefer to see it roasting on a spit, but to each his own :p

                  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
                  • F
                    feadin
                    last edited by

                    Great! It's working now, thank you! :)
                    One last thing… the logs are all duplicated, both in the Alerts menu and in the System Logs too. Not only the alerts but all snort logs including the snort startup messages.
                    Regular non-snort logs are fine.

                    1 Reply Last reply Reply Quote 0
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      I'd start a new thread for anything that isn't directly related to the error in the subject line.

                      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
                      • S
                        sronsen
                        last edited by

                        Uninstalled, cleaned up left-over files and reinstalled from package installer.

                        Still getting /libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layout

                        1 Reply Last reply Reply Quote 0
                        • F
                          feadin
                          last edited by

                          @sronsen:

                          Uninstalled, cleaned up left-over files and reinstalled from package installer.

                          Still getting /libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layout

                          What exactly did you clean up? I had that problem but now it's fixed for me (found new problems though).
                          You may want to try doing a pkg_info to see all installed packages and then manually removing every related package with pkg_delete -f. The important packages you should remove are libpcap, libnet, libdnet, daq and of course snort as far as I remember. Also make sure you're not behind a proxy which may be caching the old files.

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

                            @Feadin:

                            @sronsen:

                            Uninstalled, cleaned up left-over files and reinstalled from package installer.

                            Still getting /libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layout

                            What exactly did you clean up? I had that problem but now it's fixed for me (found new problems though).
                            You may want to try doing a pkg_info to see all installed packages and then manually removing every related package with pkg_delete -f. The important packages you should remove are libpcap, libnet, libdnet, daq and of course snort as far as I remember. Also make sure you're not behind a proxy which may be caching the old files.

                            IT WORKED!  I can't convey how much I appreciate the help after ten days of trying to get snort working again.  I guess that one of the several packages I installed in that time had a bad libpcap, libnet, libdnet or daq package which wasn't being overwritten with a new snort install.

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

                              All is working great again. Would like to Thank jimp and the other Snort developers, that are working hard on the Snort package. Will donate again soon :D

                              Edit: To be clear, I'm talking about only this issue. Having other Snort issues similar to others on this forum.

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

                                This package does work now..however I could not stop the service.  It says it's stopped, but blocking continues.  You can stop the interfaces, but not the service via the dashboard.

                                To add SNORT HTTP_inspect suppression, (which ends up blocking pfsense.org if not added) I had to reboot the server.  However, because pfsense.org was blocked, I ended up having the SQUID update fail partway through.  On reboot…the PFSENSE install was damaged, so could shell in, but routing was broken.  Ack.

                                Therefore fresh reinstall required....just a heads up!  :-)

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