Upgrade Fails (Interfaces not configured)

siefert

Hi together,

I have problems upgrading our firewall to 2.0RC1

Our Configuration

Wan (Real IPs)
Lan NAT
OPT 1 Bridged with WAN
OPT 2 NAT
OPT 3 WLAN-AP NAT

After Upgrading Rules are upgraded , I think this part works, after that many errors scrolling on the screen…

Result is all Interfaces are there but they are not configured- no IP address is assigned.

Maybe somebody is interested to locate the problem, its on the backup machine so i can play a little.

When I reboot upgrading rules is beginning again with the same result.

Thank you for your great work on pfsense and your support

Wolfgang

stenio

@siefert:

After Upgrading Rules are upgraded , I think this part works, after that many errors scrolling on the screen…

Result is all Interfaces are there but they are not configured- no IP address is assigned.

[…]

When I reboot upgrading rules is beginning again with the same result.

Hi Wolfgang,

I have the same problem:
http://forum.pfsense.org/index.php/topic,34186.msg177316.html#msg177316

Please, let me know if you find a solution.

Thanks,
Stenio

eri--

What kind of errors are we talking about?

stenio

@ermal:

What kind of errors are we talking about?

After upgrading from 1.2.3 to 2b5 and rc1 at every upgrade/reboot the interfaces must be reconfigured.

Regards,
Stenio

peer_g

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

stenio

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

jimp

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.

jpgator

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.

jpgator

@jimp:

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?

jimp

It should be

jpgator

@jimp:

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.

siefert

Same for me,

when I delete The OpenVPN Configuration before Update, Upgrade works perfect!

Wolfgang

jimp

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.

stenio

Solved resetting to factory defaults. The system than upgraded completely to 2.0RC1.

Thanks,
Stenio