Updating to latest snapshot kills pfsense

[jlepthien]

I have this with nanobsd snapshot updates. After updates it looses all NIC configuration. I am on 10/18 snap and yesterday's snap did not work and I tried just now with the New version: Fri Oct 22 00:14:23 EDT 2010 snap which also does not work…

[littlejohn]

Same problem…

2.0-BETA4  (amd64) built on Thu Oct 21 04:14:14 UTC 2010

What I did:

---> Fatal error: Cannot use [] for reading in /etc/inc/upgrade_config.inc on line 1325

in /etc/inc/upgrade_config.inc on line 1325

change
$config['crl'][];
to
$config['crl'][] = $crl;

(you can use vi)

then reboot, and everything should be back to normal. Be quick, because after about a minute, I get endless kernel messages on one of the interfaces going UP/DOWN….

Regards,
John

[nobluescreen]

I have the same issues.  Can reset to defaults and reconfigure the interfaces but upon reboot configuration is  lost.  I get the same configuration error as above running the latest snapshot.

[danderemer]

@John:

Same problem…

2.0-BETA4  (amd64) built on Thu Oct 21 04:14:14 UTC 2010

What I did:

---> Fatal error: Cannot use [] for reading in /etc/inc/upgrade_config.inc on line 1325

in /etc/inc/upgrade_config.inc on line 1325

change
$config['crl'][];
to
$config['crl'][] = $crl;

(you can use vi)

then reboot, and everything should be back to normal. Be quick, because after about a minute, I get endless kernel messages on one of the interfaces going UP/DOWN….

Regards,
John

I too have experienced this issue and John Little's fix worked for me. I am running the NanoBSD 2G BETA4 image from 10-22-2010 4:53am (file: pfSense-2.0-BETA4-2g-20101022-0014-nanobsd.img.gz) on a PC Engines ALIX.2d1.

I noticed none of the interfaces are defined at boot even after configuring them in the previous boot. I can then re-assign the interfaces and restart the webConfigurator and I am then able to function for the most part. When I get into the web GUI, the System Logs is completely blank. I went to Diagnostics -> Edit File and edited the line John Little mentioned in /etc/inc/upgrade_config.inc and now everything works.

[eduardr]

Killed my Alix Nano BSD also. Since I don't have a serial cable I can use at the moment, I had to open up the case and reflash the cf card with an older pfsenbse image.

[nobluescreen]

The above configuration change has fixed the problem for me as well.

[littlejohn]

@danderemer:

I too have experienced this issue and John Little's fix worked for me. I am running the NanoBSD 2G BETA4 image from 10-22-2010 4:53am (file: pfSense-2.0-BETA4-2g-20101022-0014-nanobsd.img.gz) on a PC Engines ALIX.2d1.

I noticed none of the interfaces are defined at boot even after configuring them in the previous boot. I can then re-assign the interfaces and restart the webConfigurator and I am then able to function for the most part. When I get into the web GUI, the System Logs is completely blank. I went to Diagnostics -> Edit File and edited the line John Little mentioned in /etc/inc/upgrade_config.inc and now everything works.

Hello danderemer. If you have access to the console / serial console, then it might be easier to just use vi or whatever other editor is available, no need to change your config at all.

For those who have never used vi, do this:

Press 8 (I'll check) to drop into a shell, then type
vi /etc/inc/upgrade_config.incENTER
1325G (should be on the line $config['crl'][]; )
$i=$crlESC (goes to the end of the line, enters insert mode, you type =$crl, then ESC to go back into command mode)
:wqENTER (save and quit, ESC, ENTER are the keyboard keys)

Cheers,
John

[danderemer]

@John:

<snip>Hello danderemer. If you have access to the console / serial console, then it might be easier to just use vi or whatever other editor is available, no need to change your config at all.</snip>

The whole re-assigning of the interfaces deal was during my troubleshooting efforts and was done by a serial cable connection to the console. Shortly after that, I found your post. I attempted your fix via the shell under the console using vi and ran into a read access error. I was then able to make the appropriate change using the Edit File utility in the web GUI. I was not able to determine what was unique about my situation that prevented me from applying your fix via vi at the console.

Thanks for the help.

-Dan

[wallabybob]

@danderemer:

I was not able to determine what was unique about my situation that prevented me from applying your fix via vi at the console.

Probably that you are using the embedded version of pfSense (which mounts the file systems read only) while John Little uses the full version of pfSense which mounts the file systems read-write

[littlejohn]

Hello wallabybob!

@wallabybob:

Probably that you are using the embedded version of pfSense (which mounts the file systems read only) while John Little uses the full version of pfSense which mounts the file systems read-write

Thanks for the info. Hopefully this thread is going to get less and less relevant in time, but would you mind posting some additional steps to change this file on the embedded version? Can you mount the filesystem image as read-write somewhere? Or is there already a different path than /etc that can be used?

edit Would this help?

@gnhb:

the next command is for embedded versions only to make the filesystem writeable.
at the command line for embedded versions only. . .

pfsense:~# mount -u -w /dev/ufs/pfSense

As seen here: http://forum.pfsense.org/index.php/topic,15555.msg81427.html#msg81427

Cheers,
John

[Efonnes]

A little late reply, but should be useful for anyone who wants to know.  On NanoBSD, run the command /etc/rc.conf_mount_rw to remount the file system as read/write.  When you are done making changes, run /etc/rc.conf_mount_ro to change it back to read-only.