Upgrade Successes
-
Successful full upgrade of a VM system from 2.3-RC to 2.3-RELEASE.
Successful upgrade of Alix 2GB nanoBSD from 2.2.6-RELEASE to 2.3-RELEASE.
I forgot to check what weird packages I had installed on the Alix (I use it for testing and playing as well as home to office VPN…). It had TFTP, which is no longer a package, so I had the TFTP menu item that went to 404, and TFTP listed as down in Status->Services. I grabbed config.xml, removed the various TFTP package menu service... bits and restored the config. All good.
Lesson before upgrading: Actually look at the packages that are installed and remove any that are not available in 2.3 - that would be the much easier way.
and successful upgrade of an APU 64-bit nanoBSD that had been sitting in the cupboard for a few months, from some old 2.3-BETA to 2.3-RELEASE.
-
Look in the /conf folder… There are .txt files there
I think I found it in my syslog server -
Apr 12 18:37:11 192.168.2.1 Apr 12 18:37:11 php-fpm[92699]: /index.php: PHP ERROR: Type: 1, File: /usr/local/www/widgets/widgets/pfblockerng.widget.php, Line: 286, Message: Call to undefined function rule_popup()
I also grabbed the upgrade log txt file, if you need anything from it.
That pfSense function (rule_popup() ) is actually from 2.2 :) Its not in 2.3 any longer… Probably safe to ignore...
-
Look in the /conf folder… There are .txt files there
I think I found it in my syslog server -
Apr 12 18:37:11 192.168.2.1 Apr 12 18:37:11 php-fpm[92699]: /index.php: PHP ERROR: Type: 1, File: /usr/local/www/widgets/widgets/pfblockerng.widget.php, Line: 286, Message: Call to undefined function rule_popup()
I also grabbed the upgrade log txt file, if you need anything from it.
That pfSense function (rule_popup() ) is actually from 2.2 :) Its not in 2.3 any longer… Probably safe to ignore...
Weird that there would be a log from a 2.2 function though. I initiated the 2.3 upgrade at 18:33, and that error is at 18:37, so I am pretty sure it happened during the upgrade.
In any case, everything is working so beats me. :)
-
I upgraded from 2.2.6 to 2.3 successfully, it was practically seamless except for the reboot…
Great job guys!!!
-
I upgraded 7 of them. No issues.
-
I upgraded from 2.2.5 to 2.3 without any issues. I did get a couple of messages saying Level 7 shaping is no longer supported and some other package. Neither one a big deal to me as don't use them.
I've upgraded to 2.2.6 a few months ago and ran into some issues so reverted back to 2.2.5. Happy to see 2.3 upgrade went without issues. Everything worked.
Love the new menus. Very clear and easy to find things on the page.
Going to find that donation page.
Keep up the great work pfSense team!!
-
I upgraded from 2.2 to 2.3 and after initially working it eventually became totally unresponsive and horked itself.
But this isn't my first rodeo. I had a USB stick and a config export at the ready and was up and going 10m later. Even a failed upgrade isn't cause for downtime if you think ahead just a little bit.
-
6 different boxes all without a hitch.
Microsoft updates today on the other hand didn't go as well. ::)
-
I upgraded from 2.2.6 to 2.3 successfully. Zero problems thanks Pfsense staff
-
Y'all have pushed a lot of bits. On the 12th (US EST) there were 4705 systems auto-updated. More specifically, 4705 unique IPs downloaded auto-update, so that's definitely under-counting to at least some extent, for those upgrading multiple systems behind NAT.
-
6 different boxes all without a hitch.
Microsoft updates today on the other hand didn't go as well. ::)
I'm an IT manager at a good size company with 240+ machines. Would given me a headache if I released the Windows updates via the WSUS server tonight. ;D I usually wait a couple of weeks to release it to give Microsoft a chance to fix whatever they broke with the updates. It is a security risk but I have other network monitoring servers running Linux to keep eye on things. Also most of my users know not to open unknown attachments or click on anything suspicious. They usually submit a ticket to have us check it out first.
Thanks for the Windows updates heads up. lol
-
I'm an IT manager at a good size company with 240+ machines. Would given me a headache if I released the Windows updates via the WSUS server tonight. ;D I usually wait a couple of weeks to release it to give Microsoft a chance to fix whatever they broke with the updates. It is a security risk but I have other network monitoring servers running Linux to keep eye on things. Also most of my users know not to open unknown attachments or click on anything suspicious. They usually submit a ticket to have us check it out first.
Thanks for the Windows updates heads up. lol
We not so big. Usually wait till the weekend. (didn't I just read a post around here about Friday updates??? :o ) Some stuff I got a little worried about I wanted to get patched. http://www.dshield.org/
Makes me very happy the router upgrades went so well. Could have waited but first one went so well I couldn't help but do the others.
-
I successfully upgraded from 2.2.6 to 2.3 in a KVM VM, except for a minor issue with squid.
-
xenserver VM updated from 2.2 to 2.3 snapshots a few weeks ago to 2.3 release tonight no issues
-
upgraded 2.26 => 2.3 No issues!
Thank you for excellent job!
Jonna
-
I must admit I started the upgrades expecting some issues. There are always problems when you upgrade software, it's just a fact of life. The trouble is I've not had a problem yet. So thanks to the team for an exceptionally well put together upgrade and thanks to all the testers for finding those annoying little bugs.
-
Upgraded from 2.2.6 to 2.3 in a Proxmox KVM environment without problems, except the crashes in pfBlockerNG.
Excellent work!
-
Upgrade from 2.2.6 to 2.3.x in under 5 minutes and hasslefree on a homebrew c2758 - as usual :) - Thanks Guys!
-
Upgraded from 2.2.6 to 2.3 on a Proxmox 4.1 VM. No issues aside from bind package not being available in 2.3.
-
(auto) upgraded from 2.2.6 to 2.3.0 - native hard disk install running on a Dell Dimension.
Wasn't checking out the upgrade process, so can't tell what happened during the install, but when I came back all was up and running.Using IPv4 and Ipv6 - Avahi and pfBlockerNG (I removed "nut" before the upgrade, I'll hope it will come back soon).
Looks perfect, as usual.
edit (10 hours afterwards) : no words, images : Munin on pfSense : https://www.test-domaine.fr/munin/brit-hotel-fumel.net/pfsense.brit-hotel-fumel.net/index.html [ I updated April, 13th, 2016 11:00 AM)
