Does not seem to Proceed to install 22.7

[OnTheGrind]

@Lynxcat - Is it possible to explain the process to proceed to the upgrade? ELI5 if possible. Thanks.

[tong2x]

@lynxcat
what did you do to unlock?
what codes to run in console if any, so we could try it also

i have 2 server, 1 proceeded normally, but the other doesnt

EDIT:
i now have another server, another site, different config and setup same thing, running updates returns

Firmware status requires to check for update first to provide more information.

the updates was smooth at first... updated to 22.1.10_4 then 22.1.9 but somehow did not actually get 22.7

***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 22.1.10_4 (amd64/OpenSSL) at Fri Jul 29 15:46:11 -08 2022
Checking connectivity for host: pkg.opnsense.org -> 89.149.211.205
PING 89.149.211.205 (89.149.211.205): 1500 data bytes
1508 bytes from 89.149.211.205: icmp_seq=0 ttl=50 time=234.208 ms
1508 bytes from 89.149.211.205: icmp_seq=1 ttl=50 time=234.438 ms
1508 bytes from 89.149.211.205: icmp_seq=2 ttl=50 time=233.927 ms
1508 bytes from 89.149.211.205: icmp_seq=3 ttl=50 time=234.457 ms

--- 89.149.211.205 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 233.927/234.257/234.457/0.215 ms
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/22.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 799 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .. done
Processing entries: .... done
SunnyValley repository update completed. 31 packages processed.
All repositories are up to date.
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:4f00:a005:5::
ping6: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/22.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Updating SunnyValley repository catalogue...
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/22.1/OpenSSL/latest/meta.txz: Non-recoverable resolver failure
repository SunnyValley has no meta file, using default settings
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/22.1/OpenSSL/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/22.1/OpenSSL/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository SunnyValley
Error updating repositories!
***DONE***

[tong2x]

22.7 downgrade to 22.1.9.
If I proceed it will go back to 22.1.10_4

which will repeat the process again,
I will then have to goto console, option 12, 22.7 update.
but in all the detected firmware is 22.1.10_4

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 22.1.10_4 (amd64/OpenSSL) at Sat Jul 30 02:37:08 -08 2022
>>> Check installed kernel version
Version 22.7 is incorrect, expected: 22.1.9
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 22.7 is incorrect, expected: 22.1.9
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
SunnyValley
OPNsense
>>> Check installed plugins
os-dyndns 1.27_3
os-sensei-updater 1.11
os-sunnyvalley 1.2_2
os-theme-cicada 1.29
os-theme-rebellion 1.8.8
os-theme-tukan 1.25
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" has 66 dependencies to check.
Checking packages: .................................................................... done
***DONE***

[OnTheGrind]

Uh...


It sucks it has to be this way, but I am simply going to roll with 22.1.10_4 until I unlazy myself and just do a fresh install.

[Lynxcat]

I have another system that refuses to upgrade to 22.7, as per @Franco request I am ELI5 (hopefully) solution :

Currently running 22.1.x with FreeBSD 13.1-RELEASE, as per previous instructions by @Franco to allow 13.1-RELEASE over 22.1.x installs as per https://forum.opnsense.org/index.php?topic=28505.0 and locked base and kernel packages in System:Firmware:Packages and clicked the little unlocked icon (to lock) at the end of base and kernel package lines (on the righthand side), as such preventing downgrades to 13.0-release while still allowing to upgrade 22.1.x all the way t 22.1.10_4 without overwriting 13.1-RELEASE.

Once at 22.1.10_4 and 13.1-RELEASE (locked), there is no way to upgrade to 22.7, as system insist that is up to date, except for usual base and kernel 13.0-RELEASE package downgrade availability (which of course are locked, therefore won't downgrade regardless).

The only way for system to detect 22.7 availability is to unlock base and kernel packages in Sytem:Firmware:Packages and hit the lock icon (to unlock) at the end of base and kernel package lines (on the righthand side) and downgrade to 13.0-RELEASE.

Once base and kernel are unlocked and downgraded to 13.0-RELEASE, the system proceeds to detect 22.7 upgrade and allows to proceed to 22.7.

Hope this helps.

[tong2x]

is this needed to be executed?

# opnsense-update -bkzr 22.7.b
# opnsense-shell reboot

[tong2x]

the locks are automatically unlocked by the installer so in may case it basically just loops back
to this final "state" where updating will show no more updates

base   22.1.9   574.5MiB   OPNsense
kernel   22.1.9   157.6MiB   OPNsense
opnsense   22.1.10_4   22.1MiB   OPNsense
opnsense-installer   22.1   88.2KiB   OPNsense
opnsense-lang   21.7.8   8.67MiB   OPNsense
opnsense-update   22.1.9   82.7KiB   OPNsense

Firmware status requires to check for update first to provide more information.

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.10_4 (amd64/OpenSSL) at Sat Jul 30 23:20:12 -08 2022
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 799 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .. done
Processing entries: .... done
SunnyValley repository update completed. 31 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (15 candidates): .......... done
Processing candidates (15 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

it is on 22.1.9 and opnsense 22.1.10_4 but somehow nonsense cant see the update

going to console, option 12, will show update 22.7 but running that will only loop back to downloading 2.1.9 base and kernel.

[franco]

is this needed to be executed?

# opnsense-update -bkzr 22.7.b
# opnsense-shell reboot

WTF? Why?

It was diagnosed that "pkg" utility segfaults during upgrade so I don't see how poking at irrelevant things like a beta kernel has any meaning here.


Cheers,
Franco

[AF1E]

I am having the same issue.  Have tried GUI and CLI update and it keeps looping back as noted.  opnsense-update -G returns nothing.  All integrity checks are fine.  Only thing I can add is if I look at my firmware change log it shows 22.7 but 22.1.10 shows as the installed version.  Appears something is preventing the 22.7 install.

[tong2x]

dont know if worth nothing...

I have updated 2units I7 system, with different config, 1 ZFS and 1 UFS. all upgrade successfully.

2 system with problem are Qotum mini PC, 1 celeron, 1 intel I5(remote location). with different config also. both reporting segmentation faults. I'll probably just clean install the one near me, and sit back for the remote unit.

it would seem that the "packages" are not being installed
if you run the CLI update to 22.7 it will install the base and kernel, once it is installed. the web updater will detect 22.1.9 update... updating will then again loop back to having 22.19 base and kernel and 22.1.10_4 opnsense, web update will report all pages are uptodate (but I guess the segfault in case case is the issue).

[franco]

Can someone with the issue on 22.7 run this and let me know the output?

# opnsense-log | grep far.gateway


Thanks,
Franco

[tong2x]

root@OPNsense:~ # opnsense-log | grep far.gateway
root@OPNsense:~ # opnsense-log | grep far.gateway

it did not out anything in my case

[franco]

Thanks. Frankly I have no idea what's going on here.


Cheers,
Franco

[tong2x]

having the following

Code: [Select]

base   22.1.9   574.5MiB   OPNsense
kernel   22.1.9   157.6MiB   OPNsense
opnsense   22.1.10_4   22.1MiB   OPNsense
opnsense-installer   22.1   88.2KiB   OPNsense
opnsense-lang   21.7.8   8.67MiB   OPNsense
opnsense-update   22.1.9   82.7KiB   OPNsense

how does opnsense determine new and updated files?
or that there should be 22.7 base, kernel and packages?

and installing via console, typing 22.7 installs base and kernel but does not updates packages to 22.7
or is the istallti9n adbruptly interupted by the segmentation fault, causing the whole upgrade process not to proceed?

it did upgrade may 2 i7 without a problem

[Elst]

I updated to 22.7 by doing a clean re-install using the 22.7 image and restoring a backup. Updated to 22.7_4 just fine.

Just hit check for updates and the Dashboard is now showing "Click to view pending updates."If I click that I'm shown "Your packages are up to date."
However the Changelog page still shows 22.7.1 available. Trying option 12 via the console and I get "Nothing to do."

I don't think I've got anything particularly unusual configured. A few floating firewall rules and an OpenVPN server. The only Plugins I have extra are: os-acme-client, os-chrony, os-lldpd and os-theme-rebellion.

It takes all of ~20 minutes to re-install, but any other suggestions to get this working?

Cheers.