2.5.0 Package Install Issues (solved in latest 2.5 snapshot)



  • Spun up a new VMware virtual machine to test with since I need to work on the Suricata 4.1.3 package for 2.5. There seems to be an issue with the update and package installation progress screen. It does not show update and installation status. Here are the steps I used:

    • Installed from March 15 ISO image into a new virtual machine with 2 GB of RAM, 20 GB of disk and two NIC interfaces.
    • Install went perfectly using the setup wizard.
    • After reboot the Dashboard showed a new snapshot update was available (the March 18 version). Clicked to install that and it went to the update page. After confirming to install the update, the screen showed "Please wait while the update system initializes" but then nothing else. I checked the console of the VM to see what was happening and noticed the update proceeded and the firewall rebooted, but still the GUI page remained static displaying just that last message.
    • I clicked to another page and then got the normal login screen to login again. The update had installed just fine.

    I also needed to install the Suricata package via Package Manager. The package fails to install. The installation process never even kicks off and no error messages (in fact, no messages related to installation) are logged.

    Tried the OpenVNP Client install just in case it might be a Suricata issue. Same result -- no install, no messages about starting or stopping the installation, and nothing logged in the system log.


  • Rebel Alliance Developer Netgate

    @bmeeks said in 2.5.0 Development Snapshots are now live!:

    • After reboot the Dashboard showed a new snapshot update was available (the March 18 version). Clicked to install that and it went to the update page. After confirming to install the update, the screen showed "Please wait while the update system initializes" but then nothing else. I checked the console of the VM to see what was happening and noticed the update proceeded and the firewall rebooted, but still the GUI page remained static displaying just that last message.

    I can't reproduce this here at the moment. I just updated a system from an earlier 2.5.0 snapshot and it showed the progress the whole way.

    I also needed to install the Suricata package via Package Manager. The package fails to install. The installation process never even kicks off and no error messages (in fact, no messages related to installation) are logged.

    I can reproduce this one, though. You can work around it by installing packages at the CLI, such as pkg install pfSense-pkg-suricata.



  • @jimp said in 2.5.0 Development Snapshots are now live!:

    @bmeeks said in 2.5.0 Development Snapshots are now live!:

    • After reboot the Dashboard showed a new snapshot update was available (the March 18 version). Clicked to install that and it went to the update page. After confirming to install the update, the screen showed "Please wait while the update system initializes" but then nothing else. I checked the console of the VM to see what was happening and noticed the update proceeded and the firewall rebooted, but still the GUI page remained static displaying just that last message.

    I can't reproduce this here at the moment. I just updated a system from an earlier 2.5.0 snapshot and it showed the progress the whole way.

    I also needed to install the Suricata package via Package Manager. The package fails to install. The installation process never even kicks off and no error messages (in fact, no messages related to installation) are logged.

    I can reproduce this one, though. You can work around it by installing packages at the CLI, such as pkg install pfSense-pkg-suricata.

    Thanks @jimp. I will install via CLI for my early package testing. I have a Suricata 4.1.3 binary ready to test. I will try the snapshot update again a bit later. Maybe it was just a fluke.


  • Rebel Alliance Developer Netgate

    I opened https://redmine.pfsense.org/issues/9410 to track the package installation issue. There is a chance it affects both packages and updates, but it might be something new that was introduced after the snapshot I tested updates on. I can't really test that again until there is a new snap.

    If you (or anyone else) finds any new problems though, let's move them to separate threads in this category.



  • @jimp said in 2.5.0 Development Snapshots are now live!:

    I opened https://redmine.pfsense.org/issues/9410 to track the package installation issue. There is a chance it affects both packages and updates, but it might be something new that was introduced after the snapshot I tested updates on. I can't really test that again until there is a new snap.

    If you (or anyone else) finds any new problems though, let's move them to separate threads in this category.

    OK. Just repeated the snapshot update (to the 1135 update) and it worked as expected, so my earlier issue with the console update appears to have been a fluke.



  • Just did fresh install (restored config.xml) of the snapshot and I had to manually install packages using steps here: https://docs.netgate.com/pfsense/en/latest/packages/fixing-a-broken-pkg-database.html

    Only thing different is path to pkg-static (/usr/local/sbin/pkg-static).

    Also I don't see any firewall logs or any indication that the firewall is not blocking stuff. Any ideas why?


  • Rebel Alliance Developer Netgate

    @strangegopher said in 2.5.0 Development Snapshots are now live!:

    Just did fresh install (restored config.xml) of the snapshot and I had to manually install packages using steps here: https://docs.netgate.com/pfsense/en/latest/packages/fixing-a-broken-pkg-database.html

    What led you do have to do that? Was there a specific error or behavior that didn't work?

    If it was just that the GUI didn't let you install packages, that's covered by https://redmine.pfsense.org/issues/9410

    Also I don't see any firewall logs or any indication that the firewall is not blocking stuff. Any ideas why?

    https://redmine.pfsense.org/issues/9411



  • @jimp said in 2.5.0 Package Install Issues:

    @strangegopher said in 2.5.0 Development Snapshots are now live!:

    Just did fresh install (restored config.xml) of the snapshot and I had to manually install packages using steps here: https://docs.netgate.com/pfsense/en/latest/packages/fixing-a-broken-pkg-database.html

    What led you do have to do that? Was there a specific error or behavior that didn't work?

    If it was just that the GUI didn't let you install packages, that's covered by https://redmine.pfsense.org/issues/9410

    Also I don't see any firewall logs or any indication that the firewall is not blocking stuff. Any ideas why?

    https://redmine.pfsense.org/issues/9411

    1. Yes, here are the full steps to what happened:
      I was originally on 2.4.5 snapshots and followed steps on the blog post to upgrade my install. First, I ensured I was on snapshots in update settings page.
      I sshed into pfsense and did sed -i '' -e 's/11/12/g; s/armv6/armv7/g; s/hardfp/softfp/g' /usr/local/share/pfSense/pkg/repos/*devel*abi /usr/local/share/pfSense/pkg/repos/*devel*conf but that didn't give me new update. Next, I selected stable builds and then re-selected latest snapshots on update settings page. That gave me access to new update. Just to make sure nothing was broken I sshed into pfsense again and ran the sed command again. At this point, I made a mistake and rebooted the pfsense box. This caused whole bunch of errors to show up when pfsense rebooted and I had no internet or access to pfsense box (ssh or gui). I knew I needed to update bios on my pfsense box so I decided to kill 2 birds with one stone and loaded up usbs with bios update and pfsense snapshot.

    2. Thanks!

    3. Thanks!

    On Unrelated note: I don't recall posting to this thread, I guess my reply got moved here.


  • Rebel Alliance Developer Netgate

    OK, so that's not too unusual. The transition for 2.4.4->2.5.0 users will be a lot smoother. We wanted to make 2.4.5 users manually opt in because we didn't want someone who was relatively stable on 2.4.5 to click the auto-update to 2.5.0 and break.

    I split off individual threads from the 2.5.0 announcement thread, so others can see them easier, which is why this is its own topic now.


Log in to reply