after upgrading to 25.03_Beta Cloned boot environment - now have PHP Fatal error code and blank blue page when attempting to access boot environments
-
Error:
[11-May-2025 23:48:01 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/www/system_be.php(89): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781
[11-May-2025 23:48:16 America/Denver] PHP Fatal error: Uncaught ValueError: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in /usr/local/pfSense/include/www/system_be.inc:781
Stack trace:
#0 /usr/local/pfSense/include/www/system_be.inc(781): array_combine(Array, Array)
#1 /usr/local/pfSense/include/www/system_be.inc(907): zfs_list('pfSense/ROOT', 'pfsense:descrip...', 'pfsense:failed', 'pfsense:lastboo...', 'pfsense:prior', 'pfsense:protect', 'pfsense:upgradi...', 'pfsense:version')
#2 /usr/local/www/system_be.php(89): be_get_bootenv_props_ex(Object(LibbeHandle), Array)
#3 {main}
thrown in /usr/local/pfSense/include/www/system_be.inc on line 781 -
So you cloned a 24.11 BE then booted in to it and upgraded that to 25.03-beta?
-
S stephenw10 moved this topic from General pfSense Questions 7 days ago
-
@stephenw10 I cloned my 24.11 Release. Did not boot out or reboot. Ran the updater 25.03 Beta and it all worked. I proceeded to System - Boot Environments - to the Active boot environment and proceeded to edit the name and description to reflect a Post 25.03-BETA boot environment. It balked at my first attempt - I assume because I used a comma. I re-edited to remove the comma and saved and here we are!
I have been here before with re-naming a boot environment and php errors.
-
Hmm, OK. What excatly was the BE named before and after?
-
Before: Current_25.03_BETA_Updated_From_24.11_RELEASE_24.11.r.20241112.1813_LAST_ACTIVE
Which is the current BEMy first edit:
Current_25.03_BETA_Updated_From_24.11_RELEASE,24.11.r.20241112.1813_LAST_ACTIVEMy final edit - which lead to the crash report - I believe:
Current_25.03_BETA_Updated_From_24.11_RELEASE_and_24.11.r.20241112.1813_LAST_ACTIVEDescription for both:
Post 25.03 BETA update -
@stephenw10 Some more information - when I decided if I could roll-back using - Diagnostics - configuration history - I get the same blank blue screen with the words "Return to dashboard."
-
@The-Party-of-Hell-No said in after upgrading to 25.03_Beta Cloned boot environment - now have PHP Fatal error code and blank blue page when attempting to access boot environments:
My first edit:
Current_25.03_BETA_Updated_From_24.11_RELEASE,24.11.r.20241112.1813_LAST_ACTIVEThe comma or periods in the name may have triggered something. Valid characters for the BE name field are
[0-9a-zA-Z_]per the help text in the GUI. -
@marcg From above:
"It balked at my first attempt - I assume because I used a comma. I re-edited to remove the comma and saved and here we are!" -
@The-Party-of-Hell-No said in after upgrading to 25.03_Beta Cloned boot environment - now have PHP Fatal error code and blank blue page when attempting to access boot environments:
when I decided if I could roll-back using - Diagnostics - configuration history - I get the same blank blue screen
So just visiting the Diag > Config History page?
-
@stephenw10 Yes same blank blue screen with the words "Return to Dashboard" which when clicked on returns me to the dashboard.