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

    Snort fatal error

    Scheduled Pinned Locked Moved pfSense Packages
    6 Posts 4 Posters 2.6k 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.
    • ?
      A Former User
      last edited by

      I installed the latest version
      May 27 12:11:59 snort[35715]: [ Number of null byte prefixed patterns trimmed: 19648 ]
      May 27 12:11:59 snort[35715]: [ Number of null byte prefixed patterns trimmed: 19648 ]
      May 27 12:11:59 snort[35715]:
      May 27 12:11:59 snort[35715]:
      May 27 12:11:59 snort[35715]: –== Initialization Complete ==--
      May 27 12:11:59 snort[35715]: –== Initialization Complete ==--
      May 27 12:11:59 snort[35715]: Snort initialization completed successfully (pid=35715)
      May 27 12:11:59 snort[35715]: Snort initialization completed successfully (pid=35715)
      May 27 12:11:59 snort[35715]: Not Using PCAP_FRAMES
      May 27 12:11:59 snort[35715]: Not Using PCAP_FRAMES
      May 27 12:11:59 snort[35715]:
      May 27 12:11:59 snort[35715]:
      May 27 12:11:59 snort[35715]: –== Reloading Snort ==--
      May 27 12:11:59 snort[35715]: –== Reloading Snort ==--
      May 27 12:11:59 snort[35715]:
      May 27 12:11:59 snort[35715]:
      May 27 12:11:59 snort[35715]: FATAL ERROR: Unable to open rules file "/usr/local/etc/snort/snort_9698_fxp0/snort.conf": No such file or directory.
      May 27 12:11:59 snort[35715]: FATAL ERROR: Unable to open rules file "/usr/local/etc/snort/snort_9698_fxp0/snort.conf": No such file or directory.
      May 27 12:11:59 kernel: fxp0: promiscuous mode disabled
      May 27 12:12:15 dnsmasq[33264]: reading /etc/resolv.conf
      May 27 12:12:15 dnsmasq[33264]: using nameserver 208.67.222.222#53
      May 27 12:12:15 dnsmasq[33264]: using nameserver 208.67.220.220#53

      1 Reply Last reply Reply Quote 0
      • G
        g4m3c4ck
        last edited by

        Three threads down….  http://forum.pfsense.org/index.php/topic,25456.0.html

        1 Reply Last reply Reply Quote 0
        • ?
          A Former User
          last edited by

          Ya i did that and that is also what caused the problem .I think i may go back to my paid astaro .Pfsense it just getting to have to many problems i new i there was reason i never used it for years after the last problem .

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

            @cdx304:

            Ya i did that and that is also what caused the problem .I think i may go back to my paid astaro .Pfsense it just getting to have to many problems i new i there was reason i never used it for years after the last problem .

            pfsense has a paid version as well.

            https://portal.pfsense.org/

            "nothing is free in life" - said by a lot of people, this is the gotcha behind all free software, little things like this happen, and usually it is fixed within hours when noticed, happened with clam av, they disabled all version of the program but the most recent, a lot of people were affected not just pfsense, as in this case as well, all users of snort are affected, see the post mentioned by g4m3c4ck.

            -Chris Stutzman
            Sys0:2.0.1: AMD Sempron 140 @2.7 1024M RAM 100GHD
            Sys1:2.0.1: Intel P4 @2.66 1024M RAM 40GHD
            freedns.afraid.org - Free DNS dynamic DNS subdomain and domain hosting.
            Check out the pfSense Wiki

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

              @cdx304

              It would be nice to have more info on your problem.

              What were doing when this error happened ?

              What version of pfsense are you running on ?

              Seems like some of your configs are missing.
              Quick fix is to resave your settings on the interface_edit.php tab.

              James

              1 Reply Last reply Reply Quote 0
              • ?
                A Former User
                last edited by

                I was doing nothing at all when snort dies .And snort will not start with pfsense after reboot .This started after the last snort update 1.26?

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