vicidial.org

Hi all,

We are facing an unexpected major issue with Vicidial. Today, 6 Jan 2017, when we login to Vicidial in the morning, we realised all the leads that were loaded into Vicidial were wiped out completely. This applies to all our lists be it Active or Inactive. We did not exercise any unique actions or configurations on the day before. The last loading of new leads was done on 3 Jan 2017, and the last call made was on 5 Jan 2017 around 6:30PM. The last login on 5 Jan 2017 was around 10+PM to export call leads, just like every other day. We still have access to our recordings, however the leads details are all wiped out. Also, we cannot load new leads into Vicidial. We have always used custom fields for our list, where we map our data to the field on the next page of the Load New Leads page. However, today the custom columns did not even load at the Load New Leads page, even though we had APPEND our custom fields to the new list. We have tried deleting old lists but nothing seems to change. How can we solve this issue? Please advise. Thank you!

Vicidial Version: 2.8-403a
Build: 130510-1350
Asterisk Version: 1.4.39.1-vici

I'm guessing that you were not backing up your system every night?
Have you checked the Admin Change Log to see what happened around that time?
Also, you are running a 3 and a half year old version of VICIdial, with known security holes, so you really should upgrade.

Thanks mflorell for your reply.
We do have backups in place every night at 1AM, but it seems to only backup the recordings.
We have checked the Admin Change Log, on 5 Jan 10:09PM we export leads, and at 6 Jan 8:54AM we modify Campaign, also usual actions that we excercise everyday. Anywhere in between these 2 times, there was no other admin changes.
The more pressing issue would be loading new leads into Vicidial. Currently, we can't load new leads into Vicidial. How can we resolve this issue?

Check for a crashed table. Run this in mysql:
"repair table vicidial_list;"

Thank you so so much mflorell. It totally works.

Glad it's resolved, thanks for posting back!