Upgrading to 22.1

[Mundan101]

When 22.1 is released, is it safe to upgrade with Zenarmor?

[franco]

Usually it takes a week or two to prepare, best to look out for announcements giving the green light.


Cheers,
Franco

[sy]

Hi,

22.1 repo for Zenarmor is published. Maybe you can try it.

[franco]

Hey sy, that was fast :D


Thanks,
Franco

[athurdent]

Hi,

22.1 repo for Zenarmor is published. Maybe you can try it.

Took a VM snapshot, upgraded my normal install (nobody home ATM 😅) and gave it a spin for an hour. No problems, all seems great here. 3.5G throughput in both directions and it looks like, finally ditching HardenedBSD made iperf3 tests stable. No eastpect crashes.
Looking forward to the multicore build... :)

[Andy112]

Hi,

22.1 repo for Zenarmor is published. Maybe you can try it.

Hi there, please can I have some assistance changing over to the new repo that is compatible with 22.1? Whenever I check for firmware & package updates I'm always met with "Could not find the repository on the selected mirror."
Thanks.

Code Select Expand

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.b_141 (amd64/OpenSSL) at Wed Jan 19 19:01:04 AWST 2022
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 777 packages processed.
Updating SunnyValley repository catalogue...
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/meta.txz: Not Found
repository SunnyValley has no meta file, using default settings
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/packagesite.txz: Not Found
Unable to update repository SunnyValley
Error updating repositories!
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

[franco]

It shouldn't point you to "21.7" so that means your upgrade was only partial. Check /var/cache/opnsense-update/.upgrade.log


Cheers,
Franco

[Andy112]

It shouldn't point you to "21.7" so that means your upgrade was only partial. Check /var/cache/opnsense-update/.upgrade.log


Cheers,
Franco

Thanks Franco. I'm not sure how it got in this state, perhaps I didn't switch from community to development image properly?? Am I correct in just simply changing 'type' to development, hitting save, rebooting and then searching for updates? If so that process seemed to complete successfully.

[franco]

Did you move via beta to 22.1? Try reinstalling os-sunnyvalley, I think it couldn't be reapplied(yet). Your main mirror URL looks fine (22.1).

[Andy112]

Did you move via beta to 22.1? Try reinstalling os-sunnyvalley, I think it couldn't be reapplied(yet). Your main mirror URL looks fine (22.1).

Oops sorry for the thread hopping, I shall stay here  :P .
No beta, I went from 21.7.7 -> 22.1.r1 (or so I thought lol  :o ).
No joy with reinstalling os-sunnyvalley, looks like my OPNsense instance has really screwed the pooch lol:

Code Select Expand

***GOT REQUEST TO REINSTALL***
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
pkg-static: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/meta.txz: Not Found
repository SunnyValley has no meta file, using default settings
pkg-static: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/packagesite.txz: Not Found
Unable to update repository SunnyValley
Error updating repositories!
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***
Shall I just reinstall a fresh 22.1 instance and restore from a 21.7.7 backup? Or have you anymore tricks up your sleeve to try. I'm also happy to provide any relevant logs as a means of understanding why this may have happened and to avoid it happening again to other users.

[franco]

Ok more force needed. Can you uninstall os-sunnyvalley and then put it back immediately?


Cheers,
Franco

[Andy112]

Good news! It appears removing os-sunnyvalley allowed my OPNsense instance to 'fully' upgrade to 22.1.r3.
However now it's doing something strange and appears to be in a loop (see attached screenshot).
I have applied the 22.1.r1 'update' as seen in the screenshot twice already but once the instance comes back online after applying it and I check for updates again, the same 22.1.r1 'update' shows despite being on .r3
Also this is the result of a Health Check Audit:

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 22.1.r_3 (amd64/OpenSSL) at Thu Jan 20 00:04:47 AWST 2022
>>> Check installed kernel version
Version 22.1.r1 is correct.
>>> Check for missing or altered kernel files
Error 2 ocurred.
boot/kernel/linker.hints:
    size (374752, 375104)
    sha256digest (0x906322a5e39d85471ecbb57b94034c3703d6594ea034074c7219512a3d862604, 0xbc72238d15ac7afba505851dd89b7c301ba39bb39e463c48f4469074e4c0f957)
>>> Check installed base version
Version 22.1.r1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> 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-devel" has 65 dependencies to check.
Checking packages: ................................................................... done
***DONE***

[franco]

This is correct. You can switch to "community" type now. The linker.hints file issue is with the FreeBSD build and a workaround has been added to the kernel build tools for 22.1.r2.


Cheers,
Franco

[Andy112]

This is correct. You can switch to "community" type now. The linker.hints file issue is with the FreeBSD build and a workaround has been added to the kernel build tools for 22.1.r2.


Cheers,
Franco

That's great thanks so much for your help Franco!! Okay so I'm back on the "community" type now and just to confirm 22.1.r1 is the latest community build?
Thanks again,Andy

[franco]

Yep, 22.1.r2 is scheduled for tomorrow if we are lucky.


Cheers,
Franco