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

mbmb

@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

jimp

Whoops, how about now?

sprout

@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

jimp

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

feadin

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.

jimp

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

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

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.

sronsen

@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.

taryezveb

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.

dwood

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! :-)