2.4.0 Release
-
Upgraded to 2.4.0 release with no issues.
-
I just updated too. OK so far. At least I can access this forum. :)
-
Just updated. No problems!
Great job, pfSense team!
-
Thx for updates!!!
Anybody tried upgrade on QOTOM box ? -
I upgraded two of my pfsense from 2.3.4-RELEASE-p1 running on vmware 6.5.
One of them upgraded without issue. The other would not come back after reboot without removing the media in the CD Drive. Not sure why it was hanging up there, but as soon as I removed it the system booted right up.
-
Simple upgrade no issues - thank you.
-
I had a strange issue, after I upgraded all my load balancer settings were blank!
I'd taken a copy before, but before I thought I'd try rebooting.
After a reboot, the settings came back and everything is fine now.
A restart of the service may have worked, but I was being lazy.
All seems well so far! -
Giant pfSense logo obscures and prevents access to controls on top 20% of graphic interface screens. Help!
-
Giant pfSense logo obscures and prevents access to controls on top 20% of graphic interface screens. Help!
Press F5 :-)
Or Ctrl-F5
Browser caches are silly.
-
Thx for updates!!!
Anybody tried upgrade on QOTOM box ?Yes, I’ve been running 2.4 since the RC came out in September without issues. I’d recommend a reinstall and configure restore so you can setup ZFS.
-
Thx for updates!!!
Anybody tried upgrade on QOTOM box ?Yes, I’ve been running 2.4 since the RC came out in September without issues. I’d recommend a reinstall and configure restore so you can setup ZFS.
@jgiannakas can you elaborate a little pls? if I do regular upgrade via web UI, is it safe? What about ZFS?
-
Thx for updates!!!
Anybody tried upgrade on QOTOM box ?Yes, I’ve been running 2.4 since the RC came out in September without issues. I’d recommend a reinstall and configure restore so you can setup ZFS.
@jgiannakas can you elaborate a little pls? if I do regular upgrade via web UI, is it safe? What about ZFS?
It is safe and that’s how I installed it at first - via the web gui. Just make sure you don’t refresh the screen till it’s done.
However you can’t get ZFS via upgrade, you’ll be stuck using ufs. If you want to move to ZFS (which you should as even in single disk mode it’s more reliable than ufs) then you need to reinstall from scratch and restore the configuration xml upon completion.
-
Thx for updates!!!
Anybody tried upgrade on QOTOM box ?Yes, I’ve been running 2.4 since the RC came out in September without issues. I’d recommend a reinstall and configure restore so you can setup ZFS.
@jgiannakas can you elaborate a little pls? if I do regular upgrade via web UI, is it safe? What about ZFS?
It is safe and that’s how I installed it at first - via the web gui. Just make sure you don’t refresh the screen till it’s done.
However you can’t get ZFS via upgrade, you’ll be stuck using ufs. If you want to move to ZFS (which you should as even in single disk mode it’s more reliable than ufs) then you need to reinstall from scratch and restore the configuration xml upon completion.
Got it thx! So if I stay on old ufs and do ZFS later, I will be good :)
-
Thx for updates!!!
Anybody tried upgrade on QOTOM box ?Yes, I’ve been running 2.4 since the RC came out in September without issues. I’d recommend a reinstall and configure restore so you can setup ZFS.
@jgiannakas can you elaborate a little pls? if I do regular upgrade via web UI, is it safe? What about ZFS?
It is safe and that’s how I installed it at first - via the web gui. Just make sure you don’t refresh the screen till it’s done.
However you can’t get ZFS via upgrade, you’ll be stuck using ufs. If you want to move to ZFS (which you should as even in single disk mode it’s more reliable than ufs) then you need to reinstall from scratch and restore the configuration xml upon completion.
Not exactly, the installer offers you a "rescue configuration" option which allows you to boot from the install media, rescue the configuration from the existing installation and then reinstall pfSense from scratch but using the rescued configuration.
-
@kpa:
Not exactly, the installer offers you a "rescue configuration" option which allows you to boot from the install media, rescue the configuration from the existing installation and then reinstall pfSense from scratch but using the rescued configuration.
Hmm, can I do upgrade without any USB media and without connection pfSense box to monitor?
What does the rescued configuration do ?Thx
-
I've been running off of development snapshots, and I'm currently on 2.4.1.a.2017*
How can I switch to the 2.4 release? Switching to stable shows I have the latest, presumably because 2.4.1 is higher than 2.4.0.
-
I tried to do the upgrade today from 2.3.4p1 remotely which unfortunately took a dump on me. Good thing no one cares if it's dead for a bit since it's just my house.
Turned out to be a drive mounting issue on bootup:
Mounting from ufs:/dev/ad4s1a failed with error 19.
I found a similar issue at blog.stefcho.eu/upgrade-from-pfsense-2-1-5-to-2-2-on-hyper-v/ which solved my boot problem, I just had to tell it to use the new drive name ada0s1a instead.
After this, pfsense continued to do its upgrade thing and then reboot. I had to follow the same steps again once it rebooted automatically after upgrading, then follow the rest of the blog article and change /etc/fstab with the new drive names ada0s1a and ada0s1b in there as appropriate. All functional again, never had a problem until this release - I've been using the same hardware since around 1.2.3 release.
Hope it helps if anyone else runs into an issue with the upgrade!
-
Turned out to be a drive mounting issue on bootup:
Mounting from ufs:/dev/ad4s1a failed with error 19.
I ran into this exact same issue. For boring reasons, I didn't end up using the solution that Razidd did. My ultimate solution was:
-
Download the 2.4.0 serial installer
-
Select the option to rescue the config.xml from the old partition
-
Proceed to reinstall with ZFS, which picked up the rescued config
In the end it was quite straightforward, but the road to straightforward was long and frustrating. :facepalm: Not great to have the usually rock-solid web UI upgrade process kill the box.
-
-
'
All seeming good here too ;DOnly one possible issue. It told me in web interface that installation failed very early in the update, the download phase.. But i just waited and eventually it restarted and booted up again. Connected monitor to see what was actually happening.
-
SG-2440. It seemed to go ok until the end. Said it would reboot in 20 sec, over, and over again. After a few minutes I headed for the closet to drag out my laptop for console connection. By the time I got that set up 2.4 was up and running.
Had 2 error messages.
/rc.filter_configure_sync: New alert found: There were error(s) loading the rules: /tmp/rules.debug:27: cannot load "/var/db/aliastables/pfB_Top_v4.txt": No such file or directory - The line in question reads [27]: table <pfb_top_v4>persist file "/var/db/aliastables/pfB_Top_v4.txt"</pfb_top_v4>and
/rc.filter_configure_sync: New alert found: There were error(s) loading the rules: /tmp/rules.debug:169: macro 'pfB_Top_v4' not defined - The line in question reads [169]: block in log quick on $WAN reply-to ( igb0 external IPv4 addr ) inet from $pfB_Top_v4 to any tracker 1770008803 label "USER_RULE: pfB_Top_v4 auto rule"No more errors in last 10 hrs so I presume these were fixed when pfBlockerNG ran it's next cron job.
Thanks.
