I have a fresh install of OPNSense running on bare metal. When I attempt to update by going to System > Firmware > Update, it checks for updates the displays a dialog stating "There are no updates available on the selected mirror.". Checking the version at Lobby > Dashboard shows the version as OPNsense 24.1-amd64. I have tired different mirrors and get the same result.
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.1 at Mon Jul 8 13:36:55 EDT 2024
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 845 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.
***DONE***
Here is the output from the health check audit:
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 24.1 at Mon Jul 8 13:50:26 EDT 2024
>>> Root file system: /dev/ada1p2
>>> Check installed kernel version
Version 24.1 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 24.1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
os-freeradius 1.9.23
os-haproxy 4.3_1
os-smart 2.2_4
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" not known to package database.
***DONE***
Since it won't update I am unable to install the plugins I need via the GUI, but was able to install them from the CLI.
***GOT REQUEST TO INSTALL***
Currently running OPNsense 24.1 at Mon Jul 8 13:44:05 EDT 2024
Installation out of date. The update to opnsense-24.1.9_4 is required.
***DONE***
*** SOLVED ***
I attempted to update from the shell by doing the following:
pkg install opnsense
pkg update
The system would not update to the latest version and instead updated to the 24.8.1 version. Furthermore, after the update, the web gui was no longer accessible. I re-installed the system and was then able to update to the latest version (24.1.10_3).
Is there a DNS entry in Settings - General ? A screenshot could help
had the same issue "pkg install opnsense" fixed this for me, but after this another error now occures: https://forum.opnsense.org/index.php?topic=40774.0
completely vanilla 24.1
Here are the DNS settings:
(https://i.postimg.cc/Ty10Xg2w/Screenshot-from-2024-07-09-11-16-37.png) (https://postimg.cc/Ty10Xg2w)
Unsure what DNS settings you meant to post...
Try updating now, either in a terminal or GUI, and post here the full output.
> >>> Check for core packages consistency
> Core package "opnsense" not known to package database.
Leads to this as mentioned:
> had the same issue "pkg install opnsense" fixed this for me
Leads to making sure to update all the other packages as well so it doesn't fail.
Cheers,
Franco
Quote from: newsense on July 09, 2024, 10:57:16 PM
Unsure what DNS settings you meant to post...
I thought the DNS settings you asked about are the DNS settings in System > Settings > General. Is this not correct?
Quote
Try updating now, either in a terminal or GUI, and post here the full output.
Here is the output from System > Firmware > Updates.
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.1 at Wed Jul 10 19:01:48 EDT 2024
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 845 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.
***DONE***
Thing is, I don't see any DNS settings if you posted it...
What does a connectivity check say ? And what mirror are you on in Firmware - Settings ? Try switching to another mirror and check for updates again.
Quote from: newsense on July 11, 2024, 02:08:31 AM
Thing is, I don't see any DNS settings if you posted it...
I don't think this is DNS problem, since the output from update shows that it is successfully checking for updates:
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.1 at Thu Jul 11 15:05:25 EDT 2024
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 852 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.
***DONE***
QuoteWhat does a connectivity check say ?
I don't think it is a connectivity problem since the system is currently being uses as the firewall for my network.
***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 24.1 at Thu Jul 11 15:22:29 EDT 2024
Checking connectivity for host: pkg.opnsense.org -> 89.149.222.99
PING 89.149.222.99 (89.149.222.99): 1500 data bytes
1508 bytes from 89.149.222.99: icmp_seq=0 ttl=54 time=114.703 ms
1508 bytes from 89.149.222.99: icmp_seq=1 ttl=54 time=114.650 ms
1508 bytes from 89.149.222.99: icmp_seq=2 ttl=54 time=114.496 ms
1508 bytes from 89.149.222.99: icmp_seq=3 ttl=54 time=114.565 ms
--- 89.149.222.99 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 114.496/114.603/114.703/0.079 ms
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/24.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 852 packages processed.
All repositories are up to date.
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:5300:a010:1::1
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/24.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!
***DONE***
Quote
And what mirror are you on in Firmware - Settings ? Try switching to another mirror and check for updates again.
I have tried all of the US repos and a couple of repos in Europe with the same result. Futhermore, four of my packages updated successfully today. So it looks like the update mechanism is working. My guess is that update is going to repos that have 24.1 as the latest release.
Not sure if this is the case. While I am somewhat familiar with apt on Linux, I have no experience using/trouble-shooting ports on FreeBSD.
Most likely, I will backup the config and re-install the system.
IPv6 is the issue there:Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:5300:a010:1::1
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/24.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!
System - Settings - General
Check Prefer to use IPv4 even if IPv6 is available and try again.
Obvious reminder that the solution post was ignored here so far.
# pkg install opnsense
Sorry, didn't see the missing package or your previous post here.
No problem. This is the definitive hint in the health audit log to look for:
>>> Check for core packages consistency
Core package "opnsense" not known to package database.
Cheers,
Franco
Quote from: franco on July 12, 2024, 07:37:11 AM
Obvious reminder that the solution post was ignored here so far.
# pkg install opnsense
Thanks for the info. I haven't been ignoring the post - I just can't risk trying it during the week when there is the possibility of un-planned network downtime. Unfortunately, I have to schedule maintenance for Friday so that I will have the weekend to fix things if it goes catastrophically wrong.
That said, I am leaning towards re-installing. I used the current system to learn OPNSense, so it could be that something got messed up when I was fumbling around learning OPNSense.
Quote from: newsense on July 11, 2024, 11:15:01 PM
IPv6 is the issue there:Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:5300:a010:1::1
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/24.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!
System - Settings - General
Check Prefer to use IPv4 even if IPv6 is available and try again.
I tried your recommendation and unfortunately it did not resolve the problem. I am pretty sure that updates are being done via IPv4 and it is only using IPv6 for the connectivity audit.
I wish there was a way to set up OPNSense IPv4 only. I know it doesn't affect anything but I find all of the IPv6 automatic rules and other un-needed IPv6 features on a IPv4 only system annoying as it unnecessarily clutters the system.
You can disable IPv6 on the WAN interface and also in Firewall - Advanced.
Reinstalling should not be required, simply installing the opnsense package and then checking for updates should suffice. You can post here the full output from both commands just to be sure.
If all goes well, post reboot do another healthcheck just to be extra safe.
I have a similar issue.
I proceeded with a series of updates on an old install and I am now stuck on the system trying to get:
http://pkg.opnsense.org/FreeBSD:14:amd64/24.1/sets/changelog.txz
which does not exist.
However
://pkg.opnsense.org/FreeBSD:13:amd64/24.1/sets/changelog.txz
exists.
The question is:
- Is that useable?
- How to force to get that file?
I have a similar issue.
I proceeded with a series of updates on an old install and I am now stuck on the system trying to get:
http://pkg.opnsense.org/FreeBSD:14:amd64/24.1/sets/changelog.txz
which does not exist.
However
http://pkg.opnsense.org/FreeBSD:13:amd64/24.1/sets/changelog.txz
exists.
The question is:
- Is that useable?
- How to force to get that file?
Quote
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.1.10_8 at Tue Jul 30 16:04:03 CEST 2024
Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/24.1/sets/changelog.txz: Not Found
Updating OPNsense repository catalogue...
pkg: Repository OPNsense has a wrong packagesite, need to re-create database
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.1/latest/meta.txz: Not Found
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.1/latest/packagesite.pkg: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.1/latest/packagesite.txz: Not Found
Unable to update repository OPNsense
Error updating repositories!
pkg: Repository OPNsense has a wrong packagesite, need to re-create database
pkg: Repository OPNsense cannot be opened. 'pkg update' required
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
You somehow managed to update your system to FreeBSD 14 while staying at OPNsense 24.1 or below. That's why the URL is not found. 24.1 is built on FreeBSD 13.
Oh we have another one... at least these days we know this helps:
# opnsense-update -pA 24.7
Cheers,
Franco
Thank you both for your quick replies.
"opnsense-update -pA 24.7" does partially work, I stumble on another error:
===> Pre-installation configuration for squid-6.10
[6/8] Extracting squid-6.10: 79%
pkg-static: Fail to set time on /usr/local/sbin/.pkgtemp.squid.8Gwysv47Hapu:No such file or directory
[6/8] Extracting squid-6.10: 100%
Thay maybe why the system updated to a newer OS version, but not the corresponding OPNsense version. I've been performing the updates from the WEBUI previously.
EDIT:
Calling upon "opnsense-update -pA 24.7" a second time fixes the issue.
> pkg-static: Fail to set time on /usr/local/sbin/.pkgtemp.squid.8Gwysv47Hapu:No such file or directory
Ok, could have been the reason why the installation failed during the actual 24.7 upgrade. I'll think about it.
Cheers,
Franco