[SOLVED] Update timeouts/delays since 17.7.2 is available

[Dronov]

Folks,

There is a strange problem with my opnsense install. I was wondering if somebody has any ideas how to resolve or at least troubleshoot it further.

I've skipped 17.7.2, as I was away for a while. Since 17.7.3 became available, the update UI always fails with "Firmware status check was aborted internally. Please try again." Often the "Update"/"Plugins"/"Packages" tabs are unusually empty. In the logs I see "config.d.py [...] returned exit status 1"

Doing opnsense-update from the command line seems to work, but it is extremely slow, takes approximately 10 minutes (mostly while doing pkg-static update and pkg-static upgrade) to check the status and then it took hours to upgrade to 17.7.3.

Another strange thing: update UI "thinks" the system is stuck at 17.7.1 (that's the latest version shown), while upgrade to 17.7.3 seems to be successful and dashboard says "OPNsense 17.7.3-amd64"

Reboot doesn't change anything. I tried multiple update mirrors, but there is no difference in timing.

Thanks a lot.

[franco]

Hi there,

Check to see if someone installed a proxy in front of OPNsense. If you e.g. don't see newer changelogs you cannot reach http://pkg.opnsense.org which works fine for IPv4 and IPv6 nowadays.


Cheers,
Franco

[Dronov]

Oh, while I am quite sure there was/is no proxy involved, that sent me in the right direction. Thanks a lot!

Most likely it was my (broken) IPv6 setup. There was, however an additional change in opnsense which triggered something, since I have not touched anything for at least 6 months.

Anyway, in my case the root cause was as follows: the opnsense box itself had no IPv6 connectivity (while the LAN and WAN were IPv6 enabled). I'll post a separate question later.

[franco]

That sounds plausible as IPv6 was added recently and the default setting is to prefer IPv6 if it can. :)


Cheers,
Franco

[fabian]

That sounds plausible as IPv6 was added recently and the default setting is to prefer IPv6 if it can. :)

This is what is required by the RFC (always prefer IPv6 if available) and should be done since around 20 years.

[franco]

Sure, the only variable here was the added IPv6 support for the mirror 1 week ago that triggered this.


Cheers,
Franco

[phoenix]

This sounds like the problem I had last week when I did an upgrade from the web UI. I also had this again today and doing the upgrade via the konsole took over half and hour to download the packages (and there weren't many this week) although the upgrade did work - I also have IPv6 enabled on the WAN & LAN nics.