Attempting to update to 23.01 DEVEL corrupts my pfSense installation

michaellacroix

@stephenw10
Thanks so much for the update.

chickendog

I was experiencing this since Christmas and have been watching this thread, can confirm I've successfully updated now to build 23.01.b.20230104.0600

Thanks guys :)

Viper_Rus

And I can't update from 23.01.b.20230102.0600 to 23.01.b.20230104.0600. Before that it was updated every day.

Viper_Rus

@viper_rus
t was not possible to determine pkg remote version

How to fix it?

stephenw10

That isn't necessarily a show-stopping error. Try running pfSense-upgrade -d at the command line.

Steve

mtarbox

@stephenw10
Upgrade went without issue, pulled everything and installed.
PFBlockerNG-Dev had some php issues that resolved with a reboot.

Now I am seeing issues with Dynamic DNS. Deleted the info, replaced the info(just to make sure), still no dice. Not a deal breaker, but it's a BETA.

Jan 4 07:52:22 pfSense php-fpm[369]: /rc.dyndns.update: Dynamic DNS googledomains (pfsense.xxxxx.xx): Public IP address could not be extracted from Check IP Service
Jan 4 07:52:22 pfSense php-fpm[369]: /rc.dyndns.update: Dynamic DNS (pfsense.xxxxx.xx) There was an error trying to determine the public IP for interface - wan (ix3 ).
Jan 4 07:52:26 pfSense php-cgi[426]: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/system-sensors.rrd N:U:U:U' returned exit code '1', the output was 'ERROR: /var/db/rrd/system-sensors.rrd: expected 4 data source readings (got 3) from N'
Jan 4 07:52:26 pfSense php-cgi[426]: rc.bootup: Creating rrd update script

Services like DNSBL doesn't show up, yet unbound does. Maybe it is supposed to be that way, IDK.

I've rebooted 5 times, just to make sure.
Do feel free to move this, as it was a "successful" update from 22.05 to 23.01DEV, but with issues.

swampkracker

Upgrade from 22.05 to 23.01.b.20230104.0600 was successful.

OpIT GmbH

i tried to update, now iam no longer be able to login or use the console menu except 8 (shell)

Parse error: syntax error, unexpected ')', expecting '|' or variable (T_VARIABLE) in /etc/inc/util.inc on line 3655

stephenw10

Hmm. The RRD error is because there is no longer any temperature data from the cordbuc device in 23.01. You will probably need to reset the RRD file to clear that.

There were some issues with dyndns in earlier testing but I'm not aware of anything still outstanding. Check the configured 'Check IP Service'.

If the service is missing the package probably didn't reinstall correctly at upgrade. I would manually reinstall it from the package manager.

Steve

OpIT GmbH

@stephenw10
the problem is that the GUI is not working and in CLI the most Menu options also... i cant use Menu 4 (Reset) because of this error...

menu 8 (Shell) is working

stephenw10

@opit-gmbh That looks like what you might see if the filesystem is full. Do you have a lot of ZFS snapshots on that box? Do you see any filesystem errors in the upgrade logs?

At the command line you can run bectl list to see how many snaps you might have. And bectl destroy xxxx to remove older snaps.

Steve

OpIT GmbH

@stephenw10

i dont know but i think not.... Its a7100 netgate

stephenw10

Hmm, OK. Not that then. Let me try to replicate it....

stephenw10

Ok, that looks like a bug: https://redmine.pfsense.org/issues/13831
Should be fixed in the next snap.

stephenw10

@opit-gmbh Do you have any of the upgrade logs from that? Any other errors shown?

The chances of hitting that bug we found are extremely low.

Viper_Rus

@stephenw10
Fixed the situation like this.

I made a backup of the settings.
Restored an older image (22.05),
updated to the latest version of 23.01,
restored setting from backup

chickendog

@viper_rus Is this what you were getting?

I'm not sure it's really an issue though since it seems to complete the checks fine in the end?

This is running the pfSense-upgrade -d as Stephen suggested.

Viper_Rus

@chickendog
I was getting this error in the WEB interface and the installation process was interrupted. Perhaps it was possible to fix it with the proposed option, I'll use it next time :))) But at the moment I have the last snapshot ;)

chickendog

@viper_rus Ah ok I see, yeah I have no error in the web interface but have it via CLI. I'll see if it persists. I assume for now I'm on the latest build and there just hasn't been a new one since 23.01.b.20230104.0600

mikeisfly

Upgrade completed successfully.