Update Firmware Status, keeps hanging

Started by IsaacFL, February 26, 2024, 10:02:58 PM

Previous topic - Next topic
When I check the update status, keeps hanging with spinning wheel. Here is attached status.
It does eventually comes back with ***DONE*** after many minutes.




***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.1.2_1 at Mon Feb 26 12:48:35 PST 2024
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /usr/local/opnsense/changelog/changelog.txz appears to be truncated: 0/128592 bytes
Updating OPNsense repository catalogue...
Waiting for another process to update repository OPNsense
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.

Check health has been running for about 20 minutes.  Currently:

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 24.1.2_1 at Mon Feb 26 13:02:31 PST 2024
>>> Root file system: /dev/gpt/rootfs
>>> Check installed kernel version
Version 24.1.2 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 24.1.2 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
os-acme-client 4.1
os-ddclient 1.21
os-qemu-guest-agent 1.2
os-wol 2.4_2
>>> 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" has 68 dependencies to check.
Checking packages: .......

QuoteFetching changelog information, please wait... fetch: transfer timed out

You might have some IPv6 not fully operational responsible for it or the primary DNS is not working/configured properly.

Otherwise you're up to date, nothing to do until 24.1.3 comes out.

Switching the mirror from "default" to LeaseWeb San Francisco (I'm in Southern California) seems to have fixed it. Never had an issue with using default before.