Has anyone tested 1.21 with a carp cluster?
-
after 2 hours? what is that meaning?
-
;D I was meaning that the cluster is runing for 2 hours without any problem.
-
-
then all is runing fine , RPC-XML sync is OK as well as CARP and pfsync.
;) -
I think, i will tested it with the newest snapshot again…
-
Heiko, is the cluster trying to sync through the WAN interface?
-
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
-
Please retry with a recent snapshot and see if the problem goes away.
-
im on image
1.2.1-RC1
built on Mon Aug 25 07:40:58 EDT 2008and 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.
-
Sync doesn't work across https.
-
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.
-
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 -
"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
-
will do thank you let me know when you need more snapshot carp tests
thanks for your help
-
Juste a feedback to say that my 1.21 cluster is still running fine without any issue regarding CARP and/or synchronization.
;D
-
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
-
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. -
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?
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.
-
can't wait ;D
-
Right, we use HTTP since the snapshot we use has problem with HTTPS. ;)