2.2.1 -> 2.2.2 upgrade Broke my Suricata

  • Had a perfectly running 2.2.1 system… Then upgraded to 2.2.2.

    1. After the upgrade, it stalled out on reinstalling packages. pfBlocker NG installed fine, it hung on the Suricata install.
    2. After waiting 45 minutes, and it not completing, I rebooted pfSense. I then uninstalled Suricata - which it did with no errors.
    3. I then rebooted pfSense again.
    4. Then I tried to install Suricata. It stops at 10% and never continues - has been there over an hour.

    I could use some help in figuring out what to do next.

    The install screen from the web gui looks like this...

    (little box at very top of package install screen):

    There is a new set of Snort VRT rules posted. Downloading...

    (larger box showing the package install):

    Beginning package installation for suricata .
    Downloading package configuration file... done.
    Saving updated package information... done.
    Downloading suricata and its dependencies...
    Checking for package installation...
    Downloading https://files.pfsense.org/packages/10/All/suricata-2.0.6-amd64.pbi ...  (extracting)
    Loading package configuration... done.
    Configuring package components...
    Loading package configuration... done.
    Additional files... done.
    Loading package instructions...
    Custom commands...
    Executing custom_php_install_command()...10%

  • Couldn't figure it out.

    Just going to start over with a clean install… Again.

    Seems like this is a recurring theme with pfSense and me (which is not a ringing endorsement).

  • What kind of system is this?  Is a conventional full install on a hard disk, or is a Nano-based installation?  If Nano, check that you aren't running out of free space on the /tmp partition.


  • Full install, virtual on hyperv 2012 r2, HD with 20+ GB free space.

    Not a huge deal, I am getting pretty good at rebuilding after things get wonky after upgrades - has happened 3 times in past 12 months (different things each time). Am back in business now. Gave me an excuse to clean a few leftovers out of the config file too.

    Since no one else is reporting 2.2.2 breaking suricata, it must have been something specific to my install…

Log in to reply