On Thu, Apr 9, 2009 at 12:37 PM, Dimitri Rodis <dimit...@integritasystems.com> wrote: > I think this is more obscure than you think-- this is on a snapshot build, > so how many people have 1) run a 1.2.3 snapshot, 2) _had_ a redundant CARP > config, and then 3) removed the redundant member and 4) added some Outbound > NAT rules and interface rules (which is what finally triggered the XMLRPC > sync, and thus the error)? > > My guess is that people with redundant configs are probably not testing > snapshot builds (or even production builds) in this manner. I don't know if > this happens on previous builds, and you are probably going to say that the > code hasn't changed, and that's very likely to be true if you say so--I'm > just saying I think the bug is present, but obscure. > > Obviously if it happens it's easy enough to fix by downloading the config, > deleting the duped sections and uploading the config again, but I would tend > to think there's a bug in there somewhere, because like I said, I didn't > dupe the section myself.
My guess would be that you installed a snapshot that contained xmlparse.inc from HEAD. Right around the hackathon time this was included but has since been removed. Scott --------------------------------------------------------------------- To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
