2.4.0 Release

jwhitley

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.

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.

JonH

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.

0xFFAA19

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.

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.

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

Jason.PNG_thumb

MrZombieJesus

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

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.

bcruze

@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

robero

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)

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

2_4_Error.jpg_thumb

Razidd

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

jimp

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

jimp

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

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

robero

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

lobotiger

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

Grimson

@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

TheUniquePaulSmith

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

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.