Bug #5285
closed
Failsafe mode
0%
Description
I'm not sure if this should be a feature request or a bug report, anyway since I've been messing around the webUI on a pfsense VM it seems like I got it broken and it doesn't complete the boot process anymore. It's probably solvable but my report is that pfSense shouldn't break like this with some wrong configuration. Maybe it should include some detection if something fails and use default values instead of giving me a dead machine.
Files
Updated by Chris Buechler over 8 years ago
- Status changed from New to Feedback
what specifically did you do to break it? that looks like $config is no longer an array and is within the config upgrade code which wouldn't be touched unless an upgrade had just happened and the config needed to be upgraded.
Updated by Fernando Munoz over 8 years ago
Unfortunately, I don't know for sure, I installed all the available packages and tried to use invalid data in every input fied I see to check for vulnerabilities. The message on the screen seems to be a warning only however it keeps calling the config.lib.inc file all the time and it doesn't continue booting, I had to reinstall.
Updated by Chris Buechler over 8 years ago
- Status changed from Feedback to Not a Bug
if the XML is invalid, and there are backups in the config history, it'll restore from there. So there is a "failsafe" there, which works in normal circumstances. "Installing every package and saving invalid data everywhere" isn't normal circumstances. Granted it shouldn't fail, but will need to know more about what triggers the failure to do anything. There is probably one or more package bugs there, if you find which, please report that as their own issues.