Snort inilization failure
-
Not any more, although it took a complete format and reinstall (without restoring the backed up .conf files) to get it to work.
Also ACS is the only mode that seems to work reliably for me, try setting that if you haven't already -
@sdale:
PC_Arcade, Coldfusion, are you guys having any troubles getting snort to start in 1.0.1?
I find that if I reboot pfSense, SNORT starts then exits. I have to hit save on the SNORT settings tab to restart SNORT….then it stays up and running. The weird thing is when SNORT exits...I go to the Services tab and it shows that it is running, but it's not. The other thing that I should mention is that if I make any changes to the system, SNORT seems to restart and stays running like it's supposed to. It only seems to happen after a reboot of the system. The good thing though is that it's not core dumping as before.
-
Not any more, although it took a complete format and reinstall (without restoring the backed up .conf files) to get it to work.
Also ACS is the only mode that seems to work reliably for me, try setting that if you haven't alreadyDitto for me….same method
-
Ok, same here. If I restore config it does not work either. Bill or scott, any idea why that is?
-
Not any more, although it took a complete format and reinstall (without restoring the backed up .conf files) to get it to work.
Also ACS is the only mode that seems to work reliably for me, try setting that if you haven't alreadyWere you able to import your config after you got snort started and snort continue to run?
-
Were you able to import your config after you got snort started and snort continue to run?
No, originally Iwas getting could not read alert file…I had to re-install pfsense. importing the config did not help.....also in order to keep it running only ACS mode seems to work otherwise you get a core dump.
I saved my conf. without the packages, then reinstalled pfsense restoring the config without the SNORT configs. Re-installed Snort and was good to go after that. -
No, originally Iwas getting could not read alert file…I had to re-install pfsense. importing the config did not help.....also in order to keep it running only ACS mode seems to work otherwise you get a core dump.
I saved my conf. without the packages, then reinstalled pfsense restoring the config without the SNORT configs. Re-installed Snort and was good to go after that.Ok. I will try that and see what I get.
-
I upgraded to snapshot 12-04 and I am not getting anymore failed to open alert file errors. Woot. Although snort will still not startup for me. It just gets in a continuous bootup cycle. I had to uninstall it. It was chewing up my resources :(.
Oddly enough, when I uninstalled it, it didnt remove snort. When I rebooted after uninstalling, snort processes booted up. I had to manually remove all snort files to stop this.
And also I had to hit reboot twice for my system to reboot. ???
Anyone else able to confirm?
-
@sdale:
I upgraded to snapshot 12-04 and I am not getting anymore failed to open alert file errors. Woot. Although snort will still not startup for me. It just gets in a continuous bootup cycle. I had to uninstall it. It was chewing up my resources :(.
Oddly enough, when I uninstalled it, it didnt remove snort. When I rebooted after uninstalling, snort processes booted up. I had to manually remove all snort files to stop this.
And also I had to hit reboot twice for my system to reboot. ???
Anyone else able to confirm?
I upgraded to snapshot 12-04 and it was chewing up my resources also…..memory was running about 8% higher and the CPU was pinned constantly to 100%. I thought maybe it was SNORT because it kept recycling. I also stopped the service but it still kept running and would not kill. I uninstalled SNORT but the processor was still pinned. I rebooted to no avail. I finally resorted back to SNAPSHOT 11-30.....but it was still pinned. I had to restore my config in order for everything to work properly. SNORT now works fine again. The CPU consumption is also back to normal. I'll try upgrading again today and see what happens.
-
@sdale:
I upgraded to snapshot 12-04 and I am not getting anymore failed to open alert file errors. Woot. Although snort will still not startup for me. It just gets in a continuous bootup cycle. I had to uninstall it. It was chewing up my resources :(.
Oddly enough, when I uninstalled it, it didnt remove snort. When I rebooted after uninstalling, snort processes booted up. I had to manually remove all snort files to stop this.
And also I had to hit reboot twice for my system to reboot. ???
Anyone else able to confirm?
I upgraded to snapshot 12-04 and it was chewing up my resources also…..memory was running about 8% higher and the CPU was pinned constantly to 100%. I thought maybe it was SNORT because it kept recycling. I also stopped the service but it still kept running and would not kill. I uninstalled SNORT but the processor was still pinned. I rebooted to no avail. I finally resorted back to SNAPSHOT 11-30.....but it was still pinned. I had to restore my config in order for everything to work properly. SNORT now works fine again. The CPU consumption is also back to normal. I'll try upgrading again today and see what happens.
I reverted back to the 11-30 snapshot as well. Now I'm getting unable to open alert file errors again.
-
Don't forget to save the snort settings after each upgrade/downgrade!
-
Don't forget to save the snort settings after each upgrade/downgrade!
Yep. I did that. Still getting unable to open alert file with the 11-30 snapshot, and continuous bootup cycle with the 12-4 snapshot.
-
I upgraded to 12-05 snapshot, and when I install snort I get stuck at Executing custom_php_install_command()…
-
Well I updated to 1.0.1-SNAPSHOT-12-05-2006 and everything seems fine. CPU and memory usage are normal. I guess the upgrade didn't take well the first time. I'll see how this goes.
sdale my alert file problem was resolved by reinstalling pfsense and snort and I haven't been getting the can't open alert file since the 11-25 SNAPSHOT. I just restored my config without the packages. It took all of 15 minutes. -
Well Im not sure what's going on, but I cant get mine to work. I tried all your suggestions and still nothing. Just keeps exiting :(.
-
Ok, after reformatting like 30 times, I've determined that one or more of the rulesets is causing snort to abort. I'll get back when I determine which one it is.
Update:
OK so I finally got some time to sit down and troubleshoot the crap out of this.
I reformatted to 1.0.1, installed snort, check ALL rulesets, snort would not bootup. Keeps failing, with no error code given.Using the same install, I finally determined that by un-checking the p2p.rules and web-misc.rule sets I can get snort to bootup. ???
Now, before you say its a ram issue, its not. With snort up and running, it only consumes 55-60% ram.
To confirm, I tried enabling just those two rules, and snort would not bootup.
I am not sure what in those files is preventing snort from booting up, but something is. Can anyone confirm my evaluation?
-
when I upgrade to 12-05 snapshot, reinstall snort, save settings, I get this error:
Dec 7 21:13:50 snort[4264]: FATAL ERROR: Failed to Lock PID File "/var/run//snort_sis0.pid" for PID "4264"
Dec 7 21:13:50 snort[4264]: FATAL ERROR: Failed to Lock PID File "/var/run//snort_sis0.pid" for PID "4264"
Dec 7 21:13:50 snort[4264]: PID path stat checked out ok, PID path set to /var/run/
Dec 7 21:13:50 snort[4264]: PID path stat checked out ok, PID path set to /var/run/
Dec 7 21:13:50 snort[4264]: Var 'sis0_ADDRESS' redefined
Dec 7 21:13:50 snort[4264]: Var 'sis0_ADDRESS' redefined
Dec 7 21:13:50 snort[4247]: Initializing daemon modeAlso, if I have backdoor.rules enabled, snort aborts. Says:
Dec 7 21:18:14 snort2c[5648]: snort2c running in daemon mode pid: 5648
Dec 7 21:18:14 snort2c[5648]: snort2c running in daemon mode pid: 5648
Dec 7 21:18:14 snort[5645]: FATAL ERROR: /usr/local/etc/snort/rules/backdoor.rules(643) => Unknown rule type: )
Dec 7 21:18:14 snort[5645]: FATAL ERROR: /usr/local/etc/snort/rules/backdoor.rules(643) => Unknown rule type: )
Dec 7 21:18:14 snort[5645]: Ports to decode telnet on: 21 23 25 119
Dec 7 21:18:14 snort[5645]: Ports to decode telnet on: 21 23 25 119Also getting
Dec 7 21:19:17 snort[5970]: FATAL ERROR: ParseRuleFile : Line 642 too long, 'alert tcp $EXTERNAL_NET $HTTP_…'
Dec 7 21:19:17 snort[5970]: FATAL ERROR: ParseRuleFile : Line 642 too long, 'alert tcp $EXTERNAL_NET $HTTP_…' -
@sdale:
when I upgrade to 12-05 snapshot, reinstall snort, save settings, I get this error:
Dec 7 21:13:50 snort[4264]: FATAL ERROR: Failed to Lock PID File "/var/run//snort_sis0.pid" for PID "4264"
Dec 7 21:13:50 snort[4264]: FATAL ERROR: Failed to Lock PID File "/var/run//snort_sis0.pid" for PID "4264"
Dec 7 21:13:50 snort[4264]: PID path stat checked out ok, PID path set to /var/run/
Dec 7 21:13:50 snort[4264]: PID path stat checked out ok, PID path set to /var/run/
Dec 7 21:13:50 snort[4264]: Var 'sis0_ADDRESS' redefined
Dec 7 21:13:50 snort[4264]: Var 'sis0_ADDRESS' redefined
Dec 7 21:13:50 snort[4247]: Initializing daemon modeAlso, if I have backdoor.rules enabled, snort aborts. Says:
Dec 7 21:18:14 snort2c[5648]: snort2c running in daemon mode pid: 5648
Dec 7 21:18:14 snort2c[5648]: snort2c running in daemon mode pid: 5648
Dec 7 21:18:14 snort[5645]: FATAL ERROR: /usr/local/etc/snort/rules/backdoor.rules(643) => Unknown rule type: )
Dec 7 21:18:14 snort[5645]: FATAL ERROR: /usr/local/etc/snort/rules/backdoor.rules(643) => Unknown rule type: )
Dec 7 21:18:14 snort[5645]: Ports to decode telnet on: 21 23 25 119
Dec 7 21:18:14 snort[5645]: Ports to decode telnet on: 21 23 25 119Also getting
Dec 7 21:19:17 snort[5970]: FATAL ERROR: ParseRuleFile : Line 642 too long, 'alert tcp $EXTERNAL_NET $HTTP_…'
Dec 7 21:19:17 snort[5970]: FATAL ERROR: ParseRuleFile : Line 642 too long, 'alert tcp $EXTERNAL_NET $HTTP_…'These are rule related problems. I have no idea how to fix these, you are somewhat on your own here.
-
These are rule related problems. I have no idea how to fix these, you are somewhat on your own here.
Yea, I'm taking a look into it.
-
@sdale:
These are rule related problems. I have no idea how to fix these, you are somewhat on your own here.
Yea, I'm taking a look into it.
I found the problem. It lies within my edit rule file. I will send the diff soon as I get it completed.