Unable to upgrade from 17.1.11

[framura]

Hi,

I tried to upgrade but get this error when I try to upgrade (from GUI or from ssh):

Fetching base-17.7-amd64.obsolete: .............................................................opnsense-verify: Unable to open /var/cache/opnsense-update/41418/base-17.7-amd64.obsolete: No such file or directory
failed


Can you help me?

TIA


Note: I use /var and /tmp in memory
Note2: In the log file I found this:

configd.py: [1b18a9de-e07f-4353-8121-ad3ef316fb82] Script action stderr returned "pkg: Repository OPNsense has a wrong packagesite, need to re-create database"

[franco]

Hi framura,

Which mirror are you using? Maybe it's not up-to-date.


Cheers,
Franco

[framura]

I tried with default, OPNSense Amsterdam with same result.

Now, i just retried with this result:

Fetching packages-17.7-LibreSSL-amd64.tar: ......... done
Fetching base-17.7-amd64.obsolete: ... done
Fetching base-17.7-amd64.txz: ..................................Signature for file not available.
failed

[franco]

This is awfully strange, it fetches two files and verifies them ok, the third one it fails to verify...

You can try to do the manual sequence as root:

# fetch https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/kernel-17.7-amd64.txz.sig
# fetch https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/kernel-17.7-amd64.txz
# fetch https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/base-17.7-amd64.obsolete.sig
# fetch https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/base-17.7-amd64.obsolete
# fetch https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/base-17.7-amd64.txz.sig
# fetch https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/base-17.7-amd64.txz
# fetch https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/packages-17.7-LibreSSL-amd64.tar.sig
# fetch https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/packages-17.7-LibreSSL-amd64.tar

(just a thought: maybe you are running out of space during fetch!)

# opnsense-update -ur 17.7 -l .
# /usr/local/etc/rc.reboot


Cheers,
Franco

[framura]

Hi,

today I just retried to update (from GUI) and, voila, update worked.

Very very strange.