pfSense Plus Software Version 23.09 BETA Now Available for Testing
-
Yes, if should be available to all Plus users at this point.
-
Hi @stephenw10, I understand it should be available, but it's not showing up and I notice nobody else has reported success yet. I just see an option for "Latest Development Snapshots (23.09)" (and of course "Previous 23.01" and "Latest 23.05"). When I select 23.09 is tells me "Latest Base System: 23.05.1" and "Status: Up to date.".
I'm just questioning whether all the deployment settings were actually correct to make the beta available to end users. Any success by other users would indicate it's a problem on my end, but no success by anyone else points to a release configuration issue.
Thanks for your weekend reply!
Mike -
@mikebenna A little while ago (perhaps and hour) I upgraded a whitebox device from 23.05.1 to 23.09 with out any issues.
Ted
-
@mikebenna said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
I understand it should be available,
this is how it shows up on my device -- I have not done the "upgrade" at this point because simply put --- it is the weekend.
-
Boom!
Notes: Upgraded my 6100 MAX from 23.05 RELEASE successfully. I ended up having to to upgrade twice after flipping the repo.
First: 23.09.b.20231013.0600
Then: 23.09.b.20231014.1618 -
Ah, interesting... my SG-6100 found the beta and upgraded just fine, but the VM I use for testing things like betas (also running plus) still can't see the beta, even after rebooting and checking again for updates. Thanks everyone for their feedback.
-
If you send me the NDI from that VM in chat I can check what it should be seeing.
-
@mikebenna 23.09.b.20231015.0519 is available now.
-
So far everything has been very smooth. I installed the 3rd 23.09 beta this morning.
-
Major packages:
Snort, pfBlockerNG, HA Proxy, and ntop. No issues whatsoever. Nice work.
-
Pulled the update tigger this morning.
Initially the GUI said "Unable to check for updates" wait a bit, nothing
so I switched back to 23.05.1 branch and it said the same "unable to check"Logged out, and back in, check again with 23.05.1 and reports current with no update
re-selected 23.09 beta - again reports "Unable to check for update"
logged out and back in with 23.09 Beta branch selected and immediately saw the 23.09 beta availableSeems like this could be a page refresh issue and nothing more, in this case
Confirmed and Updated just fine. 23.09.b.20231016.0231
All packages running as expected.
I even had two patches (of my own creation) for pfBlockerNG (for which the Auto Apply was checked just before running the update) and they both survived
the Auto Created boot environment for "default" is reporting about 2GB more under space column as compared to what "default" was before. (previous read 3.4G and the current default reads 5.24G (no issue just an observation)
-
@jrey said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
the Auto Created boot environment for "default" is reporting about 2GB more under space column as compared to what "default" was before. (previous read 3.4G and the current default reads 5.24G (no issue just an observation)
This is typical with any boot environment since it's technically just pointers to the same installed packages - just the config diffs are what's different. If you delete the old boot config, you will reclaim the 2GB+ of space.
-
No issue - just and observation ;-)
I have all my previous boot environments going back to 22.05 and the mention was only because this was by far the single largest increase in "default" from one version to the next -also the memory footprint has changed significantly from what was "normal" on 23.05.1 -- again no issue, just an observation
-
That memory should eventually be freed but you should also be able reboot again to free it. The upgrading process itself uses significant memory.
-
Hmm... my slave VM was happy running the beta over the weekend. This morning I upgraded my master VM and it crashed 3 times immediately after the upgrade. It was happy for 30min or so, then I did another reboot to see what happened and boom... crashing again during startup... once, twice, three, four times. I may simply revert. Oh wait, fifth reboot succeeded! I'll leave it here for now. :)
Looks like a page fault right around the time of bringing up a Wireguard tunnel.
Slave is running a similar Wireguard config but has never crashed.
How can I be of further assistance?
-
Better to open a thread in the 23.09 sub to troubleshoot problems: https://forum.netgate.com/category/92/plus-23-09-development-snapshots
Steve
-
@stephenw10 said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
eventually be freed
so just to close the loop on this observation, about 2 hours later I noticed that the Active and Inactive values had reverted (actually just about switched positions (crossed) from where they are shown on graph above and therefore more in line with their pre-update lines.
The value for the cache never cleared and after about 3 hours (so an hour after the other values corrected) I just let it run but "eventually" I just rebooted to flush whatever had been cached during the update.
clearly 3+ hours is not enough time to be considered eventually.
All values now trending very near pre-update values.
Still not an issue, just an observation. Have a great evening. -
@jrey said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
@stephenw10 said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
eventually be freed
so just to close the loop on this observation, about 2 hours later I noticed that the Active and Inactive values had reverted (actually just about switched positions (crossed) from where they are shown on graph above and therefore more in line with their pre-update lines.
The value for the cache never cleared and after about 3 hours (so an hour after the other values corrected) I just let it run but "eventually" I just rebooted to flush whatever had been cached during the update.
clearly 3+ hours is not enough time to be considered eventually.
All values now trending very near pre-update values.
Still not an issue, just an observation. Have a great evening.After each OS update, even a minor one, I usually let it reboot post-install, make sure all packages are up-to-date, clear most of the logs, delete the old boot environment if things looks smooth, and reboot once more manually just to start clean after post-processing. That way the system comes up in a normal state with clean resources. This has worked well for me.
-
I tested 23.09 beta on my Intel NUT where is runnin 23.05. It has several problems and I had to reload 23.05 on boot enviroment. It loads slower then 23.05, mostly I had 502 Bad Gateway when I tried access GUI. Freeradius doesnt work properly and I also do not have internet connection even if all packages were running in System/Services . Dont know why this happen, but on 23.05 is everything working fine again.
-
Open a thread in the 23.09 sub with any details you have: https://forum.netgate.com/category/92/plus-23-09-development-snapshots
