Check out http://pfsense.com/mirror.php?section=tutorials/carp/carp-cluster-new.htm
Basically at the bottom of the CARP Sync tab, the slave system shouldn't have a sync to IP but the SYNC at the top should be checked. The sync IP at the bottom is only needed at the slave if you have for example 3 failovernodes to daisychain the config: master -> backup1 -> backup2 -> ... I guess atm you have something like that: master -> backup ^ | | | ----------- permanent syncing loop ;-) Holger > -----Original Message----- > From: Bernhard Ledermann [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 07, 2006 11:10 AM > To: support@pfsense.com > Subject: AW: [pfSense Support] Empty or corrupt config.xml > > > That would be possible. Can you give me hints how this > configuration should loock like? > > -----Ursprüngliche Nachricht----- > Von: Holger Bauer [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 7. Februar 2006 11:03 > An: support@pfsense.com > Betreff: RE: [pfSense Support] Empty or corrupt config.xml > > You only have set master to sync to slave IP, right? Or is > there a chance you are syncing slave back to master as well? > If it's this way you are in a replication loop and because of > that config.xml is ALWAYS in access. > > > -----Original Message----- > > From: Bernhard Ledermann [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, February 07, 2006 10:55 AM > > To: support@pfsense.com > > Subject: AW: [pfSense Support] Empty or corrupt config.xml > > > > > > Yes, this happens on both machines. > > > > If I disable the carp synchronisation and remove the cable > > between the firewalls, then this failure doesn't happen anymore. > > > > It seems to be a pfsync replication issue. > > > > -----Ursprüngliche Nachricht----- > > Von: Holger Bauer [mailto:[EMAIL PROTECTED] > > Gesendet: Dienstag, 7. Februar 2006 10:22 > > An: support@pfsense.com > > Betreff: RE: [pfSense Support] Empty or corrupt config.xml > > > > Are you sure your drives are ok? Maybe it's just the drive > > having issues in the area where the config.xml is located. > > Does that happen on both machines? > > > > > -----Original Message----- > > > From: Bernhard Ledermann [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, February 07, 2006 10:17 AM > > > To: support@pfsense.com > > > Subject: AW: [pfSense Support] Empty or corrupt config.xml > > > > > > > > > I am running the version 1.0b2rc5 on a standard platform. > > > > > > -----Ursprüngliche Nachricht----- > > > Von: Holger Bauer [mailto:[EMAIL PROTECTED] > > > Gesendet: Dienstag, 7. Februar 2006 10:10 > > > An: support@pfsense.com > > > Betreff: RE: [pfSense Support] Empty or corrupt config.xml > > > > > > unless you are hitting a moment where the config.xml is just > > > being written that should not happen. I never had that kind > > > of issue. I'm usually powering down my testmachines by just > > > disconnecting power to see if they can recover from that > > > condition next time. I'm testing this with carp scenarios as > > > well. Which version are you running? > > > > > > Holger > > > -----Original Message----- > > > From: Bernhard Ledermann [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, February 07, 2006 9:56 AM > > > To: support@pfsense.com > > > Subject: [pfSense Support] Empty or corrupt config.xml > > > > > > > > > Hello > > > I am using pfsense firewalls in failover mode with carp > and pfsync. > > > Everything is working fine. But when I simulate an unexpected > > > power interrupt the config.xml is either empty or corrupt > > > after rebooting the firewalls. > > > Then I have to fix that on site on the console. > > > > > > Is there a way to prevent that? > > > > > > Thanks for your help! > > > > > > Regards > > > Bernhard Ledermann > > > > > > ____________ > > > Virus checked by G DATA AntiVirusKit > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > > > > > ____________ > > Virus checked by G DATA AntiVirusKit > > > > > > > --------------------------------------------------------------------- > > 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] > > > > > > ____________ > Virus checked by G DATA AntiVirusKit > > > --------------------------------------------------------------------- > 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] > > ____________ Virus checked by G DATA AntiVirusKit --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
