XML error: OPTXXXX at line 128 cannot occur more than once

ventiman

Help. I get the XML error no matter what option I pick.

pfSense console setup

0) Logout (SSH only)
1) Assign Interfaces
2) Set LAN 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: XML error: OPTXXXX at line 124 cannot occur more than onceXML error: OPTXXXX at line 124 cannot occur more than once

jimp

What version is this?

The condition that caused that error was fixed before 1.2.3 came out, I thought. It was a side effect of deleting too many interfaces in a row, IIRC.

ventiman

its pfSense 1.2.3-RC3 It came on a LinITX ALIX 2D3 LX800.

fact I think thats what happen by mistake I clicked on deleting a interface and my guess more than one got deleted

So now i stuck. Less there is way to fix it

jimp

Can you get into the WebGUI at all? Do you have SSH enabled?

It's unusual for that to happen on every menu option, because some – such as the shell invocation -- do not touch the config or PHP at all.

If you can get into the GUI you could restore an older config file, and you could do the same from the shell by copying one of the backup config files from /conf/backup/ over /conf/config.xml

vito

I had this problem about a mth ago.
once i got the error, nothing worked.

It started when i tried deleting an interface.

I had constant pings running for testing to different subnets on my PF box, once i got this error, everything dropped. (including local web access)

The only thing that i could do was take my config.xml and remove any xml segment that referred to OPTXXXX. The reason i did this was due to the fact that the OPTXXXX entry(s)
(like IP settings, DHCP) corresponded to another interface. (NOTE: it did not correspond to the interface i was deleting either) It did not seem like other interfaces had "additional" OPTXXXX entries.

Once i deleted everything labeled OPTXXXX in config.xml, everything worked fine.

Note sure if this was the right thing to do, but it was 4:00 am and not to many options. :)

NOTE: this pf box was 1.2.3 RC3 upgraded to PF 1.2.3 release.
Running on a Core2 4GB server with two onboard 100/1000 Intels and a 4port 100/1000 Intel Card.

ventiman

No I dont have shh enabled.
I can try and see if I can enable it via the serial terminal

And I can try the gui again.. But if the ports got deleted by mistake im not sure if that wil help.
Course id love to be able to just replace the config.xml with my backup config.xml.
But i cant mount the card on my linux or windows.
And there seems to lack a good bsd live cd to try and rescue it via that way.

The shell option #8 works
Ive not tried #14 yet

jimp

Go to option #8 and then:

Change to the backup folder:

# cd /conf/backup

Then look at the files there:

# ls -l

You should see a bunch of configuration files with timestamps, like so:

[...]
-rw-r--r--  1 root  wheel  26457 Apr  5 19:19 config-1270509560.xml
-rw-r--r--  1 root  wheel  26480 Apr  5 19:20 config-1270509585.xml
-rw-r--r--  1 root  wheel  27367 Apr  5 19:22 config-1270509650.xml

Pick the previous one, or one before that, and copy it over, and then remove the config cache, and reboot:

# cp config-1270509650.xml ../config.xml
# rm /tmp/config.cache
# reboot

ventiman

*** Welcome to pfSense 1.2.3-RC3-nanobsd on pfsense ***

LAN -> vr0 -> 192.168.1.xx.xx
WAN -> vr1 -> NONE(DHCP)
OPT1(WIFI) -> vr2 -> 192.168.xx.xx

pfSense console setup

0) Logout (SSH only)
1) Assign Interfaces
2) Set LAN 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)

Ive not tested it yet as far as gui log in. But compared to my 1st post the error is gone and now shows my lan IP info.

though the command rm /tmp/config.cache >/tmp/config.cache: No such file or directory< would result in that. So I just went ahead and did reboot. But seems to look good.

ventiman

Well its up ruining working ok now.
Thanks :)))

I'm more use to using PF on a old desktop so if i messed up I just reload and the restore my saved backup.
The embeds are all new to me.. saved some bit of worry, specially when someone else paid 200 some for the device.