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!


  • Rebel Alliance Developer Netgate

    @sronsen:

    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.



  • @chudak:

    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:

    @chudak:

    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?



  • @chudak:

    @jgiannakas:

    @chudak:

    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.



  • @jgiannakas:

    @chudak:

    @jgiannakas:

    @chudak:

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



  • @jgiannakas:

    @chudak:

    @jgiannakas:

    @chudak:

    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!



  • @Razidd:

    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  ;D

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



  • upgraded without issues. Thank you pfsense team!

    now only ZFS upgrade left. I will backup and re-install. I guess that is the only way.



  • @mirkwoody:

    '
    All seeming good here too  ;D

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

    The "System update failed!" error? Got that one a couple of seconds after hitting the confirm button in 2.3.4. Then I waited a minute, hit the button again and now it looks like updating went without problems.



  • Upgrade successful but I'm monitoring an issues where webaccess SSH even serial stops responding after a period of time yet internet is still going SSH or serial will allow login but never displays the splash screen/welcome screen that usually gives you a menu




  • @bartgrefte:

    @mirkwoody:

    '
    All seeming good here too  ;D

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

    The "System update failed!" error? Got that one a couple of seconds after hitting the confirm button in 2.3.4. Then I waited a minute, hit the button again and now it looks like updating went without problems.

    I too got "System update failed!" at first. waited a minute like you mentioned and ran it again. It upgraded without further issues.  Thanks for posting.



  • I too got "System update failed!" at first. waited a minute like you mentioned and ran it again. It upgraded without further issues.  Thanks for posting.

    I also got that.



  • @JKnott:

    I too got "System update failed!" at first. waited a minute like you mentioned and ran it again. It upgraded without further issues.  Thanks for posting.

    I also got that.

    Same here I wanted about 30 minutes and tried again and had a quick flawless update

    All my old tweaks worked plus I enabled aes ni under miscellaneous to ticker with



  • Upgraded from 2.3.4 to 2.4.0

    I got several errors at bootup: "There were error(s) loading the rules: pfctl: bridge1: driver does not support altq - The line in question reads [0]: @ 2017-10-13 12:53:16"

    No internet connection anymore.
    I suggest you think twice before upgrading if you have Pfsense in Bridge mode. Just installed back to 2.3.4 (luckily have old installation media)



  • Hi,
    I upgraded from web interface. And system ins not openning now!
    I attached screen.
    When I write
    ufs:/dev/ada01a
    on this screen than system started and open normally. But when I restart the system same black screen comes up?!

    What is wrong?…

    Regards,
    Mucip:)




  • @mucip:

    Hi,
    I upgraded from web interface. And system ins not openning now!
    I attached screen.
    When I write
    ufs:/dev/ada01a
    on this screen than system started and open normally. But when I restart the system same black screen comes up?!

    What is wrong?…

    Regards,
    Mucip:)

    Follow the instructions in the link in my post above (blog article has pretty much a step-by-step).  You basically just need to alter your fstab to match your new drive names from the console once PFSense has booted up for both root and swap.


  • Rebel Alliance Developer Netgate

    @hiryu:

    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.

    You'll have to reinstall, there is no proper way to force a downgrade. It's easy to reinstall though, and your config can still be used because the format hasn't changed on 2.4.1 yet.


  • Rebel Alliance Developer Netgate

    @JasonAU:

    Upgrade successful but I'm monitoring an issues where webaccess SSH even serial stops responding after a period of time yet internet is still going SSH or serial will allow login but never displays the splash screen/welcome screen that usually gives you a menu

    Sounds like maybe you're hitting what people are seeing in this thread: https://forum.pfsense.org/index.php?topic=137103.msg754234#msg754234 - Try the suggestions there, if they apply.


  • Rebel Alliance Developer Netgate

    @robero:

    I got several errors at bootup: "There were error(s) loading the rules: pfctl: bridge1: driver does not support altq - The line in question reads [0]: @ 2017-10-13 12:53:16"

    I suggest you think twice before upgrading if you have Pfsense in Bridge mode. Just installed back to 2.3.4 (luckily have old installation media)

    https://redmine.pfsense.org/issues/7936

    Also, the number of people using both bridge mode and traffic shaping at the same time is … low. :-)



  • @jimp:

    @robero:

    I got several errors at bootup: "There were error(s) loading the rules: pfctl: bridge1: driver does not support altq - The line in question reads [0]: @ 2017-10-13 12:53:16"

    I suggest you think twice before upgrading if you have Pfsense in Bridge mode. Just installed back to 2.3.4 (luckily have old installation media)

    https://redmine.pfsense.org/issues/7936

    Also, the number of people using both bridge mode and traffic shaping at the same time is … low. :-)

    Thanks for the link. Any chance traffic shaping is introduced in bridge mode in future releases? Is there any place where to download previous releases? Could not find them from download pages. I guess I have to stick with previous releases for the time being.



  • Upgraded last night and like a few others it said on the web interface that the upgrade had failed.  However after rebooting the box it came back up with the newly installed system.  Only thing I've noticed so far is that the system is using way more memory than what it was before.  It's hovering around 90% vs the <40% that I recall from before.

    LoboTiger



  • @Razidd:

    Follow the instructions in the link in my post above (blog article has pretty much a step-by-step).  You basically just need to alter your fstab to match your new drive names from the console once PFSense has booted up for both root and swap.

    No need to mess with fstab manually: https://forum.pfsense.org/index.php?topic=137929.msg754282#msg754282



  • @mucip:

    Hi,
    I upgraded from web interface. And system ins not openning now!
    I attached screen.
    When I write
    ufs:/dev/ada01a
    on this screen than system started and open normally. But when I restart the system same black screen comes up?!

    What is wrong?…

    Regards,
    Mucip:)

    Same thing happened to me. Upgraded remotely and the pfSense went offline and never came back. When I got home to address the issue, had the same mounting problem.
    At first I was able to boot by using the kernel.old, but the system was very unstable with many segmentation faults. Then after reading here online, I was able to mount the only harddrive I have in the system ada0sa1, and change the /etc/fstab.



  • @JasonAU:

    Upgrade successful but I'm monitoring an issues where webaccess SSH even serial stops responding after a period of time yet internet is still going SSH or serial will allow login but never displays the splash screen/welcome screen that usually gives you a menu

    I'm experiencing this behavior on my APU2C4 as well.


  • Rebel Alliance Developer Netgate

    @Jailer:

    @JasonAU:

    Upgrade successful but I'm monitoring an issues where webaccess SSH even serial stops responding after a period of time yet internet is still going SSH or serial will allow login but never displays the splash screen/welcome screen that usually gives you a menu

    I'm experiencing this behavior on my APU2C4 as well.

    Check to see if you're hitting this: https://forum.pfsense.org/index.php?topic=137103.msg754234#msg754234



  • @terminalhit:

    @mucip:

    Hi,
    I upgraded from web interface. And system ins not openning now!
    I attached screen.
    When I write
    ufs:/dev/ada01a
    on this screen than system started and open normally. But when I restart the system same black screen comes up?!

    What is wrong?…

    Regards,
    Mucip:)

    Same thing happened to me. Upgraded remotely and the pfSense went offline and never came back. When I got home to address the issue, had the same mounting problem.
    At first I was able to boot by using the kernel.old, but the system was very unstable with many segmentation faults. Then after reading here online, I was able to mount the only harddrive I have in the system ada0sa1, and change the /etc/fstab.

    I got the same result. I have updated it remotely through the webui: first attempt failed, the second was successfull but the router went offline. When I reached it, I found the same thing.

    I had to input the
    mountroot> ufs:/dev/ada0s1a
    in order to boot it

    Well done pfSense team!


  • Rebel Alliance Developer Netgate

    OK, this thread is officially getting unwieldy :-)

    Locking this thread for now. Please find an existing thread for a single issue topic or start separate threads for distinct issues but only after searching to see if you can find an existing related thread. We're seeing the same info in 2-3 threads and new threads for duplicate topics and so on.

    Using the "All Unread" view is especially helpful for locating new/recent threads: https://forum.pfsense.org/index.php?action=unread;all;


Locked
 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy