Snort Stable 2.9.2.3 pkg v. 2.2 Failed
-
Snort Stable 2.9.2.3 pkg v. 2.2.1 (AMD64) won't start
After removing Snort Snort Stable 2.9.2.3 pkg v. 2.2 and reinstalling Snort Stable 2.9.2.3 pkg v. 2.2.1 snort won't start.
No messages in the system log, only "Jun 15 08:58:09 pfsense SnortStartup[46856]: Snort HARD START For xxxxx_em1…"Tried removing, rebooting, reinstalling, same issue.
(Only had snort widget as an added package.) -
Same for my case!
Snort Stable 2.9.2.3 pkg v. 2.2.1 (AMD64) won't start
If I try to start the snort from Services menu, I get this in System logs
- SnortStartup[43771]: Snort HARD START For 49607_em1…
From snort interface - start, I get this message,
- SnortStartup[24252]: Interface Rule START for 0_40330_em1…
- SnortStartup[59413]: Toggle for 40330_em1…
But services and snort interface shows that snort is not running.
Pfsense 2.0.1-RELEASE (amd64)
-
If you do not get anything on the system logs probably the package did not install at all!?
Is the snort binary installed? -
@ermal:
If you do not get anything on the system logs probably the package did not install at all!?
Is the snort binary installed?How do I check for that? I'm a total FreeBSD noob :)
-
I added explicit dependencies on the package instalaltion so it pulls the right packages needed.
Can you try after 10 minutes from this post and see? -
I tried installation once again. But still same problem. ???
-
Same here with fresh installation on a Virtualbox VM running
2.0.1-RELEASE (amd64)
built on Mon Dec 12 18:16:13 EST 2011FreeBSD 8.1-RELEASE-p6
Only log line generated: SnortStartup[48564]: Snort HARD START For 23366_em1…
I only did basic settings and installed + configured snort with 1 rule category selected.
-
@ermal:
Has anyone else noticed on their Snort > Blocked (tab) that the ALERT DESCRIPTION next to each IP now says "N/A" instead of displaying a full description as it has in the past?
I've confirmed under Snort > Global Settings, my Alert file description type = FULL.
Is there any way to restore this functionality so that full alert description is listed?
It should work on latest version 2.2.1
This is still not working in the latest version 2.2.1
-
pfSense 2.1-BETA0 (amd64) built on Thu Jun 14 14:23:20 EDT 2012
snort 2.9.2.3 pkg v. 2.2.1snort will not start.
System Log:
Jun 15 07:56:44 snort[49817]: FATAL ERROR: /usr/local/etc/snort/snort_39668_em0/snort.conf(324) Unknown output plugin: "alert_pf"
Jun 15 07:56:44 snort[49817]: FATAL ERROR: /usr/local/etc/snort/snort_39668_em0/snort.conf(324) Unknown output plugin: "alert_pf" -
@ermal
Snort Stable 2.9.2.3 pkg v. 2.2.1 (AMD64)
Tried running snort from shell:
/libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layout -
Was daq-0.6.2.tbz introduced recently? Since daq depends on libpcap-1.2.1 and snort on libpcap-1.1.1_1 maybe that be the source of the problems? I don't know if libdnet uses libpcap or daq (at time of compilation or later), but if it does maybe there is the issue.
-
Been running Snort 2.9.2.3 pkg v. 2.2 (AMD64) for more than 2 full days. Everything appears to be working properly, with the exception of the dashboard widget, which I noted in an earlier post. However, it now appears that Snort is shutting down and not restarting twice-a-day. I suspect this coincides with my 12 hour update update schedule, but I can't confirm since update attempts are not logged. The shutdowns leave no log entries either.
I am able to restart Snort manually after these incidents.
Can anyone confirm this behavior on another system?
-
@ermal:
The issue with old code that is present when you upgrade to a new version will be there even when you reinstall since the damage from old code will be done.
Feadin,
that is why for 2.1 we are moving to PBIs to make especially this dependency issues go away once and for good.
For now you have to clean your environment from other packages you have as well and reinstall again.So, my question is… how does one clean the environment to stop this error:
/libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layout(e.g. what do I uninstall and install to stop this?)
-
Been running Snort 2.9.2.3 pkg v. 2.2 (AMD64) for more than 2 full days. Everything appears to be working properly, with the exception of the dashboard widget, which I noted in an earlier post. However, it now appears that Snort is shutting down and not restarting twice-a-day. I suspect this coincides with my 12 hour update update schedule, but I can't confirm since update attempts are not logged. The shutdowns leave no log entries either.
I am able to restart Snort manually after these incidents.
Can anyone confirm this behavior on another system?
I had this problem. It appears to have been a problem with the cron job that deletes blocked ip's after a set time. I fixed it by going into the general tab and selecting never, then saved, then reselected the amount of time I wanted and clicked save again. This deleted and recreated the cron job. When this was happen there was nothing in the logs either.
-
Just an update. I installed a clean pfSense 2.0.1 on a new VM, right after that I installed the snort package and it says the usual (screenshot attached)
 -
/libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layoutIs it possible that the 32bit version got put in the 64 repo for the latest snort package?
I could be way off base and I apologize if I'm making more noise than you need right now to fix this.
I am not much in the way of a freebsd coder.
BTW: Thank you for the attention you guys are giving this. I (the company I work for) paid for pfsense support for a couple of boxes so far and paid for 2 sensors of snort.
As soon as I can, I'll be personally buying some beer and chips for a couple of you guys via your "donate" buttons. -
Been running Snort 2.9.2.3 pkg v. 2.2 (AMD64) for more than 2 full days. Everything appears to be working properly, with the exception of the dashboard widget, which I noted in an earlier post. However, it now appears that Snort is shutting down and not restarting twice-a-day. I suspect this coincides with my 12 hour update update schedule, but I can't confirm since update attempts are not logged. The shutdowns leave no log entries either.
I am able to restart Snort manually after these incidents.
Can anyone confirm this behavior on another system?
I had this problem. It appears to have been a problem with the cron job that deletes blocked ip's after a set time. I fixed it by going into the general tab and selecting never, then saved, then reselected the amount of time I wanted and clicked save again. This deleted and recreated the cron job. When this was happen there was nothing in the logs either.
This seems to have worked. Snort has gone thru an automated rules update without stopping after following these steps. BTW, Snort updates are logged to /tmp/snort_update.log, although previous entries record that Snort restarted. I don't think that's accurate. It just indicates that a restart was executed, not necessarily successfully. However, the log does report the date/time of the activity which, if no Snort alerts are received after a scheduled update, may lend evidence that there's a cron job failure.
mschiek - thanks for the help.
Update: Fix one problem - find another. An hour after successfully updating, logged error:
kernel: pid 25427 (snort), uid 0: exited on signal 10
The shutdown was preceded with this entry at the same recorded time:
snort[25427]: [1:2008578:6] ET SCAN Sipvicious Scan [Classification: Attempted Information Leak] [Priority: 2] {UDP} 109.169.37.117:5065 -> [my address]:5060
Any ideas as to what's going on?
-
Been running Snort 2.9.2.3 pkg v. 2.2 (AMD64) for more than 2 full days. Everything appears to be working properly, with the exception of the dashboard widget, which I noted in an earlier post. However, it now appears that Snort is shutting down and not restarting twice-a-day. I suspect this coincides with my 12 hour update update schedule, but I can't confirm since update attempts are not logged. The shutdowns leave no log entries either.
I am able to restart Snort manually after these incidents.
Can anyone confirm this behavior on another system?
I had this problem. It appears to have been a problem with the cron job that deletes blocked ip's after a set time. I fixed it by going into the general tab and selecting never, then saved, then reselected the amount of time I wanted and clicked save again. This deleted and recreated the cron job. When this was happen there was nothing in the logs either.
This seems to have worked. Snort has gone thru an automated rules update without stopping after following these steps. BTW, Snort updates are logged to /tmp/snort_update.log, although previous entries record that Snort restarted. I don't think that's accurate. It just indicates that a restart was executed, not necessarily successfully. However, the log does report the date/time of the activity which, if no Snort alerts are received after a scheduled update, may lend evidence that there's a cron job failure.
mschiek - thanks for the help.
Update: Fix one problem - find another. An hour after successfully updating, logged error:
kernel: pid 25427 (snort), uid 0: exited on signal 10
The shutdown was preceded with this entry at the same recorded time:
snort[25427]: [1:2008578:6] ET SCAN Sipvicious Scan [Classification: Attempted Information Leak] [Priority: 2] {UDP} 109.169.37.117:5065 -> [my address]:5060
Any ideas as to what's going on?
I have had that error as well and I have not figured out as of yet what is causing it. After this error the snort process on the interface starts normally and it has not stopped again which is even more confusing.
BTW- What do you have your mem performance settings set at?, also how many wan interfaces do you have? I am just trying to figure out a common thread to this.
-
Greetings to the community!
This is my first posting - I was reading here and using pfSense for several months now. Its a good opportunity to say thank you very much for your efforts and this really great system.
Since the Snort updates of course I too get errors. Package 2.2 was ok, but also went down on my amd64 installation without obvious reason (after about 16 hours working and blocking). Since the new version 2.9.2.3 pkg v 2.2.1 it does not start at all.
My logs show an unknown preprocessor fatal error. Maybe it helps:Jun 15 21:59:02 gatekeeper snort[33708]: FATAL ERROR: /usr/local/etc/snort/snort_26132_em1/snort.conf(180) Unknown preprocessor: "ftp_telnet".
Jun 15 21:59:02 gatekeeper SnortStartup[33762]: Interface Rule START for 0_26132_em1…If I disable ftp/telnet preprocessor the next fatal error pops-up with smtp.
Greetings and again a big Thank you to all developers!
Jud3x
-
Jun 15 21:59:02 gatekeeper snort[33708]: FATAL ERROR: /usr/local/etc/snort/snort_26132_em1/snort.conf(180) Unknown preprocessor: "ftp_telnet".
Jun 15 21:59:02 gatekeeper SnortStartup[33762]: Interface Rule START for 0_26132_em1…
This just means your install had failed and or the package was missing files.
In order to solve the issue you have to remove snort pkg_delete snort it should show you that files are missing and you want to delite any snort leftover files next go to packages and reinstall snort readownload rules and your snort should be working .
There are posted directions in this forum on how to remove snort.