Project

General

Profile

Actions

Bug #1542

closed

Fatal Error during Upgrade from 2.0-RC1 to latest snapshot 2.0-RC2<May 18 built>

Added by Epi Salamanca almost 13 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
05/19/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

Hi,
I've just upgraded from pfSense-2.0-RC1-i386-20110226-1530.iso
to latest snapshot (pfSense-2.0-RC1-i386-20110518-2103.iso) using
the GUI.
Everything goes perfect until it reboots.
Once it reboots, a FATAL ERROR is generated just after "Updating Configuration",
and the boot process terminates, leaving the node without network access.
The error given is:
Updating Configuration ...
Fatal Error: Cannot use string offset as an array in /etc/inc/config.lib.inc xxx (line) 384.
code

function convert_config() {
        global $config, $g;
        $now = date("H:i:s");
        log_error("Start Configuration upgrade at $now, set execution timeout to 15 minutes");
        //ini_set("max_execution_time", "900");

        /* special case upgrades */
        /* fix every minute crontab bogons entry */
        $cron_item_count = count($config['cron']['item']);
        for($x=0; $x<$cron_item_count; $x++) {
/*384 -->*/       if(stristr($config['cron']['item'][$x]['command'], "rc.update_bogons.sh")) {
                        if($config['cron']['item'][$x]['hour'] == "*" ) {
                        $config['cron']['item'][$x]['hour'] = "3";
                                write_config("Updated bogon update frequency to 3am");
                                log_error("Updated bogon update frequency to 3am");
                        }
                }
        }
...
 

I managed to overcome this error by commenting out the code related with above 'for' loop ...

c.u.

Actions #1

Updated by Jim Pingle almost 13 years ago

  • Status changed from New to Feedback

That error would point to your config being empty or unparseable. Look farther back in the boot log for more detail. This would probably work better as a forum thread until it's confirmed.

Actions #3

Updated by Chris Buechler about 12 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF