Vicidial HA using Corosync, DRBD and Pacemaker

Any and all non-support discussions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Vicidial HA using Corosync, DRBD and Pacemaker

Postby rbbumanlag » Sat Aug 11, 2018 8:28 pm

Hi Vicidial,

Specification: ViciBox 8.0.1.(iso) | Asterisk 11.25.3-vici | VERSION: 2.14-682a BUILD: 180807-1653 | Cluster Setup | Intel(R) Xeon(R) CPU E5-2680 V3 @ 2.5GHz | 16GB DDR4 RAM | 1TB (SAS) 10kRPM |No Digium/Sangoma Hardware | No Extra Software After Installation | Virtualized on XenServer | SVN Version 3016

I am on a clustered setup with separate database, slave database, asterisk, web and archive server. my database server is in a HA setup and Web Servers is being load balanced using HAProxy. What I am encountering is that when I do a failover on the database, I am having problems on the clustered vicidial.

I am encountering problems in which when the agent login, the softphone is not being called to join the conference then time synchronization error will occur. Tried restarting NTP and making sure all Servers are in sync when it comes to the time.

I tried doing "core restart now" but still I am unable to make the softphone trigger. What I normally do to make it working is to restart the asterisk server and the web server after a database failover.

I would like to know what service I need to restart for asterisk and web.

Thanks!
rbbumanlag
 
Posts: 74
Joined: Mon Sep 26, 2016 10:37 am

Re: Vicidial HA using Corosync, DRBD and Pacemaker

Postby mflorell » Sun Aug 12, 2018 7:23 am

We have seen problems like this with clients using virtualized clusters. We never recommend using virtualized servers for VICIdial.
mflorell
Site Admin
 
Posts: 18335
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Vicidial HA using Corosync, DRBD and Pacemaker

Postby williamconley » Sun Aug 12, 2018 3:10 pm

screen -list on the dialers. These are not "services", but they are often in need of a restart. It's possible for most of them to be killed and they will auto-restart at the :00 when keepalive runs (or you can run keepalive immediately after killing them ...).

Virtual Vicidial, as pointed out by Matt, is a bad idea. Before you announce "buildout complete!" do a FULL load test with more agents than you intend to actually run on your first day (using fake calls to fake call recipients on servers outside the Vicidial system as your test set). Vicidial on Virtual tends to fall apart after just a couple agents. Even on powerful equipment it tends to die when loaded up. So if your job relies on this working, test the hell out of it FULLY loaded. If your HA system is hardware-based, you're good. But still test before launch. 8-)
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20018
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Vicidial HA using Corosync, DRBD and Pacemaker

Postby rbbumanlag » Mon Aug 13, 2018 8:47 pm

Thanks. We will take now on your inputs.
rbbumanlag
 
Posts: 74
Joined: Mon Sep 26, 2016 10:37 am


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 53 guests