OPNsense Forum
Archive => 21.7 Legacy Series => Topic started by: N0b0dy1985 on July 07, 2021, 11:30:48 pm
-
Hi, I just moved from the community to the development train. For giggles, I checked for updates after the switch, and my version 21.7.b_97 OPNsense is offering to 'upgrade' to 21.1.8. Is this expected?
-
Answered here: https://forum.opnsense.org/index.php?topic=23836.0
-
Screenshot please. You may have some packages not installing properly for one reason or another.
Cheers,
Franco
-
https://imgur.com/f6Fq1Tt (https://imgur.com/f6Fq1Tt)
(https://imgur.com/f6Fq1Tt)
Having trouble uploading a screenshot... second attempt... see if this works.
-
ntop third party repo tells me something went wrong with the packages upgrade.
Can you check /var/cache/opnsense-update/.upgrade.log for errors?
Cheers,
Franco
-
...
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. 760 packages processed.
Updating SunnyValley repository catalogue...
pkg-static: https://updates.sunnyvalley.io/opnsense/FreeBSD:12:amd64/21.1/OpenSSL/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/OpenSSL/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository SunnyValley
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
Updating ntop repository catalogue...
pkg-static: https://packages.ntop.org/FreeBSD/FreeBSD:12:amd64/latest/meta.txz: Non-recoverable resolver failure
repository ntop has no meta file, using default settings
pkg-static: https://packages.ntop.org/FreeBSD/FreeBSD:12:amd64/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository ntop
Error updating repositories!
Definitely something wrong with those repositories now. As you can see, I've added a few custom repositories for Sensei, mimugmail and ntopng. At the moment, I'm less concerned with those than I am with the update weirdness on OPNsense. What is the best way to fix this?
-
First of all if you add three third party repos the worry about update stability is yours three times over. ;)
Secondly, "Non-recoverable resolver failure" sounds like DNS failure.
Thirdly, please provide /var/cache/opnsense-update/.upgrade.log as kindly requested.
I'm happy to help, but under the current circumstances it's really difficult to do so.
Cheers,
Franco
-
Hahaha... You are totally correct, all the worries are definitely mine!
I did paste some output from the upgrade.log... but I just pasted the last handful of lines where stuff looked abnormal. Sorry for the confusion there.
Agree that it looks like DNS was failing... not sure what's up with that, resolution seems to be working now though.
I did a System>Firmware>Status>Audit>Connectivity, and all the repositories seemed to be reachable, so I went ahead and ran an update. All the packages updated correctly this time, the FW rebooted, and the GUI no longer suggests an upgrade to 21.1.8. I am all good now.
Thanks Franco. Sorry for the noob questions.
-
Hmm, I still would have liked to see that broken /var/cache/opnsense-update/.upgrade.log output (the file itself, not the output from the GUI). Now it was certainly overwritten with the successful update.
Cheers,
Franco
-
I'm sorry. I cat'd the file via CLI... most was normal stuff... I pasted the last bunch of lines because I thought they were the interesting bits. I'll follow directions next time.
-
Oh ok, that's why there is a DNS error... there is no networking on upgrade install because we prefetch our packages to install them (safely) offline. I suspect there was some package version mismatch because of installed third party packages that prevented a clean installation of all new packages.
Cheers,
Franco
-
AFAIK, there is no Sensei yet for 21.7.