Hi there,
I have tried updating 2 times (once from the GUI and one time from the CLI after SSH into the firewall and selecting option 12).
Noth times the files are downloaded and the firewall reboots, but after some time when it has rebooted I am still on 21.1.9 and am offered the update again.
How can I view what is going wrong with the update/what logs can I check?
Pete
I also notice this if I check for updates via the GUI again:
Package name Current version New version Required action Repository
base 21.7 21.1.8 upgrade OPNsense
kernel 21.7 21.1.8 upgrade OPNsense
So some has upgraded and now wants to downgrade...?
My dashboard shows:
Versions OPNsense 21.1.9_1-amd64
FreeBSD 12.1-RELEASE-p19-HBSD
LibreSSL 3.3.3
same here - after reboot - see attached pictures
Must affect many people :)
No, certainly affects people with third party repos and custom ports.
Please share your firmware status info and /var/cache/opnsense-update/.upgrade.log
Yep, had installed mimugmails repo, but uninstalled it after that.
here is the log and the Firmware status
root@OPNsense:~ # cat /var/cache/opnsense-update/.upgrade.log
bash-5.1.8: already unlocked
beep-1.0_1: already unlocked
ca_root_nss-3.68: already unlocked
choparp-20150613: already unlocked
clog-1.0.2: already unlocked
cpdup-1.22: already unlocked
cpustats-0.1: already unlocked
curl-7.78.0: already unlocked
cyrus-sasl-2.1.27_1: already unlocked
dhcp6c-20200512_1: already unlocked
dhcpleases-0.2: already unlocked
dnsmasq-2.85_1,1: already unlocked
dpinger-3.0: already unlocked
e2fsprogs-libuuid-1.46.2: already unlocked
expat-2.4.1: already unlocked
expiretable-0.6_2: already unlocked
filterlog-0.4_2: already unlocked
flock-2.30.1: already unlocked
flowd-0.9.1_3: already unlocked
gettext-runtime-0.21: already unlocked
glib-2.66.8,2: already unlocked
gmp-6.2.1: already unlocked
hostapd-2.9_4: already unlocked
hyperscan-5.4.0: already unlocked
icu-69.1,1: already unlocked
ifinfo-10.1: 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.13.1: already unlocked
json-c-0.15_1: already unlocked
krb5-1.19.1: already unlocked
ldns-1.7.1_2: already unlocked
libargon2-20190702: already unlocked
libcbor-0.8.0: already unlocked
libcjson-1.7.14: already unlocked
libedit-3.1.20210216,1: already unlocked
libevent-2.1.12: already unlocked
libffi-3.3_1: already unlocked
libfido2-1.7.0: already unlocked
libiconv-1.16: already unlocked
liblz4-1.9.3,1: already unlocked
libnet-1.1.6_5,1: already unlocked
libnghttp2-1.43.0: already unlocked
libsodium-1.0.18: already unlocked
libucl-0.8.1: already unlocked
libxml2-2.9.12: already unlocked
libyaml-0.2.5: already unlocked
lighttpd-1.4.59: already unlocked
lzo2-2.10_1: already unlocked
monit-5.28.0: already unlocked
mpd5-5.9: already unlocked
mpdecimal-2.5.1: already unlocked
nettle-3.7.3: already unlocked
nspr-4.32: already unlocked
nss-3.68: already unlocked
ntp-4.2.8p15: already unlocked
oniguruma-6.9.7.1: already unlocked
openldap-sasl-client-2.4.59: already unlocked
openssh-portable-8.6.p1,1: already unlocked
openssl-1.1.1k_1,1: already unlocked
openvpn-2.5.3: already unlocked
opnsense-21.1.9_1: already unlocked
opnsense-installer-21.7: already unlocked
opnsense-lang-21.1.7: already unlocked
opnsense-update-21.1.8_1: already unlocked
os-adguardhome-maxit-1.5: already unlocked
os-dyndns-1.24_2: already unlocked
os-postfix-1.18: already unlocked
os-wireguard-1.7: already unlocked
pam_opnsense-19.1.3: already unlocked
pcre-8.44_1: already unlocked
pcre2-10.37: already unlocked
perl5-5.32.1_1: already unlocked
pftop-0.7_9: already unlocked
php74-7.4.21: already unlocked
php74-ctype-7.4.21: already unlocked
php74-curl-7.4.21: already unlocked
php74-dom-7.4.21: already unlocked
php74-filter-7.4.21: already unlocked
php74-gettext-7.4.21: already unlocked
php74-google-api-php-client-2.4.0: already unlocked
php74-json-7.4.21: already unlocked
php74-ldap-7.4.21: already unlocked
php74-mbstring-7.4.21: already unlocked
php74-openssl-7.4.21: already unlocked
php74-pdo-7.4.21: already unlocked
php74-pecl-psr-1.1.0: already unlocked
php74-pecl-radius-1.4.0b1_1: already unlocked
php74-phalcon4-4.1.2: already unlocked
php74-phpseclib-2.0.32: already unlocked
php74-session-7.4.21: already unlocked
php74-simplexml-7.4.21: already unlocked
php74-sockets-7.4.21: already unlocked
php74-sqlite3-7.4.21: already unlocked
php74-xml-7.4.21: already unlocked
php74-zlib-7.4.21: already unlocked
pkg-1.16.3: already unlocked
postfix-sasl-3.5.10,1: already unlocked
py37-Babel-2.9.1: already unlocked
py37-Jinja2-2.11.2_1: already unlocked
py37-certifi-2021.5.30: already unlocked
py37-cffi-1.14.6: already unlocked
py37-chardet-4.0.0,1: already unlocked
py37-cryptography-3.3.2: already unlocked
py37-dnspython-1.16.0: already unlocked
py37-idna-2.10: already unlocked
py37-markupsafe-1.1.1_1: already unlocked
py37-netaddr-0.8.0: already unlocked
py37-openssl-20.0.1: already unlocked
py37-pycparser-2.20: already unlocked
py37-pysocks-1.7.1: already unlocked
py37-pytz-2021.1,1: already unlocked
py37-requests-2.25.1: already unlocked
py37-setuptools-57.0.0: already unlocked
py37-six-1.16.0: already unlocked
py37-sqlite3-3.7.11_7: already unlocked
py37-ujson-4.0.2: already unlocked
py37-urllib3-1.25.11,1: already unlocked
py37-yaml-5.4.1: already unlocked
python37-3.7.11: already unlocked
radvd-2.19_1: already unlocked
readline-8.1.1: already unlocked
rrdtool-1.7.2_4: already unlocked
samplicator-1.3.8.r1_1: already unlocked
sqlite3-3.35.5_3,1: already unlocked
squid-4.15: already unlocked
strongswan-5.9.2_2: already unlocked
sudo-1.9.7p1: already unlocked
suricata-5.0.7: already unlocked
syslog-ng-3.33.2: already unlocked
syslogd-12.1: already unlocked
unbound-1.13.1: already unlocked
wireguard-go-0.0.20210424,1: already unlocked
wireguard-tools-1.0.20210424: already unlocked
wpa_supplicant-2.9_11: 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.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 764 packages processed.
Updating mimugmail repository catalogue...
pkg-static: https://opn-repo.routerperformance.net/repo/FreeBSD:12:amd64/meta.txz: Non-recoverable resolver failure
repository mimugmail has no meta file, using default settings
pkg-static: https://opn-repo.routerperformance.net/repo/FreeBSD:12:amd64/packagesite.txz: Non-recoverable resolver failure
Unable to update repository mimugmail
Error updating repositories!
I think I see the issue, it looks like because sensei is not ready maybe:
root@OPNsense:~ # cat /var/cache/opnsense-update/.upgrade.log
alsa-lib-1.1.2_2: already unlocked
bash-5.1.8: already unlocked
beep-1.0_1: already unlocked
ca_root_nss-3.68: already unlocked
choparp-20150613: already unlocked
clog-1.0.2: already unlocked
cpdup-1.22: already unlocked
cpustats-0.1: already unlocked
curl-7.78.0: already unlocked
cyrus-sasl-2.1.27_1: already unlocked
dejavu-2.37_1: already unlocked
dhcp6c-20200512_1: already unlocked
dhcpleases-0.2: already unlocked
dmidecode-3.3: already unlocked
dnsmasq-2.85_1,1: already unlocked
dpinger-3.0: already unlocked
e2fsprogs-libuuid-1.46.2: already unlocked
elasticsearch5-5.6.8_5: already unlocked
expat-2.4.1: already unlocked
expiretable-0.6_2: already unlocked
filterlog-0.4_2: already unlocked
flock-2.30.1: already unlocked
flowd-0.9.1_3: already unlocked
fontconfig-2.13.93,1: already unlocked
freetype2-2.10.4: already unlocked
gettext-runtime-0.21: already unlocked
glib-2.66.8,2: already unlocked
gmp-6.2.1: already unlocked
gnu-watch-3.3.17: already unlocked
hostapd-2.9_4: already unlocked
hw-probe-1.6.b2: already unlocked
hwstat-0.5.1: already unlocked
hyperscan-5.4.0: already unlocked
ifinfo-10.1: already unlocked
iftop-1.0.p4: already unlocked
indexinfo-0.3.1: already unlocked
iperf3-3.10.1_1: already unlocked
isc-dhcp44-relay-4.4.2P1: already unlocked
isc-dhcp44-server-4.4.2P1_1: already unlocked
jansson-2.13.1: already unlocked
java-zoneinfo-2021.a: already unlocked
javavmwrapper-2.7.7: already unlocked
jna-5.7.0: already unlocked
json-c-0.15_1: already unlocked
krb5-1.19.1: already unlocked
ldns-1.7.1_2: already unlocked
libICE-1.0.10,1: already unlocked
libSM-1.2.3,1: already unlocked
libX11-1.6.12,1: already unlocked
libXau-1.0.9: already unlocked
libXdmcp-1.1.3: already unlocked
libXt-1.2.1,1: already unlocked
libargon2-20190702: already unlocked
libcbor-0.8.0: already unlocked
libcjson-1.7.14: already unlocked
libedit-3.1.20210216,1: already unlocked
libevent-2.1.12: already unlocked
libffi-3.3_1: already unlocked
libfido2-1.7.0: already unlocked
libfontenc-1.1.4: already unlocked
libiconv-1.16: already unlocked
libinotify-20180201_2: already unlocked
liblz4-1.9.3,1: already unlocked
libnet-1.1.6_5,1: already unlocked
libnghttp2-1.43.0: already unlocked
libpthread-stubs-0.4: already unlocked
libressl-3.3.3: already unlocked
libsodium-1.0.18: already unlocked
libucl-0.8.1: already unlocked
libunwind-20201110: already unlocked
libxcb-1.14_1: already unlocked
libxml2-2.9.12: already unlocked
libyaml-0.2.5: already unlocked
lighttpd-1.4.59: already unlocked
lscpu-1.2.0: already unlocked
lzo2-2.10_1: already unlocked
mkfontscale-1.2.1: already unlocked
monit-5.28.0: already unlocked
mpd5-5.9: already unlocked
mpdecimal-2.5.1: already unlocked
nano-5.8: already unlocked
nettle-3.7.3: already unlocked
nspr-4.32: already unlocked
nss-3.68: already unlocked
ntp-4.2.8p15: already unlocked
oniguruma-6.9.7.1: already unlocked
openjdk8-8.282.08.1: already unlocked
openldap-sasl-client-2.4.59: already unlocked
openssh-portable-8.6.p1,1: already unlocked
openvpn-2.5.3: already unlocked
opnsense-21.1.9_1: already unlocked
opnsense-installer-21.7: already unlocked
opnsense-lang-21.1.7: already unlocked
opnsense-update-21.1.8_1: already unlocked
os-api-backup-1.0_1: already unlocked
os-dyndns-1.24_2: already unlocked
os-hw-probe-1.0_1: already unlocked
os-iperf-devel-1.0_1: already unlocked
os-sensei-1.9.2: already unlocked
os-sensei-updater-1.9: already unlocked
os-smart-2.2: already unlocked
os-sunnyvalley-1.2_1: already unlocked
os-theme-cicada-1.28: already unlocked
os-theme-rebellion-1.8.7: already unlocked
os-wireguard-1.7: already unlocked
pam_opnsense-19.1.3: already unlocked
pcre-8.44_1: already unlocked
pcre2-10.37: already unlocked
perl5-5.32.1_1: already unlocked
pftop-0.7_9: already unlocked
php74-7.4.21: already unlocked
php74-ctype-7.4.21: already unlocked
php74-curl-7.4.21: already unlocked
php74-dom-7.4.21: already unlocked
php74-filter-7.4.21: already unlocked
php74-gettext-7.4.21: already unlocked
php74-google-api-php-client-2.4.0: already unlocked
php74-json-7.4.21: already unlocked
php74-ldap-7.4.21: already unlocked
php74-mbstring-7.4.21: already unlocked
php74-openssl-7.4.21: already unlocked
php74-pdo-7.4.21: already unlocked
php74-pecl-psr-1.1.0: already unlocked
php74-pecl-radius-1.4.0b1_1: already unlocked
php74-phalcon4-4.1.2: already unlocked
php74-phpseclib-2.0.32: already unlocked
php74-session-7.4.21: already unlocked
php74-simplexml-7.4.21: already unlocked
php74-sockets-7.4.21: already unlocked
php74-sqlite3-7.4.21: already unlocked
php74-xml-7.4.21: already unlocked
php74-zlib-7.4.21: already unlocked
pkg-1.16.3: already unlocked
png-1.6.37_1: already unlocked
py37-Babel-2.9.1: already unlocked
py37-Jinja2-2.11.2_1: already unlocked
py37-aiohttp-3.7.4.p0: already unlocked
py37-async_timeout-3.0.1: already unlocked
py37-attrs-21.2.0: already unlocked
py37-certifi-2021.5.30: already unlocked
py37-cffi-1.14.6: already unlocked
py37-chardet-4.0.0,1: already unlocked
py37-cryptography-3.3.2: already unlocked
py37-dnspython-1.16.0: already unlocked
py37-idna-2.10: already unlocked
py37-markupsafe-1.1.1_1: already unlocked
py37-multidict-5.1.0: already unlocked
py37-netaddr-0.8.0: already unlocked
py37-openssl-20.0.1: already unlocked
py37-pycparser-2.20: already unlocked
py37-pysocks-1.7.1: already unlocked
py37-pytz-2021.1,1: already unlocked
py37-requests-2.25.1: already unlocked
py37-setuptools-57.0.0: already unlocked
py37-six-1.16.0: already unlocked
py37-speedtest-cli-2.1.3: already unlocked
py37-sqlite3-3.7.11_7: already unlocked
py37-typing-extensions-3.10.0.0: already unlocked
py37-ujson-4.0.2: already unlocked
py37-urllib3-1.25.11,1: already unlocked
py37-yaml-5.4.1: already unlocked
py37-yarl-1.6.3: already unlocked
python37-3.7.11: already unlocked
radvd-2.19_1: already unlocked
readline-8.1.1: already unlocked
rrdtool-1.7.2_4: already unlocked
ruby-2.7.4,1: already unlocked
samplicator-1.3.8.r1_1: already unlocked
smartmontools-7.2_1: already unlocked
sqlite3-3.35.5_3,1: already unlocked
squid-4.15: already unlocked
strongswan-5.9.2_2: already unlocked
sudo-1.9.7p1: already unlocked
suricata-5.0.7: already unlocked
syslog-ng-3.33.2: already unlocked
syslogd-12.1: already unlocked
ubench-0.32: already unlocked
unbound-1.13.1: already unlocked
wireguard-go-0.0.20210424,1: already unlocked
wireguard-kmod-0.0.20210606_1: already unlocked
wireguard-tools-1.0.20210424: already unlocked
wpa_supplicant-2.9_11: already unlocked
xorgproto-2020.1: 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.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 761 packages processed.
Updating SunnyValley repository catalogue...
pkg-static: https://updates.sunnyvalley.io/opnsense/FreeBSD:12:amd64/21.1/LibreSSL/latest/meta.txz: Non-recoverable resolver failure
repository SunnyValley has no meta file, using default settings
pkg-static: https://updates.sunnyvalley.io/opnsense/FreeBSD:12:amd64/21.1/LibreSSL/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository SunnyValley
Error updating repositories!
Here is my firmware page also for completeness.
https://github.com/opnsense/update/commit/99b5aae0918
Should be this. I am a bit surprised that this went completely unreported.
Cheers,
Franco
Quote from: franco on July 28, 2021, 03:12:52 PM
https://github.com/opnsense/update/commit/99b5aae0918
Should be this. I am a bit surprised that this went completely unreported.
Cheers,
Franco
No worries! Thats why we are all here :)
Do you think we will be able to update later if this change is made on your side?
having the exact same issue, I tried upgrading from both web & console
I'm updating 21.1.9 later after confirming this works and then it should fly to 21.7.
Give me 30 minutes...
Cheers,
Franco
No problem, you are a gentleman and a scholar. Thanks!
As mentioned in my duplicate thread of this issue (please delete if you want) I had the same issue.
As franco suspected it appears to have been caused by the mimugmail repo. I deleted the repo and initiated another update (after making sure I had no pkg from said repo installed). Unfortunately my system is not coming up again (it has been about 15 minutes now) and I can only check later when I get home.
Quote from: pp on July 28, 2021, 03:25:42 PM
As mentioned in my duplicate thread of this issue (please delete if you want) I had the same issue.
As franco suspected it appears to have been caused by the mimugmail repo. I deleted the repo and initiated another update (after making sure I had no pkg from said repo installed). Unfortunately my system is not coming up again (it has been about 15 minutes now) and I can only check later when I get home.
It may come up. Drink a coffee and check again. No stressing!
Quote from: pp on July 28, 2021, 03:25:42 PM
As mentioned in my duplicate thread of this issue (please delete if you want) I had the same issue.
As franco suspected it appears to have been caused by the mimugmail repo. I deleted the repo and initiated another update (after making sure I had no pkg from said repo installed). Unfortunately my system is not coming up again (it has been about 15 minutes now) and I can only check later when I get home.
Same here, system didn't come up after the upgrade. I can investigate further when I'm home. I'm only using the sensei repository, no other 3rd party repository.
Ok hopefully nothing major... :( Im sure it will be fixable.
Alright, looks like this is a side effect of https://github.com/opnsense/update/issues/69
We will be addressing this tomorrow after more upgrade tests.
Cheers,
Franco
No problem, if you need me to test or do anything let me know :)
I was able to ssh back into my router (it was not down and has not updated). I made the mistake of starting the last update attempt via console connected over wireguard without tmux or similar. So when the wireguard service was stopped, the update did not continue as the session was killed I assume.
I started up wireguard again and restarted the update via webgui. Everything worked out smooth in the end after disabling the third party repo.
User error, sorry about the noise ;)
So my OPNSense seems to be little broken.
Startup takes 10 minutes. configd does not start due to missing pyhton library.
SSH gives me "Access denied" for all users + root.
EDIT: Problem report sent. Maybe franco can see more from his side, as I'm not able to access opnsense logs anymore. However internet access is restored, but can view logs or access via ssh.
Let's not clutter this thread with all sorts of oddities....
The fix seems to be https://github.com/opnsense/update/commit/9abe08ee and if anyone would help confirm that would be extremely helpful:
# opnsense-revert -r 21.1.9_multi opnsense-update
Suffice to say upgrades with enabled third party repos could fail for any number of reasons that we can't really cover from our side. Please be wary.
Cheers,
Franco
Quote from: franco on July 28, 2021, 04:57:04 PM
Let's not clutter this thread with all sorts of oddities....
The fix seems to be https://github.com/opnsense/update/commit/9abe08ee and if anyone would help confirm that would be extremely helpful:
# opnsense-revert -r 21.1.9_multi opnsense-update
Suffice to say upgrades with enabled third party repos could fail for any number of reasons that we can't really cover from our side. Please be wary.
Cheers,
Franco
I can confirm that this worked on my system experiencing the issue.
Confirmed, update successful; checking firmware updates after indicates no updates available, as expected.
Thanks! :)
Its not clear what we are supposed to do to upgrade to 21.7.
Do I just run opnsense-revert -r 21.1.9_multi opnsense-update and after check for updates and upgrade to 21.7 normally?
Pete
I ran the revert, then attempted update and ended up with 21.1.8 and then updated again and 21.7 was installed. I was confused about that as well...but that actually worked.
Quote from: gpb on July 28, 2021, 06:50:38 PM
I ran the revert, then attempted update and ended up with 21.1.8 and then updated again and 21.7 was installed. I was confused about that as well...but that actually worked.
Ok and Can I do this with sensei or is that not a good idea?
Well, that's above my pay-grade. I will say that ntopng no longer works...so...uh...yeah...don't know.
Screw it I guess I will just try and fix it if it breaks.
Ok it seems to have worked. Here are the exact steps I completed.
1) Ssh into box and run opnsense-revert -r 21.1.9_multi opnsense-update
2) reboot box
3) Ssh into box and use option 12, type 21.7 to upgrade to 21.7
4) Reboots automatically.
5) Open Web GUI. Check for updates. It finds 1 update for sunnyvalley.
6) Install update, reboot.
7) Open Web GUI. Check for updates (none are found).
8) Check Dashboard - should say 21.7 is now installed. ( OPNsense 21.7-amd64)
9) Check Firmware page. Should say "Version 21.7"
10) Check no additional updates - there are none for me.
11) Confirm all working and no issues (I am still doing this but seems ok after a couple of minutes so far).
Pete
after updating the file /usr/local/sbin/opnsense-update
see >> https://github.com/opnsense/update/commit/9abe08ee (https://github.com/opnsense/update/commit/9abe08ee)
with
if (${PKG} update -f -r ${PRODUCT} && \
${PKG} upgrade -fy -r ${PRODUCT}) > ${PIPEFILE} 2>&1; then
upgrade to 21.7 works perfect.
so far no problems!!
thx franco! :D
Quote from: franco on July 28, 2021, 04:57:04 PM
Let's not clutter this thread with all sorts of oddities....
The fix seems to be https://github.com/opnsense/update/commit/9abe08ee and if anyone would help confirm that would be extremely helpful:
# opnsense-revert -r 21.1.9_multi opnsense-update
Suffice to say upgrades with enabled third party repos could fail for any number of reasons that we can't really cover from our side. Please be wary.
Cheers,
Franco
Hi guys,
same problem with the included repositories (OPNsense, SunnyValley, mimugmail, ntop) fixed via the solution pointed out by Franco.
Everything fine, AdGuard, Sensei, ntopng everything runs. Only ntopgn had a problem with the certificate for a short time (SSL_ERROR_RX_RECORD_TOO_LONG).
Greetings and thanks Meditux
Quote from: franco on July 28, 2021, 04:57:04 PM
Let's not clutter this thread with all sorts of oddities....
The fix seems to be https://github.com/opnsense/update/commit/9abe08ee and if anyone would help confirm that would be extremely helpful:
# opnsense-revert -r 21.1.9_multi opnsense-update
Suffice to say upgrades with enabled third party repos could fail for any number of reasons that we can't really cover from our side. Please be wary.
Cheers,
Franco
I was able to reproduce 2 times on a system with 2 external repos. The fix did it. Thanks! :)
So is the solution, running:
# opnsense-revert -r 21.1.9_multi opnsense-update
before upgrading to 21.7?
Ok, I'll update the 21.1.9 version on the mirror then... Thanks all!
EDIT: Main mirror now has opnsense-update 21.1.8_2 available with the fix so simply check for updates. Mirror sync times may vary.
Cheers,
Franco
Quote from: opn_nwo on July 28, 2021, 07:56:52 PM
So is the solution, running:
# opnsense-revert -r 21.1.9_multi opnsense-update
before upgrading to 21.7?
Yep
Quote from: mimugmail on July 28, 2021, 08:50:58 PM
Quote from: opn_nwo on July 28, 2021, 07:56:52 PM
So is the solution, running:
# opnsense-revert -r 21.1.9_multi opnsense-update
before upgrading to 21.7?
Yep
Yes and no. It should work with the default packages now (opnsense-update at 21.1.8_2 as mentioned).
Just ran through the update from the GUI and it worked fine.
Mine showed an update to 21.1.9_1, not 21.1.8_2. Is the upgrade fix included in that version as well?
I was stuck initially on trying to run through opnsense-revert via the console, as I was seeing:
# opnsense-revert -r 21.1.9_multi opnsense-update
Fetching opnsense-update.txz: .. failed
I had the Australian repo mirror set in the web UI as I'm located in Australia. Perhaps the Australian mirror isn't fully up to date for this process, as things didn't work until I changed back to the default Deciso repo. I also temporarily removed mimugmail's repo just to be sure.
Having done that, seems like things are okay now, as the rest of the upgrade process went very smoothly on my Qotom appliance.
Quote from: abraxxa on July 28, 2021, 10:04:52 PM
Mine showed an update to 21.1.9_1, not 21.1.8_2. Is the upgrade fix included in that version as well?
Try my steps on the bottom of page 2. This procedure worked fine for me when it wanted to update to an older version from the gui.
Quote from: allebone on July 28, 2021, 11:08:36 PM
Quote from: abraxxa on July 28, 2021, 10:04:52 PM
Mine showed an update to 21.1.9_1, not 21.1.8_2. Is the upgrade fix included in that version as well?
Try my steps on the bottom of page 2. This procedure worked fine for me when it wanted to update to an older version from the gui.
Thanks, but as I'm running Sensei I'll wait until they announce that a 21.7 compatible version is available or the current one already is.
After the update to OpnSense 21.7 I see the Sensei 1.9.3 availabilty, release notes:
What is new in Sensei 1.9.3
Integrations
Bug-Fix: OPNsense 21.7 compatibility enhancements
Yup both sensei and opnsense already patched and fixed so 2.7 will go fine for everyone else not affected from now on. A huge thanks to both teams for providing a solution in under 24h to a community build of an open source project. Enterprise level support.
:)
Hi,
has the same problem.
Doing the 11 Steps, at step 3 it is now
and it´s fetching since 20 Minutes?
Proceed with this action? [21.7/y/N]: 21.7
Fetching packages-21.7-OpenSSL-amd64.tar: ................... done
Fetching base-21.7-amd64.txz: ........................................................................ ... ... ... ... ... ...
Now one hour
Fetching packages-21.7-OpenSSL-amd64.tar: ................... done
Fetching base-21.7-amd64.txz: ........................................................................ ... ... ... ... ... ...
Quote from: abraxxa on July 28, 2021, 10:04:52 PM
Mine showed an update to 21.1.9_1, not 21.1.8_2. Is the upgrade fix included in that version as well?
opnsense-update is 21.1.8_2 and opnsense is 21.1.9_1 ;)
Quote from: Bytechanger on July 29, 2021, 06:46:39 AM
and it´s fetching since 20 Minutes?
It's rather impractical to comment on individual setup's ability to download files from the mirror. It's only a file transfer and issues like slow speed, proxy woes and so forth are not in our hands.
Cheers,
Franco
So if under System:Firmware:Packages it shows these versions
base 21.1.8
kernel 21.1.8
opnsense 21.1.9_1
opnsense-update 21.1.8_2
the system should be ready for a trouble-free update?
Except for the igb issue we are hunting down at the moment, yes.
We will replace the problematic kernel as soon as that is confirmed.
Cheers,
Franco
Hi Franco,
Perhaps this helps.
I tried multiple times to update from 21.1.9_1 to 21.7 without success. Last try I left it overnight ie about 8 hours and did not finish. Just kept adding dots to the log.
Then I changed the mirror to OPNSense (HTTPS,Amsterdam,NL) and the upgrade completed in less than 5 minutes.
The mirror used to be LeaseWeb Amsterdam but I also tried Leaseweb Frankfurt without success.
Regards,
Craig
Hi Franco,
is it now safe to update to OPNsense 21.7.1 with igb interfaces or it is better to install fresh?
My Firmware Packages:
base 21.1.8
kernel 21.1.8
opnsense 21.1.9_1
opnsense-update 21.1.8_2
opnsense-installer 21.7
I use a IPU662 with Intel i211AT Ethernet Controller from NRG Systems.
Regards,
hloiter
Igb issue was i210 I think and has been fixed 3 days after 21.7 came out. As safe as it gets I presume.
Let me know how it went for you.
Cheers,
Franco
HELP...
After my update to the latest version from 21.1.9 to 21.7, nothing happens. It rebooted after the update, then it was quiet. Connected it to mouse, keyboard and screen. Not even a bios on the display.
Connected it back in the network and tried to access it by ssh on the WAN and LAN ports. Ssh is enabled and worked previously. Unfortunally it doesn't allow me access.
Is there another way to access it by SSH?
Thx
Quote from: hvleest on August 09, 2021, 12:01:58 PM
HELP...
After my update to the latest version from 21.1.9 to 21.7, nothing happens. It rebooted after the update, then it was quiet. Connected it to mouse, keyboard and screen. Not even a bios on the display.
Connected it back in the network and tried to access it by ssh on the WAN and LAN ports. Ssh is enabled and worked previously. Unfortunally it doesn't allow me access.
Is there another way to access it by SSH?
Thx
Sounds like a hardware problem if you don't even see the BIOS screen or boot messages.
I connected a display on the HDMI, but it gave 'no signal' on both ports. Then connect a LAN cable on WAN. I can ping the IP (192.168.1.3), but can't connect to it as root. SSH is enabled, and worked in the past with my known password.
Is there a way to reset it to factory default? Without access to SSH?
Also the default password opnsense does not work
Quote from: athurdent on August 09, 2021, 12:18:53 PM
Quote from: hvleest on August 09, 2021, 12:01:58 PM
HELP...
After my update to the latest version from 21.1.9 to 21.7, nothing happens. It rebooted after the update, then it was quiet. Connected it to mouse, keyboard and screen. Not even a bios on the display.
Connected it back in the network and tried to access it by ssh on the WAN and LAN ports. Ssh is enabled and worked previously. Unfortunally it doesn't allow me access.
Is there another way to access it by SSH?
Thx
Sounds like a hardware problem if you don't even see the BIOS screen or boot messages.
Also the default password opnsense does not work
If you're locket out from the shell you might need to reinstall and import config. But you still need to be able to access a console to do that. What are you using as output, serial, VGA? It might be worth opening your own post.
Quote from: franco on July 30, 2021, 10:22:28 AM
Igb issue was i210 I think and has been fixed 3 days after 21.7 came out. As safe as it gets I presume.
Let me know how it went for you.
Cheers,
Franco
Hi Franco,
today I updated to OPNsense 21.7.1.
Everything went without any problems.
Many thanks to the developers and the support here in the forum.
Regards,
hloiter
I also have problems upgrading from 21.1.9_1-amd64 to 21.7. Upgrade (from web gui) fails at the beginning:
***GOT REQUEST TO UPGRADE***
Fetching packages-21.7-OpenSSL-amd64.tar: ............................... failed, no signature found
***DONE***
Mirror is LeaseWeb (HTTP, Washington, DC, US)
/var/cache/opnsense-update/.upgrade.log hasn't been touched since the upgrade to 21.1.
A new --empty-- directory was made today, apparently when I attempted the upgrade:
/var/cache/opnsense-update/71076
Still at 21.1.9_1, and apparently running without problems.
Not sure whether I should follow the revert process discussed on this thread -- my symptoms are a bit different.
Please advise.
Running on firewall appliance with Atom CPU E3845 @ 1.91GHz (4 cores).
Thanks for your help.
****Update: Successfully upgraded to 21.7, then 21.7.1, after changing mirror to NYC*BUG (HTTP, New York, US)
I am blocked from upgrading 21.1.9_1-amd64 to 21.7 and none of the workarounds listed in this thread are working.
As others have mentioned, when I attempt to upgrade from the GUI it fails:
***GOT REQUEST TO UPGRADE***
Fetching packages-21.7-OpenSSL-amd64.tar: ............................... failed, no signature found
***DONE***
When I attempt SSH into box and run opnsense-revert -r 21.1.9_multi opnsense-update it fails:
root@OPNsense:~ # opnsense-revert -r 21.1.9_multi opnsense-update
Fetching opnsense-update.txz: ............................... failed
root@OPNsense:~ #
I confirmed that the edits defined here https://github.com/opnsense/update/commit/9abe08ee (https://github.com/opnsense/update/commit/9abe08ee) are present in the /usr/local/sbin/opnsense-update file:
LINES 501-504
elif ! diff -uq ${WORKDIR}/${PRODUCT}.conf ${ORIGIN}; then
# rerun sync before there are any complaints
${PKG} update ${DO_FORCE}
fi
LINES 773-776
${TEE} ${LOGFILE} < ${PIPEFILE} &
if (${PKG} update -f -r ${PRODUCT} && \
${PKG} upgrade -fy -r ${PRODUCT}) > ${PIPEFILE} 2>&1; then
# re-register local packages repository
Not sure where to go from here, any ideas Franco?
Quote from: hvleest on August 09, 2021, 12:30:24 PM
Also the default password opnsense does not workQuote from: athurdent on August 09, 2021, 12:18:53 PM
Quote from: hvleest on August 09, 2021, 12:01:58 PM
HELP...
After my update to the latest version from 21.1.9 to 21.7, nothing happens. It rebooted after the update, then it was quiet. Connected it to mouse, keyboard and screen. Not even a bios on the display.
Connected it back in the network and tried to access it by ssh on the WAN and LAN ports. Ssh is enabled and worked previously. Unfortunally it doesn't allow me access.
Is there another way to access it by SSH?
Thx
Sounds like a hardware problem if you don't even see the BIOS screen or boot messages.
Also the default password opnsense does not work
UPDATE. old install was corrupt after update. New install boots.
Also, make sure when you connect a screen, its a small screen. 22inch is to big. 19inch works perfect
Quote from: wleeb1010 on August 17, 2021, 05:15:16 PM
I am blocked from upgrading 21.1.9_1-amd64 to 21.7 and none of the workarounds listed in this thread are working.
[...]
Not sure where to go from here, any ideas Franco?
Try changing the mirror and make sure that IPv6 works or is otherwise turned off.
Cheers,
Franco
I disabled IPv6 and the upgrade completed successfully.
Thanks Franco!
I have tried all of the solutions in this topic and am still stuck and my system does not see an upgrade path. I have tried a variety of mirrors.
Type opnsense
Version 21.1.9_1
Architecture amd64
Flavour OpenSSL
Commit e10896164
Mirror https://pkg.opnsense.org/FreeBSD:12:amd64/21.1
Repositories OPNsense
Updated on Wed Jul 28 11:47:08 EDT 2021
Checked on N/A
And when I run update in console or at CLI:
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option: 12
Fetching change log information, please wait... done
This will automatically fetch all available updates and apply them.
Proceed with this action? [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 (0 candidates): . done
Processing candidates (0 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
The following package files will be deleted:
/var/cache/pkg/opnsense-update-21.1.8_2~7e3799d419.txz
/var/cache/pkg/opnsense-update-21.1.8_2.txz
The cleanup will free 63 KiB
Deleting files: .. done
All done
Your system is up to date.
Is there any way to see more detailed logs or otherwise troubleshoot why it cannot see the upgrade?
Please run a health audit. This doesn't look right?
> Proceed with this action? [y/N]: y
That's not how to invoke a major upgrade and also it should tell you about "21.7" which is the correct input...
Cheers,
Franco
EDIT: I am good to go, see below.
Quote from: franco on September 07, 2021, 09:01:06 PM
Please run a health audit. This doesn't look right?
> Proceed with this action? [y/N]: y
That's not how to invoke a major upgrade and also it should tell you about "21.7" which is the correct input...
Thanks. So this is probably my fault, as I deleted these files based on another post related to the signature issue...before I found this topic.
opnsense-21.1.9_1: missing file /usr/local/opnsense/firmware-message
opnsense-21.1.9_1: missing file /usr/local/opnsense/firmware-upgrade
I assume I can manually pull those files down from a mirror?EDIT: I reinstalled the opnsense package and it replaced those files. Then I checked for an upgrade and everything went smoothly!
Thanks for the prompt reply and help!
Full health check output:
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 21.1.9_1 (amd64/OpenSSL) at Tue Sep 7 15:07:54 EDT 2021
>>> Check installed kernel version
Version 21.1.8 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 21.1.8 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: ....
opnsense-21.1.9_1: missing file /usr/local/opnsense/firmware-message
opnsense-21.1.9_1: missing file /usr/local/opnsense/firmware-upgrade
Checking all packages......... done
>>> Check for core packages consistency
Core package "opnsense" has 66 dependencies to check.
Checking packages: .................................................................... done
***DONE***
Ok, good. Just reinstall "opnsense" package from System: Firmware: Packages tab. Or from the shell:
# opnsense-revert opnsense
Could be that you're back to a previous error but need to look at this one too.
Also can you share your "uname -v" output to see if you are in a partial upgrade state or if it never started in the first place.
Cheers,
Franco
Quote from: franco on September 07, 2021, 09:26:25 PM
Ok, good. Just reinstall "opnsense" package from System: Firmware: Packages tab. Or from the shell:
# opnsense-revert opnsense
That did it, thanks! Now running 21.7.2 with no issues!
Yay, nice :)