Snort inilization failure
-
Thanks Scott.
-
Didn't do that for me, BUT it also didn't trigger any alerts
-
Try running a port scan from http://www.grc.com. You should see it appear in alert as a ping.
-
I'm pretty much screwed with the same alert after I upgraded SNORT. Now the service will not start and stay running.
-
Scott, I see where you reverted snort back to the 2.6.0.2.5. I reverted back to that version and I'm still getting the same error. The trouble must be in the latest snapshot.
-
Try running a port scan from http://www.grc.com. You should see it appear in alert as a ping.
I know, and it doesn't.
I've reverted back to the older version and it still doesn't raise any alerts at all ???
-
What snapshot are you running? I'm thinking it has something to do with that since I too reverted back to the older version of snort.
-
Version 1.01
-
What snapshot are you running? I'm thinking it has something to do with that since I too reverted back to the older version of snort.
1.0.1-SNAPSHOT-11-19-2006
-
Well, it boiled down to me just re-installing pfSense(1.01) and re-installing SNORT. It started fine. I kept getting could not open alert file…..no matter what I did.......but now (keeping my fingers crossed) everything looks good.
-
I think I'd rather do without snort than re-install from scratch
-
Backup your configuration, reinstall, restore configuration.
It takes about 6 minutes on a 800 mhz machine.
-
If you backup your configuration to a media (floppy/USB stick) to /conf/config.xml your users will only see 2 short downtimes while the pfSense is rebooting. The livecd will come up with your old config and the system will be usable while you are installing it to the hdd ;)
-
Thanks Hoba, I'll give that a try later.
Oh, Fyi everyone, I've taken on a little issue I saw with snort. I've been wanting an easy way to enable, disable, and edit snort rules. So I've started workin on this. It's not done yet, but the screenshot below shows the progress I've made in the last day.
Right now I've got it to list the rules in a cleaner format, but they are not yet editable.
Enjoy.
 -
Thanks Hoba, I'll give that a try later.
Oh, Fyi everyone, I've taken on a little issue I saw with snort. I've been wanting an easy way to enable, disable, and edit snort rules. So I've started workin on this. It's not done yet, but the screenshot below shows the progress I've made in the last day.
Right now I've got it to list the rules in a cleaner format, but they are not yet editable.
Enjoy.
Nice!
-
Thanks. I plan on having it look very similar to the firewall rules. Right now functionality is what I am focusing on. Then I will make it look pretty :).
-
~~No go for me.
I've tried everything.
Fresh install of 1.0.1. No config file uploaded. Downloaded snort, enter info, and nothing starts up. I'm not getting the error "can't read alert file", but snort is not starting up.~~
Nevermind, it helps to enable rules. all good now :).
-
If I upgrade to the latest snapshot from 1.0.1 with snort already installed, I get unable to open alert file errors.
-
Ok. I am totally perplexed here. I can't get snort running at all now. After upgrading to the 11-29 snapshot last night, I got unable to open snort alert file errors.
So I reinstalled 1.0.1, did not import config, installed snort, entered the snort code, etc, and now it won't start up.
I've downloaded the rules, enabled them, etc. Still nothing :(.
Also, when I upgraded to 11-29 snapshot, it took FOREVER. I'm talking about an hour and a half to upload the file before I got the prompt to install the firmware. I have never gotten that type of response before.
Anyone else having these issues?
Here's the log error Im getting with 1.0.1 and snort 2.6.0.2.5
Nov 30 22:27:46 snort[17160]: Daemon parent exiting
Nov 30 22:27:46 snort[17160]: Daemon parent exiting
Nov 30 22:27:46 snort[17160]: Child exited unexpectedly
Nov 30 22:27:46 snort[17160]: Child exited unexpectedly
Nov 30 22:27:45 snort[17176]: FATAL ERROR: Failed to Lock PID File "/var/run//snort_sis0.pid" for PID "17176"
Nov 30 22:27:45 snort[17176]: FATAL ERROR: Failed to Lock PID File "/var/run//snort_sis0.pid" for PID "17176"
Nov 30 22:27:45 snort[17176]: PID path stat checked out ok, PID path set to /var/run/
Nov 30 22:27:45 snort[17176]: PID path stat checked out ok, PID path set to /var/run/ -
Not sure about that one unless FreeBSD 6.2 is causing the issue. I'm sorta tied up at the moment but will check into it as soon as I get some free cycles.