(solved) Update to 21.1.1 wont start

[shade73]

Hello,

When I am trying to update from 21.1 to 21.1.1 OPNsense says:

Error updating repositories!
A firmware update is currently in progress.

I have tried rebooting, but still same message.

[franco]

Try to run

# pkg -d update -f

Let us know what it complains about.


Thanks,
Franco

[shade73]

It says:

pkg -d update -f
DBG(1)[67278]> pkg initialized
Updating OPNsense repository catalogue...
DBG(1)[67278]> PkgRepo: verifying update for OPNsense
DBG(1)[67278]> Pkgrepo, begin update of '/var/db/pkg/repo-OPNsense.sqlite'
DBG(1)[67278]> Request to fetch pkg+https://mirror.dns-root.de/opnsense/FreeBSD:12:amd64/21.1/libressl/meta.conf
DBG(1)[67278]> opening libfetch fetcher
DBG(1)[67278]> Fetch > libfetch: connecting
DBG(1)[67278]> Fetch: fetching from: https://mirror.dns-root.de/opnsense/FreeBSD:12:amd64/21.1/libressl/meta.conf with opts "i"
DBG(1)[67278]> Fetch: fetcher chosen: https
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
DBG(1)[67278]> Request to fetch pkg+https://mirror.dns-root.de/opnsense/FreeBSD:12:amd64/21.1/libressl/packagesite.txz
DBG(1)[67278]> opening libfetch fetcher
DBG(1)[67278]> Fetch > libfetch: connecting
DBG(1)[67278]> Fetch: fetching from: https://mirror.dns-root.de/opnsense/FreeBSD:12:amd64/21.1/libressl/packagesite.txz with opts "i"
DBG(1)[67278]> Fetch: fetcher chosen: https
Fetching packagesite.txz: 100%  198 KiB 202.6kB/s    00:01
DBG(1)[67278]> PkgRepo: extracting packagesite.yaml of repo OPNsense
DBG(1)[78321]> PkgRepo: extracting signature of repo in a sandbox
DBG(1)[67278]> Pkgrepo, reading new packagesite.yaml for '/var/db/pkg/repo-OPNsense.sqlite'
Processing entries: 100%
OPNsense repository update completed. 725 packages processed.
Updating SunnyValley repository catalogue...
DBG(1)[67278]> PkgRepo: verifying update for SunnyValley
DBG(1)[67278]> PkgRepo: need forced update of SunnyValley
DBG(1)[67278]> Pkgrepo, begin update of '/var/db/pkg/repo-SunnyValley.sqlite'
DBG(1)[67278]> Request to fetch https://updates.sunnyvalley.io/opnsense/repo//meta.conf
DBG(1)[67278]> opening libfetch fetcher
DBG(1)[67278]> Fetch > libfetch: connecting
DBG(1)[67278]> Fetch: fetching from: https://updates.sunnyvalley.io/opnsense/repo//meta.conf with opts "i"
DBG(1)[67278]> Request to fetch https://updates.sunnyvalley.io/opnsense/repo//meta.txz
DBG(1)[67278]> opening libfetch fetcher
DBG(1)[67278]> Fetch > libfetch: connecting
DBG(1)[67278]> Fetch: fetching from: https://updates.sunnyvalley.io/opnsense/repo//meta.txz with opts "i"
pkg: https://updates.sunnyvalley.io/opnsense/repo//meta.txz: Not Found
repository SunnyValley has no meta file, using default settings
DBG(1)[67278]> Request to fetch https://updates.sunnyvalley.io/opnsense/repo//packagesite.txz
DBG(1)[67278]> opening libfetch fetcher
DBG(1)[67278]> Fetch > libfetch: connecting
DBG(1)[67278]> Fetch: fetching from: https://updates.sunnyvalley.io/opnsense/repo//packagesite.txz with opts "i"
pkg: https://updates.sunnyvalley.io/opnsense/repo//packagesite.txz: Not Found
Unable to update repository SunnyValley
Error updating repositories!

[lfirewall1243]

Seems Sunnyvalley isn't ready for 21.1.1

[shade73]

But I do not have Sensei installed, so that should not stop me from updating OPNsense :o

[franco]

You have the SunnyValley repository installed. If you want it not to error for trying to reach it since your system is configured for it simply it remove it by removing os-sunnyvalley plugin or if that isn't installed the configuration file that needs to be removed is /usr/local/etc/pkg/repos/SunnyValley.conf


Cheers,
Franco

[shade73]

My plugin page are empty, like there is nothing there at all.

I deleted the /usr/local/etc/pkg/repos/SunnyValley.conf so the repository was removed, now the update worked and after it finished the upgrade to 21.1.1 the plugin page also works :)

Thanks for the help.

[franco]

We re adding a "Repositories" hint on the new firmware status page for 21.7 that displays registered repositories (whether or not they are installed as plugins or not).

They were added at some point on the target machine for some reason so we try to offer visibility for it to provide quicker support.


Cheers,
Franco