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

    Snort stops working after snort update (newest 2.0 RELEASE)

    Scheduled Pinned Locked Moved pfSense Packages
    113 Posts 25 Posters 60.7k 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
      miles267
      last edited by

      Since upgrading from a working 2.0 RC3 to 2.0-RELEASE, Snort consistently stops on my WAN connection following each Snort update (auto or manual).  It requires you to manually start it via Services > Snort > Snort Interfaces.  However it will then fail again the next snort definitions update and so on.  Has anyone identified a resolution for this behavior?

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

        same here.

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

          @serialdie:

          same here.

          Hi I noticed someone else recommended you change your snort interface settings to AC-BNFA mode to lower memory usage.  I was set to AC-STD prior to upgrade and everything worked fine.  Now that I changed to AC-BNFA after upgrade it appears to be working so far.  Will keep monitoring.

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

            @miles267:

            @serialdie:

            same here.

            Hi I noticed someone else recommended you change your snort interface settings to AC-BNFA mode to lower memory usage.  I was set to AC-STD prior to upgrade and everything worked fine.  Now that I changed to AC-BNFA after upgrade it appears to be working so far.  Will keep monitoring.

            I just changed it but I dont see how this can be an issue. I have 4Gigs of ram…
            Hopefully this does the job :)

            Thanks

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

              I too have 4 GB of RAM but somehow it seems to have resolved my issue and dramatically reduced my memory usage.

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

                @lonevipr:

                I made a post about this as well. However I just started trying to use it so don't know if it was an issue in the past. However I just tried to adjust my memory usage to AC-BNFA & my WAN interface still will not start.

                Perhaps I spoke too soon.  It would appear that, after, Snort performs its scheduled definitions update (and attempts to restart), it crashes.  I must then manually start each snort interface but monitor periodically to ensure they didn't stop.  Haven't yet identified any pattern in the logs to indicate what might be causing it to stop.  Also, am not quite convinced that changing memory setting from AC-STD to AC-BNFA has any impact at all.

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

                  @miles267:

                  @lonevipr:

                  I made a post about this as well. However I just started trying to use it so don't know if it was an issue in the past. However I just tried to adjust my memory usage to AC-BNFA & my WAN interface still will not start.

                  Perhaps I spoke too soon.  It would appear that, after, Snort performs its scheduled definitions update (and attempts to restart), it crashes.  I must then manually start each snort interface but monitor periodically to ensure they didn't stop.  Haven't yet identified any pattern in the logs to indicate what might be causing it to stop.  Also, am not quite convinced that changing memory setting from AC-STD to AC-BNFA has any impact at all.

                  As I thought.
                  I think the issue is that snort has some how change there definition pattern once again.

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

                    How is this thread not firing off sirens?  We surely aren't the only ones having this issue.  Would expect the majority of users are experiencing this but simply haven't checked their snort interface statuses to ensure they stay running (without a restart)

                    1 Reply Last reply Reply Quote 0
                    • E
                      eri--
                      last edited by

                      Well probably a bug in snort which does not like to reload the rulesets.
                      Maybe changing snort to stop and start again would be a better choice i guess.

                      1 Reply Last reply Reply Quote 0
                      • E
                        eri--
                        last edited by

                        BTW can you post the system logs here for review and hopefully fixing that?

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

                          ermal,

                          I been trying to catch it but is so random that I have been unable to… usually happens overnight...

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

                            Ermal here is the system log.
                            Sep 30 09:03:55 snort[5170]: Snort exiting
                            Sep 30 09:03:55 snort[5170]: Snort exiting
                            Sep 30 09:03:54 snort[6986]: Snort exiting
                            Sep 30 09:03:54 snort[6986]: Snort exiting
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2408044 type=Limit tracking=src count=1 seconds=60 filtered=8
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2408044 type=Limit tracking=src count=1 seconds=60 filtered=8
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2406628 type=Limit tracking=src count=1 seconds=60 filtered=18
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2406628 type=Limit tracking=src count=1 seconds=60 filtered=18
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2403304 type=Limit tracking=src count=1 seconds=3600 filtered=1
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2403304 type=Limit tracking=src count=1 seconds=3600 filtered=1
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2001569 type=Both tracking=src count=70 seconds=60 filtered=331
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2001569 type=Both tracking=src count=70 seconds=60 filtered=331
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2406036 type=Limit tracking=src count=1 seconds=60 filtered=4
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2406036 type=Limit tracking=src count=1 seconds=60 filtered=4
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2001579 type=Both tracking=src count=70 seconds=60 filtered=330
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2001579 type=Both tracking=src count=70 seconds=60 filtered=330
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2408002 type=Limit tracking=src count=1 seconds=60 filtered=31
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2408002 type=Limit tracking=src count=1 seconds=60 filtered=31
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2406690 type=Limit tracking=src count=1 seconds=60 filtered=2
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2406690 type=Limit tracking=src count=1 seconds=60 filtered=2
                            Sep 30 09:03:53 snort[5170]: | gen-id=1 sig-id=2403312 type=Limit tracking=src count=1 seconds=3600 filtered

                            1 Reply Last reply Reply Quote 0
                            • bmeeksB
                              bmeeks
                              last edited by

                              Just to add confirmation – I, too, have noticed this behavior of Snort not restarting upon a rules update.  However, you can immediately manually start it without issue.  Like one of the other posters, the only message in the log of note is "...snort exiting."  Not much help for troubleshooting.

                              I discovered my event by kicking off a manual update and then coming back an hour later to check that everything was cool.  Found pfSense running fine but Snort not running.  I looked in the log and saw only the "snort exiting" message.  I made no changes to anything and simply clicked the little green arrow icon to start Snort.  It then started up successfully.

                              This seems to have only occurred after my upgrade to the 2.0-Release.  Prior to that I was running the Release Candidate (RC3) and did not see this issue.

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

                                I'm experiencing the same problem since upgrading to 2.0-Release. The system log shows the usual Snort initialization messages but with the last one indicating 'Snort exiting' and it generally occurs just after midnight EST (I assume after a ruleset update …which I have set for once a day).

                                I also used to run with the AC-STD memory setting, but can no longer do so since the upgrade (Snort won't run for more than an hour or two with AC-STD, so I changed to AC-SPARSEBANDS). Last, Snort seems to take quite a bit longer to start up (several minutes) since the upgrade.

                                I hope that this problem is going to be investigated ... thx.

                                1 Reply Last reply Reply Quote 0
                                • X
                                  xarope
                                  last edited by

                                  I hate to post a "me too" reply, but unfortunately, me too. Snort 2.9.0.5 pkg 2.0, pfsense 2.0-RELEASE (i386)
                                  built on Tue Sep 13 17:28:43 EDT 2011.

                                  All I can find in the kernel log for snort is "snort exiting".  And as with the others, this always happens overnight.  Unlike the others, I had upgraded/updated to 2.0 final, a few weeks ago.  But only noticed this behaviour since, maybe end of last week?

                                  Prior to that, snort had been running ok.

                                  So I'm suspecting maybe it's one of the rules that's causing a problem?  From memory, one of the snort categories always caused me problems (e.g. snort_exploit.rules), so maybe another is doing the same thing?

                                  Update: I just tried a manual update of rules, and restarted snort.  Now the snort instance running on my WAN interface (AC-BNFA) has died a few minutes later (15 minutes), and with an error message "kernel: pid 23257 (snort), uid 920: exited on signal 11".  More logs:

                                  Oct 5 11:32:43 	snort[35687]: PID path stat checked out ok, PID path set to /var/log/snort/run
Oct 5 11:32:43 	snort[35687]: PID path stat checked out ok, PID path set to /var/log/snort/run
Oct 5 11:32:43 	snort[35687]: Writing PID "35687" to file "/var/log/snort/run/snort_em0_vlan78035309.pid"
Oct 5 11:32:43 	snort[35687]: Writing PID "35687" to file "/var/log/snort/run/snort_em0_vlan78035309.pid"
Oct 5 11:32:43 	snort[35687]: Set gid to 920
Oct 5 11:32:43 	snort[35687]: Set gid to 920
Oct 5 11:32:43 	snort[35687]: Set uid to 920
Oct 5 11:32:43 	snort[35687]: Set uid to 920
Oct 5 11:32:43 	snort[35687]:
Oct 5 11:32:43 	snort[35687]:
Oct 5 11:32:43 	snort[35687]: --== Initialization Complete ==--
Oct 5 11:32:43 	snort[35687]: --== Initialization Complete ==--
Oct 5 11:32:43 	snort[35687]: Commencing packet processing (pid=35687)
Oct 5 11:32:43 	snort[35687]: Commencing packet processing (pid=35687)
Oct 5 11:48:26 	kernel: pid 23257 (snort), uid 920: exited on signal 11
                                  1 Reply Last reply Reply Quote 0
                                  • X
                                    xarope
                                    last edited by

                                    And famous last words, now snort on the WAN interface is crashing regularly after a restart:

                                    Oct 5 12:52:44 	snort[14024]: Set uid to 920
Oct 5 12:52:44 	snort[14024]:
Oct 5 12:52:44 	snort[14024]:
Oct 5 12:52:44 	snort[14024]: --== Initialization Complete ==--
Oct 5 12:52:44 	snort[14024]: --== Initialization Complete ==--
Oct 5 12:52:44 	snort[14024]: Commencing packet processing (pid=14024)
Oct 5 12:52:44 	snort[14024]: Commencing packet processing (pid=14024)
Oct 5 13:42:06 	kernel: pid 14024 (snort), uid 920: exited on signal 11

                                    I'll have to start disabling rules and see if it is indeed the rules causing the problem…

                                    1 Reply Last reply Reply Quote 0
                                    • X
                                      xarope
                                      last edited by

                                      FYI I removed snort_exploit.so.rules from the categories I was using on the WAN interface (as well as snort_exploit.rules that I always had issues with crashing snort pretty much from startup), yesterday afternoon.  Monitored last night and this morning, snort hasn't crash yet.

                                      So might be worth your while to test as well to see if it is this set of rules causing your snort problem.

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

                                        Just got this in my system logs after what appears to be an update; things have been running really solid up until now.

                                        Oct 6 12:06:43 snort[39831]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                                        Oct 6 12:06:43 snort[39831]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                                        Oct 6 12:04:14 snort[39831]: 377 out of 1024 flowbits in use.
                                        Oct 6 12:04:14 snort[39831]: 377 out of 1024 flowbits in use.

                                        Now Snort service is stopped.  I forced an update and it's back up and going again.

                                        We'll see what happens next.  So far so good. :)

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

                                          Got this error again; once this morning and once now.  I don't know if it's related to updates, because I have it set for 12 hours and it hasn't been yet.

                                          Oct 7 12:06:20 snort[11782]: FATAL ERROR: Could not create rule maps
                                          Oct 7 12:06:20 snort[11782]: FATAL ERROR: Could not create rule maps
                                          Oct 7 12:03:36 snort[11782]: 377 out of 1024 flowbits in use.
                                          Oct 7 12:03:36 snort[11782]: 377 out of 1024 flowbits in use.

                                          Doing manual update of rules starts it up again.

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

                                            And got this again with a slightly different error.

                                            Oct 7 20:27:08 kernel: pid 27248 (snort), uid 920: exited on signal 11
                                            Oct 7 20:27:07 snort[27248]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                                            Oct 7 20:27:07 snort[27248]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                                            Oct 7 20:25:09 snort[27248]: 377 out of 1024 flowbits in use.
                                            Oct 7 20:25:09 snort[27248]: 377 out of 1024 flowbits in use.

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