Page 1 of 1

Dedicated Mysql Server Question

PostPosted: Wed Feb 09, 2011 1:48 am
by chasejordan1
So I just migrated the Mysql to a separate server pretty simple actually loaded mysql server client etc, then did a dump, copied dump using winscp then created "asterisk" database, restored dump in new server and created privileges. Then went into astguiclient.conf and pointed dbserver to new server IP, rebooted both server and and all seems fine (had to sync time though). Stopped Mysql on original (goautodial all in one box). Made some test calls logged in as admin agent etc. But I noticed in Admin - Phones that the phones show the DBX server field empty. Is this ok? Did I miss something? or do I just have to type the new DBX server IP in the field and all should be fine? Last question how close should the Msql Server and the Goautodial server be, same LAN, or a city away with a ping of 35ms? Thanks Thad


Goautodial
VERSION: 2.2.1-237
BUILD: 100510-2015
asterisk version
1.4.27

PostPosted: Wed Feb 09, 2011 5:09 am
by mackoko
is it only the admin - phones that has the problem? how about the other info like the users, campaigns, etc...?

For the last question, I would suggest same lan. I rather have everything locally especially when you need to troubleshoot the servers.

PostPosted: Wed Feb 09, 2011 9:17 am
by chasejordan1
admin - phones is the only place that has a "spot" for the DBX server address by default it is left blank. So my question is do I put the new DBX server IP address in the field or do I leave it blank and did I miss anything? Thanks Thad

PostPosted: Wed Feb 09, 2011 9:29 am
by williamconley
does that admin phone ... work?

your mysql server is in CONSTANT contact (every second, often for more than a second overlapping the next call). If you have ANY hiccups in your network, your vicidial server can (and will, i guarantee it) become unreliable. you'll experience prospects landing in the wrong room, delays in arrival at those rooms, spikes in the processor usage in the Vicidial server, all sorts of stuff.

Keep the MySQL server local. Use the built-in replication feature if you need the "live" data somewhere else. If you don't need Live, just push the data nightly with the built-in backup.

If your concern is that your powerful server is in the wrong city ... it'll be worth the investment to move it. Lost time cannot be recovered (along with lost sales) from having an unreliable system under heavy load (which is the LAST time you want to have to say "oops").

PostPosted: Wed Feb 09, 2011 9:53 am
by chasejordan1
Thank You and the phone works fine. So from what you can tell I didn't miss anything? Thad

PostPosted: Wed Feb 09, 2011 10:08 am
by williamconley
If you feel like "looking for trouble", don't do it in Vicidial. LOL

Things you can check:

Admin->Servers

Verify your max trunks is within the limits of your available trunks (based on bandwidth or carrier limits)

Verify your calls per second is no more than 1 for every 10 agents (and try to stay under 5 unless you discuss it with your carrier, they get touchy about that).

/var/log

Check all your logs for all installed software for errors. Look them up if you find any to see if they are "actionable".

After that, you should consider turning off logging in Vicidial and Asterisk until you need to debug something (save processor and disk i/o).

Logging in Vicidial: Admin->Servers
Logging in Asterisk: /etc/asterisk/logger.conf

And check out Kumba's sticky of "best practices" (! What am I saying! Of course you've already done that ... because reading the stickies is required before posting :) right?)