vicidial.org

Hi all,

Apologies in advance, I am new to posting in the forum.

VERSION: 2.14-708a
BUILD: 190414-0924
Standalone server

I had a power trip over night and when we came in, my agents could not login. The softphones did not ring and the agent screen kept on getting disabled.
After much searching throughout the forums, i did the following:

mysqlcheck -u root -p --auto-repair --optimize --all-database

-which gave me the following errors

Repairing tables
asterisk.vicidial_callbacks OK
asterisk.vicidial_closer_log
Error : Incorrect file format 'vicidial_closer_log'
error : Corrupt
asterisk.vicidial_dnc
Error : Incorrect file format 'vicidial_dnc'
error : Corrupt
asterisk.vicidial_list
Error : Incorrect file format 'vicidial_list'
error : Corrupt
asterisk.vicidial_live_agents
Error : Incorrect file format 'vicidial_live_agents'
error : Corrupt
asterisk.vicidial_log
Error : Incorrect file format 'vicidial_log'
error : Corrupt
asterisk.vicidial_manager
Error : Incorrect file format 'vicidial_manager'
error : Corrupt

To fix this, i logged into mysql and repaired each table individually.
>REPAIR TABLE vicidial_manager USE_FRM;

After doing this, the agents were able to log on with no issues.

The problem now is that all the data loaded from the beginning of time on the dialer has disappeared. If you go Lists>show lists and select an active list, all of them show empty. I have tried loading more data which worked perfectly and the agents are dialing, however i need the old data back (data prior to the crash)

Any help will be much appreciated.

Thanks

Kiresh

Based on the output of mysqlcheck above You would need to issue "REPAIR TABLE" on each of the corrupt tables. Which should hopefully restore all your data.

bourneshell wrote:Based on the output of mysqlcheck above You would need to issue "REPAIR TABLE" on each of the corrupt tables. Which should hopefully restore all your data.

Thanks for the reply,

I did run "REPAIR TABLE" on each of the corrupt tables and after a mysqlcheck there are no more corrupt tables. I have done this the 2nd time round to no avail...

Any other way to get the data back ?

Did you use "USE_FRM" on all the repair table commands?

You can check the /srv/mysql/data/asterisk and see if the table files still contain the data. Which should be on the files with .MYD

bourneshell wrote:Did you use "USE_FRM" on all the repair table commands?

You can check the /srv/mysql/data/asterisk and see if the table files still contain the data. Which should be on the files with .MYD

Hi,
Yes sir, i did use "USE_FRM" on all the repair commands.
I cannot find the path you are referring to.

optimal:/ # cd /srv
optimal:/srv # dir
total 16
drwxr-xr-x 2 root root 4096 Sep 30 2015 ftp
drwxr-xr-x 2 svn svn 4096 May 6 2016 svn
drwxr-x--- 2 tftp tftp 4096 Dec 7 2016 tftpboot
drwxr-xr-x 4 root root 4096 Jan 13 2017 www

unless i am going about it wrong.

also, What i have noticed is that; when i loaded the new data yesterday the lead ID's started of from "1" again...

I logged into the myphpadmin, looking at 'vicidial_list' it only shows entries from yesterday and nothing prior However the space on the hard drive has not changed before and after the crash.

check your call_log table if you can see your old calls.

ed123 wrote:check your call_log table if you can see your old calls.

Yes i can see all calls made since 2018 (inception)

have you attempted any upgrades or anything else during the process?

Code: Select all

mysql asterisk -u cron -p1234 -e "select count(*) from vicidial_list"