VitalPBX Replica

VitalPBX Community Support General Discussion VitalPBX Replica

  • Post
    PitzKey
    Participant
    US
    Up
    0
    Down
    Hey everyone.

    I came across the VitalPBX Replica solution from Rodrigo on Github https://github.com/VitalPBX/vitalpbx_replica.

    I discovered a issues with the queues and queue members, and I am also wondering if it is possible to run this with a cronjob every night. So have sort of a warm spare machine ready in case the primary goes down.

    I documented the information in detail under the issues tab: https://github.com/VitalPBX/vitalpbx_replica/issues/1

    Please let me know if you need any further information

    Thank you

    0
Viewing 4 replies - 1 through 4 (of 4 total)
  • Replies
    Rodrigo Cuadra
    Keymaster
    US
    Up
    0
    Down
    PitzKey:
    Because asterisk is active on both servers and it is a replica (it is not High Availability), the MySqLite astdb database cannot be replicated since asterisk blocks it on the backup server. This is a limitation of this model. The only thing that can be done is to stop the asterisk on the secondary server and clone this database as well.

    By stopping Asterisk on the backup server, it implies that Asterisk could not start automatically on both servers, we would have to start it manually.

    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Hi Rodrigo, sorry for the delayed response.

    There is two different issues.

    1. A general queue issue: The queues are not populated in asterisk until you run vitalpbx fully-dump-conf. I even tried restarting Asterisk prior to running that command, but there were no queues.
    2. Dynamic agents: They are not getting logged in to the queues on the secondary server.

    So, as mentioned on github, the question is: Is there a possibility to modify the script to support the following?

    • Hardcode both IPs, so we can run it with a cronjob every few hours or every night.
    • The script should run on the secondary the following commands, so it builds the queues:
      • vitalpbx fully-dump-conf
      • vitalpbx check-integrity
    • Once the restore is done, stop asterisk on the secondary, clone the primary AsteriskDB, restore it on the secondary, start asterisk again on the secondary.

    Adding the above would make it much easier to run a replica script a few times a day. That way we can have the config on both servers very similar one to the other.

    Let me know if you have any questions

    Thank you

    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Bump?
    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Following up. Is there a way to make this a bit more friendly to do a daily replication or even every few hours?
    0
Viewing 4 replies - 1 through 4 (of 4 total)
  • The forum ‘General Discussion’ is closed to new topics and replies.