How To Repair Vicidial Database
Issues :
- Agent session disabled
- Autodial calls not landing to agents
- Realtime reports are not getting updated
- Lead uploading failed
- server stopped responding
Fix :
you can easily fix or repair Mysql by using these commands.
Step 1: Delete Recording files
Login to the server via SSH using PUTTY and check the free available space on the hard disk.
[root@ve1228 ~]# df -h
Output :
Filesystem Size Used Avail Use% Mounted on/dev/sda3 221G 5.4G 204G 3% /tmpfs 16G 0 16G 0% /dev/shm/dev/sda1 976M 106M 820M 12% /boot
Whether it shows 100% or near to greater than 80% being used percent section then hard disk drive is full and you have to delete the tracks and logs files of the
server.
Now go to the directory where you keep all your recording files. Usually, it is located at
/var/spool/asterisk/monitorDONE/ORIG
cd /var/spool/asterisk/monitorDONE/ORIG
You have to delete all recorded files under the ORIG directory if you like to help keep recording it’s better to copy all of your recording files to a local computer or other places aside from this server.
[root@ve1228 ORIG]# rm -rf *
The above command will delete all the files under the ORIG directory.
If the above command displays cannot delete file too lengthy, then download the WINSCP software and log in to the server and visit
/var/spool/asterisk/monitorDONE/ORIG select all files and delete it. Deleting files through WINSCP may take an extended period.
you should use another alternative approach to delete lengthy file names.
Run this command
[root@ve1228 ORIG]# find . -type f -name “*.wav” | xargs -l500 rm -f
This will delete every 1500 files one by one and empty the folder.
Go to /var/spool/asterisk/monitorDONE/MP3
[root@ve1228 ORIG]# cd /var/spool/asterisk/monitorDONE/MP3[root@ve1228 MP3]# rm -rf *
If u record in gsm then go to GSM, /var/spool/asterisk/monitorDONE/GSM directory and follow the above steps to delete files.
Step 2: Delete LOG msg
you also need to delete log files which can also consume some hard disk space.
Login through Winscp and go to directory /var/log/ and delete the message.1,2,4 secure.1,2,3… ,boot.1,2,3…..
Delete asterisk and Httpd log msg as well using the below commands or using WinSCP .
[root@ve1228 MP3]# cd /var/log/asterisk[root@ve1228 asterisk]# rm -rf messages.*[root@ve1228 asterisk]# cd /var/log/httpd/[root@ve1228 httpd]# rm -rf error.*[root@ve1228 httpd]# rm -rf acces.*
Step 3: Repair Mysql
Start Mysql and repair it using the command
[root@ve1228 ~]# /etc/init.d/mysqld start [root@ve1228 ~]# mysqlcheck -u cron -p –auto-repair –check –optimize –all-databases
The default password for cron users is 1234 if you haven’t changed it.
Once finishes the repair of the MYSQL, reboot the server and check whether you are getting errors or not.
It is advisable to optimize your MySQL databases on regular basis to avoid any downtime and to keep running your server at its optimal performance.
Resources :
Putty downloads
Winscp downloads
Summary :
By using the above command you will be able Vicidial database repair. Tell me in the comments should you still face any risk to correct Vicidial MySQL.
Comments
Post a Comment