Does not seem to Proceed to install 22.7

Started by tong2x, July 29, 2022, 09:01:30 AM

Previous topic - Next topic
I manage to update 1 server but this one just doesnt

OPNsense 22.1.10_4-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1q 5 Jul 2022

in gui it only says no more updates
QuoteFirmware status requires to check for update first to provide more information.

Quote"Your packages are up to date.
***DONE***"

QuoteChange Log
22.7   2022-07-28   
22.1.10 (installed)   2022-07-07

in console, after supposedly extracting 22.7, it says 22.1.10_4, like nothing happened.
did this 3 times already
QuoteEnter an option: 12

Fetching change log information, please wait... done

This will automatically fetch all available updates and apply them.

A major firmware upgrade is available for this installation: 22.7

Make sure you have read the release notes and migration guide before
attempting this upgrade.  Around 500MB will need to be downloaded and
require 1000MB of free space.  Continue with this major upgrade by
typing the major upgrade version number displayed above.

Minor updates may be available, answer 'y' to run them instead.

Proceed with this action? [22.7/y/N]: 22.7

Fetching packages-22.7-OpenSSL-amd64.tar: ................................................................................................. done
Fetching base-22.7-amd64.txz: ................... done
Fetching kernel-22.7-amd64.txz: ......... done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Extracting packages-22.7-OpenSSL-amd64.tar... done
Extracting base-22.7-amd64.txz... done
Installing kernel-22.7-amd64.txz... done
Please reboot.
>>> Invoking stop script 'beep'
>>> Invoking stop script 'freebsd'
Stopping API dispatcher
Stop : zone 0
stop captiveportal background process
Stopping mongod.
Waiting for PIDS: 74761.
Stopping flowd.
Stopping flowd_aggregate...done
>>> Invoking stop script 'backup'
>>> Invoking backup script 'captiveportal'
>>> Invoking backup script 'dhcpleases'
>>> Invoking backup script 'duid'
>>> Invoking backup script 'netflow'
>>> Invoking backup script 'rrd'
>>> Invoking stop script 'config'
Shutdown NOW!
shutdown: [pid 64578]

*** FINAL System shutdown message from root@OPNsense.localdomain ***

System going down IMMEDIATELY

System shutdown time has arrived

> FreeBSD 13.0-STABLE

and

> Installing kernel-22.7-amd64.txz... done

doesn't fit?


Cheers,
Franco

not after reboot it will show

QuoteOPNsense 22.1.10_4-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1q 5 Jul 2022

relogin in to console, displays
Quote*** OPNsense.localdomain: OPNsense 22.1.10_4 (amd64/OpenSSL) ***

running again in the console would do the same, show that 22.7 is available
and running the it via web GUI will say no updates.
I have tried for 4 times already...


now i''m thingking of putting the unit to defaults, running the updates and restoring to a saved backup config.

July 29, 2022, 10:22:12 AM #3 Last Edit: July 29, 2022, 10:25:16 AM by Elst
I'm having pretty much the same issue, same GUI issue etc. Although I was only half paying attention when presented with the 3rd update prompt yesterday, which I vaguley recall acually being a downgrade back to 22.1.10_4.

Now when trying to up update via the console I get:

Enter an option: 12

Fetching change log information, please wait... done

This will automatically fetch all available updates and apply them.

A major firmware upgrade is available for this installation: 22.7

Make sure you have read the release notes and migration guide before
attempting this upgrade.  Around 500MB will need to be downloaded and
require 1000MB of free space.  Continue with this major upgrade by
typing the major upgrade version number displayed above.

Minor updates may be available, answer 'y' to run them instead.

Proceed with this action? [22.7/y/N]: y

Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (26 candidates): .......... done
Processing candidates (26 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Starting web GUI...done.
Generating RRD graphs...done.


Via opnsense-update at the shell and I get "Nothing to do."

Am I reinstalling using the latest image and restoring a backup to fix this?

Cheers.

July 29, 2022, 10:46:08 AM #4 Last Edit: July 29, 2022, 10:51:14 AM by tong2x
it was a downgrade to 22.1.9 in my case

but for 1 of may server after 22.1.9, was the update for 22.7, it completed
for this server though, it keeps getting back to 22.1.10_4

if you ruin in console and select 22.7 as upgrade option
it should say 2.1.9(in the web GUI, not in console) in the next upgrade...
but in may case will revert back.

Just run this and give output:

# opnsense-update -G

Some sort of package conflict not being able to install.


Cheers,
Franco

error in code
QuoteChecking for upgrades (170 candidates): .
Child process pid=408 terminated abnormally: Segmentation fault


full message
Quoteroot@OPNsense:~ # opnsense-update -G
alsa-lib-1.2.2_1: already unlocked
beep-1.0_1: already unlocked
boost-libs-1.79.0_1: already unlocked
ca_root_nss-3.78: already unlocked
choparp-20150613: already unlocked
cpdup-1.22: already unlocked
cpustats-0.1: already unlocked
curl-7.84.0: already unlocked
cyrus-sasl-2.1.28: already unlocked
cyrus-sasl-gssapi-2.1.28: already unlocked
dejavu-2.37_1: already unlocked
dhcp6c-20200512_1: already unlocked
dhcpleases-0.2: already unlocked
dnsmasq-2.86_4,1: already unlocked
dpinger-3.2: already unlocked
e2fsprogs-libuuid-1.46.5: already unlocked
expat-2.4.8: already unlocked
expiretable-0.6_2: already unlocked
filterlog-0.6: already unlocked
flock-2.37.2: already unlocked
flowd-0.9.1_3: already unlocked
fontconfig-2.13.94_2,1: already unlocked
freetype2-2.12.1: already unlocked
gettext-runtime-0.21: already unlocked
giflib-5.2.1: already unlocked
glib-2.72.2,2: already unlocked
gmp-6.2.1: already unlocked
hostapd-2.10_5: already unlocked
hyperscan-5.4.0: already unlocked
icu-71.1,1: already unlocked
ifinfo-13.0: already unlocked
iftop-1.0.p4: already unlocked
indexinfo-0.3.1: already unlocked
isc-dhcp44-relay-4.4.2P1: already unlocked
isc-dhcp44-server-4.4.2P1_1: already unlocked
jansson-2.14: already unlocked
java-zoneinfo-2021.e: already unlocked
javavmwrapper-2.7.9: already unlocked
json-c-0.16: already unlocked
krb5-1.20: already unlocked
ldns-1.8.1: already unlocked
libICE-1.0.10,1: already unlocked
libSM-1.2.3,1: already unlocked
libX11-1.7.2,1: already unlocked
libXau-1.0.9: already unlocked
libXdmcp-1.1.3: already unlocked
libXext-1.3.4,1: already unlocked
libXfixes-6.0.0: already unlocked
libXi-1.8,1: already unlocked
libXrender-0.9.10_2: already unlocked
libXt-1.2.1,1: already unlocked
libXtst-1.2.3_2: already unlocked
libargon2-20190702: already unlocked
libcbor-0.9.0: already unlocked
libcjson-1.7.15: already unlocked
libedit-3.1.20210910,1: already unlocked
libevent-2.1.12: already unlocked
libffi-3.4.2: already unlocked
libfido2-1.11.0: already unlocked
libfontenc-1.1.4: already unlocked
libiconv-1.16: already unlocked
libidn2-2.3.2: already unlocked
libinotify-20211018: already unlocked
liblz4-1.9.3,1: already unlocked
libnet-1.1.6_5,1: already unlocked
libnghttp2-1.48.0: already unlocked
libpsl-0.21.1_4: already unlocked
libpthread-stubs-0.4: already unlocked
libsodium-1.0.18: already unlocked
libucl-0.8.1: already unlocked
libunistring-1.0: already unlocked
libxcb-1.14_1: already unlocked
libxml2-2.9.13_2: already unlocked
libyaml-0.2.5: already unlocked
lighttpd-1.4.65: already unlocked
lzo2-2.10_1: already unlocked
mkfontscale-1.2.1: already unlocked
mongodb42-4.2.19_1: already unlocked
monit-5.32.0: already unlocked
mpd5-5.9_9: already unlocked
mpdecimal-2.5.1: already unlocked
nettle-3.8: already unlocked
nspr-4.34: already unlocked
nss-3.80: already unlocked
ntp-4.2.8p15_5: already unlocked
oniguruma-6.9.8_1: already unlocked
openjdk8-8.332.09.1: already unlocked
openldap24-client-2.4.59_4: already unlocked
openssh-portable-8.9.p1_4,1: already unlocked
openssl-1.1.1q,1: already unlocked
openvpn-2.5.7: already unlocked
opnsense-22.1.10_4: already unlocked
opnsense-installer-22.1: already unlocked
opnsense-lang-21.7.8: already unlocked
opnsense-update-22.1.9: already unlocked
os-dyndns-1.27_3: already unlocked
os-sensei-updater-1.11: already unlocked
os-sunnyvalley-1.2_2: already unlocked
os-theme-cicada-1.29: already unlocked
os-theme-rebellion-1.8.8: already unlocked
os-theme-tukan-1.25: already unlocked
pam_opnsense-19.1.3: already unlocked
pcre-8.45_1: already unlocked
pcre2-10.40: already unlocked
perl5-5.32.1_1: already unlocked
pftop-0.8: already unlocked
php74-7.4.30: already unlocked
php74-ctype-7.4.30: already unlocked
php74-curl-7.4.30: already unlocked
php74-dom-7.4.30: already unlocked
php74-filter-7.4.30: already unlocked
php74-gettext-7.4.30: already unlocked
php74-google-api-php-client-2.4.0: already unlocked
php74-json-7.4.30: already unlocked
php74-ldap-7.4.30: already unlocked
php74-mbstring-7.4.30: already unlocked
php74-openssl-7.4.30: already unlocked
php74-pdo-7.4.30: already unlocked
php74-pecl-radius-1.4.0b1_2: already unlocked
php74-phalcon-5.0.0.r2: already unlocked
php74-phpseclib-2.0.37: already unlocked
php74-session-7.4.30: already unlocked
php74-simplexml-7.4.30: already unlocked
php74-sockets-7.4.30: already unlocked
php74-sqlite3-7.4.30: already unlocked
php74-xml-7.4.30: already unlocked
php74-zlib-7.4.30: already unlocked
pkg-1.17.5_1: already unlocked
png-1.6.37_1: already unlocked
py39-Babel-2.10.2: already unlocked
py39-Jinja2-3.0.1: already unlocked
py39-certifi-2022.5.18.1: already unlocked
py39-cffi-1.15.0_1: already unlocked
py39-charset-normalizer-2.0.12: already unlocked
py39-cryptography-3.4.8: already unlocked
py39-dnspython-2.2.1,1: already unlocked
py39-idna-3.3: already unlocked
py39-markupsafe-2.1.1: already unlocked
py39-netaddr-0.8.0: already unlocked
py39-openssl-20.0.1,1: already unlocked
py39-pycparser-2.21: already unlocked
py39-pysocks-1.7.1: already unlocked
py39-pytz-2021.3,1: already unlocked
py39-requests-2.28.0: already unlocked
py39-setuptools-62.1.0_1: already unlocked
py39-six-1.16.0: already unlocked
py39-sqlite3-3.9.13_7: already unlocked
py39-ujson-5.0.0: already unlocked
py39-urllib3-1.26.9,1: already unlocked
py39-vici-5.9.3: already unlocked
py39-yaml-5.4.1: already unlocked
python37-3.7.13_2: already unlocked
python39-3.9.13: already unlocked
radvd-2.19_1: already unlocked
readline-8.1.2: already unlocked
rrdtool-1.7.2_6: already unlocked
samplicator-1.3.8.r1_1: already unlocked
snappy-1.1.9_1: already unlocked
snappyjava-1.1.7.5: already unlocked
sqlite3-3.38.5,1: already unlocked
squid-4.15: already unlocked
strongswan-5.9.6_2: already unlocked
sudo-1.9.11p3: already unlocked
suricata-6.0.5_3: already unlocked
syslog-ng-3.37.1: already unlocked
unbound-1.16.0: already unlocked
unzip-6.0_8: already unlocked
wpa_supplicant-2.10_6: already unlocked
xorgproto-2021.5: already unlocked
zip-3.0_1: already unlocked
Updating OPNsense repository catalogue...
pkg-static: Repository OPNsense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 797 packages processed.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (170 candidates): .
Child process pid=408 terminated abnormally: Segmentation fault

Ok, unsure what to fix here and/or how this is caused.

Health audit? Maybe opnsense-bootstrap can help.


Cheers,
Franco

Pretty much the same for me, with fewer packages:

Updating OPNsense repository catalogue...
pkg-static: Repository OPNsense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 778 packages processed.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (192 candidates): .
Child process pid=458 terminated abnormally: Segmentation fault



how do I force down grade to say 22.1.10 or lower then just upgrade back
health check says version incorrect

Quote***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 22.1.10_4 (amd64/OpenSSL) at Fri Jul 29 01:52:51 -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***

The GUI update should offer 22.1.9 "upgrade" in your case. Once you install that, it'll try to get you to 22.7 again which may likely fail again.

That being said 22.7 base/kernel are not harmful in 22.1.x.


Cheers,
Franco

I had FreeBSD 13.1 installed on top of 22.1 ever since it was allowed and had base and kernel packages locked in order to avoid being downgraded to 13.0 upon each 22.1.x update.

That actually prevented detecting the 22.7 upgrade, it kept telling me up to date (except for available 13.0 downgrade) I actually had to unlock base and kernel, update/downgrade to 13.0/22.1.10_4

And then hit Check for Updates and finally the 22.7 upgrade showed up...

Ideally you only lock the kernel and base system which let's you pull all other updates including 22.1.10_4, which then offers you 22.7 and overrides the base/kernel lock anyway.

At least that is how it's supposed to work. :D


Cheers,
Franco

I am having the same issue, was offer the upgrade, upgraded, however, still stuck at 22.1.10*. Selected check updates again, offered upgrade, upgraded, still at 22.1.10*. Checked upgrade again, offered to upgrade the kernel only.

However, nothing is actually upgrading except the kernel.

What say you @Franco? How do I fix this?


***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 22.1.10_4 (amd64/OpenSSL) at Fri Jul 29 16:40:06 EDT 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.1.9 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
SunnyValley
OPNsense
>>> Check installed plugins
os-api-backup 1.0_1
os-ddclient 1.8
os-dmidecode 1.1_1
os-dyndns 1.27_3
os-hw-probe 1.0_1
os-sensei 1.11.4
os-sensei-agent 1.11.3
os-sensei-updater 1.11
os-smart 2.2
os-sunnyvalley 1.2_2
os-theme-cicada 1.29
>>> 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: ....................................


Thanks.

@Franco
The locked 13.1 base & kernel prevented the detection of availability of 22.7 from 22.1.10_4, that's why I made my comments about unlocking manually.

If 22.7 is supposed to unlock and upgrade automatically, that didn't happen for me, I was forced to unlock and downgrade to 13.0 in order for my install to detect 22.7 availability.

I was scratching my head prior and even changing download mirror, thinking mirroring had not down streamed completely at that point.