Errors on boot after upgrade to 2.3 BETA

  • 2.3-BETA (i386)
    built on Wed Jan 27 12:42:00 CST 2016

    This was an upgrade from 2.2.6.  I had snort installed before the upgrade.

    It seemed to come up ok and I don't know of any issues yet but I just wanted to let the dev team know about the errors.  I will look closer at snort and see if it is working as I do see the menu is there.  I will first do more research to find out if it even should be working yet :).

    Starting device manager (devd)…kldload: can't load ums: No such file or directory

    Further down when upgrading there were some pkg errors.  It seemed like the same error happened twice but the first one scrolled by before I got the pic so I only got the second pkg error.  I had snort installed before the upgrade so maybe that is the cause as it might not be fully ready yet for 2.3.

    ERROR!!! An error occurred on pkg execution (rc = -1) with parameters 'install -y -f pfSense-pkg-snort':

  • @adam65535:

    Starting device manager (devd)…kldload: can't load ums: No such file or directory

    pfSense didn't find a driver for your USB mouse. On a firewall, this isn't really important.


    ERROR!!! An error occurred on pkg execution (rc = -1) with parameters 'install -y -f pfSense-pkg-snort':

    I managed to reinstall the Snort package successfully on my test VM just now, though I use amd64, not i386. It might be the issue is something to do with your pre-existing Snort configuration. What happens if you reinstall Snort from the Packages screen?

    If your device supports amd64, you are strongly recommended to back up your configuration, wipe the device and install the amd64 of pfSense 2.3, then restore your configuration. Booting the amd64 version from a CD or USB memory stick may well be sufficient to determine whether your device is amd64 compatible.

  • Thanks for the info.  I have a USB to ps2 adapter with separate mouse and keyboard connectors.  I only have a keyboard connected to the keyboard connector so that makes sense as I don't have a mouse connected but the adapter itself is probably showing up as a mouse anyway.

    For snort I can't uninstall it now.  I get an error.
    *** EDIT***: Even though it showed an error, It did uninstall.  I was able to reinstall it again without any install errors.

    Package removal
    >>> Removing pfSense-pkg-snort... 
    Checking integrity... done (0 conflicting)
    Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):
    Installed packages to be REMOVED:
    The operation will free 1 MiB.
    [1/1] Deinstalling pfSense-pkg-snort-
    Removing snort components...
    Menu items... done.
    pfSense-pkg-snort removal failed!

    As for 32/64bit,  The system is only a 32bit CPU… I have found that out the hard way a few times over the years as I forgot :).

  • The only issue after reinstalling snort is that the gui is messed up but maybe snort is just not ready for 2.3 yet.

  • The Snort GUI is as expected. The new Bootstrap GUI for Snort is under development and will be released as an updated package when it is ready. Snort should work OK; it's just the GUI that will look like Snort on 2.2 but with most of the icons missing. There may be some parts of the GUI that don't work properly, but you should be able to use a configuration upgraded from 2.2 successfully.

    Your PS/2 to USB adapter will likely be detected as a USB mouse even though no mouse is plugged in. The error related to ums is really only cosmetic.

    The pfSense developers are considering dropping x86 support after the last release in the 2.3.x series, as the majority of users have moved on to amd64. This means there is no need for immediate action, but it is worth starting to think about the options for replacing your existing hardware. The chances are that something modern will be more power efficient, giving some sort of payback over time.

    There have been some hints that there will be an ARM version of pfSense in the future, but there is no firm commitment over whether this will happen. Additional platform support takes resources, so it may well be that the medium term intention is to use the resources freed up by dropping i386 to support a limited number of ARM boards. For now, if you are looking to buy replacement hardware, you need to look for an amd64 device.

Log in to reply