On my network I have a live OPNsense machine and an identically configured backup. This is not HA. It's just a backup machine dangling on the network by its WAN port so I can keep it updated and swap it in if the main router fails. It doesn't route anything because the LAN port isn't connected. The setup has been fine for ages.
I noticed recently when I check for updates, the output doesn't look right. I have not changed anything in either configuration for a long time. I just apply updates as they become available. Does anyone have any theories?
MAIN MACHINE
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.7.4_1 (amd64) at Fri Sep 25 09:59:47 EDT 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
BACKUP MACHINE
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.7.4_1 (amd64) at Fri Sep 25 10:00:22 EDT 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
All repositories are up to date.
Checking for upgrades (86 candidates): .......... done
Processing candidates (86 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
I ran this command from the shell:
opnsense-update -fp
That seemed to clear everything up. Both machines are current and now show zero candidates.