pfSense Plus 25.07 Beta Now Available
-
Upgraded my 4200 MAX without difficulty. However, I just noticed something strange with the the Status-->Monitoring display. The number of processes listed is huge in comparison to what top shows (64 processes)
-
@WN1X Here is the image:
-
You, image shows two things : "300" processes, which is a lot. 3x times to much.
But then : if you've installed and activated every possible pfSense package, it might be normal.The avarage pocessor usage is actually close to "zero" so if there are really 200 processes to much, they don't 'cost' you anything : tjhe are probably all sleeping.
Anyway, it time to leave the "all goes well" interface, the GUI, and use the real one.
Use the console, or ven better, activate SSH and ssh into your pfsense, use menu option 8 and type in the magic command :topand you'll see in an interactive way what processes are doing what.
You could get the big list with all processes with
ps auxUse
ps aux | wc -lto count.
edit : Humm : Diagnostics > System Activity ;)
Be ware : this GUI 'top' version lists probably all the threads. Not just the processes - a process can have multiple threads.
and now I understand you question
I saw the
Status > Monitoring and selected "System > Processor".and surprise :
so your 4200 and my 4100 are running nominal, and just fine
The monitoring tools show, imho, threads, not processes.
-
@Gertjan Either the labels need to be changed to say "threads" or the data source should be changed to show actual process counts.
Either way, it's just a minor bug.
-
@WN1X Digging into the /var/db/rrd/updaterrd.sh script which collects the data, I see it is using:
PROCS=`ps uxaH | wc -l | awk '{print $1;}'`to collect the process count. I believe the fix is to change this to:
PROCS=`ps uxa | wc -l | awk '{print $1;}'` -
On the other hand, your question / our discussions shows (me) somewhat that there is no 'good' number to be shown, but more a constant number (if all goes well).
Like this : my own pfSense 'process' stats over one year. As you can see, the number, whatever it might be, is stable, and that's what counts. -
Updated from 24.11 without issues !
-
@xenta said in pfSense Plus 25.07 Beta Now Available:
Updated from 24.11 without issues !
On SG 1100....
-
@dennypage said in pfSense Plus 25.07 Beta Now Available:
The release notes indicate:
This release includes support for DHCPv6 Prefix Delegation in the Kea DHCP daemon.For clarification, does this work with IPv6 Track Interfaces?
I.E. Can Kea provide an IPv6 delegation to a client on the on LAN interface if the LAN IPv6 interface is set up as a Track Interface following the WAN interface (which has received a /56 from the ISP via DHCP)?
@pfGeorge would you be able to comment on this please? Thanks.
-
@pfGeorge
Hello!
the last version doesn't work for me !
the reboot get stuck at setting the ipv6 default getway
I had to restore the last good boot config.
have good day ! -
Latest beta update (around 14 or 15 July) introduces something new :
-
-
@PiAxel Call it a RC and I am on it.
-
Does this change once the final is released?
-
Upgraded my SG4200 from 25.07.b.20250707.2346 to 25.07.r.20250709.2036 without issues. Running ACME, DynDNS, HAProxy, pfBlockerNG and some other minor packages.
-
@MBehr2 said in pfSense Plus 25.07 Beta Now Available:
Does this change once the final is released?
Yes it will.
And actually what it says is correct. Beta versions are always newer than release versions.
-
I'm currently on Beta 25.03.b.20250515.1415 and cant upgrade to 25.07.r.20250715.1733.
Hardware - Netgate 4200
Every time I initiate an upgrade I get the following error in the web UI:
- list itemSystem update failed!
- list itemAnother instance of pfSense-upgrade is running. Try again later
From the shell I get the following:
Enter an option: 13 pfSense-repoc-static: failed to fetch the repo data failed to read the repo data. failed to update the repository settings!!! failed to update the repository settings!!!Rebooting the system makes no difference.
-
Ok Fixed it with:
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade -
@brezlord said in pfSense Plus 25.07 Beta Now Available:
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
Spoke to soon. After reboot the system is still on 25.03.b.20250515.1415
I get the following error when trying to update packages:
pkg-static update -f Updating pfSense-core repository catalogue... pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package repository pfSense-core has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package repository pfSense has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package Unable to update repository pfSense Error updating repositories! -
UI Update output.
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching data.pkg: . done Processing entries: . done pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching data.pkg: .......... done Processing entries: .......... done pfSense repository update completed. 733 packages processed. All repositories are up to date. >>> Setting vital flag on pkg...done. >>> Setting vital flag on pfSense...done. >>> Renaming current boot environment from 25.03 to 25.03_20250719205419...done. >>> Cloning current boot environment 25.03_20250719205419...done. >>> Removing vital flag from php83...done. >>> Upgrading packages in cloned boot environment 25.03... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (10 candidates): .......... done Processing candidates (10 candidates): .......... done The following 10 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: if_pppoe-kmod: 25.03.b.20250515.1415.1500029 -> 25.07.r.20250715.1733.1500029 [pfSense] pfSense: 25.03.b.20250515.1415.1500029 -> 25.07.r.20250715.1733.1500029 [pfSense] pfSense-base: 25.03.b.20250515.1415 -> 25.07.r.20250715.1733 [pfSense-core] pfSense-boot: 25.03.b.20250515.1415 -> 25.07.r.20250715.1733 [pfSense-core] pfSense-default-config-serial: 25.03.b.20250515.1415 -> 25.07.r.20250715.1733 [pfSense] pfSense-kernel-pfSense: 25.03.b.20250515.1415 -> 25.07.r.20250715.1733 [pfSense-core] pfSense-pkg-Nexus: 25.03.b.20250515.1415 -> 25.07.r.20250715.1733 [pfSense] pfSense-pkg-System_Patches: 2.2.21_1 -> 2.2.21_2 [pfSense] pfSense-repoc: 20250419 -> 20250520 [pfSense] unbound: 1.22.0_1 -> 1.23.0 [pfSense] Number of packages to be upgraded: 10 The operation will free 12 MiB. 214 MiB to be downloaded. [1/10] Fetching unbound-1.23.0.pkg: .......... done [2/10] Fetching pfSense-pkg-System_Patches-2.2.21_2.pkg: ......... done [3/10] Fetching if_pppoe-kmod-25.07.r.20250715.1733.1500029.pkg: ... done [4/10] Fetching pfSense-pkg-Nexus-25.07.r.20250715.1733.pkg: .......... done [5/10] Fetching pfSense-kernel-pfSense-25.07.r.20250715.1733.pkg: .......... done [6/10] Fetching pfSense-base-25.07.r.20250715.1733.pkg: .......... done [7/10] Fetching pfSense-25.07.r.20250715.1733.1500029.pkg: .......... done [8/10] Fetching pfSense-boot-25.07.r.20250715.1733.pkg: .......... done [9/10] Fetching pfSense-default-config-serial-25.07.r.20250715.1733.pkg: . done [10/10] Fetching pfSense-repoc-20250520.pkg: .......... done Checking integrity... done (0 conflicting) [1/10] Upgrading unbound from 1.22.0_1 to 1.23.0... ===> Creating groups Using existing group 'unbound' ===> Creating users Using existing user 'unbound' [1/10] Extracting unbound-1.23.0: .......... done [2/10] Upgrading pfSense-repoc from 20250419 to 20250520... [2/10] Extracting pfSense-repoc-20250520: .. done [3/10] Upgrading if_pppoe-kmod from 25.03.b.20250515.1415.1500029 to 25.07.r.20250715.1733.1500029... [3/10] Extracting if_pppoe-kmod-25.07.r.20250715.1733.1500029: .. done [4/10] Upgrading pfSense-boot from 25.03.b.20250515.1415 to 25.07.r.20250715.1733... [4/10] Extracting pfSense-boot-25.07.r.20250715.1733: .......... done [5/10] Upgrading pfSense-pkg-System_Patches from 2.2.21_1 to 2.2.21_2... [5/10] Extracting pfSense-pkg-System_Patches-2.2.21_2: .......... done [6/10] Upgrading pfSense-pkg-Nexus from 25.03.b.20250515.1415 to 25.07.r.20250715.1733... [6/10] Extracting pfSense-pkg-Nexus-25.07.r.20250715.1733: .......... done [7/10] Upgrading pfSense-kernel-pfSense from 25.03.b.20250515.1415 to 25.07.r.20250715.1733... [7/10] Extracting pfSense-kernel-pfSense-25.07.r.20250715.1733: .......... done [8/10] Upgrading pfSense-base from 25.03.b.20250515.1415 to 25.07.r.20250715.1733... [8/10] Extracting pfSense-base-25.07.r.20250715.1733: ... done ===> Keeping a copy of current version mtree ===> Removing schg flag from base files ===> Extracting new base tarball ===> Removing static obsoleted files [9/10] Upgrading pfSense from 25.03.b.20250515.1415.1500029 to 25.07.r.20250715.1733.1500029... [9/10] Extracting pfSense-25.07.r.20250715.1733.1500029: .......... done [10/10] Upgrading pfSense-default-config-serial from 25.03.b.20250515.1415 to 25.07.r.20250715.1733... [10/10] Extracting pfSense-default-config-serial-25.07.r.20250715.1733: [10/10] Extracting pfSense-default-config-serial-25.07.r.20250715.1733... done Failed
