XML error: OPTXXXX at line 123 cannot occur more than once
-
Hey all,
I was setting up my vlans and clicked save and got this message "XML error: OPTXXXX at line 123 cannot occur more than once". Anyone know how to correct this? I rebooted and still get this message when logging into my interface.
Thank you
WaydeI should probably tell you it's the latest version of PFSense - sorry
-
sftp (or from console) to it and overwrite config.xml with one from backup dir and reboot.
Clarify what you are doing (step by step) if it happen again.
-
sftp (or from console) to it and overwrite config.xml with one from backup dir and reboot.
Clarify what you are doing (step by step) if it happen again.
I didn’t do anything out of the ordinary… just went into Interfaces (assign) clicked on VLANs and created my “lab” vlan 2 (clicked save) and did the same for “wireless” vlan 3 (clicked save). My WebGUI hung briefly and gave me that message.
I checked my Cisco router right after that error message and saw there was a collision on vlan 2. My Cisco switch is setup fine, doubt my switch caused the problem (?)
Your thoughts? -
sftp (or from console) to it and overwrite config.xml with one from backup dir and reboot.
Clarify what you are doing (step by step) if it happen again.
I didn’t do anything out of the ordinary… just went into Interfaces (assign) clicked on VLANs and created my “lab” vlan 2 (clicked save) and did the same for “wireless” vlan 3 (clicked save). My WebGUI hung briefly and gave me that message.
I checked my Cisco router right after that error message and saw there was a collision on vlan 2. My Cisco switch is setup fine, doubt my switch caused the problem (?)
Your thoughts?So since my last post I’ve had PF Sense working fine with all my vlans. I noticed vlan 2 was showing lots of collisions again and decided to remove it until I had more time tonight to check into it and bang, this time it reads XML error: OPTXXXX at line 153 cannot occur more than once.
I had a friend of mine (Sr. Network Engineer) to check my Cisco switches and found no issues with how they are setup.
Not sure what is causing this to occur… maybe hardware? Anyone else hear about this?Thank you for your time…
-
I was getting this for an option which didn't appear at all in the config.xml, and appeared to be gone from the config.cache. The only place it appeared was in /conf/backup. I grepped every file on the system.
After removing /conf/backup to root's homedir for now, the problem went away. So something is parsing backup configs and throwing a hard error when it doesn't like them, it seems.