pfSense 2.4.5-RELEASE-p1 Now Available
-
Hello!
I upgraded several routers yesterday to 2.4.5.1 - a variety of sg-1100's, sg-3100's, and oddballs. All had extra packages installed (snort, pfb, cron, etc...) that the main upgrade screen said were being upgraded.
On the first router, after the upgrade completed, I went to the Package Manager and noticed that packages were still listed as needing upgrades. After clicking on one of the update package links I got the "Please wait while the update system initializes" message.
I discovered that, at least in my case, you do not need to manually install the package updates.
Once my router rebooted from the main upgrade, it started installing package upgrades in the background. There was no indication that it was doing this other than tailing the system log. It eventually completed the background package updates and all was fine.
I verified this on subsequent router upgrades. The lesson for me was to wait a good 10-15 minutes after the initial reboot to let the packages upgrade in the background while also checking the system log. After waiting, the Package Manager correctly showed no upgrades required.
In general, the upgrade process was rock solid. I did a few remote long distance upgrades last as wasnt even nervous....okay, maybe just a little... :)
John
-
@revengineer said in pfSense 2.4.5-RELEASE-p1 Now Available:
killall pkg-static
That indeed gets the stuck process out of jail and you can retry to update one by one without rebooting the whole box.
But the package manager definitely has a problem in 2.4.5p1!
-
Just did the upgrade 2.4.5 to 2.4.5-p1 for my home pfSense.
This also automatically triggered pfBlockerNG-devel upgrade 2.2.5_32 > 2.2.5_33
Smooth as silk, took about 5 Minutes total, thanks Netgate /pfSense team!-Rico
-
I had an Openvpn client from pfsense to PIA a few months ago, but I removed it yesterday.
Removed it completely, deleted the gateway, removed the interface, nat rules, certificate, everything related to that VPN connection.
I was checking my xml configuration file, and noticed that the dnsgw3 and dnsgw4 were still pointing to the PIA gateway.
Searched, and it seems that this is related to Bug #8922 (https://redmine.pfsense.org/issues/8922)
I've fixed by manually editing the XML file, and now it seems that everything is properly removed.
-
re: upgrading with packages installed:
https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html#packages -
@teamits said in pfSense 2.4.5-RELEASE-p1 Now Available:
re: upgrading with packages installed:
https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html#packagesThis is NOT a user error. I wiped the drive and did a fresh install and restore the latest config. Upon reboot the package installation hands. I waited up to 20 minutes for one package to complete. There is another post reporting to have waited hours. This is not right and did not used to be this way.
-
I meant "...package installation HANGS." (Cannot edit the post.)
-
Hello!
I guess it could seem like it is hung if it is taking more than 20 minutes. Thats a long time.
What is that they say, "The logs are the window to the soul.", or something like that...
John
-
@serbus said in pfSense 2.4.5-RELEASE-p1 Now Available:
Hello!
I guess it could seem like it is hung if it is taking more than 20 minutes. Thats a long time.
What is that they say, "The logs are the window to the soul.", or something like that...
John
I have been using "ps aux|grep pkg-static" to verify that it was hung on a single package for that long. I was not clear if there is a better place showing additional details of the install process. Pointer appreciated and I will take a look what happened.
-
killall pkg-staticGave me the possibility back to upgrade, yet after I tried to install the pfBlockerNG package it go stuck again
Had to do a
killall pkg-staticTo get back out again
So no solution here...
-
Upgraded two machines this past week to 2.4.5p1 from 2.4.5 and everything went smoothly. Both are baremetal installs. On one of the boxes I have some sizable IP block lists and so was happy to see that the pfctl issue is now fixed. System seems snappier and no more latency spikes. Thanks everyone for the quick turnaround on this.
-
@tman222 That doesn't help the few of us that are experiencing problems, but we are glad that everything went smooth for you and things are better! That indeed is nice!
-
When I hangs
78285 0 S+ 0:00.00 grep pkg [2.4.5-RELEASE][root@pfSense.localdomain]/root: ps ax | grep 'pkg' 53675 - IN 0:00.00 /bin/sh /etc/rc.update_pkg_metadata 56258 - IC 0:00.01 tee -a /cf/conf/pkg_log_pfSense-pkg-pfBlockerNG-devel 56497 - I 0:00.00 pkg-static -o EVENT_PIPE=/tmp/pfSense-upgrade.sock up 56729 - I 0:01.74 pkg-static -o EVENT_PIPE=/tmp/pfSense-upgrade.sock up 85699 0 S+ 0:00.00 grep pkg -
Which pkg version are you guys running?
I noticed someting strange in my logs...Jun 10 23:16:37 php [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload Jun 10 23:15:00 php [pfBlockerNG] Starting cron process. Jun 10 22:20:56 pkg-static pkg upgraded: 1.12.0_1 -> 1.13.2 Jun 10 22:16:40 php [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload Jun 10 22:15:00 php [pfBlockerNG] Starting cron process.This happened automatically, I wasn't at home at this time and also not logged in to the pfSense WebGUI.
-Rico
-
@Rico Sorry can't help you I have decided to reinstall pfS and now everything is fine.
-
Well I have no problem, just wondering what differs from my setup with others having issues.
-Rico
-
The issue with the packages getting "stuck" during (re)install appears to be due to how the install process launches services/daemons from within the install functions. If the daemons are killed (or stopped and started), then pkg will continue. So likely it was stuck, and then when a cron job came along and restarted the pfBlockerNG services, then pkg was able to continue.
-
@jimp said in pfSense 2.4.5-RELEASE-p1 Now Available:
The issue with the packages getting "stuck" during (re)install appears to be due to how the install process launches services/daemons from within the install functions. If the daemons are killed (or stopped and started), then pkg will continue. So likely it was stuck, and then when a cron job came along and restarted the pfBlockerNG services, then pkg was able to continue.
Thanks for weighing in, Jim. Is there a solution or workaround for this issue other than killing each daemon upon install? Will this require a code change for each package affected?
-
Not yet, we are still looking into it
-
@jimp said in pfSense 2.4.5-RELEASE-p1 Now Available:
Not yet, we are still looking into it
Perfect, thank you!!!
