Screenshot
-
Re: [Crash report error in Diagnostics > Backup & Restore > Configuration history](/top
image url)ic/197981/crash-report-error-in-diagnostics-backup-restore-configuration-history) -
@chris-doldolia Does it recur? There’s a bug in Plus where the history wasn’t being pruned. Accessing that page will do so but may time out the first time.
-
@SteveITS What do you mean Sir, every time we access that module of the pfSense will take more minutes and crash report appeared.
Thank you
-
@chris-doldolia what is in (from memory) /cf/conf/backup?
-
@SteveITS form configuration history Sir.
-
@SteveITS in configuration history module
-
This looks like it should have a crash dump submitted to support for Batman .. I mean Netgateman.
In all reality do you have the core dump?
-
The netgate technical support told me about our configuration setting. But I reviewed my configuration and found nothing wrong. The different configuration from this unit to the branch is the VPN configuration setup of the Wire Guard, because we have to manage our own server.
-
@chris-doldolia said in Screenshot:
But I reviewed my configuration and found nothing wrong
Look at your daily backup, the one you exported.
What is its size ?@chris-doldolia said in Screenshot:
the pfSense will take more minutes and crash report appeared
The "xmlparse.inc" contains the logic that checks the main pfSense config file (the one you backup daily). Its an xml file file after all. "xmlparse.inc validates ans parses all the entries.
If this file is to big, PHP (the interpreter that executes the "xmlparse.inc" script file on behalf of the web server GNIC, the GUI) will- run out of memory, and die.
- reach the maximum timeout out, and die.
Or, if inconsistencies are found, like circular references, it will be any of the above, thus die.
So, the cause can most probably found in the /cf/conf/config.xml.Btw : the pfSEnse config, all of it, is maybe 100 K bytes or so.
But package info is also stored, and also ... the rrd stats info.
-
@Gertjan Thank you sir
