OPNsense Forum
Archive => 17.7 Legacy Series => Topic started by: phoenix on October 05, 2017, 04:33:38 pm
-
I'm having problems updating via the web ui, I see the following error message when I hit the "check for updates" button:
Firmware status check was aborted internally. Please try again.
If I try to update from the console I see this:
Enter an option: 12
Fetching change log information, please wait... fetch: transfer timed out
fetch: /tmp/changelog/changelog.txz.sig appears to be truncated: 0/1332 bytes
This will automatically fetch all available updates, apply them,
and reboot if necessary.
Proceed with this action? [y/N]: y
Updating OPNsense repository catalogue...Fifteen minutes later and not much has happened, it eventually gets going and the full update for 17.7.5 took about one hour. Before I got to this point I did try a reboot as it worked for a previous update but no luck today.
This originally started on 17.7.3 when I had the same symptoms, a reboot and check for update and it worked fine that time but not since. Today I have tried each of the mirrors individually and left it at the default and nothing much changed, it was painfully slow. The only thing that's changed recently is my internet connection was upgraded (30th Aug) to fibre and I now have a working and configured IPv6 configuration on all my machines.
-
Hi Bill,
Can you try to ping the server using IPv6?
# ping6 pkg.opnsense.org
Then, go to System: Settings: General: and prefer IPv4 over IPv6.
Ping should tell us why your setup doesn't work. The setting should ensure that the update goes through ok. :)
Cheers,
Franco
-
Hi Franco
Thanks for that, I'd completely forgotten about the 'prefer ipv4' noption. Generally the check worked from the UI but took abot three minutes and the konsole gave this:
Enter an option: 12
Fetching change log information, please wait... fetch: transfer timed out
This will automatically fetch all available updates, apply them,
and reboot if necessary.
Proceed with this action? [y/N]: y
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (19 candidates): .......... done
Processing candidates (19 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Nothing to do.
Starting web GUI...done.
Generating RRD graphs...done.Obviously nothing much to do as I've just updated. :) I'll leave it as is for now and see if anything else happens, thanks for the help.
-
Ok, we'll catch it next time then!
-
Hello. New user here. :) I have the issue described above with 17.7.11.
I tried the suggestion of switching prefer IPv4 on and it didn't help. It would seem to work briefly on reboot/restarting the services but then break again. This got me thinking... what starts later in the boot/restart process?
Do you by any chance use OpenDNS and sign in to it though Services/OpenDNS? This adds IPv6 OpenDNS nameservers in /etc/resolv.conf *before* the IPv4 ones. I have found that disabling the signin to OpenDNS and and just manually putting only the IPv4 OpenDNS nameservers in System/Settings resolves the issue for me. I have not tried reenabling it and manually changing the order of the nameservers in /etc/resolv.conf to put the IPv6 ones last but I will when I get a chance. :)
Loving the project by the way. Really great work. Thanks.
Charlie
-
Hi Charlie,
Interesting. The code in OpenDNS actually honours prefer IPv4, but only if it's switched off, saved, and turned back on. Let me change that so that any "save" on the page will automatically fix it.
Cheers,
Franco