23.05 - Strange mention and not the same on two pfsense!?
-
Strange mention and not the same on two pfsense!?
[23.05-RELEASE][xxxxxx@pfSense.xxxxxx.xxx]/home/xxxxxx: sudo pkg upgrade
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 (1 candidates): 100%
Processing candidates (1 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.On my pfsense which is in use, I have "1 candidates" and on the one which is not in use, but in reserve in case of failure of the one in use I have "0 candidates".
Do you know what this means?
Is this a sign of a problem?
why not the same message between my two pfsense?Thanks for your advice
-
@SwissSteph said in 23.05 - Strange mention and not the same on two pfsense!?:
pkg upgrade
Not sure what that means exactly - ran it on mine and I had a package to update.
[23.05-RELEASE][admin@sg4860.local.lan]/root: pkg upgrade 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 (2 candidates): 100% Processing candidates (2 candidates): 100% The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-repoc: 20230523 -> 20230530_2 [pfSense] Number of packages to be upgraded: 1 5 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching pfSense-repoc-20230530_2.pkg: 100% 5 MiB 5.1MB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pfSense-repoc from 20230523 to 20230530_2... [1/1] Extracting pfSense-repoc-20230530_2: 100% [23.05-RELEASE][admin@sg4860.local.lan]/root: pkg upgrade 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 (1 candidates): 100% Processing candidates (1 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [23.05-RELEASE][admin@sg4860.local.lan]/root: -
what's strange is that even if you update ... you'll get, like me, "candidate 1" ... whereas I have "candidates 0" on my other pfsense.
I don't think this is too serious. The difference between my two pfsenses is that the one that has "Candidate 1" is an update from 23.01 to 23.05 just when it went online and the one that says "Candidate 0" is a new installation made yesterday following my NVME failure.
So I went from the 2.7 beta of February 15 -> 23.01 -> 23.05
I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
... And now I'm living with a Netgate 8200
... And sorry for my bad English... -
@SwissSteph I think one of the new things in 23.05 was wireguard installs, when new install. So maybe that is the 1 that is missing on the upgraded ones, from my understanding it doesn't install if not already installed on an upgrade.
https://docs.netgate.com/pfsense/en/latest/releases/23-05.html
WireGuard is now installed by default on new installations. This does not affect upgrades or factory reset configurations, only fresh installations.Mine is an upgrade from 23.01
-
@SwissSteph ok bit of digging, its prob related to this??
[23.05-RELEASE][admin@sg4860.local.lan]/root: pkg version -vRL= 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. py311-maxminddb-2.2.0_2 > succeeds remote (remote has 2.2.0_1) [23.05-RELEASE][admin@sg4860.local.lan]/root:Seems something is not quite in sync - but not sure if any sort of thing to be concerned about?
-
the "sudo pkg version -vRL=" command gives me the same answer as yours.
And then I always get "1 candidate": 100%".
I'm just trying to understand why there are differences, and also if I can put everything the same ;-)
-
@SwissSteph yeah I am with you.. Also like to understand why the remote is not the same as the local.. But only on updated systems? Something not quite in sync for sure.
Have to look to what installed that maxminddb - my guess would be maybe pfblocker, as it lists py-maxminddb-2.2.0_1 as a dependency.. But how is it an upgraded box got newer version? Maybe there is an update coming to pfblocker?
I am also curious to what exactly pfSense-repoc is ;)
-
pfSense-repoc is the dynamic repository client pfSense uses to pull in new repo data and the certs to access them.
-
On my brand new pfsense (my first Netgate, an 8200) it says:
"0 candidate: 100%".
