I am not sure whether this has anything to do with the latest update (23.1.5_4), but I can't check for a firmware update.
In the WebUI it's stuck at:
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 23.1.5_4 at Tue Apr 4 19:56:57 EDT 2023
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. 817 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.
At line Updating OPNsense repository catalogue..., it is stuck for 1 minute and 10 seconds.
At line Fetching meta.conf: . done, it is stuck for 1 minute and 13 seconds.
Then at the last line Your packages are up to date., it's stuck forever. I've been waiting for 10 minutes and the spinner in the Updates tab is spinning. It never returns, nor does the green dialog pop up that tells me that there are no updates.
I did a reboot, but that did not help.
And on the command line, it is stuck here:
Enter an option: 12
Fetching change log information, please wait... done
This will automatically fetch all available updates and apply them.
I did not see any error messages in the log. Any idea what's going on?
I found additional info. So it seems that the following process is stuck:
/bin/sh -c pkg update -q && pkg rquery -U "%n|||%v|||%c|||%sh|||0|||0|||%L|||%R|||%o"
I checked the following manually on the command line:
pkg update -q runs without a problem. Same is true for pkg rquery -U "%n|||%v|||%c|||%sh|||0|||0|||%L|||%R|||%o".
However, for some reason pkg update -q && pkg rquery -U "%n|||%v|||%c|||%sh|||0|||0|||%L|||%R|||%o" never completes.
Same issue here, however I have noticed there is a rather massive downtime alert for Cloudflare noting increased latency.
That could be causing it?
Quote from: TheGreatBellend on April 05, 2023, 04:20:08 AM
Same issue here, however I have noticed there is a rather massive downtime alert for Cloudflare noting increased latency.
That could be causing it?
I doubt it. In that case the pkg update commands would not work or timeout.
What I do not underatnd is why
cmd1 && cmd2 never finishes. This is a perfectly valid shell construct.
Same issue here.
I have 3 opnsense installations in 3 different places and all of them have the same problem.
I setup Google DNS in Settings -> General and then flagged "Do not use the local DNS service as a nameserver for this system" in DNS server options as suggested in other threads.
Unfortunately the problem persists in all of 3 installations.
I tried a system update from the Gui (from version 23.1.1 to 23.1.5) and the download speed is really slow. At a certain point procedure stucks at number 16 (fetching DNSmask) and nothing happens.
Anyone knows what's going on?
Hopre to hear good news about it very soon.
Best regards,
Michele.
Looking at another thread dealing with much the same issue -- try using a different mirror. The DE mirror seems to not have issues. I am going to confirm later today on a second system. I finally got my first test system updated over night using its default mirror (assuming the US since that is where I am), but it took over 8 hours to do.
Quote from: dd2594opn on April 05, 2023, 01:37:21 PM
Looking at another thread dealing with much the same issue -- try using a different mirror. The DE mirror seems to not have issues. I am going to confirm later today on a second system. I finally got my first test system updated over night using its default mirror (assuming the US since that is where I am), but it took over 8 hours to do.
That's what I did few hours ago and it worked!
I used Aalbrog University mirror and it was ok. Default mirror, don't know what it is, stucks.
Thanks for reply,
Michele.
The same problems here. Several OPNsense's distributed over different locations. All mirrors which speak IPv6 are not reachable or it takes hours until they update the packets.
Remedy has brought us c0urier.net in Sweden, this speaks only IPv4.