OPNsense Forum

Archive => 21.7 Legacy Series => Topic started by: 0xDEADBEAF314 on February 12, 2022, 09:05:34 PM

Title: Solved: Update problem
Post by: 0xDEADBEAF314 on February 12, 2022, 09:05:34 PM
Hello,
recently I update my opnsense to 21.7.8, it semm all is ok, but not :
The base package and kernel still remain to 21.7.6.
I try to re-install base package and I obtain :
***GOT REQUEST TO REINSTALL***
Fetching base-21.7.8-amd64.txz: ............................... failed, no signature found
***DONE***

/tmp is anougth big and have more than 3G of free space.
If I try to download the file manually, all is OK, the fole can be downloaded. But when I start the reinstall from GUI it will be quick and the temporary directory in /var/cache/opnsense-update/XXX/ still empty

is it possible to re-install manually the package ? (I have the same problem with kernel package)

Also when I try to update I got :
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 21.7.8 (amd64/OpenSSL) at Sat Feb 12 21:37:43 CET 2022
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /tmp/changelog/changelog.txz.sig appears to be truncated: 0/1332 bytes
Updating OPNsense repository catalogue...
pkg: 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. 777 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages 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.

Title: Solved: Update problem
Post by: 0xDEADBEAF314 on February 13, 2022, 12:03:58 AM
Try an anoyher mirror, and do /usr/local/opnsense/scripts/firmware/connection.sh until no problems and especially some mirror with IPv6 enabled but no service ...
Found one with only IPv4 and all be ok  now :)
Title: Re: Solved: Update problem
Post by: koushun on February 13, 2022, 01:23:43 PM
I am experiencing the same problem.

I tried to update from 21.7.7 to 21.7.8 -- clicked update, went away from the computer for a long time because I knew it had to do a reboot and that takes time.

Got back, had to log in - saw on the front page that the version was
* Versions   OPNsense 21.7.8-amd64
and thought everything was OK

Installed the Realtek plugin for my Realtek NIC -- and then I tried to update to 22.1 via "Click to check for updates"; however; checking for updates I saw the firmware and the kernel was not upgraded and was waiting for 21.7.8.

Now it is just stuck on

***GOT REQUEST TO UPDATE***
Currently running OPNsense 21.7.8 (amd64/OpenSSL) at Sun Feb 13 10:29:16 CET 2022
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Checking for upgrades (3 candidates): ... done
Processing candidates (3 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.
Fetching base-21.7.8-amd64.txz: ...


Although I am not exactly sure what the problem is; probably the default mirror? Because internet works just fine? The default mirror stated on the System > Firmware > Status page was
* "Mirror   https://pkg.opnsense.org/FreeBSD:13:amd64/22.1"

For anyone coming here, go to System > Firmware > Settings to change the Firmware Mirror setting. I have changed the mirror, did a reboot, and then I was able to upgrade to 21.7.8 prior to upgrading to 22.1

Title: Re: Solved: Update problem
Post by: franco on February 13, 2022, 08:17:31 PM
Not seeing a health audit, impossible to tell otherwise.


Cheers,
Franco