"error in version information" at login update check, but successful upgrade from CLI

[stephenw10]

Hmm, nope that all looks fine. Nothing there is a show stopping error.

Yet you still see: unable to check for updates on the update page?

[beatvjiking]

@stephenw10 Yup... still the same. I ran a couple of filesystem check reboots (this machine is on UFS), did the minor update offered by option 13, and still unable to check for updates on the GUI.

[stephenw10]

Any errors logged?

Do you have IPv6?

[beatvjiking]

@stephenw10 I can't find any errors logged anywhere - it's why I'm pulling my hair out :) and no IPv6, either. Manually configured, no v6 addresses or routes on the machine.

[stephenw10]

Does it show available packages in the package manager?

[beatvjiking]

@stephenw10 yes, looks like a full and complete list. I compared it to another 2.8.1Beta machine I have running.

[stephenw10]

Hmm. Puzzling indeed!

Try: pfSense-upgrade -dC

The upper case C there causes it to check all configured repos which is what the dashboard check does.

[beatvjiking]

@stephenw10 again... no errors. It's kind of wild...

[2.8.1-BETA][admin@waw-staff-vpn.cic.com]/root: pfSense-upgrade -dC
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf:
Fetching data.pkg:
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:
Fetching data.pkg:
pfSense repository is up to date.
All repositories are up to date.
Your system is up to date
[2.8.1-BETA][admin@waw-staff-vpn.cic.com]/root:

[beatvjiking]

The plot thickens - on the login panel:

On the Update page:

Successful upgrade using option 13 via SSH, unchanged webUI behavior after upgrade. It's obviously running the check and able to parse something out of it because it updates the branch information displayed, but it's still wonky.

[reberhar]

@beatvjiking It seems to catch up after a little while.