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

    Sort service will no longer start (2.9.4.6 pkg v. 2.5.9)

    Scheduled Pinned Locked Moved pfSense Packages
    4 Posts 3 Posters 1.3k 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.
    • arch113A
      arch113
      last edited by

      Snort has been working fine untill September 13, don't know what happened, but the service will not start.  Tried a reinstall, didn't see any errors, but still doesn't start.

      This is all I get in the system log:

      Sep 18 13:27:51 SnortStartup[21280]: Snort START for WAN(10723_bge1)…

      2.0.3-RELEASE (amd64)
      built on Fri Apr 12 10:27:15 EDT 2013
      FreeBSD 8.1-RELEASE-p13

      1 Reply Last reply Reply Quote 0
      • A
        asterix
        last edited by

        Uninstall.. make sure you un-check the option to save settings. Reboot. Do a clean install and re-configure Snort.

        1 Reply Last reply Reply Quote 0
        • arch113A
          arch113
          last edited by

          @asterix:

          Uninstall.. make sure you un-check the option to save settings. Reboot. Do a clean install and re-configure Snort.

          That worked…  I hope I dont have to do that too often......

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

            @arch113:

            @asterix:

            Uninstall.. make sure you un-check the option to save settings. Reboot. Do a clean install and re-configure Snort.

            That worked…  I hope I dont have to do that too often......

            If you upgrade to 2.1-RELEASE of pfSense these kinds of issues very likely will not happen anymore.  The 2.1 code base uses PBI to manage packages.  This is a huge improvement over the TBZ process in 2.0.x.  Under the old system, any update of a package runs the risk of overwriting some critical shared library with a different version than might have been placed there by existing packages.  So in that case something will break.

            Under the 2.1 code base with PBI, each package gets installed in the equivalent of its own "chroot jail" (not a perfectly accurate analogy, to be sure, but close enough for this discussion  ;D ).  This way each package can have its own private copy of "shared" libraries.  In effect they really are not shared anymore.  This prevents the problem where one package overwrites some critical library used by a different package.

            Bill

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