2.70 CE release any issues so far??
-
Not an issue, but a difference
Your system might run "Hotter" on newer CPU's , due to FreeBSD 14+ preferring Speed Shift on newer CPU's
Just "tune it down a bit" .... See:
https://forum.netgate.com/post/1113744 -
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
The per-log settings issue is now patched: https://redmine.pfsense.org/issues/14545#note-3
-
@Cool_Corona said in 2.70 CE release any issues so far??:
Just as the title says...
Looking to upgrade from 2.5.2 but are hesitent.
Honestly, I have never upgrade my pfSense production boxes and ran into issues I could not resolve almost immediately...where is your faith in your abilities?
-
Perhaps a better question would be; what issue in 2.6 prevented you upgrading to that?
-
I got a php error after a few days, but nothing afterwards.
-
Like during the upgrade or immediately after it? If it doesn't return during normal use it was almost certainly an artifact from the php change at upgrade.
-
I got it after the version upgrade.
From a clean install a few months ago of version 2.6 to version 2.7.
Not got it back so far. -
@stephenw10 We run about 320 VLAN's and there was an issue with 2.6
-
My brother tried an upgrade from 2.6.0 to 2.7.0 and it was a disaster. He removed the packages as instructed, but after the upgrade he got a message "fetching pakket 154 libpcap" which would not go away. Tried to go back to 2.6.0 , but GUI would not start. Even reset to factory defaults would not help. After a long battle, he managed to get 2.6.0 re-installed. Even then, several messages like "WARNING: Current pkg repository has a new PHP major version. pfSense should be upgraded beforeinstalling any new package.'
Seeing other results on this forum about strange behaviour after the upgrade, I will wait for the next fix in 2.7.1 or so before I take the plunge.
-
Why not re-install from scratch ver 2.7?
Then the upgrade will no longer be needed. -
@Waqar-UK said in 2.70 CE release any issues so far??:
Why not re-install from scratch ver 2.7?
Then the upgrade will no longer be needed.He's probably got same issue I have. I'm sticking with 2.6.0 CE till next version of 2.7.x CE comes out. I've tried upgrading and tried fresh install of 2.7.0 CE. It gets to end and says install complete and then hangs in the reboot. I had no packages installed but that doesn't seem to make a difference. I've let it try to reboot for at least an hour one time and it never completed reboot. I'm tired of messing with it.
This is the first time in at least 7-8+ years that I've ever had an issue with a pfSense upgrade. Would seem that Netgate messed something up. I'm going to stay with 2.6.0 CE until further notice. Don't have time to keep beating a dead horse.
-
Sadly looks as something is needed to be done with ver 2.7.
Have you tried another computer? -
Hanging at reboot is not the same issue as failing to pull in packages. That's more like a hardware compatibility issue in which case, yes, upgrading or installing clean may not make much difference. @jdeloach do you have an open thread for that?
@Cool_Corona Is that a specific bug or simply a usability issue with that many interfaces?
-
@stephenw10 Its related to limiters not working on VLAN's in 2.6
-
Hmm, you have a link to that bug and/or thread?
This perhaps? https://redmine.pfsense.org/issues/14433
I'm certainly not aware of any issues with Limiters and VLANs in 2.7.
Edit: Oh you mean this? https://redmine.pfsense.org/issues/12954
Not VLAN specific but also solved in 2.7. -
Hi,
I've got issues. After upgrading from 2.6 to 2.7 the Web Interface becomes super slow after 2 or 3 pages (for instance, if you are configuring Traffic Shaper, after step 2 or 3 the page does not load). IT does happen across the board if you are navigating between pages
I did some investigation by:
-
Opening Chrome on the developer to check mode and it keeps waiting for the PFSense to respond. Any other site or application (I do have servers on the LAN) opens fine for testing purposes.
-
Nginx access log does not show the GET requests. I tried to check the Nginx error logs, but nothing
-
Memory is not going over 6% (My box rans on 16GB)
-
CPU does not go over 8%
-
Disk is only 2% used
I've also tried to install it from scratch and restore the configuration... But the same performance issues.
It was working for years on the old version (which us upgraded before from the old Old version).
Is anyone having the same issue?
-
-
@stephenw10 said in 2.70 CE release any issues so far??:
Hanging at reboot is not the same issue as failing to pull in packages. That's more like a hardware compatibility issue in which case, yes, upgrading or installing clean may not make much difference. @jdeloach do you have an open thread for that?
@Cool_Corona Is that a specific bug or simply a usability issue with that many interfaces?
No, I do not have an open thread for that.
-
@alexmh said in 2.70 CE release any issues so far??:
I've also tried to install it from scratch and restore the configuration... But the same performance issues.
Does it do it in the default config before you have restored your file into it?
Is something in your config preventing the firewall connect out?
Does it do it on every page? The screenshot shows it from status_gateways which has to pull in the actual gateway data.
-
@jdeloach said in 2.70 CE release any issues so far??:
No, I do not have an open thread for that.
Ok, then I would start a new thread for that so we can review what's happening there.
-
- No, it only does after I've imported my configs
- Nothing is preventing the FW to connect out, same hardware (hardware settings, KVM/QEMU VM, same Linux Debian host, same switches config, ISP.. all the same)
- Yes, it does on every page, unfortunately
