Has anyone tested 1.21 with a carp cluster?

[heiko]

after 2 hours? what is that meaning?

[Juve]

;D I was meaning that the cluster is runing for 2 hours without any problem.

[heiko]

@Juve:

;D I was meaning that the cluster is runing for 2 hours without any problem.

upps, and then…

[Juve]

then all is runing fine , RPC-XML sync is OK as well as CARP and pfsync.
;)

[heiko]

I think, i will tested it with the newest snapshot again…

[eri--]

Heiko, is the cluster trying to sync through the WAN interface?

[heiko]

Yes, the configuration is the same as 1.2 (Wan Carp, lan Carp), but with 1.21 it didn´t run. The same test scenario, but if all people says, it runs, i will test it again..,thanks ermal

[eri--]

Please retry with a recent snapshot and see if the problem goes away.

[UnderCover]

im on image

1.2.1-RC1
built on Mon Aug 25 07:40:58 EDT 2008

and get this error with carp

php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin https://10.1.0.2:443.

[ask]

Sync doesn't work across https.

See http://forum.pfsense.org/index.php/topic,11019.0.html

[UnderCover]

ok i went over to http and got this

php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin http://10.1.0.2:80.

[heiko]

Carp works with https in 1.2 as it should, 1.21 have a few bugs, at the moment with ipsec and carp clustering, wait and see…

regards
heiko

[ask]

"UnderCover",

Start a shell (via console or ssh) and try

fetch http://10.1.0.2:80/

If that doesn't work (with the username and password of the system that's trying to sync – remember, they have to be the same on both boxes), then figure out to fix that first.

• ask

[UnderCover]

will do  thank you  let me know when you need more snapshot carp tests

thanks for your help

[Juve]

Juste a feedback to say that my 1.21 cluster is still running fine without any issue regarding CARP and/or synchronization.

;D

[ask]

@Juve:

Juste a feedback to say that my 1.21 cluster is still running fine without any issue regarding CARP and/or synchronization.

Do you use HTTP or HTTPS for the web interface?

• ask

[databeestje]

We confirmed that https synchronisation atleast is not succeeding.

It should be fixed in a upcoming snapshot.

The carp cluster should otherwise function normally. It does so in my production setup at work.
We are still investigating a few other issues here.

[ask]

@databeestje:

We confirmed that https synchronisation atleast is not succeeding.

It should be fixed in a upcoming snapshot.

Great – will you post a note here when the fix is in a snapshot?

@databeestje:

The carp cluster should otherwise function normally. It does so in my production setup at work.
We are still investigating a few other issues here.

I can confirm that CARP (and syncing over http) is working.

[UnderCover]

can't wait  ;D

[Juve]

Right, we use HTTP since the snapshot we use has problem with HTTPS.  ;)