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

    Suricata 4.1.5_1 on pfsense 2.5.0-DEVELOPMENT (amd64) can't start

    Scheduled Pinned Locked Moved IDS/IPS
    13 Posts 3 Posters 1.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.
    • W
      war
      last edited by

      @kiokoman

      Thanks for your reply. I already removed banyard2. Still suricata can't start.

      Screenshot_20191108_195415.png
      Screenshot_20191108_195458.png

      1 Reply Last reply Reply Quote 0
      • W
        war
        last edited by

        I have experience this bug.
        Screenshot_20191108_201642.png

        bmeeksB 1 Reply Last reply Reply Quote 0
        • kiokomanK
          kiokoman LAYER 8
          last edited by

          uhm idk maybe try to uninstall and reinstall suricata, remember to remove this option before uninstalling

          Immagine.jpg

          or maybe @bmeeks can help you about this

          ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
          Please do not use chat/PM to ask for help
          we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
          Don't forget to Upvote with the 👍 button for any post you find to be helpful.

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

            @war said in Suricata 4.1.5_1 on pfsense 2.5.0-DEVELOPMENT (amd64) can't start:

            I have experience this bug.
            Screenshot_20191108_201642.png

            That PHP crash report is very confusing. When I look in that GUI package source code file, there is no such line using the explode() function at that line number. The function is actually called a few lines above. Nevertheless, I don't think that will cause Suricata not to start. That is just a warning message from the PHP compiler. I will address that issue in the next GUI package update.

            To see why Suricata is not starting, you need to look in the suricata.log file for the interface. Go to the LOGS VIEW tab and select a Suricata interface in the drop-down. Then choose suricata.log in the drop-down log file chooser. Read through that log and see what Suricata complains about. It should list any errors preventing startup in there.

            1 Reply Last reply Reply Quote 0
            • W
              war
              last edited by

              Hi guys,

              This is the output of my suricata logs.

              Screenshot_20191111_182459.png
              Screenshot_20191111_182446.png
              Screenshot_20191111_182414.png
              Screenshot_20191111_182430.png

              1 Reply Last reply Reply Quote 0
              • kiokomanK
                kiokoman LAYER 8
                last edited by

                from console delete that file

                rm /var/run/pid/suricata*
                

                try to start it again

                ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                Please do not use chat/PM to ask for help
                we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                Don't forget to Upvote with the 👍 button for any post you find to be helpful.

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

                  Do what @kiokoman said and that should let Suricata start.

                  That error message indicates the running Suricata process crashed and did not have a chance to clean up after itself.

                  1 Reply Last reply Reply Quote 0
                  • W
                    war
                    last edited by

                    Hi guys,

                    I already deleted /var/run/suricata*, there is no /var/run/pid/suricata*. error is still the same.

                    Screenshot_20191112_193932.png
                    Screenshot_20191112_193918.png

                    1 Reply Last reply Reply Quote 0
                    • kiokomanK
                      kiokoman LAYER 8
                      last edited by

                      nope, not the same, the error is now different,
                      now.. i see you have 16 cores
                      increase the Stream Memcap value on the FLOW/STREAM tab (inside interface) to at least 256 MB and try to start again, increse that value until it run. remove the pid again if necessary

                      ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                      Please do not use chat/PM to ask for help
                      we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                      Don't forget to Upvote with the 👍 button for any post you find to be helpful.

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

                        @kiokoman is right again. High core-count CPUs will need way more TCP stream memory than the default.

                        1 Reply Last reply Reply Quote 0
                        • W
                          war
                          last edited by

                          Thanks guys its now working.

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