traffic_shaper_wizard_dedicated crash
-
Version:
I selected all of the default values except specified the download and upload date rates to match the maximum supported by my ISP. When the last page was reached the wizard crashed.
[09-Feb-2023 16:34:46 America/New_York] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/wizards/traffic_shaper_wizard_dedicated.inc:729
Stack trace:
#0 /usr/local/www/wizards/traffic_shaper_wizard_dedicated.inc(626): apply_all_chosen_items()
#1 /usr/local/www/wizard.php(116) : eval()'d code(1): step8_stepsubmitphpaction()
#2 /usr/local/www/wizard.php(116): eval()
#3 {main}
thrown in /usr/local/www/wizards/traffic_shaper_wizard_dedicated.inc on line 729 -
Might be a variation of this issue:
https://redmine.pfsense.org/issues/13915
You might be able to work around it by removing the
<ezshaper>...</ezshaper>
section from your config and then trying the wizard again. -
@jimp I agree it looks like the same issue.
What is the best way to edit the configuration without using the wizard? -
You can either download a config backup, edit it out, and restore, or if you are familiar with
vi
you can useviconfig
from a console/ssh shell session. That's a bit more dangerous, though. Easy to make a wrong edit and break things. -
@jimp My apologies for my ignorance, but what is the path to the configuration via the shell?
-
/conf/config.xml
-
@jimp unrelated to the traffic shaper wizard crash when I enter the shell there are recent core files in /root
-rw------- 1 root wheel 241942528 Feb 7 12:15 snort.core
-rw------- 1 root wheel 11517952 Feb 3 23:28 rate.corewhich will be from a slightly earlier RC version. Do you want those?
-
No, they aren't likely to be helpful at this point.
-
@jimp after backing up and restoring the edited configuration the wizard succeeds.
However, two other problems occurred during the restore:
- I use the 4100 igc3 as the WAN port since its 2.5 gbit/s. During the restore the WAN port was restored as igc0 which conflicted with the LAN port.
- The acme certificate that was restored was not current. It was the first certificate that was obtained via acme. I had to manually request a new certificate which was successful. However, due to HTTP STS I couldn't successfully connect by hostname until the new cert was obtained.