Scott Ullrich wrote:
I cannot reproduce this one. I would say something in your XML is
nice and hosed. If you ever accidentally updated to -HEAD then this
is surely part of it.
Scott
On 2/10/07, William Armstrong <[EMAIL PROTECTED]> wrote:
Warning: Invalid argument supplied for foreach() in
/etc/inc/xmlparse.inc on line 184 Warning: Cannot modify header
information - headers already sent by (output started at
/etc/inc/xmlparse.inc:184) in /usr/local/www/diag_backup.php on line
102 Warning: Cannot modify header information - headers already sent
by (output started at /etc/inc/xmlparse.inc:184) in
/usr/local/www/diag_backup.php on line 104 Warning: Cannot modify
header information - headers already sent by (output started at
/etc/inc/xmlparse.inc:184) in /usr/local/www/diag_backup.php on line
105
I've got a similar problem last week.
After you've done several tens changes to the config (not that hard on a
production firewall), the time used for reindexing the backups increases
to a significant amount.
If something goes wrong during that time (in my case it was a panic
related to a CARP virtual IP, that firewall is still using BETA4) the
index becomes invalid and you are not even able to boot. My guess is
that something similar has happened to the original poster.
My solution has been to boot single user and rename /cf/conf/backup to
/cf/conf/badbackup.
Maybe pfSense should detect if the current config backup cache is
invalid, and reindex the backup directory accordingly.
Angelo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
