2.4 upgrade woes
-
This has not been a good update from my experience.
The UI is much slower than it was, the assign interfaces page (which has an open bug report for being too slow and hence unusuable with a large number of interfaces) is now 8x slower than it was in 2.3.x
ifconfig keeps losing interfaces (pppoe0 in particular), the system log is full of failed commands and a reboot kills the system completely (Have to log into console and manually bounce the LAN interface to bring it back, then have to restart PHP-FPM to get the webui back).
All this is after I had to manually fix a cock-up by the update process (broken symlink for a php related .so file that caused PHP to crap itself on startup)
as an aside, the new favicon is much less identifiable in amongst a sea of tabs.
I've gone back to 2.3.4
-
Glad you're saying what issues you're running into. Many people just complain with no examples.
My general rule of thumb is to wait until the point release hasn't changed in a month. 2.4.1 is almost out already.
-
Looks like corrupted install. I would reinstall pfSense 2.4.0-RELEASE and see if it helps.
-
Why in the world team have decided to bump all of us to 2.4.0 major release? I would never expect that bump from 2.3.4 to 2.4.0 would cause the underlying OS upgrade too! :o
On top of this - I see 2.3.5 release development is in progress. What the heck? If we all jumped to 2.4.x what is the point of having 2.3.x alive, especially when there's no option to choose - major vs. minor upgrade versions?
2.4.0 barely works after upgrade on my ESXi. 2.3.4 worked flawlessly. Now I'm constantly loosing connections, and CPU usage is permanently > 15%, even when there are only 5 connections active. Load average of the system never goes below 0.80.
And I cannot seem to find source image for 2.3.4-p1 or what it was released in July?
-
Why in the world team have decided to bump all of us to 2.4.0 major release? I would never expect that bump from 2.3.4 to 2.4.0 would cause the underlying OS upgrade too! :o
Check out the motivation : one of the reasons was : "FreeBSD 10" is to old, the new "11" had to be included.
Many other reasons exists.
Like https://www.netgate.com/blog/pfsense-software-version-2-4-release-highlights.htmlOn top of this - I see 2.3.5 release development is in progress. What the heck? If we all jumped to 2.4.x what is the point of having 2.3.x alive, especially when there's no option to choose - major vs. minor upgrade versions?
2.4 is "64 bit land only". For some time - a year or so, a 2.3.5 will co-exists which still support 32 bit systems.
2.4.0 barely works after upgrade on my ESXi. 2.3.4 worked flawlessly. Now I'm constantly loosing connections, and CPU usage is permanently > 15%, even when there are only 5 connections active. Load average of the system never goes below 0.80.
Check out the "Virtualization installations and techniques" forum.
I'm not using any VM techniques but pfSense works just fine - so it's a 'local' setup thing.And I cannot seem to find source image for 2.3.4-p1 or what it was released in July?
I guess files still exist somewhere. ( I only found this https://snapshots.pfsense.org/i386/pfSense_RELENG_2_3/installer/?C=M;O=D but I looked 30 seconds max).
But, who needs old version ? ;) -
Why in the world team have decided to bump all of us to 2.4.0 major release? I would never expect that bump from 2.3.4 to 2.4.0 would cause the underlying OS upgrade too! :o
I'm not sure why you wouldn't expect that, the underlying OS is always upgraded in those cases. Every X.Y release has had a version upgrade, going back 10 years: https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD
On top of this - I see 2.3.5 release development is in progress. What the heck? If we all jumped to 2.4.x what is the point of having 2.3.x alive, especially when there's no option to choose - major vs. minor upgrade versions?
For people who can't upgrade to 2.4 because 2.4 does not run on their hardware. 2.4 is amd64 and ARM only, no more i386 and no more NanoBSD. Rather than drop people on older hardware entirely, we're giving them a full year to transition.
2.4.0 barely works after upgrade on my ESXi. 2.3.4 worked flawlessly. Now I'm constantly loosing connections, and CPU usage is permanently > 15%, even when there are only 5 connections active. Load average of the system never goes below 0.80.
There are some ESXi issues which are known and have been fixed – see not only the release notes but also the other boards on the forum here. There is a FreeBSD VTY race condition which can stop it from booting, and also an SNMP issue which causes high CPU, memory leaks, disk activity, and potentially other problems.
And I cannot seem to find source image for 2.3.4-p1 or what it was released in July?
2.3.4-p1 was a patch only release, no installers. You have to use 2.3.4 and upgrade to 2.3.4-p1.
If you want to stay on 2.3.x, 2.3.5 will be out later this week, but 2.4.1 will be out (probably today) and it addresses most of the problems people have had with 2.4.0.
-
Why in the world team have decided to bump all of us to 2.4.0 major release?
Nobody from Netgate has shown up at my office and forced me to upgrade. I deliberately wait at least a couple of weeks after a major release. If it's critical, I will test it out in my lab first. I might suggest you try this approach next time.
