vicidial.org

Hi guys,,

Asterisk 1.4.27-vici
Dahdi current
Vicidial 2.4
Mysql/Apache -1 Server
asterisk/vicidial- 2 Servers
Ubuntu 8.04 LTS

Base on your vicidial large deployments how do often you getting problem with DB like hopper suddenly don't load leads, sometime it load but tables get corrupted, then you do repair then reboot servers and then work fine again, are this really often to DB problem, what should ways to prevent this or solutions, 2 weeks with no DB problem is a relief but beyond that there would really table corrupts like within a month of usage- any idea things to do or DB configuration would help this eased up.
(You may comment that its a bad setup or install- but what if its a proper install) - Maybe you can share some proper value of my.cnf value to optimized DB ( which i already have it form vicidial itself its value) Its somehow hard to perfect stability but might it can be rewarding to lessen DB problem..

In our large deployments, DB corruption is extremely rare and usually caused by power loss or forced rebooting without properly shutting down MySQL.

Using properly sized hardware for the installation is key to a stable system, and starting from the my-huge.cnf is usually where we start, although that also needs to be altered somewhat depending on the available hardware.

I concur with matt about the corruption is usually caused by power interruption more so by hardware failure.

You also need to prune and archive some table datas every now and then.

@mflorell

Where i can cehck this myhuge.cnf...? can i ask for the link of this..?

corruption is caused by bad ram, or a damaged hard drive, interrupted power, underspecc'd server, misconfigured my.cnf

It depends on how you installed MySQL as to where the my-huge.cnf file is, but it should be in all default installs of mysql server.

http://download.vicidial.com/conf/my-vicidb.cnf

thats what i used for one of my centrall db servers