Upgrade Fails (Interfaces not configured)
-
Seems like your config file got some errors. Maybe it is the same behaviour like this with the same solution?
http://forum.pfsense.org/index.php?topic=33790.0
Please report the errors as a log here!
-Peter
-
Hi Peter,
I don't think that this is same problem. The system starts but I have to reconfigure the interfaces every time. The next time I'll do a reboot I'll save a boot log. Maybe that will help to diagnose the problem.
Do you know if the system already save a log on startup?Thanks,
Stenio -
Something in the old config is causing it to be tossed out. Can you send me a copy of your 1.2.3 config so I can look it over?
jimp (at) pfsense [dot] org.
-
I'm having the same issue. What's weird is I'm running a 2 pfsense setup with carp. The backup machine upgraded perfectly (from 1.2.2). The master machine had the problem you described above. During bootup I see a bunch of config related errors flash by quickly, then the interfaces are listed by name (wan, lan, dmz, dmzadmin, apps, pfsync) but none have any ip's.
-
Something in the old config is causing it to be tossed out. Can you send me a copy of your 1.2.3 config so I can look it over?
jimp (at) pfsense [dot] org.
Not sure if you need mine as well, but will a copy of the backup xml file from the webgui work or are you looking for a different config?
-
It should be
-
It should be
Thanks to jimp a solution was quickly found. I disabled (actually deleted) the OpenVPN server config I had setup and the install ran perfectly. I've now got both boxes successfully upgraded to 2.0.
-
Same for me,
when I delete The OpenVPN Configuration before Update, Upgrade works perfect!
Wolfgang
-
OK, I've got these configs already, but if anyone else hits the same issue, I'd like to see the configs also, for comparison and testing. I'll be running some tests on the OpenVPN upgrade code in the meantime, but it may be a few days.
-
Solved resetting to factory defaults. The system than upgraded completely to 2.0RC1.
Thanks,
Stenio
