Do not use special characters in the description. they will not parse and give you grief.
On 3/6/06, Amorim, Nuno Alexandre (ext) <[EMAIL PROTECTED]> wrote: > Well, some more tests on this. > > It's not a password problem. I've deleted everything, and start from a beta2 > full install. Configured the two nodes and the first rules they were > synchronized. > Then, after I created the third VIP, the synchonization failed with "Code > 104: XML error: not well-formed (invalid token) at line 187". The line is > many times different. > > Soooo... I've made a tcpdump of the comunication between the nodes, on port > 80. What puzzled me was that the line was many times different. And to > problem was caracters. In the description of one rule I had two portuguese > caracters (ç an ã) that were not parsed. > > > -----Original Message----- > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > Sent: sexta-feira, 3 de Março de 2006 19:29 > To: support@pfsense.com > Subject: Re: [pfSense Support] Configuration sync problem > > See http://cvstrac.pfsense.com/tktview?tn=831,6 for more information. > > On 3/3/06, Amorim, Nuno Alexandre (ext) <[EMAIL PROTECTED]> wrote: > > I'm not doubting that it works, because I've not found anything about this > > error in the mailing list and in the forum. > > > > What is code 104? And the line that it is refering to, is in what file? > > > > I've noticed that when I change the password, the error line also changes. > > > > -----Original Message----- > > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > > Sent: sexta-feira, 3 de Março de 2006 19:18 > > To: support@pfsense.com > > Subject: Re: [pfSense Support] Configuration sync problem > > > > Generally when that error comes up its one of the two. I have syncing > > enabled here at work and home, so I know it works... > > > > On 3/3/06, Amorim, Nuno Alexandre (ext) <[EMAIL PROTECTED]> wrote: > > > Same passwords and both nodes in HTTP. Tried also with different > > > passwords on the nodes. > > > > > > This happens in all versions I have tried (beta1, snapshot 2-19-06, > > > snapshot 2-20-06 and now in beta2) > > > > > > Right now I have node 1 with lots of rules and alias, and carp enabled. > > > Node 2 is completely blank, except for the interfaces and SYNC rule. I'm > > > thinking that maybe first I have to sync the nodes and then start the > > > firewall configurations. > > > > > > -----Original Message----- > > > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > > > Sent: sexta-feira, 3 de Março de 2006 19:03 > > > To: support@pfsense.com > > > Subject: Re: [pfSense Support] Configuration sync problem > > > > > > Mismatching passwords between the firewalls and or mismatched access > > > type (http/https). > > > > > > On 3/3/06, Amorim, Nuno Alexandre (ext) <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > Hello all. > > > > > > > > I'm having a problem with the xmlrpc sync between two nodes. It just > > > > doesn't > > > > happen. On node 1, it gives an error on system log: > > > > > > > > php: : An error code was received while attempting XMLRPC sync > > > > with > > > > http://10.10.10.2:80 - Code 104: XML error: not well-formed (invalid > > > > token) > > > > at line 29 > > > > > > > > What is causing this? > > > > > > > > Thanks, > > > > > > > > > > > > Nuno Amorim > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
