next »

[clarknova]

I just updated from the 20 October snapshot to this one:
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/pfSense-Full-Update-2.0-BETA4-20101021-1108.tgz

and pfsense didn't come up properly. I tried configuring the LAN interface on the console but no dice. Here's the pasted contents of the console on a fresh boot.

Code:

Timecounters tick every 1.000 msec

IPsec: Initialized Security Association Processing.

usbus0: 12Mbps Full Speed USB v1.0

usbus1: 480Mbps High Speed USB v2.0

ugen0.1: <Intel> at usbus0

uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0

ugen1.1: <Intel> at usbus1

uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1

ad14: 228936MB <OCZ VERTEX2 1.11> at ata7-master UDMA100 SATA 3Gb/s

GEOM: ad14: partition 2 does not start on a track boundary.

GEOM: ad14: partition 2 does not end on a track boundary.

SMP: AP CPU #1 Launched!

Root mount waiting for: usbus1 usbus0

uhub0: 2 ports with 2 removable, self powered

uhub1: 2 ports with 2 removable, self powered

Trying to mount root from ufs:/dev/ad14s1a

Mounting filesystems...

     ___
 ___/ f \
/ p \___/ Sense
\___/   \
    \___/

Welcome to pfSense 2.0-BETA4  ...

Creating symlinks......done.
appending output to nohup.out
Launching the init system... done.
Initializing................................ done.
Starting device manager (devd)...done.
Loading configuration......done.
Updating configuration...
Fatal error: Cannot use [] for reading in /etc/inc/upgrade_config.inc on line 1325
Starting CRON... done.
Executing rc.d items...
 Starting /usr/local/etc/rc.d/*.sh...done.
Bootup complete


FreeBSD/i386 (Amnesiac) (ttyu0)




*** Welcome to pfSense 2.0-BETA4-pfSense (i386) on pfsense ***

  WAN (wan)                 -> pppoe0     -> NONE (PPPoE)
  LAN (lan)                 -> em1_vlan85 -> NONE
  WISP (opt1)               -> em1_vlan102 -> NONE
  UBNT (opt2)               -> em1_vlan250 -> NONE
  MODEM1 (opt3)             -> em0_vlan201 -> NONE
  MODEM2 (opt4)             -> em0_vlan202 -> NONE
  MODEM3 (opt5)             -> em0_vlan203 -> NONE
  MODEM4 (opt6)             -> em0_vlan204 -> NONE
  MODEM5 (opt7)             -> em0_vlan205 -> NONE
  MODEM6 (opt8)             -> em0_vlan206 -> NONE
  MODEM7 (opt9)             -> em0_vlan207 -> NONE
  MODEM8 (opt10)            -> em0_vlan208 -> NONE
  WIFI (opt11)              -> em1_vlan51 -> NONE

 pfSense console setup
***************************
 0)  Logout (SSH only)
 1)  Assign Interfaces
 2)  Set interface(s) IP address
 3)  Reset webConfigurator password
 4)  Reset to factory defaults
 5)  Reboot system
 6)  Halt system
 7)  Ping host
 8)  Shell
 9)  PFtop
10)  Filter Logs
11)  Restart webConfigurator
12)  pfSense Developer Shell
13)  Upgrade from console
14)  Enable Secure Shell (sshd)

Enter an option: em0: link state changed to UP
em1: link state changed to UP

In particular, I like this line: "FreeBSD/i386 (Amnesiac) (ttyu0)". Prophetic!

I did a fresh install of the latest amd64 build and that boots.

[Phobia]

Hi there,

My attempted upgrade from a build a couple of days ago (I believe it was from Oct.19) was borked by :

pfSense-Full-Update-2.0-BETA4-20101021-1108.tgz

I saw a fatal error on startup flash by too similar to what CN reports above :

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

The console shows all interfaces with no IP information.  I was able to manually set the LAN interface IP address, and afterwards was able to restart the webconfigurator and get into the WWW GUI.  After manually entering each interface and clicking save, the interface would come up and get an IP, but I still had no internet access.

Tried deleting all gateways, and changing my firewall rules to point to the "default" GW instead of my routing group gateway.

On reboot, all IP information is again lost and I need to repeat the steps above to regain access to the WWW GUI.  I see the same(?) fatal error message flash by before the console menu comes up.

Like CN, I have multi-WAN.  2xPPPoE + 1 DHCP.  (VDSL, DSL, Cable)

I have reverted to :

2.0-BETA4 (i386)
built on Wed Oct 20 20:31:52 EDT 2010
FreeBSD 8.1-RELEASE-p1

All seems OK from there.  Something is definitely broken with the latest snap.

-- Phob

[ermal]

Yeah it should have been fixed and a new snapshot should be ok.
It was a issue with upgrading the config to latest version.

[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...

[John Little]

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]

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.

[John Little]

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]

<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]

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

[John Little]

Hello 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?

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

[Efonne]

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.