Project

General

Profile

Actions

Bug #1928

closed

Can't sync voucher database when carp peer is also active

Added by Sander Naudts over 12 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Ermal Luçi
Category:
CARP
Target version:
Start date:
10/06/2011
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:
i386

Description

Hi,

When I try to sync the voucher database from the slave to the master I get a "Disallowing CARP sync loop" message on the master node.

That same slave is also part of a carp cluster. When I remove the slave ip from the "Synchronize config to IP" textbox on the master the voucher database works just fine but I can't have them both on. (Or voucher database in sync or config in sync)

Sander

Actions #1

Updated by Chris Buechler over 12 years ago

  • Target version deleted (2.0.1)
Actions #2

Updated by Ermal Luçi over 12 years ago

It is not meant to work that way!
The voucher sync will sync with the master or use it as its central database.

It can work independently if it cannot reach the master though the only issue i see is not advertise some events when the master comes back up.
The question on this is how long you should queue these events?

Actions #3

Updated by Sander Naudts over 12 years ago

I deleted the CARP sync so that the voucher database keeps syncing fine but when the master goes down I still can't get the vouchers to work on the slave.

If I use an expired voucher it gives me the correct message that the voucher is no longer valid and is expired. However when I try an unused voucher it first gives me a communications error while attempting CaptivePortalVoucherSync XMLRPC (correct, because master is down), but then gives me a FAILURE message in the Portal Auth log and the voucher cannot be used.

Do I have to configure something special for it to work independently if it cannot reach the master? I can't find any documentation about this.

Actions #4

Updated by Jim Pingle over 11 years ago

  • Target version set to 2.1

This is definitely an issue still.

If you are in a carp setup, setting the voucher sync on the slave as directed in the notes will be denied, as the xmlrpc code will disallow what it believes to be a loop.

Perhaps the exec_php method needs to be excluded from the loop check.

Actions #5

Updated by Ermal Luçi over 11 years ago

  • Assignee set to Ermal Luçi
Actions #6

Updated by Ermal Luçi about 11 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #7

Updated by Chris Buechler over 10 years ago

  • Target version changed from 2.1 to 2.2
Actions #8

Updated by Ermal Luçi over 9 years ago

I am unsure if this should be allowed!
Normally switching to master it should have the latest voucher status synched from master and what is the purpose of having a carp cluster but also a voucher sync ?

Actions #9

Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to Resolved

fixed. Voucher sync is separate from CP's config sync, it does work.

Actions

Also available in: Atom PDF