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

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.

stephenw10

Yup I would expect it to show the data after a refresh or two. But for @beatvjiking it seems like that doesn't happen in the GUI.

beatvjiking

@stephenw10 @reberhar correct. I've got a few dozen other pfSense machines that are doing it properly, it's just this one that wants attention.

syhm

@beatvjiking I’m experiencing the same problem and also only with one instance. The error message "Error in version information" is misleading — the underlying issue is that error messages can overwrite each other, so the original cause (in this case "Unable to check for updates") gets lost. I’ll fix that and open a ticket. However, I’m still investigating what is actually causing "Unable to check for updates".

reberhar

@syhm Thanks

syhm

Ok, I found out what was missing in my case — maybe this will help you too. The package pfSense-base was missing.

I ran:

pkg install -f pfSense-base

and everything started working again.

stephenw10

Huh, that's interesting. Can you see when that was removed in the logs?

syhm

I had to reinstall, I had a free pfsense plus licence which sadly was now invalid. After the first boot everything worked but after restoring the pfsense plus config the error started showing up.

beatvjiking

@syhm Thanks, although I did try that and unfortunately no dice.