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 64.1k 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.
    • 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
              • E
                eri--
                last edited by

                I will try to give it a look and reproduce it somehow depending on availble time.
                Seems like something has changed somewhere….

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

                  Okay, an update on what I'm seeing.  I have the snort.exploits running on both servers with no problem(I don't know if we should compare rules running.), but I did have spamd installed/running and I uninstalled it and also did an install of County Block.  So far the Snort service has not quit; ermal… I don't know if that helps with anything you are looking at, but I know the one p3 system I have running has not quit out at all, where my xeon system was exiting almost every 6 hours or so and seemed consistant.  My updates are set for 12 hours and all I would have to do is run the update check and it would somehow repair and start the service again.  It didn't even download any new rules, it would run through some of the other standard processes and then say things were updated.

                  Let you know if anything changes.  I'm sure it's tough trying to pin point issues when so many other software packages have to be considered.  Thanks for your work on this ermal.

                  Update 10/9/11@7:05am So far so good; no exits or errors after update.  Still keeping an eye on things.

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

                    Stopped again -

                    Oct 9 12:05:57 kernel: pid 44648 (snort), uid 920: exited on signal 11
                    Oct 9 12:05:56 snort[44648]: FATAL ERROR: Could not create rule maps
                    Oct 9 12:05:56 snort[44648]: FATAL ERROR: Could not create rule maps
                    Oct 9 12:03:39 snort[44648]: 377 out of 1024 flowbits in use.
                    Oct 9 12:03:39 snort[44648]: 377 out of 1024 flowbits in use.

                    ** UPDATE **

                    11/10/2011 - Error and exit again today.

                    Oct 10 12:05:44 snort[56669]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                    Oct 10 12:05:44 snort[56669]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                    Oct 10 12:03:42 snort[56669]: 377 out of 1024 flowbits in use.
                    Oct 10 12:03:42 snort[56669]: 377 out of 1024 flowbits in use.

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

                      Still getting these messages - fyi, but only on my xeon system; i386 system has not gone down at all.  Is there a process that happens every 6 hours or less?  I know this is not happening from the updates set to run every 12 hours.  I'm going to change my updates to 6 hours and see if that helps.

                      Oct 12 12:07:37 snort[62719]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                      Oct 12 12:07:37 snort[62719]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                      Oct 12 12:04:49 snort[62719]: 377 out of 1024 flowbits in use.
                      Oct 12 12:04:49 snort[62719]: 377 out of 1024 flowbits in use.

                      1 Reply Last reply Reply Quote 0
                      • J
                        jamesdean
                        last edited by

                        @mentalhemroids

                        Looks like snort.org updated code that references fpcreate.c.

                        http://www.snort.org/downloads/1165

                        Your going to have to wait till will update the port to the newest version.

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

                          @jamesdean:

                          @mentalhemroids

                          Looks like snort.org updated code that references fpcreate.c.

                          http://www.snort.org/downloads/1165

                          Your going to have to wait till will update the port to the newest version.

                          Thanks for the update jamesdean!  Hope things are well!  I'll wait to hear any news.

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

                            Well, Snort continues to randomly terminate and I don't see the fpcreate.c errors posted above. The last bit of my system log is attached, but it just indicates that Snort is exiting…

                            
Oct 13 03:06:47 	snort[22289]: ===============================================================================
Oct 13 03:06:47 	snort[22289]: SSL Preprocessor:
Oct 13 03:06:47 	snort[22289]: SSL Preprocessor:
Oct 13 03:06:47 	snort[22289]: SSL packets decoded: 15472
Oct 13 03:06:47 	snort[22289]: SSL packets decoded: 15472
Oct 13 03:06:47 	snort[22289]: Client Hello: 1990
Oct 13 03:06:47 	snort[22289]: Client Hello: 1990
Oct 13 03:06:47 	snort[22289]: Server Hello: 1917
Oct 13 03:06:47 	snort[22289]: Server Hello: 1917
Oct 13 03:06:47 	snort[22289]: Certificate: 1425
Oct 13 03:06:47 	snort[22289]: Certificate: 1425
Oct 13 03:06:47 	snort[22289]: Server Done: 4049
Oct 13 03:06:47 	snort[22289]: Server Done: 4049
Oct 13 03:06:47 	snort[22289]: Client Key Exchange: 1281
Oct 13 03:06:47 	snort[22289]: Client Key Exchange: 1281
Oct 13 03:06:47 	snort[22289]: Server Key Exchange: 199
Oct 13 03:06:47 	snort[22289]: Server Key Exchange: 199
Oct 13 03:06:47 	snort[22289]: Change Cipher: 3541
Oct 13 03:06:47 	snort[22289]: Change Cipher: 3541
Oct 13 03:06:47 	snort[22289]: Finished: 0
Oct 13 03:06:47 	snort[22289]: Finished: 0
Oct 13 03:06:47 	snort[22289]: Client Application: 3118
Oct 13 03:06:47 	snort[22289]: Client Application: 3118
Oct 13 03:06:47 	snort[22289]: Server Application: 1489
Oct 13 03:06:47 	snort[22289]: Server Application: 1489
Oct 13 03:06:47 	snort[22289]: Alert: 610
Oct 13 03:06:47 	snort[22289]: Alert: 610
Oct 13 03:06:47 	snort[22289]: Unrecognized records: 5002
Oct 13 03:06:47 	snort[22289]: Unrecognized records: 5002
Oct 13 03:06:47 	snort[22289]: Completed handshakes: 0
Oct 13 03:06:47 	snort[22289]: Completed handshakes: 0
Oct 13 03:06:47 	snort[22289]: Bad handshakes: 0
Oct 13 03:06:47 	snort[22289]: Bad handshakes: 0
Oct 13 03:06:47 	snort[22289]: Sessions ignored: 1489
Oct 13 03:06:47 	snort[22289]: Sessions ignored: 1489
Oct 13 03:06:47 	snort[22289]: Detection disabled: 23
Oct 13 03:06:47 	snort[22289]: Detection disabled: 23
Oct 13 03:06:47 	snort[22289]: ===============================================================================
Oct 13 03:06:47 	snort[22289]: ===============================================================================
Oct 13 03:06:50 	snort[22289]: Snort exiting
Oct 13 03:06:50 	snort[22289]: Snort exiting
                            1 Reply Last reply Reply Quote 0
                            • M
                              mentalhemroids
                              last edited by

                              No errors or exits after unselecting emerging-current_events.rules; I don't know if that is the real reason, but it is working so far for me on the xeon system; never had that selected on the i386 system.  I still feel the issue comes from overwhelming memory with rules.

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

                                Although memory utilization might indeed be an issue, I don't have emerging-current_events.rules selected in my configuration. In addition, my server has 4 gigs of RAM and since the only package that I've installed and run is Snort, I would think that would be more than enough.

                                With Snort running, the dashboard indicates about 37% memory utilization. With the previous release of Snort running on pfSense 2.0-RC1, the dashboard showed about 50% memory utilization …but Snort never once failed in that configuration.

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

                                  @Slab

                                  Are you running i386 or x64?  My xeon is i386 and I have another p3 i386; do we know if this is affecting both platforms or just one?  I know x64 has had other issues that are referred in previous posts.

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

                                    @mentalhemroids:

                                    @Slab

                                    Are you running i386 or x64?

                                    I'm running the i386 version.

                                    1 Reply Last reply Reply Quote 0
                                    • AhnHELA
                                      AhnHEL
                                      last edited by

                                      Might be common knowledge but restarting an OpenVPN Server causes Snort to exit as well if anyone is investigating strange Snort stoppages.

                                      AhnHEL (Angel)

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

                                        @onhel:

                                        Might be common knowledge but restarting an OpenVPN Server causes Snort to exit as well if anyone is investigating strange Snort stoppages.

                                        Good to know… I had OpenVPN enabled, but haven't used it.  I just disabled the instance and we'll see if that makes a difference too.  I had Snort exit our around midnight for the first time in more than a day, so I thought I was making progress.
                                        One test at time.

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

                                          Error just a few minutes ago…  going to run update again and things will be fine for a while.  OpenVPN is disabled.

                                          Oct 19 12:06:33 kernel: pid 60457 (snort), uid 920: exited on signal 11
                                          Oct 19 12:06:32 snort[60457]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                                          Oct 19 12:06:32 snort[60457]: FATAL ERROR: fpcreate.c(1557) Failed to compile port group patterns.
                                          Oct 19 12:03:47 snort[60457]: 377 out of 1024 flowbits in use.
                                          Oct 19 12:03:47 snort[60457]: 377 out of 1024 flowbits in use.

                                          1 Reply Last reply Reply Quote 0
                                          • L
                                            lonevipr
                                            last edited by

                                            Everything of mine was working fine when I went to bed last night. Power went out in the middle of the night & my pfsense box went to hell in a handbasket.

                                            Had to issue a backup config to get everything working. Now Snort was working perfectly before. Now it's broke. I'm getting a

                                            snort[2391]: FATAL ERROR: /usr/local/etc/snort/snort_19773_nfe0/snort.conf(308) Unknown output plugin: "alert_pf"

                                            This error was suppose to be fixed months ago.
                                            http://redmine.pfsense.org/issues/1590

                                            Not sure how when i reinstalled snort why i'm getting this. Is there a bsd command I can issue to check to make sure all dependencies for snort are installed? I've even tried uninstalling & reinstalling snort numerous times with no help. I know this error has to do with "block offenders" is enabled, but it was enabled & running fine before power outage. I do want it to block offenders.

                                            I ran the "ln -s /lib/libpcap.so.7 /lib/libpcap.so.1" listed as the fix. But my error log still shows same error & putty says that the file exists.

                                            Edit:Turned off "block offenders" to see if I could get it running with just alerts. Now i'm getting another error.

                                            snort[60765]: FATAL ERROR: Failed to initialize dynamic preprocessor: SF_SSLPP (IPV6) version 1.1.4 (-2)

                                            Now this error isn't really listed on the bug tracker. Thoughts?

                                            Running pfSense 2.2-RELEASE (amd64)

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