Upgrade Successes



  • Thought it might be nice to have a single thread (to prevent forum pollution) for people to post some positive experiences…

    I upgraded from 2.2.6 to 2.3 successfully.

    I did get a crash report on the pfBlocker widget during the upgrade, and submitted the crash report to the developers. Even though I got a crash report, pfBlocker seems to have installed correctly and is working.

    Good job guys!

    Jason


  • Moderator

    What was the widget error?



  • Was at 2.2.6 to 2.3 beta to RC and followed cmb post about fetch keys then upgraded finally to 2.3 final.
    Smooth transition throughout.
    Beers for everyone. I think jimp said he was buying.
    Good job.



  • @BBcan177:

    What was the widget error?

    Good question… I didn't write it down since it asked me to submit it, which I did. lol. It was a PHP error, I'll see if I can find it in the logs somewhere... Sorry about that.

    Edit - I think this was it:

    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()

    Jason


  • Moderator

    Look in the /conf folder… There are .txt files there



  • @BBcan177:

    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.



  • 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.


  • Moderator

    @JasonJoel:

    @BBcan177:

    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...



  • @BBcan177:

    @JasonJoel:

    @BBcan177:

    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.




  • @chpalmer:

    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



  • @Darkk:

    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)



  • Upgrade successful!  Nice job!  Love the new UI…much better for old tired eyeballs like my own.

    It went almost completely without error...but...I still get that stupid "DXIO Commit" thing (supposing of course that I spelled DXIO in the right order or whatever).  I get that after every upgrade/update.  And usually in between when there is a reboot involved.  I looked through the forums awhile back for it (a year or two ago) and didn't find much on it, nor anything that I cared to try in the way of fixing it.  But it doesn't seem to cause any major issues either so when I see it flashing at the top of my screen, I know that I've had a power outage or some other cause for reboot and I go looking through the logs to see what happened.  So for now I just use it as my own personal reboot indicator flag.

    You guys did a fantastic job with the new release.  Please accept my gratitude in lieu of my gold subscription this time around.  I just started a new business and have dumped literally everything into it but the kitchen sink --and they called yesterday wanting that too.  When she turns a buck or two I'll renew on the gold.  But for now, Thank You for the fine job you've done.

    David Tucker



  • Great work by all the devs, this is a really good step forward.

    I had no issues so far with the upgrade, some things in the UI are still a little rough around the edges but less so than before.

    Thumbs up from me!



  • I successfully upgraded to 2.3 from 2.2.6 on my 4860.

    The only thing acting weird was Squid would not start, but it also wouldn't write an error on why.  I scrolled through the logs and only found this:

    Apr 13 09:09:42 squid 99607 Squid Parent: will start 1 kids
    Apr 13 09:09:42 squid 99607 Squid Parent: (squid-1) process 315 started
    Apr 13 09:09:43 squid 99607 Squid Parent: (squid-1) process 315 exited with status 1
    Apr 13 09:09:46 squid 99607 Squid Parent: (squid-1) process 7179 started
    Apr 13 09:09:46 squid 99607 Squid Parent: (squid-1) process 7179 exited with status 1
    Apr 13 09:09:49 squid 99607 Squid Parent: (squid-1) process 32303 started
    Apr 13 09:09:49 squid 99607 Squid Parent: (squid-1) process 32303 exited with status 1
    Apr 13 09:09:52 squid 99607 Squid Parent: (squid-1) process 40231 started
    Apr 13 09:09:53 squid 99607 Squid Parent: (squid-1) process 40231 exited with status 1
    Apr 13 09:09:56 squid 99607 Squid Parent: (squid-1) process 47132 started
    Apr 13 09:09:56 squid 99607 Squid Parent: (squid-1) process 47132 exited with status 1
    Apr 13 09:09:56 squid 99607 Squid Parent: (squid-1) process 47132 will not be restarted due to repeated, frequent failures
    Apr 13 09:09:56 squid 99607 Exiting due to repeated, frequent failures

    Squid was giving me some issues with my small network prior to this, so I just removed it until I have time to figure out the appropriate settings that won't throttle/choke/die whenever a steam client updates or a game updates.



  • I got some PHP errors on first boot after the upgrade but they didn't show up on second boot anymore. Everything worked fine though from the first boot and onwards.



  • Upgraded from 2.2.6 to 2.3 in minutes with out any problems.

    Have a few packages installed:
    pfblockerng
    nmap
    autobackup
    openvpnclientexport

    Like the new interface.



  • worked like a charm, 2.2.6 -> 2.3 atom box



  • Had no issues at all using GUI update.



  • thus far i've updated 4 systems remotely. all worked fine as I expected.

    1 of systems that had an old 2.1.4-release running had an issue with reinstalling some packages upon initial boot; reinstalling them after the upgrade fixed that.



  • Upgraded from 2.2.6 to 2.3. No issues.

    I can finally control the IPv6 RA and DHCPv6 server settings on LAN interfaces that track the WAN interface for IPv6 prefix delegation. Been wanting this feature for a while as it makes it much simpler to set things up so that all the hosts on my LAN use my internal DNS server. The new UI is pretty slick too.



  • Me to :) , upgraded from 2.2.6 to 2.3 successfully, on my  Dell 850, RAID1, Intel(R) Pentium(R) D CPU 3.00GHz
    2 CPUs, 8 Gb DDR2 ECC. Thank u PFSense Team you are "GREAT" !!!!



  • I've upgraded 5 systems in the past 24 hours, all production systems.

    1x SG-8860
    1x SG-2220
    1x SG-2440
    1x Dell PowerEdge 320
    1x VM

    Not a single issue



  • Upgraded from 2.2.6 to 2.3 in less than 10 minutes last night with no issues.  Atom D525, 64 bit.

    Still finding my way around the new menus, but the box is fast and stable.

    Nice job devs!



  • Upgrade 2.2.6 to 2.3 went without a problem. 8 ipsec site-to-site tunnels, snort, pfblockerNG and freeradius. Everything working ok after update. Thank you all that worked/tested/contributed in some way to make pfSense amazing.

    Wish I could send you all a beer. 8)



  • Upgraded today from 2.2.6 to 2.3 on a Zotac mini computer and so far everything appears to be working fine.  Snort and OpenDNS are really the only things extra that I'm using and both are working ok.  New interface is interesting…might take some time to get used it after all these years with the older one.

    The only oddities I noticed was a message about layer 7 traffic shaping no longer supported. Going to need to look into to that as I was using it before.  And the RRD traffic graphs no longer being available.  I really liked having one page where I could see my traffic utilization from hours to years nicely represented.  Also from another thread, I too would like to see the total amount of transferred data brought back to the graph section.  This was handy to compare my usage vs what my ISP tells me.

    Good job everyone!

    LoboTiger