PfSense 2.4.0-RELEASE Now Available!

johnpoz

thanks jimp - I took a snap, added the kern.vty=sc to /boot/loader.conf.local

Ran the upgrade from the gui which was on snap from oct 9th..

Now spouting 2.4.0

2.4.0-RELEASE (amd64)
built on Tue Oct 10 06:43:01 CDT 2017
FreeBSD 11.1-RELEASE-p1

The system is on the latest version.
Version information updated at Thu Oct 12 12:19:42 CDT 2017

heper

A quick heads up, if you are running pfSense as a VM under ESXi 6.5.0 U1 (Bulld 6765664), read this: https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues

Jim,
I believe I experienced the same thing with esxi 5.5 (remove if its something different)
Had to powercycle the VM 5 times before it wanted to complete the boot up.
See picture below:
https://imgur.com/a/5ZAUC

I've rebooted a couple of times after adding the boot option & seems to be solved.

Could you update the doc, so others don't have to drive to the office at 6.30am ? ;)

jimp

@heper:

@jimp:

A quick heads up, if you are running pfSense as a VM under ESXi 6.5.0 U1 (Bulld 6765664), read this: https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues

I believe I experienced the same thing with esxi 5.5 (remove if its something different)

That looks like the same crash, strange. I have been running FreeBSD 11.1 on ESX 6.5.0 (not U1) for months and never saw that at all until I updated to U1. I updated the note on the wiki doc.

epionier

Thx for the release and your work!

I got the same boot problem under ESXI 6.0 Update 3a (latest version).

I made a snapshot in advance and reverted this way the corrupt 2.4 installation. I added the line as provided in boot.local.conf and then the update and boot went fine but there were some PHP errors / warnings. But the second reboot went fine and 2.4 is up and running.

Would be nice if there would be a post in the future when this problem is resolved and the line in boot.local.conf could be removed (if this makes a difference).

jimp

@epionier:

Thx for the release and your work!

I got the same boot problem under ESXI 6.0 Update 3a (latest version).

I made a snapshot in advance and reverted this way the corrupt 2.4 installation. I added the line as provided in boot.local.conf and then the update and boot went fine but there were some PHP errors / warnings. But the second reboot went fine and 2.4 is up and running.

Would be nice if there would be a post in the future when this problem is resolved and the line in boot.local.conf could be removed (if this makes a difference).

We already have a patch staged in 2.4.1 to test, keep an eye on https://redmine.pfsense.org/issues/7925 and https://forum.pfsense.org/index.php?topic=137628.0 for info.

tman222

Upgrade from October 4th 2.4.0-RC snapshot to 2.4.0-RELEASE went smooth with no issues whatsoever. Thanks for all your hard work on this everyone!

ibm_new

Nice interface! Like the layout and colors. Mostly I liked the update, but… after update to 2.4 the CPU use doubled and is now constantly in use. Also the memory went to max. So I went from 2 to 4 GB but still the memory is on 97% constantly. See the difference before and after update in the attached picture. I think I will revert to the 2.3 version if this is not solved.

Additional Update: PFSense stoped out of the blue! The internal interface wasn't accepting any requests anymore. Had to give a hard-reset. The strange thing is that external everything worked. Definitely going back to the old version since this version isn't stable.

Capture.JPG_thumb

21hertz

Just updated our testmachine to 2.4.0, running on ESXi 5.5.0. No crash here. The vmware-guestd service didn't automatically start though for some reason.

shavenne

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126

It that known by the pfsense devs? Went into this trouble at work today. Even SSH wasn't working anymore.

ivor

Are you sure you're not having a pfBlockerNG / DNSBL issue?

shavenne

Pretty sure because I don't use pfBlocker or something similar (at least.. as far as I know :D).

I also got this error in dmesg:
[zone: pf states] PF states limit reached

Pftop showed many connections with expiry time 00:00:00. Most of them were simple https connections with an age of many hours.

States graph attached.

![Bildschirmfoto zu 2017-10-19 16-13-35.png](/public/imported_attachments/1/Bildschirmfoto zu 2017-10-19 16-13-35.png)
![Bildschirmfoto zu 2017-10-19 16-13-35.png_thumb](/public/imported_attachments/1/Bildschirmfoto zu 2017-10-19 16-13-35.png_thumb)

ivor

Open a new topic with issues you're having please.